Mitel Teleworker V5.1.11.0. Hickups during calls

[Miteltechuser]

We are using the Mitel Telewoker Solution for som time now, but the Mitel local Support does not have offered a solution to the next 2 problems:

1.When calling external (TW<>customer) or internal (TW-loc1<>TW-loc2) we experience hickups during the calls.
Like a dead line for about 1,2 seconds whereafter the line is coming back up.

2.If no hickups, a slight delay of speech is experienced. Mitel suggested to turn on local streaming on all phones.
This helped a bit when calling external (TW<>Customer), but not for internal calls (TWloc1<>TWloc2).

Does anyone have a solution or experiencing the same?

Mitel Teleworker server located behind SDSL 2,3Mb 1:1.
TW locations behind ADSL 2Mb/512kb 1:50.
QoS not configured

 

[UncleRalph]

When you say "dead line" does that mean just no audio or the display goes out or both?
I'm acutally suprised that the local streaming helped for external calls but not TW to TW since it's specifically supposed to affect only TW to TW.

What version of TW are you running? Same question for the 3300.

Is it running is server gateway mode or server only.

Ralph

 

[bobcheese]

the twloc1 & tw loc 2 different locations or same site? do you have compression switched on or off?

 

[Miteltechuser]

Hi, thx 4 the reply.

Dead line means just no sound like disconnected, however the line comes back on after 1 second and the other caller party responds with "sorry what did you say? I lost you for a second".

You are right the streaming solved the issue for 75% between TW <> TW.

Versions:
Teleworker Solution (V5.1.11.0)
ServiceLink Mitel Standard Linux (V8.5)
ICP 3300 (7.1.5.13)

 

[Miteltechuser]

@bobscheese:

Compression was advised by MitelSupport to turn off.
TW locations 1,2 are on physical different sites. (they are travel agencies)

 

[RDECIT]

I've posted a similar question, with exactly the same problem but on MCD and the new Teleworker software (Border gateway)

Most people suggested it was a bandwidth issue, we've upgraded the router and taken additional services off the line (VPN) and things seem better.

 

[Miteltechuser]

@uncleralph


Ralph, the MBG is running in gateway mode. (just 1 NIC)

 

[Miteltechuser]

@RobEvansonCIT:

If I check the eventlog, I see a lot of exessive jitter messages.

Teleworker excessive jitter 08:00:0F:24:584 minor Fri Feb 26 10:23:27 2010 excessive jitter, 30 rtp packets queued
Teleworker excessive jitter 08:00:0F:27:AB:63 minor Fri Feb 26 10:23:27 2010 excessive jitter, 30 rtp packets queued
Teleworker excessive jitter 08:00:0F:27:A5:07 minor Fri Feb 26 10:23:27 2010 excessive jitter, 30 rtp packets queued

 

[bobcheese]

I would look at compression via 3300. Mitel would have advised to turn off compression on the teleworker server itself as this puts excessive load on the server and can cause more problems than it fixes.

However it is possible to program compression preformed by the 3300 between IP sets (internal) without the need for licenses. You need to put them in different compression zones.