[cisco-voip] Recovery on timer expiry...

[Wes Sisk]

Tamer,

The call was presented at R2 as evidenced by the setup/setupack.  Then 
R2 must route call to next destination.  In order to do this R2 must 
examine the called party number.  Configure 'direct inward dial' on the 
serial interface of R2.

/Wes

Tamer Mohamed Bayomy wrote:
>
> 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.
>
> TB
>
> ------------------------------------------------------------------------
>
> This body part will be downloaded on demand.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20080511/5fd37195/attachment-0001.html