[c-nsp] AS5400XM Question

Brian Turnbow b.turnbow at twt.it
Fri Jun 29 10:40:16 EDT 2007


Yes it can do it 
You need a "data" dial peer to use to specify which are data calls.

http://www.cisco.com/en/US/products/sw/iosswrel/ps1839/products_feature_guide09186a0080110d2b.html


Regards
Brian 

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Paul Stewart
Sent: venerdì 29 giugno 2007 16.23
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] AS5400XM Question

Hi folks....

We are having an issue with dial-up customers and hoping someone can shed
some light on a possible solution.  There are several options and one of
them could involve a configuration change on our 5400XM....

At a remote POP, we have 10 T1's coming into a AS5400XM box which then takes
these *voice* T1's and sends them off to our Metaswitch system.  The T1's
are handling regular voice calls plus they are now handling modem traffic
recently as well....   When the modem traffic hits the Metaswitch, it is
then sent off to a series of T1's to our Nortel CVX1800 box ....

Roughly 80% of the clients dialing in are having no problems, but 20% of
them are having handshaking problems on dial-up.  It seems (on the surface)
that the further away these customers are geographically, the more likely
they are having the problem - but that's unconfirmed for sure....

My question is specifically.. can the AS5400XM handle the modem calls in
these voice T1's?  So, if it's a modem calling then the 5400 will terminate
the modem call and become the NAS but if it's voice then it will continue on
it's current path to our Metaswitch?  OR, is there something in this
configuration that could be causing some of this grief?

The remote POP is connected via 100 meg fiber back to our main facilities
which is where the Metaswitch is located.  There is no packet loss, jitter
etc. on the connection - looks great/clean.

Config looks like this:

voice call carrier capacity active
!
voice service voip
 fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback pass-through
g711ulaw
controller T1 6/0
 framing sf
 linecode ami
 ds0-group 0 timeslots 1-24 type none service mgcp
 description 211T1 - Local Transiting - IXC
!
controller T1 6/1
 framing sf
 linecode ami
 ds0-group 0 timeslots 1-2 type none service mgcp
 description 212T1 - 711
!
controller T1 6/2
 framing sf
 linecode ami
 ds0-group 0 timeslots 1-24 type none service mgcp
 description 201T1 - Bill and Keep
!
controller T1 6/3
 framing sf
 linecode ami
 ds0-group 0 timeslots 1-24 type none service mgcp
 description 202T1 - Bill and Keep
!
controller T1 6/4
 framing sf
 linecode ami
 ds0-group 0 timeslots 1-24 type none service mgcp
 description 203T1 - Bill and Keep
!
controller T1 6/5
 framing sf
 linecode ami
 ds0-group 0 timeslots 1-24 type none service mgcp
 description 204T1 - Bill and Keep
!
controller T1 6/6
 framing sf
 linecode ami
 ds0-group 0 timeslots 1-24 type none service mgcp
 description 205T1 - Bill and Keep
!
controller T1 6/7
 framing sf
 linecode ami
 ds0-group 0 timeslots 1-24 type none service mgcp
 description 206T1 - Bill and Keep
!
controller T1 7/0
 framing sf
 linecode ami
 ds0-group 0 timeslots 1-24 type none service mgcp
 description 207T1 - Bill and Keep
!
controller T1 7/1
 framing sf
 linecode ami
 ds0-group 0 timeslots 1-24 type none service mgcp
 description 208T1 - Bill and Keep
!
controller T1 7/2
 framing sf
 linecode ami
 ds0-group 0 timeslots 1-24 type none service mgcp
 description 209T1 - Bill and Keep
!
controller T1 7/3
 framing sf
 linecode ami
 ds0-group 0 timeslots 1-24 type none service mgcp
 description 210T1 - Bill and Keep
!
controller T1 7/4
 framing sf
 linecode ami
 ds0-group 0 timeslots 1-24 type none service mgcp
!
controller T1 7/5
 framing sf
 linecode ami
 ds0-group 0 timeslots 1-24 type none service mgcp
!
controller T1 7/6
 framing sf
 linecode ami
 ds0-group 0 timeslots 1-24 type none service mgcp
!
controller T1 7/7
 framing sf
 linecode ami
 ds0-group 0 timeslots 1-24 type none service mgcp
!
interface Group-Async0
 no ip address
 encapsulation slip
 group-range 2/00 5/107
!
voice-port 6/0:0
 echo-cancel coverage 64
!
voice-port
!
voice-port 6/2:0
 echo-cancel coverage 64
!
voice-port 6/3:0
 echo-cancel coverage 64
!
voice-port 6/4:0
 echo-cancel coverage 64
!
voice-port 6/5:0
 echo-cancel coverage 64
!
voice-port 6/6:0
 echo-cancel coverage 64
!
voice-port 6/7:0
 echo-cancel coverage 64
!
voice-port 7/7:0
 echo-cancel coverage 64
!
voice-port 7/0:0
 echo-cancel coverage 64
!
voice-port 7/1:0
 echo-cancel coverage 64
!
voice-port 7/2:0
 echo-cancel coverage 64
!
voice-port 7/4:0
 echo-cancel coverage 64
!
voice-port 7/5:0
 echo-cancel coverage 64
!
voice-port 7/6:0
 echo-cancel coverage 64
!
voice-port 7/3:0
 echo-cancel coverage 64
!
mgcp
mgcp call-agent xxx.xxx.xxx.xx service-type mgcp version 1.0
mgcp dtmf-relay voip codec low-bit-rate mode nte-gw
mgcp max-waiting-delay 500
mgcp restart-delay 2
mgcp package-capability dtmf-package
mgcp package-capability mf-package
mgcp tse payload 102
no mgcp timer receive-rtcp
mgcp fax t38 inhibit
mgcp bind control source-interface Loopback0
mgcp bind media source-interface Loopback0
!
mgcp profile default
!
dial-peer cor custom
!
!
!
!
!
ss7 mtp2-variant Bellcore 0
ss7 mtp2-variant Bellcore 1
ss7 mtp2-variant Bellcore 2
ss7 mtp2-variant Bellcore 3
!
line 2/00 3/59
 no flush-at-activation
 modem InOut
line 4/00 5/107
 no flush-at-activation
 modem InOut

Thanks in advance,

Paul



_______________________________________________
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