Caller ID over Voip Trunks

[Mick23]

I have 2 bcm 400's (4.0 and 3.6) with MCDN keycodes.
They Have both been fully patched and pass the private caller id very inconsistently. Does anyone have any ideas or steps i should take in order to troubleshoot.

 

[Boomarang]

Are sets configured to receive Cid on all trunks?

 

[SupportDude]

Define inconsistently.


-SD-

http://www.mysupportguy.net

 

[Mick23]

Well as i now understand they see the extension number from the private OLI but not the name.
Anyway to make the name pass thru on the voip trunks

 

[DBrewsky]

Setup the business name on each system.

 

[SupportDude]

As DBrewsky stated ... you need the business name configured for each system. I always suggest a space as the last character of the business name or it will get smooshed together with the set name.
You also need to configure the set name and the private OLI.

Be sure that none of your Public PRI's are configured for send name. If your serving switch is a 5E, it could stop your outbound dialing.

-SD-

http://www.mysupportguy.net

 

[Executor71]

There is a chapter on your BCM 200/400 called Network configuration guide, in this document you'll find how to configure the CLID properly into a VoIP trunk or into an ISDN configuration.
Hope this will help you!

Bye

 

[Mick23]

Thanks Guys for all you help, I got it to work and actually found out that not only does the private OLI field need to be complete but the public OLI field as well.