The Road to a VoIP guru
Search This Blog
Sunday, April 17, 2016
A change of pace
Wednesday, February 17, 2016
Cisco 8841 to Analog Paging Choppy Audio
I know it's been awhile but things have been a bit slow around here so I've been using my spare time to learn Linux inside and out the best I can. Figured another technology under my belt surely can't hurt anything. Last week however was a change of pace with a strange issue.
I have a customer that is experiencing choppy audio when dialing their analog paging system. They are on 10.5(2) so everything in place works and is supported even prior to their upgrade. Their 8841s go off hook and dial a paging number that hits a voice gateway and then pushes out an FXO port to their paging system. Every time they call the number the overhead paging sounds like crap. At first, they thought the paging system was bad but with a buttset hooked up to the POTS line going to the paging system, everything sounded fantastic. That leaves Cisco's side of things.
I had to rule out the DSPs and the FXO port. I had them make a call and after a "show voice call x/x/x" and saw nothing out of the ordinary. Logs on the gateway were also fine so what the heck? They only have a two port FXO card so I wasn't about to ask them to pull their primary line inbound to test. I instead asked a coworker to go on-site and with a spare FXO card that we know works. We swapped out the card and the same thing still happened, so piss!
After that fiasco, we went back to the drawing board and tried dialing from a phone that isn't an 8841 and everything sounded good. That old 7912 from over ten years ago still works and pointed the finger to the 8841. I don't know if it's the G.722 codec, firmware, or somehow and someway SIP is screwing up the call setup using a weird codec but I will need to pull logs to find out for sure. I need to schedule another test call with them and pull logs relevant only to that time period so I can get a fresh cap.
Hopefully this pans out to be firmware but with it suddenly happening who knows. I don't see SIP screwing up since it's just a SIP phone pushing to an H.323 gateway. At that point CUCM should have already done the heavy lifting of protocol conversion.
Monday, January 25, 2016
Out of Compliance on CUCM and need to delete some devices?
Thursday, January 14, 2016
Cisco UCS Password
Thursday, December 17, 2015
Voice PCM capture
- Debug mgcp packet (if applicable)
- Debug isdn q931
- voice hpi capture buffer 1000000
- voice hpi capture destination flash:pcm.dat
- exit
- test voice port 0/0/0:23.23 pcm-dump caplog 7 30
- :::::::::Make Test Call::::::::::::;
- test voice port 0/0/0:23.23 pcm-dump disable
- conf t
- no voice hpi capture buffer 1000000
- no voice hpi capture destination flash:pcm.dat
voice pcm capture buffer 200000
voice pcm capture destination flash:
exit
!
test voice port 0/1/3 pcm-dump caplog 7
:::::::::Make Test Call::::::::::::;
test voice port 0/1/3 pcm-dump disable
conf t
no voice pcm capture buffer 200000
no voice pcm capture destination flash:
On dial peer:
conf t
voice pcm capture buffer 80000000
voice pcm capture destination flash:
dial-peer voice 1
pcm-dump caplog FFFFFFF 254
!
After the all is done, to stop:
conf t
no voice pcm capture buffer 80000000
no voice pcm capture destination flash:
dial-peer voice 1
pcm-dump caplog disable
!
Intermittent one-way audio issues Resolved!
Tuesday, December 15, 2015
Intermittent One-Way Audio on Select phones
At this point I am thinking PRI. I push the call out another PRI and the phones are fine. This nixes the phones being bad as they worked immediately after switching from one PRI to another. This goes back to the PRI being part of the problem but I can see packets being transmitted and received at the proper G.711u-law codec. Ultimately, I am going to have to see if the carrier is willing to troubleshoot since the problem is most likely something sporadic on their side. This problem has been a hindrance since before a major upgrade and followed it afterwards. It is strange for something like this to be popping up like this. More information will follow as I find out the issue.