Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

ISDN between 2 Cisco VG - Calls don't complete...

Dear All,

Two Cisco routers are connected as follows:

VoIP--> R1 -->ISDN--> R2 -->VoIP

Appreciate any ideas or recommendations to get successful calls from R1 to R2?

The Problem: When the call leaves R1 to R2 over the ISDN link in between i see the call coming on R2 and then disconnected with the following disconnect reason:

Cause i = 0x82E6 - Recovery on timer expiry

R1 config:

---------------

!

interface Serial4/0:15

no ip address

encapsulation hdlc

no logging event link-status

isdn switch-type primary-net5

isdn overlap-receiving T302 5000

isdn protocol-emulate network

isdn incoming-voice voice

no cdp enable

!

dial-peer voice 10 pots

preference 1

destination-pattern 000T

progress_ind alert enable 8

direct-inward-dial

port 4/0:15

!

dial-peer voice 11 pots

preference 3

destination-pattern .T

progress_ind alert enable 8

direct-inward-dial

port 4/0:15

forward-digits 5

!

R2 config:

--------------

!

interface Serial2/0:15

no ip address

encapsulation hdlc

no logging event link-status

isdn switch-type primary-net5

isdn overlap-receiving T302 4000

isdn incoming-voice voice

isdn send-alerting

isdn sending-complete

no cdp enable

!

dial-peer voice 99 pots

tone ringback alert-no-PI

preference 2

destination-pattern .T

progress_ind setup enable 3

progress_ind alert enable 8

progress_ind progress enable 1

progress_ind connect enable 1

incoming called-number .T

no digit-strip

direct-inward-dial

port 2/0:15

!

dial-peer voice 100 voip

destination-pattern 89...

progress_ind setup enable 3

progress_ind progress enable 1

progress_ind connect enable 1

voice-class codec 1

session target ipv4:10.1.1.2

incoming called-number .T

no vad

!

Debug isdn q931 from R2

------------------------------------

*May 7 13:39:25.129: ISDN Se2/0:15 Q931: RX <- SETUP pd = 8 callref = 0x014D

Bearer Capability i = 0x8090A3

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98381

Exclusive, Channel 1

Net Specific Fac i = 0x00E2

Calling Party Number i = 0x2181, '4364574474'

Plan:ISDN, Type:National

Called Party Number i = 0xA1, '89222'

Plan:ISDN, Type:National

*May 7 13:39:25.133: ISDN Se2/0:15 Q931: TX -> SETUP_ACK pd = 8 callref = 0x814D

Channel ID i = 0xA98381

Exclusive, Channel 1

*May 7 13:39:34.841: ISDN Se2/0:15 Q931: RX <- DISCONNECT pd = 8 callref = 0x014D

Cause i = 0x82E6 - Recovery on timer expiry

*May 7 13:39:34.845: ISDN Se2/0:15 Q931: TX -> RELEASE pd = 8 callref = 0x814D

*May 7 13:39:34.853: ISDN Se2/0:15 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x014D

--------------------------

Any ideas or recommendations to get successful calls from R1 to R2?

Thanks in advance.

1 REPLY
Blue

Re: ISDN between 2 Cisco VG - Calls don't complete...

Clearly your q9.31 is being released immediately after your setup. (no proceed, capabilities, facility, nofity or alerting are being completed)

This is commonly caused by h.323 packets being sourced from an incorrect interface.

(you can confirm this with the 'debug h225 events' & 'debug h225 asn1')(the source ip address is written in hex but you'll be able to see it if you review the debug output when placing a call and converting the hex to decimal)(there is also 'debug h225 q931' which provides more detail in the q931 processes but it will basically tell you the same thing....released immediately after setup_ack)

You may need to post more of your config as the serial ports & dialpeers are not the only pieces of the router that are supporting your VoIP.

Your ethernet interfaces, and specifically your voice vlan interface, also are supporting your voip.

Add the following to the Voice interface (or subinterface; or better yet a Loopback interface) on both routers:

h323-gateway voip bind srcaddr 10.1.100.1

(replace 10.1.100.1 with your loopback or voice interface ip address)

Also, how are your PRIs registered? to CME or CCM?

Please see the following link for more info on the h323 binding command:

http://www.cisco.com/en/US/docs/ios/voice/command/reference/vr_h1.html#wp1053156

175
Views
0
Helpful
1
Replies
CreatePlease to create content