[c-nsp] 2811, VWIC-1MFT-E1 and inbound calls
MacKinnon, Ian
Ian.MacKinnon at thus.net
Wed Mar 16 07:35:47 EST 2005
From
http://www.cisco.com/en/US/customer/products/hw/routers/ps274/products_tech_
note09186a00800b6e0f.shtml
If you set up the card to use ISDN PRI signaling, there is no support for
ISDN data connection. The card cannot terminate ISDN 64K or 56K data
connection; the card only supports voice-call termination with ISDN PRI
signaling.
> -----Original Message-----
> From: Brett Looney [mailto:brett at looney.id.au]
> Sent: 16 March 2005 12:20
> To: cisco-nsp at puck.nether.net
> Subject: [c-nsp] 2811, VWIC-1MFT-E1 and inbound calls
>
>
> Greets,
>
> Long story here, but best presented up front so that the
> question at the
> end is more specific. ;-)
>
> I have a 2811 with a VWIC-1MFT-E1 which I need to accept
> incoming ISDN data
> calls from remote routers (all 1600's, currently connected to
> a BRI service
> on another router). Running 12.3(11)T3 but have also tried 12.3(8)T7.
>
> Standard PRI config in this environment looks like this:
>
> controller e1 <slot number>
> pri-group timeslots 1-31
> interface serial <slot number>:15
> no ip address
> isdn switch-type primary-net5
> dialer pool-member 1
> no cdp enable
> encapsulation ppp
> ppp authentication chap
> interface Dialer 1
> <lots of dialer stuff>
> dialer pool 1
> encapsulation ppp
> ppp authentication chap
> <other dialer stuff>
>
> Anyway, when configuring the virtual serial interface it
> works fine (i.e.
> MULTIPLE_FRAME_ESTABLISHED from "show isdn status") until we
> type in the
> ppp commands. Then, the serial interface (effectively the
> PRI) goes down
> and gets stuck in TEI_ASSIGNED. Never comes back. Calls are
> not accepted.
> The PRI (eventually) comes back when we remove the ppp commands.
>
> So, I think - unlike every other PRI config I've done this
> one doesn't work
> with the ppp commands. No problems.
>
> The ppp commands get taken out but now when a call comes in
> it doesn't get
> accepted. Easy. I put in "dialer pool-member 1". Now the call
> is accepted
> but "debug dialer" tells me that it can't find an interface
> to bind to.
>
> No problems. I look at
> http://www.cisco.com/warp/public/129/23.html > (in
> particular
> the "dialing in" section) and I see the comments about "dialer
> called". So, I go to the dialer interface and add "dialer
> called <number>".
> Woohoo! "debug dialer" now shows me that it is bound to the
> dialer. Bit of
> a hack but we'll deal with that later.
>
> But - still no connection. So, I do "debug ppp negotiation".
> I can see the
> link come up, the dialer get bound to an ISDN channel and I
> can see LCP
> requests going out. Nothing coming in. Calls drop after about
> 20 seconds.
>
> So - and here are the questions:
>
> (1) Am I doing anything wrong? As far as I can tell, this is
> a standard
> config - the only new thing is the MFT VWIC.
> (2) What else can I try? My understanding is that I have to have
> "encapsulation ppp" on the serial interface but when I put it
> on my PRI drops.
>
> Any suggestions? Yes, I have raised a TAC call but it is going *very
> slowly*. Yes, I have asked my friendly cisco people - they
> are checking
> internally... Thought I might ask here for advice also...
>
> B.
>
> _______________________________________________
> cisco-nsp mailing list cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
More information about the cisco-nsp
mailing list