Can't connect via VOIP to some sites

[acewarlock]

Have 60 BCM's that were able to call each other, but I have gotten complaints that they can no longer call some sites. After doing some checking, I'am finding is the same sites that they all can't call, so this seems to be a system wide problem and the only thing I can find in common is they all are 3.6 and have Clum patch 2 & 3 on them. While watching the BCM monitor IP Devise TAB while making a call, when the call does work I get (G729 3 fpp, small jb) under the info TAB and when it doesn't work I get
( G711_ULAW 2fpp Small jb) under the info TAB. No database changes have been made other then adding patch Culm 2 &3.

 

[Crowtalks]

Check all your VoIP trunks (especially in the sometimes non-responsive systems) to make sure the trunk codecs are all G.729.

If you find one or more that isn't, change them to G.729 and see if this corrects the problem.

 

[acewarlock]

I have all the VOIP set to G.729, but every time I make a call it shows G.711 u-law on the Monitor.

 

[biv343]

Are the calls that fail going back to your Option 11 or to another BCM?

 

[acewarlock]

It's from site to site that only some fail, all sites can call the Option 11C with no problem.

 

[Crowtalks]

There has to be something in the call flow, whether it is VoIP trunks, or whatever that is set at G.711 that is screwing with your calls.

You indicated that when the calls fail it shows G.711.

I would verify the trunk codecs anyway, if it were me.

 

[acewarlock]

But this has worked for 4 years without any problems until After I did the Culm patch 2 or 3, I did about 6 months ago and last friday was the first complaint i have received and then I started checking other sites and I found that all site have the same problem calling the same sites. There's no way it could have happened at every site except by a patch upgrade as that is the only thing all sites have in common.

 

[Crowtalks]

You do have a hell of a point in why would cumulative patches affect something that has been working for 4 years.

Did you apply the patch to all 60 sites?

The only commanlity I see is there is a codec mismatch somewhere which your BCM Monitor is indicating.

I have no clue where or why, or even answers, just observations, which are basically useless in the practical world...

 

[acewarlock]

Yes Culm patch was installed on all 60 site's within a 3 day period.

 

[acewarlock]

I when't to 10 sites at random and they all can't dial the same sites. I know they were able to dial these site as we do a test call to each site when they are installed and I just checked the old logs for these sites and they all show they could dial these other sites at cutover. Again the only thing in common are Cumulative Patch 2 & 3 and the DST Patch on all 3.6 BCM's And I have 1 BCM at 3.7 and I have not added any Patches to it, but it is having the same problem calling the same sites. This is really strange.

 

[Crowtalks]

I don't have any more ideas, but I would sure like to hear what the problem was when you finally figure it out...

 

[DigitelD]

I don't know if this is an option for you but Nortel can dial in and remove the patch files. It would be costly.

SHK Certified (School of Hard Knocks)

 

[MagnaRGP]

Are you certain that nothing about the network routing has changed? Traceroute and pings are all ok?

Watching the BCM monitor MCDN, do you see the calls setting up and just failing to connect, or do they fail to setup too?

 

[acewarlock]

If I watch the BCM monitor IP Devices at both sites as I make a call, I see the call setup on the originating BCM and I get a momintary falsh of setup at the terminating end and them it drops. If the calls connects it shows G.729. if it falls it shows G.711.

Of the 60 sites I have, these are the only one's left that I can connect to.

Destination codes, These sites can call each other.
6582
6201
6080
6082
6086
6562
6105
6204
6107
6050
6060
6558

 

[teekow]

I have had problems in the past with the BCM and G.729. Why don't you try putting G.711 as the first choice codec for 2 sites (1 working site and 1 problem site) and see if this works consistently. If BW is a major concern, try G.723. Nobody ever uses it, but it sounds fine. I had to setup a dial plan to use G.723 because I could never get my Option 11 to talk to my BCM using G.729. That was 2 years ago, but the problems may still be there.

Hope this helps
Rob

 

[MagnaRGP]

Could be a codec negotiation issue. Check the payloads on the sites to ensure that each codec has the same payload configured (could also be why teekow couldn't get the Option to play nicely with his BCM). Also if you have a routing service created (I know, obvious) ensure that it is in fact on and no one (or the patch) turned it off.

 

[acewarlock]

What is a routing service?

 

[MagnaRGP]

A routing service would need to be created and activated if you are doing off-net dialing and need a fail-over to PSTN.

Example. User in site a dials 9-1-npa-nnx-xxxx and this is a local call to sites b and c. site a could be set up try to use site b's pstn, then if not possible, site c's pstn and then if still not possible it could fail out it's own pstn (toll charge).

Perhaps there is one in place and it's been turned off? How about control sets on the voip trunks?

Can you do a test call and post the MCDN messaging from BCM monitor? That might give us a clue.

 

[acewarlock]

OK, that's why I didn't know what routing service was, we don't use it and it is OFF.

 

[cook1082]

Had same problem with Voip trunks after the patches and you have to make sure you also up date with the FEPS patch.