×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

ISDN Overlap Receiving Issue

Unanswered Question
Jan 14th, 2014
User Badges:

Hi,


I have a H323 Voicegateway working with CUCM 9.1.2.10000-28. Voicegateway is a 3925 Router with Version 15.3(2)T1.


At the moment I have the Problem that some Calls from external fail because the Telco send the digits in overlap at not as en-block as you can see in the following ISDN q931 debug:


Jan 14 13:20:02.158: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8  callref = 0x1B0F

Bearer Capability i = 0x9090A3

  Standard = CCITT

  Transfer Capability = 3.1kHz Audio

  Transfer Mode = Circuit

  Transfer Rate = 64 kbit/s

Channel ID i = 0xA98392

  Exclusive, Channel 18

Progress Ind i = 0x8183 - Origination address is non-ISDN 

Calling Party Number i = 0x2181, 'xxxxxx'

  Plan:ISDN, Type:National

Called Party Number i = 0xC1, '152500'

  Plan:ISDN, Type:Subscriber(local)

Jan 14 13:20:02.158: ISDN Se0/0/0:15 Q931: Received SETUP  callref = 0x9B0F callID = 0x6D54 switch = primary-net5 interface = User

Jan 14 13:20:02.158: ISDN Se0/0/0:15 Q931: TX -> SETUP_ACK pd = 8  callref = 0x9B0F

Channel ID i = 0xA98392

  Exclusive, Channel 18

Jan 14 13:20:02.258: ISDN Se0/0/0:15 Q931: RX <- INFORMATION pd = 8  callref = 0x1B0F

Called Party Number i = 0xC1, '6'

  Plan:ISDN, Type:Subscriber(local)

Jan 14 13:20:02.270: ISDN Se0/0/0:15 Q931: TX -> CALL_PROC pd = 8  callref = 0x9B0F

Jan 14 13:20:02.610: ISDN Se0/0/0:15 Q931: TX -> DISCONNECT pd = 8  callref = 0x9B0F

Cause i = 0x80A2 - No circuit/channel available

Jan 14 13:20:02.662: ISDN Se0/0/0:15 Q931: RX <- RELEASE pd = 8  callref = 0x1B0F

Jan 14 13:20:02.662: ISDN Se0/0/0:15 Q931: TX -> RELEASE_COMP pd = 8  callref = 0x9B0F

Jan 14 13:20:02.158: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8  callref = 0x1B0F


Called Number is "152500631" but I receive on the Gateway at first "152500" an then in a scond message the digit "6". The digits "31" are missing.

For testing I've configured ISDN Overlap Receiving on the Serial 0/0/0:15 with 20000 msec, but it still isn't working.

Is there a Timer to fix the problem?

The following is a part of the configuration of the H323-Gateway:

!
interface Serial0/0/0:15
description *** PMX 1 ***
no ip address
encapsulation hdlc
no logging event link-status
isdn switch-type primary-net5
isdn overlap-receiving T302 20000

isdn incoming-voice voice
isdn send-alerting
isdn sending-complete
isdn outgoing-voice info-transfer-capability 3.1kHz-audio
no cdp enable
!

voice-port 0/0/0:15
no vad
playout-delay fax 40
cptone DE
description *** PMX 1 ***
bearer-cap 3100Hz
!

dial-peer voice 1 pots
description **INCOMING CALLS**

translation-profile incoming PSTN_IN
incoming called-number .T
direct-inward-dial
port 0/0/0:15
!

Thank you and best regards,

Thomas

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Suresh Subramanian Tue, 01/14/2014 - 05:47
User Badges:
  • Gold, 750 points or more
  • Community Spotlight Award,

    Mobile User, October 2015

what is your outbound dial-peer to CUCM? did you try configuing the wildcard mask 'T' in the outbound dial-peer to CUCM also?



Please rate all the useful posts

tkauer2591 Tue, 01/14/2014 - 05:49
User Badges:

That's the Dial-Peer to CUCM:


