10-25-2017 10:37 AM - edited 03-17-2019 11:28 AM
I am facing an issue with a client's Gateway,we are testing their E1 ISDN PRIs and when calling into it (inbound fron the PSTN) debug isdn q931 does not show called number as illustrated below. we need the called number to route calls to their users (DID) did anyone experience a similar issue.please help here at least for better isolation of the problem.
Debug isdn q931 result:
*Oct 25 18:17:34.025: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8 callref = 0x0062
Sending Complete
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98384
Exclusive, Channel 4
Progress Ind i = 0x8283 - Origination address is non-ISDN
Calling Party Number i = 0x0083, '911111135'
Plan:Unknown, Type:Unknown
Calling Party Number i = 0x0083, '911111135'
Plan:Unknown, Type:Unknown
*Oct 25 18:17:34.025: ISDN Se0/0/0:15 Q931: Received SETUP callref = 0x8062 callID = 0x0012 switch = primary-net5 interface = User
*Oct 25 18:17:34.045: ISDN Se0/0/0:15 Q931: TX -> CALL_PROC pd = 8 callref = 0x8062
Channel ID i = 0xA98384
Exclusive, Channel 4
Progress Ind i = 0x8188 - In-band info or appropriate now available
*Oct 25 18:17:34.045: ISDN Se0/0/0:15 Q931: TX -> CONNECT pd = 8 callref = 0x8062
*Oct 25 18:17:34.081: ISDN Se0/0/0:15 Q931: RX <- CONNECT_ACK pd = 8 callref = 0x0062
*Oct 25 18:17:34.081: %ISDN-6-CONNECT: Interface Serial0/0/0:3 is now connected to 911111135 N/A
*Oct 25 18:17:36.209: ISDN Se0/0/0:15 Q931: RX <- DISCONNECT pd = 8 callref = 0x0062
Cause i = 0x8290 - Normal call clearing
Progress Ind i = 0x8288 - In-band info or appropriate now available
*Oct 25 18:17:36.209: %ISDN-6-DISCONNECT: Interface Serial0/0/0:3 disconnected from 911111135 , call lasted 2 seconds
*Oct 25 18:17:36.213: ISDN Se0/0/0:15 Q931: call_disc: PI received in disconnect; Postpone sending RELEASE for callid 0x12
*Oct 25 18:17:36.221: ISDN Se0/0/0:15 Q931: TX -> RELEASE pd = 8 callref = 0x8062
*Oct 25 18:17:36.237: ISDN Se0/0/0:15 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x0062
Solved! Go to Solution.
10-26-2017 02:10 AM
10-29-2017 02:02 PM
Hi Yaarub,
There a mistake in the received ISDN Setup Control Message that is sent by the provider, you get the field "Calling Party Number" twice, according to regular ISDN Q931 capture the 2nd one should be the "Called Party Number", also notice the other highlighted values.
Finally, there is Codeset part missing that is used by ISDN parties to know what fields are used in the control messages; and this part comes at the end of Setup Control Message.
So, the provider operation engineers have correct the configuration in their side for these missing info to appear in the Setup Control Message.
For more info about ISDN Layer 3 Basic Call Control, check this document from ETSI:
http://www.etsi.org/deliver/etsi_i_ets/300100_300199/30010201/01_60/ets_30010201e01p.pdf
Debug isdn q931 result:
*Oct 25 18:17:34.025: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8 callref = 0x0062
Sending Complete
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98384
Exclusive, Channel 4
Progress Ind i = 0x8283 - Origination address is non-ISDN
Calling Party Number i = 0x0083, '911111135'
Plan:Unknown, Type:Unknown
Calling Party Number i = 0x0083, '911111135'
Plan:Unknown, Type:Unknown
Locking Shift to Codeset 5
Codeset 5 IE 0x2A
*Oct 25 18:17:34.025: ISDN Se0/0/0:15 Q931: Received SETUP callref = 0x8062 callID = 0x0012 switch = primary-net5 interface = User
*Oct 25 18:17:34.045: ISDN Se0/0/0:15 Q931: TX -> CALL_PROC pd = 8 callref = 0x8062
Channel ID i = 0xA98384
Exclusive, Channel 4
Progress Ind i = 0x8188 - In-band info or appropriate now available
*Oct 25 18:17:34.045: ISDN Se0/0/0:15 Q931: TX -> CONNECT pd = 8 callref = 0x8062
*Oct 25 18:17:34.081: ISDN Se0/0/0:15 Q931: RX <- CONNECT_ACK pd = 8 callref = 0x0062
*Oct 25 18:17:34.081: %ISDN-6-CONNECT: Interface Serial0/0/0:3 is now connected to 911111135 N/A
*Oct 25 18:17:36.209: ISDN Se0/0/0:15 Q931: RX <- DISCONNECT pd = 8 callref = 0x0062
Cause i = 0x8290 - Normal call clearing
Progress Ind i = 0x8288 - In-band info or appropriate now available
*Oct 25 18:17:36.209: %ISDN-6-DISCONNECT: Interface Serial0/0/0:3 disconnected from 911111135 , call lasted 2 seconds
*Oct 25 18:17:36.213: ISDN Se0/0/0:15 Q931: call_disc: PI received in disconnect; Postpone sending RELEASE for callid 0x12
*Oct 25 18:17:36.221: ISDN Se0/0/0:15 Q931: TX -> RELEASE pd = 8 callref = 0x8062
*Oct 25 18:17:36.237: ISDN Se0/0/0:15 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x0062
Looking forward for you to solve this issue to be the 1st engineer who implemented DID in LIBYA.
Best of luck buddy.
Regards.
10-25-2017 11:12 AM
Hi,
This usually is TSP related so you should troubleshoot it with them
Can you please post your actual running config of your VG?
Thanks
Regards
Carlo
10-25-2017 03:17 PM
Here you go :
network-clock-participate wic 0
network-clock-select 1 E1 0/0/0
!
multilink bundle-name authenticated
!
!
!
!
isdn switch-type primary-net5
!
!
controller E1 0/0/0
framing NO-CRC4
pri-group timeslots 1-31
!
controller E1 0/0/1
framing NO-CRC4
pri-group timeslots 1-31
!
ip ssh version 2
!
interface Serial0/0/0:15
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn incoming-voice voice
!
interface Serial0/0/1:15
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn incoming-voice voice
no cdp enable
!
router eigrp 7
network 77.77.77.77 0.0.0.0
network 172.16.20.252 0.0.0.3
no auto-summary
!
ip forward-protocol nd
ip http server
no ip http secure-server
!
!
!
!
!
!
!
!
!
control-plane
!
!
!
voice-port 0/0/0:15
!
voice-port 0/1/0
!
voice-port 0/1/1
!
voice-port 0/1/2
!
voice-port 0/1/3
!
voice-port 0/0/1:15
!
!
!
!
!
dial-peer voice 10 pots
incoming called-number 366T
direct-inward-dial
!
dial-peer voice 11 pots
destination-pattern 9T
port 0/0/0:15
!
!
!
!
telephony-service
max-ephones 10
max-dn 10
ip source-address 77.77.77.77 port 2000
auto assign 1 to 5
max-conferences 8 gain -6
transfer-system full-consult
create cnf-files version-stamp Jan 01 2002 00:00:00
!
!
ephone-dn 1
number 3660630
!
!
ephone 1
device-security-mode none
mac-address 000C.29BD.F052
type CIPC
button 1:1
10-25-2017 08:45 PM
Hi,
please add the lines below to your configuration and than send me again a debug isdn q931 output
interface serial0/0/0:15
isdn overlap-receiving
isdn overlap-receiving T302 5000
Voice-port 0/0/0:15
bearer-cap speech
dial-peer voice 10 pots
port 0/0/0:15
logging buffered 4096
logging monitor debug
Thanks
HTH
Regards
Carlo
10-25-2017 09:00 PM
debug isdn q931:
*Oct 26 04:50:11.087: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8 callref = 0x0065
Sending Complete
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98387
Exclusive, Channel 7
Progress Ind i = 0x8283 - Origination address is non-ISDN
Calling Party Number i = 0x0083, '911111135'
Plan:Unknown, Type:Unknown
Calling Party Number i = 0x0083, '911111135'
Plan:Unknown, Type:Unknown
*Oct 26 04:50:11.091: ISDN Se0/0/0:15 Q931: Received SETUP callref = 0x8065 callID = 0x0015 switch = primary-net5 interface = User
*Oct 26 04:50:11.107: ISDN Se0/0/0:15 Q931: TX -> CALL_PROC pd = 8 callref = 0x8065
Channel ID i = 0xA98387
Exclusive, Channel 7
Progress Ind i = 0x8188 - In-band info or appropriate now available
*Oct 26 04:50:11.107: ISDN Se0/0/0:15 Q931: TX -> CONNECT pd = 8 callref = 0x8065
*Oct 26 04:50:11.143: ISDN Se0/0/0:15 Q931: RX <- CONNECT_ACK pd = 8 callref = 0x0065
*Oct 26 04:50:11.147: %ISDN-6-CONNECT: Interface Serial0/0/0:6 is now connected to 911111135 N/A
*Oct 26 04:50:14.547: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:6, changed state to up
*Oct 26 04:50:21.487: ISDN Se0/0/0:15 Q931: RX <- DISCONNECT pd = 8 callref = 0x0065
Cause i = 0x8290 - Normal call clearing
Progress Ind i = 0x8288 - In-band info or appropriate now available
*Oct 26 04:50:21.491: %ISDN-6-DISCONNECT: Interface Serial0/0/0:6 disconnected from 911111135 , call lasted 10 seconds
*Oct 26 04:50:21.491: ISDN Se0/0/0:15 Q931: call_disc: PI received in disconnect; Postpone sending RELEASE for callid 0x15
*Oct 26 04:50:21.503: ISDN Se0/0/0:15 Q931: TX -> RELEASE pd = 8 callref = 0x8065
*Oct 26 04:50:21.515: ISDN Se0/0/0:15 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x0065
10-25-2017 10:38 PM
Hi ,
Thanks for the output.
Please also attach a debug voip dialpeer inout.
Thanks
Regards
Carlo
10-25-2017 11:05 PM
debug voip dialpeer inout :
*Oct 26 06:51:14.946: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8 callref = 0x0066
Sending Complete
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA9839F
Exclusive, Channel 31
Progress Ind i = 0x8283 - Origination address is non-ISDN
Calling Party Number i = 0x0083, '911111135'
Plan:Unknown, Type:Unknown
Calling Party Number i = 0x0083, '911111135'
Plan:Unknown, Type:Unknown
*Oct 26 06:51:14.950: ISDN Se0/0/0:15 Q931: Received SETUP callref = 0x8066 callID = 0x0016 switch = primary-net5 interface = User
*Oct 26 06:51:14.950: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Calling Number=911111135, Called Number=, Voice-Interface=0x49B42840,
Timeout=TRUE, Peer Encap Type=ENCAP_VOICE, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
*Oct 26 06:51:14.950: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=11
*Oct 26 06:51:14.950: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Calling Number=911111135, Called Number=, Voice-Interface=0x49B42840,
Timeout=TRUE, Peer Encap Type=ENCAP_VOICE, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
*Oct 26 06:51:14.950: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=11
*Oct 26 06:51:14.970: ISDN Se0/0/0:15 Q931: TX -> CALL_PROC pd = 8 callref = 0x8066
Channel ID i = 0xA9839F
Exclusive, Channel 31
Progress Ind i = 0x8188 - In-band info or appropriate now available
*Oct 26 06:51:14.970: ISDN Se0/0/0:15 Q931: TX -> CONNECT pd = 8 callref = 0x8066
*Oct 26 06:51:15.006: ISDN Se0/0/0:15 Q931: RX <- CONNECT_ACK pd = 8 callref = 0x0066
*Oct 26 06:51:15.006: %ISDN-6-CONNECT: Interface Serial0/0/0:30 is now connected to 911111135 N/A
*Oct 26 06:51:24.546: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:30, changed state to up
*Oct 26 06:51:31.406: ISDN Se0/0/0:15 Q931: RX <- DISCONNECT pd = 8 callref = 0x0066
Cause i = 0x8290 - Normal call clearing
Progress Ind i = 0x8288 - In-band info or appropriate now available
*Oct 26 06:51:31.406: %ISDN-6-DISCONNECT: Interface Serial0/0/0:30 disconnected from 911111135 , call lasted 16 seconds
*Oct 26 06:51:31.410: ISDN Se0/0/0:15 Q931: call_disc: PI received in disconnect; Postpone sending RELEASE for callid 0x16
*Oct 26 06:51:41.402: ISDN Se0/0/0:15 Q931: RX <- RELEASE pd = 8 callref = 0x0066
Cause i = 0x8290 - Normal call clearing
*Oct 26 06:51:41.406: ISDN Se0/0/0:15 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x8066
*Oct 26 06:51:41.414: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Calling Number=9T, Called Number=, Voice-Interface=0x0,
Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
*Oct 26 06:51:41.414: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Result=NO_MATCH(-1) After All Match Rules Attempt
REALLY APPRECIATE YOUR HELP
10-26-2017 02:10 AM
10-26-2017 02:41 AM
Thank you for your time and constructive info.I am truly grateful
10-26-2017 02:51 AM
10-29-2017 02:02 PM
Hi Yaarub,
There a mistake in the received ISDN Setup Control Message that is sent by the provider, you get the field "Calling Party Number" twice, according to regular ISDN Q931 capture the 2nd one should be the "Called Party Number", also notice the other highlighted values.
Finally, there is Codeset part missing that is used by ISDN parties to know what fields are used in the control messages; and this part comes at the end of Setup Control Message.
So, the provider operation engineers have correct the configuration in their side for these missing info to appear in the Setup Control Message.
For more info about ISDN Layer 3 Basic Call Control, check this document from ETSI:
http://www.etsi.org/deliver/etsi_i_ets/300100_300199/30010201/01_60/ets_30010201e01p.pdf
Debug isdn q931 result:
*Oct 25 18:17:34.025: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8 callref = 0x0062
Sending Complete
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98384
Exclusive, Channel 4
Progress Ind i = 0x8283 - Origination address is non-ISDN
Calling Party Number i = 0x0083, '911111135'
Plan:Unknown, Type:Unknown
Calling Party Number i = 0x0083, '911111135'
Plan:Unknown, Type:Unknown
Locking Shift to Codeset 5
Codeset 5 IE 0x2A
*Oct 25 18:17:34.025: ISDN Se0/0/0:15 Q931: Received SETUP callref = 0x8062 callID = 0x0012 switch = primary-net5 interface = User
*Oct 25 18:17:34.045: ISDN Se0/0/0:15 Q931: TX -> CALL_PROC pd = 8 callref = 0x8062
Channel ID i = 0xA98384
Exclusive, Channel 4
Progress Ind i = 0x8188 - In-band info or appropriate now available
*Oct 25 18:17:34.045: ISDN Se0/0/0:15 Q931: TX -> CONNECT pd = 8 callref = 0x8062
*Oct 25 18:17:34.081: ISDN Se0/0/0:15 Q931: RX <- CONNECT_ACK pd = 8 callref = 0x0062
*Oct 25 18:17:34.081: %ISDN-6-CONNECT: Interface Serial0/0/0:3 is now connected to 911111135 N/A
*Oct 25 18:17:36.209: ISDN Se0/0/0:15 Q931: RX <- DISCONNECT pd = 8 callref = 0x0062
Cause i = 0x8290 - Normal call clearing
Progress Ind i = 0x8288 - In-band info or appropriate now available
*Oct 25 18:17:36.209: %ISDN-6-DISCONNECT: Interface Serial0/0/0:3 disconnected from 911111135 , call lasted 2 seconds
*Oct 25 18:17:36.213: ISDN Se0/0/0:15 Q931: call_disc: PI received in disconnect; Postpone sending RELEASE for callid 0x12
*Oct 25 18:17:36.221: ISDN Se0/0/0:15 Q931: TX -> RELEASE pd = 8 callref = 0x8062
*Oct 25 18:17:36.237: ISDN Se0/0/0:15 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x0062
Looking forward for you to solve this issue to be the 1st engineer who implemented DID in LIBYA.
Best of luck buddy.
Regards.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide