06-01-2017 10:04 AM - edited 03-17-2019 10:29 AM
Hi,
We have a ISR4331 with a NIM-2FXS where a postal meter need to me connected. The PSTN is with a PRI. The postal meter is configured to dial 9 before the numbre that must be reached. When the device place a call we get fast busy and in the debugs we see that only 91 is process by the router instead of the full number. The call flow is :
Device > FXS > ISR > PRI > Telco
If we connect an analog phone, we can dial any number without problems.
Any idea? Maybe the way the postal meter is sending the digits is different that dialing each number on the analog phone?
Here is a sample of the config and dial-peers. I've also joint some debugs
Thanks
voice class dpg 112
dial-peer 5
dial-peer 6
voice-port 0/1/0
cptone us
timeouts interdigit 10
station-id number 2222
dial-peer voice 5 pots
description ** Local calls **
preference 5
destination-pattern 9[2-9]..[2-9]......$
port 0/2/0:23
forward-digits 10
!
dial-peer voice 6 pots
description ** Long-Distance calls **
preference 5
destination-pattern 91[2-9]..[2-9]......$
port 0/2/0:23
forward-digits 11
dial-peer voice 320 pots
description InboundFXS
preference 6
answer-address 2222
destination dpg 112
05-30-2018 08:23 AM
Hi m.chartier,
I have a quite similar problem: ISR4351 router, directly connected analog phone on FXS port, and VoIP dial-peers to remote voice gateways. Although I added no digit-strip and forward-digits all options to local POTS dial-peers, and the DSP API does see all digits, the router just takes the first two digits and tries to match a VoIP dial-peer - of course it will be unsuccessful because we need more digits to initialize a call. We try to fight this issue with Cisco TAC, and we have already checked all trivial pitfalls. If your troubleshooting was successful, could you please share the solution?
Regards,
Peter
05-30-2018 08:34 AM
05-30-2018 08:44 AM
Cisco IOS XE Software, Version 03.16.04b.S - Extended Support Release
Cisco IOS Software, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.5(3)S4b, RELEASE SOFTWARE (fc1)
05-30-2018 09:32 AM
05-30-2018 12:51 PM
Thanks a lot for pointing out to this bug. Tomorrow I will upgrade the software and share results.
05-31-2018 05:44 AM
Nipun, your hint was correct. After an upgrade to 15.5(3)S7b, the issue has gone... Thank you.
05-31-2018 06:23 AM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide