Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SIP --> Cisco 5400 ISDN --> PSTN - Calling Number Problem

Status
Not open for further replies.

saleck

IS-IT--Management
Mar 13, 2011
8
NG
Hi all,
Could somebody please help me in regards to an outgoing calls from my SIP gateway to the PSTN via our PRI.
The Cisco 5400 send the calling number but on my mobile I receive 65535 as calling number for all calls.
I have tried every possible config option for isdn.
Below is a isdn q931 debug of.

Mar 13 12:11:06.534: ISDN Se7/2:15 Q931: Applying typeplan for sw-type 0x12 is 0 x0 0x1, Calling num 22236613001
Mar 13 12:11:06.534: ISDN Se7/2:15 Q931: Applying typeplan for sw-type 0x12 is 0 x0 0x1, Called num 22236376020
Mar 13 12:11:06.538: ISDN Se7/2:15 Q931: TX -> SETUP pd = 8 callref = 0x18B1
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA9839F
Exclusive, Channel 31
Display i = '444'
Calling Party Number i = 0x0180, '22236613001'
Plan:ISDN, Type:Unknown
Called Party Number i = 0x81, '22236376020'
Plan:ISDN, Type:Unknown
Mar 13 12:11:06.666: ISDN Se7/2:15 Q931: RX <- SETUP_ACK pd = 8 callref = 0x98B 1
Channel ID i = 0xA9839F
Exclusive, Channel 31
Mar 13 12:11:06.666: ISDN Se7/2:15 Q931: RX <- CALL_PROC pd = 8 callref = 0x98B 1
Progress Ind i = 0x8288 - In-band info or appropriate now available
Mar 13 12:11:10.714: ISDN Se7/2:15 Q931: RX <- ALERTING pd = 8 callref = 0x98B1
Progress Ind i = 0x8288 - In-band info or appropriate now available
Mar 13 12:11:12.606: ISDN Se7/2:15 Q931: RX <- DISCONNECT pd = 8 callref = 0x98 B1
Cause i = 0x8091 - User busy
Mar 13 12:11:12.610: ISDN Se7/2:15 Q931: TX -> RELEASE pd = 8 callref = 0x18B1
Mar 13 12:11:12.746: ISDN Se7/2:15 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x 98B1
Mar 13 12:11:17.790: %CALLTRKR-6-CALL_RECORD: ct_hndl=6194, service=None, origin


AS5400 config

dial-peer voice 102 pots
description old_plan
translation-profile outgoing 44
service session
destination-pattern 222.......
direct-inward-dial
port 7/2:D
forward-digits all

interface Serial7/2:15
no ip address
encapsulation ppp
dialer-group 1
isdn switch-type primary-net5
isdn incoming-voice modem
peer default ip address pool setup_pool
fair-queue 64 256 0
no cdp enable
ppp authentication chap pap
ppp multilink


controller E1 7/2
framing NO-CRC4
pri-group timeslots 1-31
trunk-group SM timeslots 1-31

isdn switch-type primary-net5
isdn voice-call-failure 0

Thanks
 
The q931 debug you attached shows that you are sending 22236376020 as the calling party number. If you get something else on the other end, the provider is masking the call and ignoring the calling party number you are sending out.
have you contacted your provider?
 
Hi,
Thanks for your prompt reply.
I checked everything and the calling part number displayed on the mobile is 65535[/color red] in all cases.
The operator said that on his soft-switch the configuration is clip transparency.
Saleck
 
I understand but the q931 debugs don't lie. 65535 is not coming from you assuming that you posted the correct debug. Since the voice gateway is your endpoint of connectivity to the PSTN, it is somewhere in the providers cloud that the issue is caused and you'll have to work with them to fix it.
I am not sure what you mean by the operator but if I were you I would open a ticket with the provider.
 
I'm posting the correct debug.
The voice gateway is the endpoint of connectivity to the PSTN.
I'll check again with the provider.
I mean by operator, the Telecom operator who provide me access to the PSTN (PRI, E1) to forward received traffic from SIP.
Thanks
 
Hello,
This log from the provider shows that the calling number is received but the problem is user-provided-not-screened!!
Can you help about that?

......calling-party-number-1
53> 41 ----0001 ........numbering-plan-identification:isdn-or-telephony-numbering-plan (1)
-100---- ........type-of-number:subscriber-number (4)
0------- ........ext:0x0 (0)
54> 80 ------00 ........screening-indicator:user-provided-not-screened (0)
---000-- ........spare:0x0 (0)
-00----- ........presentation-indicator:presentation-allowed (0)
1------- ........ext1:0x1 (1)
55> 34 00110100
56> 31 00110001
57> 34 00110100
58> 34 00110100
59> 35 00110101
60> 34 00110100
61> 33 00110011
62> 37 00110111
63> 31 00110001
64> 33 00110011
65> 30 00110000 ........number:41444444456
66> 70 01110000 T
67> 0C 00001100 L

Thanks
 
This issue usually causes outboubds calls to fail since they get rejected by the provider. You only mention that they do not pass your caller id which I find strange and not accurate.
However if that is truly your issue this should fix it:

Find the CgpnScreeningIndicator, a Cisco CallManager service parameter in the Service Parameter page. Set the CgpnScreeningIndicator to value 1 (User-provided, verified, and passed).


 
So what's the phone system or soft switch behind the AS5400? Something is telling the router to initiate these calls right? what is it?

 
Calls are initiated by a voip provider using SIP trunk.
 
Then you need to ask the SIP trunk provider to change that setting on their SIP side. That is where the "user-provided-not-screened" request is coming from.
I don't think there is a way to change that on the router.
 
you should check with ITSP, seems ITSP replace the calling number as 65535 for all outbound calls; PSTN PRI switch can do this;
 
Hi
The problem is resolved by the ISDN provider.
Thanks for your help
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top