[cisco-voip] E1 CAS card in Mexico not getting enough digits

Jason Aarons (AM) jason.aarons at dimensiondata.com
Mon Nov 17 04:50:16 EST 2014


More like Tequila!

I'm in Mexico City this week...and this case deserved a large bottle of it!

From: Ryan Huff [mailto:ryanhuff at outlook.com]
Sent: Monday, November 17, 2014 4:11 AM
To: Jason Aarons (AM); Anthony Holloway; cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] E1 CAS card in Mexico not getting enough digits

Well it had to either be the Telco or an inbound xlate. Glad you found it! Good job, now go have an Iced Tea and a vacation!
________________________________
From: jason.aarons at dimensiondata.com<mailto:jason.aarons at dimensiondata.com>
To: avholloway+cisco-voip at gmail.com<mailto:avholloway+cisco-voip at gmail.com>; ryanhuff at outlook.com<mailto:ryanhuff at outlook.com>; cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: RE: [cisco-voip] E1 CAS card in Mexico not getting enough digits
Date: Mon, 17 Nov 2014 06:03:23 +0000
So after about 5 CCIEs looked at it and 5 Cisco AS onsite engineers and 2 days of effort we found the translation-profile on the voice-port was somehow responsible.  Seems the incoming digits took longer on router-b.  Go figure.  We move the translation-profile from the voice port to the dial-peer.

I hate CAS.

From: Anthony Holloway [mailto:avholloway+cisco-voip at gmail.com]
Sent: Sunday, November 16, 2014 9:38 PM
To: Jason Aarons (AM); Ryan Huff; cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] E1 CAS card in Mexico not getting enough digits

What if...just what if, it's alternating between 3 and 4 digits every time you unplug it?  Try unplugging it and re-plugging it into the same router to validate this crazy idea.
On Sun Nov 16 2014 at 7:21:11 PM Jason Aarons (AM) <jason.aarons at dimensiondata.com<mailto:jason.aarons at dimensiondata.com>> wrote:
If you move circuit to another router and it works, then its hard to blame the carrier!

CAS stinks.


Sent from my Verizon Wireless 4G LTE Smartphone

-------- Original message --------
From: Ryan Huff
Date:11/16/2014 15:45 (GMT-05:00)
To: "Jason Aarons (AM)" , cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: RE: [cisco-voip] E1 CAS card in Mexico not getting enough digits

Ahh, missed the part about CAS, sorry.

So is the provider doing something on their side with the MAC of the E1 on your side? If the provider is sending 3 digits (regardless if it works on the other router) then it should be their issue.

You have the plan and type set according to what the provider expects?

Are you getting 3 digits for the calling or called party?
________________________________
From: jason.aarons at dimensiondata.com<mailto:jason.aarons at dimensiondata.com>
To: ryanhuff at outlook.com<mailto:ryanhuff at outlook.com>; cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: RE: [cisco-voip] E1 CAS card in Mexico not getting enough digits
Date: Sun, 16 Nov 2014 19:56:50 +0000
CAS no q931

Debug shows on bad router we receive 3 digits from provider, move circuit to another router we receive 4 digits from provider.

From: Ryan Huff [mailto:ryanhuff at outlook.com<mailto:ryanhuff at outlook.com>]
Sent: Sunday, November 16, 2014 8:52 AM
To: Jason Aarons (AM); cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: RE: [cisco-voip] E1 CAS card in Mexico not getting enough digits


So on router B, do the following and then place an inbound call from a known number:

hostname# conf t
hostname (config)# logging console
hostname (config)# exit
hostname# term mon
hostname# debug isdn q931

What do you see for "Calling Party Number i =", "Plan:" and "Type:"? The "plan" and "type" fields should be located below the "calling party  number" field. Once you've determined that you really are receiving 4 digits from the telco on that circuit the next step is to figure out what in the router config is stripping the digit. If you find that you are not receiving 4 digits from the telco, you can either work with the telco to fix it on the PRI or if the missing digit is a constant, you can add it with an inbound voice translation rule.

Look at your inbound dial peers; do you have any voice translation rules that are doing any digit stripping? Are the inbound voice translations using different regex than on the router that is working and if so, what is different?

Thanks,

Ryan Huff
CCIE Collaboration (Written), CCNP Voice, CCNA Voice
CCNA Route/Switch, CCNA Wireless, UCCX Specialist
________________________________
From: jason.aarons at dimensiondata.com<mailto:jason.aarons at dimensiondata.com>
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Date: Sun, 16 Nov 2014 08:18:22 +0000
Subject: [cisco-voip] E1 CAS card in Mexico not getting enough digits
I have a problem with a E1 CAS site in Mexico.  I have two routers. Router B is problem.

In router A I see 4 digits come in on DTMF.
In router B I see 3 digits come in on DTMF. We are missing 1 digit.

I swap the circuit and works fine in router A.  Same IOS both routers.

Controller e1 0/0/0
   Framing NO-CRC4
   dso-group 0 timeslots 1-10 type r2-digital dtmf dnis
   cas-custom 0
   Country telmex
   Seizure-ackt-time 2





_______________________________________________ cisco-voip mailing list cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net> https://puck.nether.net/mailman/listinfo/cisco-voip


itevomcid
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20141117/fab9088a/attachment.html>


More information about the cisco-voip mailing list