dial-peer voice 30 voip

description 3stellig zum CUCM

preference 1

destination-pattern [1-9]..T

session target ipv4:10.0.0.128

voice-class codec 1 

dtmf-relay h245-alphanumeric

no vad

Regards,

Thomas

Suresh Subramanian Tue, 01/14/2014 - 05:58
User Badges:
  • Gold, 750 points or more
  • Community Spotlight Award,

    Mobile User, October 2015

Instead of 'destination-pattern [1-9]..T' could you please try 'destination-pattern 1T' in a test dial-peer and check?


also from the debug you posted, the call was disconnected with Cause i = 0x80A2 - No circuit/channel available.


Could you please check the ISDN channel status with 'show isdn service' command to ensure all channels are up and idle?



Please rate all the useful posts

tkauer2591 Tue, 01/14/2014 - 06:07
User Badges:

I've configured the Dial-Peer with the 'destination-pattern 1T' but I have the same problem.


ISDN Channel is up:


ISDN Se0/0/0:15, Channel [1-31]

  Configured Isdn Interface (dsl) 0

   Channel State (0=Idle 1=Proposed 2=Busy 3=Reserved 4=Restart 5=Maint_Pend)

    Channel :  1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1

    State   :  0 0 0 2 0 0 0 0 0 0 0 0 0 0 2 3 0 0 2 2 0 2 0 2 2 2 2 0 2 0 2

Global ISDN Switchtype = primary-net5

ISDN Serial0/0/0:15 interface

        dsl 0, interface ISDN Switchtype = primary-net5

    Layer 1 Status:

        ACTIVE

    Layer 2 Status:

        TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED

    Layer 3 Status:

        12 Active Layer 3 Call(s)

        CCB:callid=6D56, sapi=0, ces=0, B-chan=27, calltype=VOICE

        CCB:callid=6D99, sapi=0, ces=0, B-chan=15, calltype=VOICE

        CCB:callid=6D9A, sapi=0, ces=0, B-chan=4, calltype=VOICE

        CCB:callid=E5DD, sapi=0, ces=0, B-chan=20, calltype=VOICE

        CCB:callid=E608, sapi=0, ces=0, B-chan=30, calltype=VOICE

        CCB:callid=E60B, sapi=0, ces=0, B-chan=24, calltype=VOICE

        CCB:callid=E60C, sapi=0, ces=0, B-chan=28, calltype=VOICE

        CCB:callid=E60F, sapi=0, ces=0, B-chan=29, calltype=VOICE

        CCB:callid=E610, sapi=0, ces=0, B-chan=25, calltype=VOICE

        CCB:callid=E611, sapi=0, ces=0, B-chan=23, calltype=VOICE

        CCB:callid=E612, sapi=0, ces=0, B-chan=21, calltype=VOICE

        CCB:callid=E613, sapi=0, ces=0, B-chan=26, calltype=VOICE

    Active dsl 0 CCBs = 12

    The Free Channel Mask:  0xC0273FF7

    Number of L2 Discards = 0, L2 Session ID = 3

Suresh Subramanian Tue, 01/14/2014 - 06:20
User Badges:
  • Gold, 750 points or more
  • Community Spotlight Award,

    Mobile User, October 2015

when you configure "destination-pattern 1T" what is the disconnect cause code you get? same 0x80A2?


could you please post debug isdn q931 again with 1T config?



Please rate all the useful posts

tkauer2591 Tue, 01/14/2014 - 06:32
User Badges:

Same Error:

Jan 14 14:25:58.975: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8  callref = 0x1BB8

Bearer Capability i = 0x9090A3

  Standard = CCITT

  Transfer Capability = 3.1kHz Audio

  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 = 0x2183, '83039239214'

  Plan:ISDN, Type:National

Called Party Number i = 0xC1, '152500'

  Plan:ISDN, Type:Subscriber(local)

