Search results for query: *

PRI wasn't supported until MICS 5.0.

Then I agree with Deweyhumbolt - seems that the provider is not sending the calling name.

Question: does each site have it's own PRI or does one site have PRI and CLID is being passed from the main site over the VoIP netowrk? If the latter, is it only the networked sites that are not receiving calling name?

Log into "Maintenance", select "Inventory" - from there you'll have a selection to view patches amongst other things about the BCM.

I'm guessing that the H245 Tunneling config was not the answer? I had another thought which causes the same symptom ... IF there happens to be a Cisco PIX Firewall (or two) in this network, disable H323 "fixup protocols" in the PIX. There are two for ports 1718, 1719 and 1720. These fixup...

Sounds like a config issue to me. Can you provide a little detail as to the configuration? 1. You have 8 Voice Channels (min/max is what? 2/8?) 2. What sort of trunks are incoming to the BCM (PRI, T1 or analog lines?) 3. Is there more than one number that customers dial to get to the call...

There are too many variables to give an answer since you can use DHCP or Static routes. If using VoIP trunks as well, codecs and payloads much match, etc. However, to make things easier than having to read the Network Config and Device config guides, try using the "task based guide"...

I don't personally know of a way to do what you are suggesting. Perhaps someone else does. If not: Depending on how many digital, analog and IP sets you require, you may consider an Expansion Gateway configuration. The only thing is in this configuration, the resources available for IP sets...

If this BCM has a MCDN keycode, you can try using BCMMON UIP trace to see if any specific message is being received from the distant end when you attempt a call. If no MCDN keycode, then you can try looking at the feps logs - sometimes the error is obvious (in English). Good luck...

Did you add blocB to line pool access on the set?

If none of the above works - if you make a test call and stamp it (F9*9) and post the feps log, I may be able to help further.

As norstarboy125 mentioned - are you sure ALL of the appropriate ports are open in your routers? Another possibility: Have you got any Cisco Routers or a Cisco PIX firewall in the network? There are some "gotchas" with Cisco/Nortel interop. If Cisco Routers are in the network: Cisco...

It's always best to check the gas before rebuilding the engine, eh? LOL! Sorry I tried to complicate matters.

I forgot to mention, if you feel you have the configuration correct already, you should try a stop/start of the feps service. Sometimes after a number of changes have been made, even if you get a window that states the feps services will be automatically restarted, a manual stop/start as...

Sorry, I'm only familiar with the SIP config when interoping with another BCM or CS1000. However, if I were in your shoes I'd consult the "task based guide" for BCM50 3.0, under IP Telephony. If you've not seen these before, you'll see that they put specific tasked into one fast, easy manual...

You can't manually start the gateway,it will change to running once the service is up and working. The config depends upon what you are connecting to via SIP. Another BCM? A CS1000? Something else?

Maybe H245 Tunneling mismatch...? All I can offer is what causes this exact issue when interoping CMME with BCM. Maybe it will turn out to be the same when interoping with CS1000. By default, all Cisco equipment (CCM and Routers) have H245 Tunneling enabled. BCM/SRG have this disabled by...

Unfortunatey, there is no way to convert the backup files on a 3.x system which has always been a bit of problem for people. In BCM50 and BCM 4.0 you can backup the system AND download all of the configuration into a readable html file.

Well, if the task was simply replacing a hard drive then telephony would not need to be restored since the programming is located on the MSC. However if telephony is defaulted - for whatever reason - as seems to be the case here - then that is clearly the purpose of having a telephony backup.

At the risk of sounding ridiculous - there IS a simple fix for the 3.7 upgrade being stalled at 78%. Unfortunately, I can't recall the exact fix action nor can I find a cheat-sheet on my PC. If you have access to Nortel solutions database, there is definitly a solution with a fix action. I...