Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MCDN and MW lamp

Status
Not open for further replies.

vztech

Programmer
Jun 19, 2003
1,127
US
I networked 6 BCM 50's and 1- 400 (MCDN) all worked fine.
Now one location has lost the ability to get a message waiting indicator.
SIP trunking.
checked the target lines MWSET is checked.
This is what I get from the BCM monitor (at the remote end)when it tries to light the lamp.

No translation for address of such nature
Null facility reject

Looks like it tries to light the lamp on the far end but gets rejected.

Router issue maybe ? No data traffic is on this yet.



It's only dialtone-VZ
 
I thought the same thing but it's there.


It's only dialtone-VZ
 
yes
I'm going to try to reboot the main BCM.

It's only dialtone-VZ
 
reboot didn't work now another site is being effected.
anyone having this issue with SIP trunking ?

It's only dialtone-VZ
 

What release are your Bcm50's?
Have you tried rebooting one of the affected bcm50's?
 
Found out it was the uri under sip settings not matching with the far end.

unknownunknown,private.e135 etc.
The centralized vmail side had nothing.

Still strange it affected only one location.

It's only dialtone-VZ
 

Did you have to modify the Bcm50 or the Bcm400 side?
 
BCM 400 had no URI mapping at all. So I input all those.

on the BCM 50 sides I just added the :unknownunknown

Funny -it only effected 1 of the 50's the other 5 worked fine.

It's only dialtone-VZ
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top