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.aar...@dimensiondata.com To: cisco-voip@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@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
