Nortel Signaling Server/SIP Trunks

[pbxter]

I have a Nortel M81C at the main facility and have a BCM 450 at a remote location with SIP trunking between the two systems. I have an itermittent problem that will cause the link between the 81C and the BCM 450 to stop functioning. Sometimes this will make all of the Nortel IP phones stop working (they have "forwarding" displayed on their screens)as well. The only way to restore the link and the IP phones is to reboot the signaling server.

When the issue arises, I can ping the elan and clan of the Signaling server, but I am unable to ping the Node ID. I check the network switch that the PBX and peripherals are connected to, and I don't find any problems there. Any idea where I should start troubleshooting? The vendor can't seem to figure it out.

 

[spanton]

what release are you currently running?

 

[pbxter]

I am running release 4.5

 

[KCFLHRC]

There is no CLAN on the Signal server, only a ELAN and TLAN. If you cant ping the node IP during this outage sounds like your SS may be shooting craps. Is it an ISP 1100 SS?

 

[pbxter]

It is an ISP 1100.

 

[mugen112]

It's possible that you have a routing loop which when the DN in question gets called consumes all SIP channels. If the condition occurs again I would stat the SIP trunk route to see if all channels are busy...

http://voipdesigner.blogspot.com/

Jason Black, Senior Design Specialist

 

[NZNewbie]

pbxter...

I have the same problem SIP on 4.5 to multiple sites but only one site effected. Only differance it that our problem is on a OPT11 Branch Office.

What we have picked up is another device trying to log in with either the TLAN IP or the NODE IP address. We are changing these IP addresses this friday to see what happenes. Will hopefully remember to post results

 

[NZNewbie]

OK Changing TLAN and NODE IP Addresses didnt work... looked good for 3Hrs during bussiness hours then crashed again same problem as you.

1. Can ping Elan / Tlan
2. Cant Ping Node IP
3. Cant access SIP
4. No build up alarms as a matter of fact there are no alarms at all unti it fails then all I get are PRI241 /PRI226 alarms
5. Cant log into Sig Server by WEB
6. Only resolution is reboot sig server

We have swapped Sig Servers. MC32. Cables. Isolated ELAN. Patched. Unpatched. Repatched.

Running 4.5 and was working great before earthquake.

 

[pbxter]

I did realize that the dhcp scope that I had set up for the tlan included the whole subnet. I created exclusions for the node ip, the two signaling servers, and the gateway card for the pbx. Just grasping for straws at the moment.