isdn overlap send recieve

pwenger · ‎12-13-2007

Hi

I've got a CiscoCommunications Manager 6.0.1 Business Edition with a cisco2851 MGCP Gateway. As the server is installed in Germany I need isdn overlap send recieve. On the RoutePattern configuration page I entered 0.0!as RoutePattern and checked Allow Overlap Sending. The T302 Timer on the SystemParameter Page is set to default (15000). Some incomig calls can not be established as I don't recieve the whole number. See below a debug isdn q931 output.

Dec 13 16:48:26.700: ISDN Se0/0/0:15 Q931: TX -> SETUP pd = 8 callref = 0x0244

Bearer Capability i = 0x8090A3

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA9839D

Exclusive, Channel 29

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

Calling Party Number i = 0x2181, '61967005743921245'

Plan:ISDN, Type:National

Called Party Number i = 0x80, '140'

Plan:Unknown, Type:Unknown

Dec 13 16:48:26.740: ISDN Se0/0/0:15 Q931: RX <- SETUP_ACK pd = 8 callref = 0x8244

Channel ID i = 0xA9839D

Exclusive, Channel 29

Dec 13 16:48:31.696: ISDN Se0/0/0:15 Q931: RX <- DISCONNECT pd = 8 callref = 0x1D9B

Cause i = 0x82E6 - Recovery on timer expiry

Dec 13 16:48:31.700: ISDN Se0/0/0:15 Q931: TX -> RELEASE pd = 8 callref = 0x9D9B

Dec 13 16:48:31.700: ISDN Se0/0/0:15 Q931: TX -> DISCONNECT pd = 8 callref = 0x0244

Cause i = 0x82E6 - Recovery on timer expiry

Dec 13 16:48:31.716: ISDN Se0/0/0:15 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x1D9B

Dec 13 16:48:31.756: ISDN Se0/0/0:15 Q931: RX <- RELEASE pd = 8 callref = 0x8244

Dec 13 16:48:31.772: ISDN Se0/0/0:15 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x0244

Dec 13 16:48:35.484: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8 callref = 0x1D9C

Bearer Capability i = 0x9090A3

Standard = CCITT

Transfer Capability = 3.1kHz Audio

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA9839D

Exclusive, Channel 29

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

Calling Party Number i = 0x00A3, N/A

Plan:Unknown, Type:Unknown

Called Party Number i = 0xC1, '7007100'

Plan:ISDN, Type:Subscriber(local)

Dec 13 16:48:35.516: ISDN Se0/0/0:15 Q931: TX -> CALL_PROC pd = 8 callref = 0x9D9C

Channel ID i = 0xA9839D

Exclusive, Channel 29

Dec 13 16:48:35.516: ISDN BR0/2/1 Q931: TX -> SETUP pd = 8 callref = 0x26

Sending Complete

Bearer Capability i = 0x8090A3

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0x8A

Exclusive, B2

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

Calling Party Number i = 0x00A1, N/A

Plan:Unknown, Type:Unknown

Called Party Number i = 0x80, '7100'

Plan:Unknown, Type:Unknown

Dec 13 16:48:35.548: ISDN BR0/2/1 Q931: RX <- ALERTING pd = 8 callref = 0xA6

Dec 13 16:48:35.556: ISDN Se0/0/0:15 Q931: TX -> ALERTING pd = 8 callref = 0x9D9C

Progress Ind i = 0x8088 - In-band info or appropriate now available

Does someone have an idea what I have to change?

Regards

Peter

Zin.Karzazi · ‎12-14-2007

Are you using SIgnificant Digits (CCM) with a PRI MGCP Router`? if yes, this is not supported. Try to set the Significant Digits to ALL and route your Inbound Calls using translation Pattern. Also Make sure the Parameter "OverlapReceivingForPriFlag" is set to true.

pwenger · ‎12-19-2007

You were right. After I removed the significant digits and added some Translation Patterns it worked fine. Thanks a lot!

Regards

Peter

MICHAEL BASTINCK · ‎12-14-2007

In my German H323 Gateway, I've configured the overlap-receiving at my Serial Interface and this is working fine. Not sure if this is helpfull for you.

interface Serial0/0/0:15

no ip address

no logging event link-status

isdn switch-type primary-net5

isdn overlap-receiving T302 2500

yxsjwsb · ‎12-14-2007

I'm not sure what you need to change. You might look at downloading the PRI debug program at pippinsoftware.com - demo shows ten channels for free.

It basically gives you a gui from the q931 debugs.

yxsjwsb · ‎12-22-2007

The first beta of this PRI debugger had some issues, there's a revised beta posted at pippinsoftware.com now.