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

AS5350XM ISDN connection encapsulation failed

We get the following phenomenon:

A terminal makes an ISDN connection to the AS5350 with an ISDN line that does'nt send its CLID (q931).

The terminal gets connected but the AS5350 cann't route ip packets back to the terminal.

'Debug ip packets' gives as information 'encapsulation failed'

When we redo the same exercise but with a ISDN that presents its CLID we have no problem.

Has somebody an idea what's the reason for this behaviour.

IOS = c5350-is-mz.124-7c.bin

our config:

resource-pool profile customer TERM

limit base-size all

limit overflow-size 0

resource RESOURCE_ISDNPORTS digital

resource RESOURCE_SPEMODEMS speech

dnis group TERM

source template TERM

template TERM

peer ip address forced

peer default ip address pool TERM

ppp timeout idle 70

interface Loopback1

description loopback interface for summarization pool addresses

ip address x.x.15.193 255.255.255.192

!

interface Serial3/0:15

description ISDN pra interface

no ip address

encapsulation ppp

ip tcp header-compression

dialer rotary-group 1

dialer-group 1

no snmp trap link-status

isdn switch-type primary-net5

isdn fast-rollover-delay 5

isdn incoming-voice modem

isdn send-alerting

no peer default ip address

no cdp enable

!

interface Dialer1

description async interface for ISDN/PPP calls

ip unnumbered Loopback1

ip access-group security_dialup in

ip verify unicast reverse-path

encapsulation ppp

ip tcp header-compression

dialer in-band

dialer idle-timeout 70

dialer-group 1

no snmp trap link-status

peer default ip address pool TERM

no keepalive

no cdp enable

!

ip local pool TERM x.x.15.194 x.x.15.254

!

ip route 0.0.0.0 0.0.0.0 x.x.0.193

ip route x.x.15.192 255.255.255.192 Null0 200

!

dialer dnis group TERM

number xxxxx

dialer-list 1 protocol ip permit

1 ACCEPTED SOLUTION

Accepted Solutions
Hall of Fame Super Gold

Re: AS5350XM ISDN connection encapsulation failed

Hello,

when no mapping is possible with caller number information, PPP authentication is required, but I don't see it configured in above.

Hope this helps, please rate post if it does!

4 REPLIES
Hall of Fame Super Gold

Re: AS5350XM ISDN connection encapsulation failed

Hello,

when no mapping is possible with caller number information, PPP authentication is required, but I don't see it configured in above.

Hope this helps, please rate post if it does!

New Member

Re: AS5350XM ISDN connection encapsulation failed

This information is new to me, we used to use a competitors device, for which this problem never occured.

PPP authentication isn't an option, hence we will add this requirement into our specs.

Thanks.

Hall of Fame Super Gold

Re: AS5350XM ISDN connection encapsulation failed

I have to correct myself on this.

In lack of clid, is not that you need authentication, but more precisely IP address negotiation. For example, you assign an IP address to the caller from a pool. This way, the router will be able to build a dynamic dialer-map that you can see with "show dialer map".

New Member

Re: AS5350XM ISDN connection encapsulation failed

In the config IP negotiation is included pointing to a pool (here called TERM)

I will redo tests and check the dialer map.

First connection (with CLID) gives following input:

Dynamic dialer map ip x.x.15.231 name 7689b366f30f4e55a895207ebe72724a00000000 () on Di1

could it be a bug in the software?

187
Views
0
Helpful
4
Replies
CreatePlease login to create content