Mitel Forums - The Unofficial Source
Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: drichter012 on January 30, 2018, 10:14:16 AM
-
System Summary:
MBG V6.1.10.0 used for SIP and Teleworker (5330 IP sets)
Mitel 3300 ICP - MXe-III on MCD 5.0 SP1 PR1
AT&T Flex Reach SIP Service
All equipment listed above is on the same subnet internally.
Reported Issue:
Calls fail (drop) at 30 minutes.
Testing Reveals:
a.) Calls appear to fail at 30 minutes with a static crackle and loss of voice audio that continues until disconnected manually when placed from teleworker sets programmed through MBG above on ICP above onto outbound SIP trunks above.
b.) When said calls are placed on hold and then retrieved, audio is restored and they are fine for another 30 minutes.
c.) When calls are re-directed to another ICP via xnet trunk and then sent back to this ICP via xnet trunk and out the SIP trunks above, the call does not fail.
d.) Calls do not fail if the Teleworker is connected through a different MBG at another location but still programmed on the ICP above in the same scenario.
Summary:
Calls only appear to fail or get "garbled" when the call is a Teleworker set routing to the above ICP and then directly to the SIP trunks. If the call is "manipulated" to appear as an xnet call out the same SIP trunks, no issues arise. We have calls from many other ICPs in the cluster (including the above) as well as another Teleworker server at another location using these SIP trunks as their PSTN outbound access point without any issues. The only calls we see issues on are the ones coming through the above mentioned MBG to the above mentioned ICP and directly out the above mentioned SIP trunks.
-
I have a similar issue where the call goes one way audio after 12 minutes
If you put the call on hold and back again the audio is restored
so far i have figured out the the time is from the session timer in the peer (1440sec =24min)
I have the session refresh timer set at 50% = 12 miinutes
We have increased the timer to 1800 sec (30 minutes) and the issue happens at 15 minutes
So the quick fix is to max out the timer at 9999 and set the refresh percentage to 99%
or set timer to 0
You will risk having stale sip session build up if you set the timer to 0
Could work around this with a weekly/monthly reboot schedule
Let me know how you get on
-
I have a similar issue where the call goes one way audio after 12 minutes
If you put the call on hold and back again the audio is restored
so far i have figured out the the time is from the session timer in the peer (1440sec =24min)
I have the session refresh timer set at 50% = 12 miinutes
We have increased the timer to 1800 sec (30 minutes) and the issue happens at 15 minutes
So the quick fix is to max out the timer at 9999 and set the refresh percentage to 99%
or set timer to 0
You will risk having stale sip session build up if you set the timer to 0
Could work around this with a weekly/monthly reboot schedule
Let me know how you get on
Here is the current timer page in the peer. It does not appear to me that this is where the problem lies unless I'm looking in the wrong place.
Keep-Alive (OPTIONS) Period 120
Registration Period 3600
Registration Period Refresh (%) 50
Registration Maximum Timeout 90
Session Timer 0
Subscription Period 3600
Subscription Period Minimum 300
Subscription Period Refresh (%) 80
Invite Ringing Response Timer 0
Dale
-
Try setting your INTERNAL call duration timer setting to maximum allowed time or make sure it is off..
-
Try setting your INTERNAL call duration timer setting to maximum allowed time or make sure it is off..
Where is this setting at?
-
COS setting under call duration. Check your trunks COS as well.
-
I have a similar issue where the call goes one way audio after 12 minutes
If you put the call on hold and back again the audio is restored
so far i have figured out the the time is from the session timer in the peer (1440sec =24min)
I have the session refresh timer set at 50% = 12 miinutes
We have increased the timer to 1800 sec (30 minutes) and the issue happens at 15 minutes
So the quick fix is to max out the timer at 9999 and set the refresh percentage to 99%
or set timer to 0
You will risk having stale sip session build up if you set the timer to 0
Could work around this with a weekly/monthly reboot schedule
Let me know how you get on
Here is the current timer page in the peer. It does not appear to me that this is where the problem lies unless I'm looking in the wrong place.
Keep-Alive (OPTIONS) Period 120
Registration Period 3600
Registration Period Refresh (%) 50
Registration Maximum Timeout 90
Session Timer 0
Subscription Period 3600
Subscription Period Minimum 300
Subscription Period Refresh (%) 80
Invite Ringing Response Timer 0
Dale
Yep session timer already set to 0 so not that.
Good luck