cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1702
Views
5
Helpful
2
Replies

H323 gateway duplicate set-up calls

JAMES WEST
Level 1
Level 1

Hi,

I have configured an H323 gateway and all incoming call receive the following -

I have attached the config, but the dial-peers seem to be matched, so l am not sure why the incoming calls fail.

Jan 26 13:02:49.176: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8  callref = 0x0001

        Sending Complete

        Bearer Capability i = 0x8090A3

                Standard = CCITT

                Transfer Capability = Speech 

                Transfer Mode = Circuit

                Transfer Rate = 64 kbit/s

        Channel ID i = 0xA98381

                Exclusive, Channel 1

        Calling Party Number i = 0x2180, '1383413747'

                Plan:ISDN, Type:National

        Called Party Number i = 0x81, '427199'

                Plan:ISDN, Type:Unknown

Jan 26 13:02:49.176: ISDN Se0/0/0:15 Q931: Received SETUP  callref = 0x8001 callID = 0x0061 switch = primary-net5 interface = User

Jan 26 13:02:49.176: ASSERTION FAILED : ../voip/cctsp/tsp_cdapi.c:  tsp_cdb_assert_check:  9517

Jan 26 13:02:53.156: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8  callref = 0x0001

        Sending Complete

        Bearer Capability i = 0x8090A3

                Standard = CCITT

                Transfer Capability = Speech 

                Transfer Mode = Circuit

                Transfer Rate = 64 kbit/s

        Channel ID i = 0xA98381

                Exclusive, Channel 1

        Calling Party Number i = 0x2180, '1383413747'

                Plan:ISDN, Type:National

        Called Party Number i = 0x81, '427199'

                Plan:ISDN, Type:Unknown

Jan 26 13:02:53.156: ISDN Se0/0/0:15 **ERROR**: L3_GetUser_NLCB: DUPLICATE SETUP, message ignored.

Jan 26 13:02:56.328: ISDN Se0/0/0:15 Q931: RX <- DISCONNECT pd = 8  callref = 0x0001

        Cause i = 0x8090 - Normal call clearing

Jan 26 13:02:56.328: ISDN Se0/0/0:15 Q931: TX -> RELEASE pd = 8  callref = 0x8001

Jan 26 13:02:56.392: ISDN Se0/0/0:15 Q931: RX <- RELEASE_COMP pd = 8  callref = 0x0001

FCBC-POR-R01#

Jan 26 13:04:42.400: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

   Calling Number=1383413747, Called Number=427199, Voice-Interface=0x2B675B6C,

   Timeout=TRUE, Peer Encap Type=ENCAP_VOICE, Peer Search Type=PEER_TYPE_VOICE,

   Peer Info Type=DIALPEER_INFO_SPEECH

Jan 26 13:04:42.400: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

   Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming Dial-peer=802

Jan 26 13:04:42.400: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:

   dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=0

Jan 26 13:04:42.400: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

   Calling Number=1383413747, Called Number=427199, Voice-Interface=0x0,

   Timeout=TRUE, Peer Encap Type=ENCAP_VOICE, Peer Search Type=PEER_TYPE_VOICE,

   Peer Info Type=DIALPEER_INFO_FAX

Jan 26 13:04:42.400: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

   Result=NO_MATCH(-1) After All Match Rules Attempt

Jan 26 13:04:42.400: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:

   dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=-1

Jan 26 13:04:42.400: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:

   Calling Number=, Called Number=427199, Peer Info Type=DIALPEER_INFO_SPEECH

Jan 26 13:04:42.400: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:

   Match Rule=DP_MATCH_DEST; Called Number=427199

Jan 26 13:04:42.400: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:

   Result=Success(0) after DP_MATCH_DEST

Jan 26 13:04:42.400: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:

   dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=0

Jan 26 13:04:42.400: //-1/xxxxxxxxxxxx/DPM/dpMatchPeers:

   Result=SUCCESS(0)

   List of Matched Outgoing Dial-peer(s):

     1: Dial-peer Tag=1

     2: Dial-peer Tag=2

Jan 26 13:04:42.400: ASSERTION FAILED : ../voip/cctsp/tsp_cdapi.c:  tsp_cdb_assert_check:  9517

Thanks,

James

2 Replies 2

acampbell
VIP Alumni
VIP Alumni

James,

Looks like you are hitting a bug

CSCsm31235

CSCsm31235 Bug Details
Inbound ISDN calls fail with **ERROR**: Module-CCPRI ...CCPCC_CallIdle.
Symptom:
Incoming ISDN calls fail with the following error after the SETUP message is received:
ISDN **ERROR**: Module-CCPRI Function-CCPCC_CallIdle Error-Unknown event received in message from L3 or Host: 90

Another SETUP may be sent by the carrier due to no response, which generates this error:
ISDN Se0/0/0:23 **ERROR**: L3_GetUser_NLCB: DUPLICATE SETUP, message ignored.

Workaround:
None
Status Status
Fixed
(Resolved)
Severity Severity
1 - catastrophic

Last Modified Last Modified
In Last Year

Product Product
Cisco IOS software

Technology Technology


1st Found-In 1st Found-in
12.4(15)T2
Known Affected Versions KAV


Fixed-In Fixed-in
12.4(15)T3

Component(s) Component
isdn

Regression http://tools.cisco.com/Support/BugToolKit/images/Field%20Definitions.html

Check IOS and up or downgrade

Regards

Alex

Please rate useful posts

Regards, Alex. Please rate useful posts.

Alex,

Thanks for getting back to me on this.

I had logged a TAC case at the same time of creating this on the forums. Cisco TAC advised me that they have a number of internal notes highlighting the a reboot of the ISR router was required for the H323 incoming call leg to be functional.

I scheduled a reload for that evening, and after the router was back online, l could make calls into the CUCM system.

Thanks for getting back to me.

Regards,

James