Alternate Routing fails

[drichter12]

What am I missing? Here is the scenario...

ARS Dig Dialed = 91 + 10
Route List 1

1. SIP Peer1​

2. SIP Peer2​

3. SIP Peer3​

4. SIP Peer4​

5. TDM Trunk Group1 (PRIs)​

We lost power to the SIP MBG which takes down all 4 SIP peers. This should have still left the PRIs as a viable destination but outbound calls would time-out and fail. I confirmed the PRIs were up and working and there were inbound calls on them as well as available trunks for outbound. The COR is the same for both the TDM and SIP trunks as well. Any suggestions or guidance would be appreciated.

Mitel 3300 MXe-II
MiVB 4.2 (10.2.0.26_2)

Thanks,


Dale

 

[kwbMitel]

I feel that the SIP trunks are not in fact fully out of sevice as far as the MCD is concerned

As such, the system is attempting to call out on SIP

Check the status via Maintenance Command - SIP LINK STATE ALL

If Necessary, use command SIP LINK BUSY [Peer}
**********************************************
What's most important is that you realise ... There is no spoon.

 

[drichter12]

Is there some way to tell the MCD that the SIP trunks are down when the proxy server is down or at the very least is there some way to get these calls to route alternately when the SIP peers are unresponsive?


Thanks,
Dale

 

[drichter12]

In looking through the logs, the entry below (one of many) appears to be related to the trunk failures.

[tt]
Log Type Software
Log Number 1671
Severity Warning
Date 2018/Sep/11
Time 14:51:27
Source IPSP
Description HandleDisablePort: Port found but is closed! Key=[ 747 ] DN=[ 4120 ] IP=[ 10.4.109.61 ] MAC=[ 0x8-0x0-0xF-0x74-0xB8-0xFA ]
Module Main
File Name and Line Number PortManager.cpp;1613
[/tt]



Thanks,
Dale

 

[TCSI17]

You can look at the SIP Peer Profile form, Timers tab, 'Invite Ringing Response Timer'. I seem to think the default is '0' but dont know what the actual time is that it will wait to try other routes. It's possible it will wait a full 30secs maybe and the call is just timing out before advancing to the next route?
I had this issue when I was testing resiliency on SIP Peers and it was taking too long to advance in the route list. My calls weren't failing they were just taking a while...
Not sure if this would be your issue in particular, just something to check.

 

[drichter12]

TCSI17,
That sounded promising until I looked through the peer profile and it does not appear as an option under 4.2 although it does show in one of our upgraded systems.


Thanks,
Dale

 

[kwbMitel]

Is there some way to tell the MCD that the SIP trunks are down when the proxy server is down

The command I suggested above was close but not exact.

Use SIP BUSY <Peer Name> or SIP BUSY FORCE <Peer Name>


**********************************************
What's most important is that you realise ... There is no spoon.