Another thing to check would be the timers on the trunks as I've seen it before where a call comes in and is immediately routed back out another trunk...and the timer prevents the call. Orbital timer is one thats caused issues in the past.
http://voipdesigner.blogspot.com/
Jason Black
It is very dangerous utilizing the route ACOD as there are almost no call controls. A much better approach would be to utilize the Callpilot's RPL (restriction permission lists) to define exactly what digits are diallable for this application. Another check/balance is to program the Callpilot...
You would use either an MG1000 or MG1010 CS1000E Chassis...which is IP enabled. The fiber would be used to extend the LAN to the new location to drive a network switch where the MG1000/1010 is connected...or just use the existing network connections.
Hope that helps clear it up...
Nortel CS1000 SIP was really buggy up until around Release 5.5....good luck with getting it to run on R4.5!!! Once you get it working just don't breathe on the switch...
http://voipdesigner.blogspot.com/
Jason Black, Senior Design Specialist
I have a lot of customers who are at the cross roads of upgrading or forklifting...but what we are doing is leveraging the Nortel gear for high density Analog/Digital and then pushing for expansion with IP. IP could be either on the Nortel or Avaya side with lot's of new phones and soft clients...
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
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.