I got a configuration that worked fine untill it upgraded. We have 16 fxo port configured in CUCM 6.1 (gateway ios is Version 12.4(15)T10) it all working fine. But when we upgraded the number of fxo ports 16 to 24 there comes the problems. There is some bad quality in three fxo ports, the IVR that we configured using CUE not work sometimes, also sometimes supervisory disconnect problems etc...
My fxo gateway is configured in H 323, will it help me if I changed it in to MGCP. I am attaching my configuration files along with this please go through it suggest me some solutions.
I'm assuming here that the new FXO lines are from the same service provider etc? If so, then the same supervisory disconnect mechanisms should be used, so the configuration of the ports should be identical.
2) MGCP/H323 - switchign to MGCP wouldn't improve the quality of the FXO line, and with CM6 would also mean that you not get caller ID any more.
3) Bad lines:
If you are still experiencing problems after impedance matching the lines then it could be for a lot of reasons - it could be simply bad termination/connection of the wires on your premises, bad connections/cabling from the service provider presentation to your router, or problems further into the service provider network.
Anything like that could cause the tones being sent to your IVR to not be clear enough to be picked up, and the same for any supervisory disconect tones.
I would first rule out bad hardware by moving a problem line to one of the original 16 ports that was working well. If the problems move with the line, then you know your hardware is OK, and you should raise a call with the service provider.
Please rate helpful posts...
Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
1) Yes the FXO line are from the same service provider (total of 24 FXO lines for one single number). And yes I gave same supervisory disconnect mechanisms that I gave to the earlier 16 FXO ports (which worked fine).
2) I asked about switching to H323 to MGCP gateway because I like to know which is better to handle and troubleshoot and also I don't know that MGCP doesn't support call id for CUCM6.
3)For the impedence match selection I need to test it and I'll let you know the result as soon as possible.
4)And for the bad voice quality I don't think its due to faulty hardware, because we checked it many times (including the cables).
Can go through my gateway configuration that I gave and suggest me some tips, it'll be much helpfull.
I am really sorry for one my mistake. Actually the voice quality is fine. The problem is the FXO port is not connecting or forwarding the calls. Which means if "voice-port 1/1/0" is the faulty one and if the CUCM try to connect to it for an outside call, from the ip phone we can hear a loud noise (ssshhh...), sometime there is no sound at all and no call is connected to outside. Same case if some outside call comes it don't detecting the calls not forwarding to AA. I hope you understand my situation. These problems shows only for 3 FXO ports and there is no problem with incoming service provider lines.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...