Jan 14 14:25:58.975: ISDN Se0/0/0:15 Q931: Received SETUP  callref = 0x9BB8 callID = 0x6DFC switch = primary-net5 interface = User

Jan 14 14:25:58.975: ISDN Se0/0/0:15 Q931: TX -> SETUP_ACK pd = 8  callref = 0x9BB8

Channel ID i = 0xA98387

  Exclusive, Channel 7

Jan 14 14:25:59.075: ISDN Se0/0/0:15 Q931: RX <- INFORMATION pd = 8  callref = 0x1BB8

Called Party Number i = 0xC1, '3'

  Plan:ISDN, Type:Subscriber(local)

Jan 14 14:25:59.087: ISDN Se0/0/0:15 Q931: TX -> CALL_PROC pd = 8  callref = 0x9BB8

Jan 14 14:25:59.411: ISDN Se0/0/0:15 Q931: TX -> DISCONNECT pd = 8  callref = 0x9BB8

Cause i = 0x80A2 - No circuit/channel available

Jan 14 14:25:59.471: ISDN Se0/0/0:15 Q931: RX <- RELEASE pd = 8  callref = 0x1BB8

Jan 14 14:25:59.471: ISDN Se0/0/0:15 Q931: TX -> RELEASE_COMP pd = 8  callref = 0x9BB8

acampbell Tue, 01/14/2014 - 06:48
User Badges:
  • Green, 3000 points or more

Thomas,


I think your issue is either on on the link or the ISDN service.


If the problem was the didit signalling you would more likely send a cause

Cause i = 0x8081 - Unallocated/unassigned number

You are sending

Cause i = 0x80A2 - No circuit/channel available



Regards,
Alex.
Please rate useful posts.

Ayodeji Okanlawon Tue, 01/14/2014 - 06:53
User Badges:
  • Super Bronze, 10000 points or more
  • Cisco Designated VIP,

    2017 IP Telephony

Alex is spot on here...Your gateway is sending a disconnect of

Cause i = 0x80A2 - No circuit/channel available

You need to investigate that before anything else...


Please rate all useful posts


"The essence of christianity is not the enthronement but the obliteration of self --William Barclay"

tkauer2591 Tue, 01/14/2014 - 07:23
User Badges:

I have the Error "Cause i = 0x80A2 - No circuit/channel available" only when I receive a call like I've described above. All other calls are working without any errors

Ayodeji Okanlawon Tue, 01/14/2014 - 07:29
User Badges:
  • Super Bronze, 10000 points or more
  • Cisco Designated VIP,

    2017 IP Telephony

Nest step will be to take your logs and contact your provider.Ask them why they are sending overlap digits...Find out the reason for this anomaly..Since the rest of your calls are sent enbloc..Show them your logs..



Please rate all useful posts


"The essence of christianity is not the enthronement but the obliteration of self --William Barclay"

tkauer2591 Tue, 01/14/2014 - 07:41
User Badges:

I've already talked to the provider. The told me that they can't change anything in their configuration. When a call is established from an analog phone from external it's sending overlap digits. When the call is established from an ISDN or VoIP Phone it's sending enbloc...

tkauer2591 Thu, 01/23/2014 - 04:33
User Badges:

I've opened a TAC-Case for this issue. I will update this discussion if I have any solutions.

MOHIT SINGH Thu, 01/23/2014 - 06:18
User Badges:
  • Bronze, 100 points or more

Hi Thomas,


In case of overlap receiving PRI you should not configure "direct-inward-dial" in inbound POTS dial peer. If direct-inward-dial is configured then gateway will try to route the call as soon as ISDN setup is received and it will not wait for remaining digits due to which call will fail with "unallocated/unassigned number". To fix the issue you should remove direct inward dial from dial peer


dial-peer voice 1 pots

no direct-inward-dial


Below is good doc wich explains the overlap behaviour in detail


https://supportforums.cisco.com/docs/DOC-25562


Regards,

Mohit Singh

Actions

This Discussion

Related Content