Messages

1

Mitel MiVoice Business/MCD/3300 / Re: Bulk Delete Hotdesk Users

« on: November 05, 2018, 06:48:33 PM »

I am not using MiCollab currently. I would say that the percentage to be deleted is around 90%.

2

Mitel MiVoice Business/MCD/3300 / Bulk Delete Hotdesk Users

« on: November 05, 2018, 10:36:20 AM »

I have approximately 400 hotdesk users that I need to delete on a Rel8 MiVB system. Is there something I have missed or is this going to require manual deletion of each individual user?

Dale

3

Mitel MiVoice Business/MCD/3300 / Re: Teleworker calls fail on SIP outbound trunks

« on: January 31, 2018, 10:28:43 AM »

Try setting your INTERNAL call duration timer setting to maximum allowed time or make sure it is off..

Where is this setting at?

4

Mitel MiVoice Business/MCD/3300 / Re: Teleworker calls fail on SIP outbound trunks

« on: January 31, 2018, 09:03:11 AM »

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

5

Mitel MiVoice Business/MCD/3300 / Teleworker calls fail on SIP outbound trunks

« 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.

6

Mitel Software Applications / Re: Teleworker fails on IPv6

« on: January 16, 2018, 12:14:21 PM »

The set is a 5330(not 5330e) IP connecting to MCD Release 5.0 through an MBG. Is the recommendation you are providing 2 seperate possibilities (this OR that) or all in one (this AND that)? We would like to avoid having to do anything on the server side just for 1 out of 400 users. I am hoping that we can accomplish the goal with just a change on the end users side. Is this possible?

7

Mitel Software Applications / Re: Teleworker fails on IPv6

« on: January 16, 2018, 10:44:03 AM »

Okay, on the MBG side, we are strictly IPv4 and I don't think that will change any time too soon. Is there something that needs to be done on the users end so that his phone will start working again or will this no longer be an option for him?

Thanks,

8

Mitel Software Applications / Teleworker fails on IPv6

« on: January 16, 2018, 09:50:39 AM »

We are based in Santa Barbara, California with teleworkers scattered all around the world. We have 1 user in Amsterdam who has been using the same Teleworker phone for a few years now without any issues. Last month, his ISP (German Telekom) switched him over to IPv6 and now his phone no longer connects to our MBG. On our end we do not currently use IPv6 and are not sure where we should be looking to to start troubleshooting. Any help or guidance would be greatly appreciated.

Dale