Troubleshooting Analog/Fax Lines on a VG-224

[Mark Wagnon]

Hello,

I'm having some difficulty troubleshooting a fax (more likely a voice) issue on our VG-224. The VG-224 is only used for fax lines. Last summer we upgraded our voice system from Call Manager 7.x to Call Manager 10.5.2.12901-1. Our vendor had to touch our routers and analog gateways to change session targets, etc. About two to three months after the project was completed, I started to get reports from one of our departments that they were unable to send faxes to certain numbers. I asked them to send me some numbers they could and could not fax and started to try to troubleshoot the issue. I don't understand why I can dial some remote faxes and can't dial others.

Here are some numbers that I can dial:

918587150091
916193973384

Here are some numbers that I can't dial:

913103725192
918582792953
916196909608
916197967252

show dialplan number for each of these numbers matches a dialpeer. I have debug voip ccapi inout enabled. Attached are the config for the VG-224 and output from show dialpeer and call debugs. If anyone can take a quick look at them and give me some tips on where I should look for more troubleshooting (or a solution :) ), I'd appreciate it.

Thanks for your time,
Mark

[David Blankenship]

What happens if you connect an analog phone directly up at the VG224 port and then try to dial out to the numbers that cannot be dialed out to?

[Mark Wagnon]

I knew I forgot something. I did just that and it was how I test the numbers they bring me instead of sitting on their fax machine and testing. The results being the same as in my original post. Calls  to numbers that I can dial successfully have a disconnect code of 16 and those I can't are 47 (no resource).

Thanks!

Mark

[David Blankenship]

Mark,

I did find some discussion on the 47 code.  If you have access to the Cisco Call Manager that the VG224 is registered to perhaps there is a MTP or transcoder resource shortage.

http://www.routerdiscussions.com/viewtopic.php?f=4&t=17072

I know that you have confirmed the calling search space in the Cisco Call Manager but it is worth a second look.  I am also assuming that this port on the VG224 can do internal calls as well.

[Mark Wagnon]

Thanks for the info David. I'll have a look and report back. Mark

[Ryan Huff]

Mark,

You'll very likely need to configure (and place into the call path), an IOS based MTP. I'd need to see a trace for one of the failed calls in UC Manager to be sure however; you are likely dealing with heterogeneous DTMF methods. You'll want an IOS based MTP to support the passthrough codec.

You should be able to do some software MTP sessions right off of the VG224 (http://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unified-communications-manager-callmanager/112148-mtp-config.html#ios).

Thanks,

Ryan

(.. Please rate helpful posts ..)

[Mark Wagnon]

I'm not sure if I setup/captured the correct trace. I followed the instructions at https://supportforums.cisco.com/document/126666/collecting-cucm-traces-cucm-862-tac-sr . The only changes I made were to the filters and selected Enable MTP Trace only. What I ended up with were a couple folders, one for each call manager. They are 4-5 MB each, so I'm not sure if I can post those here. I made a couple test calls to two numbers in the list in my original post and after downloading the files I found this in one of the tgz files:

2016/02/25 11:43:00.045|CC|SETUP|129557400|129557401|71680|918587150091|918587150091
2016/02/25 11:43:00.050|CC|OFFERED|129557400|129557401|71680|918587150091|918587150091|10.200.40.3|10.200.40.2
2016/02/25 11:43:03.779|CC|SETUP|129557404|129557405|73500|83550|83550
2016/02/25 11:43:03.782|CC|OFFERED|129557404|129557405|73500|83550|83550|SEP00260B5BE27D|SEP002584184F5B
2016/02/25 11:43:04.226|CC|SETUP|129557402|129557403|85317|85372|85372
2016/02/25 11:43:04.228|CC|OFFERED|129557402|129557403|85317|85372|85372|SEP0025841851EA|SEP00260B5BE654
2016/02/25 11:43:06.451|CC|RELEASE|129557390|129557391|16
2016/02/25 11:43:06.630|CC|RELEASE|129557383|129557384|16
2016/02/25 11:43:09.331|CC|RELEASE|129557395|129557396|16
2016/02/25 11:43:11.002|CC|REJECT|129557400|129557401|71680|918587150091|918587150091|47


2016/02/25 11:43:39.985|CC|SETUP|129557430|129557431|71680|913103725192|913103725192
2016/02/25 11:43:39.989|CC|OFFERED|129557430|129557431|71680|913103725192|913103725192|10.200.40.3|10.200.40.2
2016/02/25 11:43:40.017|CC|RELEASE|129557381|129557382|16
2016/02/25 11:43:49.053|CC|SETUP|129557432|129557433|85317|85372|85372
2016/02/25 11:43:49.055|CC|OFFERED|129557432|129557433|85317|85372|85372|SEP0025841851EA|SEP00260B5BE654
2016/02/25 11:43:51.271|CC|REJECT|129557430|129557431|71680|913103725192|913103725192|47

We have two MTPs defined in our call manager, but they look rather generic to me, here is an example of one:

Media Termination Point Information
Registration:    Registered with Cisco Unified Communications Manager 10.200.40.8
IPv4 Address:    10.200.40.8
Media Termination Point TypeRequired Field     Cisco Media Termination Point Software
Host ServerRequired Field     10.200.40.8
Media Termination Point NameRequired Field    
Description    
Device PoolRequired Field    
Trusted Relay Point


Is this helpful at all? If not, maybe I need to collect more/different information in the trace? Also, can I upload the trace files for inspection, or is that frowned upon? One other thing, the first number in the trace was rejected, but when I first tested it and retested before posting, I was able to connect to the remote fax machine.

Thanks for all your help,
Mark