Yealink T46 delayed outbound dialing

[Doberman_Tech]

Hey guys need some help with this one. Client is annoyed with a 14 second delay when dialing out. I have went through the entire system including the patton 4114 and tried tightening up the time before it dials out and also turned on live dial on the yealinks in the web GUI. At this point I have got it down to about 11 seconds before they hear ringing. Any other options I can change on this or am I stuck since it is using POTS?

 

[leejor]

Have you determined where the delay occurs using the Activity Log? Usually, with a PSTN gateway, immediately after DTMF has been sent, audio is cut through, and progress tones should be heard. Is the gateway connected to lines from a central office, or a "box" (ATA) supplied by a VoIP company?

 

[AramS_3CX]

Hey guys need some help with this one. Client is annoyed with a 14 second delay when dialing out. I have went through the entire system including the patton 4114 and tried tightening up the time before it dials out and also turned on live dial on the yealinks in the web GUI. At this point I have got it down to about 11 seconds before they hear ringing. Any other options I can change on this or am I stuck since it is using POTS?

Hi Doberman_Tech,
We tried to reproduce your problem using the same environment that you have, but without success.
In our case it takes 2-3 seconds before we hear the ringing.
Does the phones and Patton GW are provisioned using the 3CX default templates?
Do you have the latest supported version installed on the phones?
If so, I agree with leejor, try to determine where the delay occurs using the Activity Log. You need to check when SIP Ringing message comes from Patton to PBX and when it's send from PBX to the Yealink phone. This will show you where is the delay.
If you will see that the delay is coming from the Patton GW, you need to contact to the PSTN service provider of that customer and check the analog line settings.

 

[Doberman_Tech]

Hi Doberman_Tech,
We tried to reproduce your problem using the same environment that you have, but without success.
In our case it takes 2-3 seconds before we hear the ringing.
Does the phones and Patton GW are provisioned using the 3CX default templates?
Do you have the latest supported version installed on the phones?
If so, I agree with leejor, try to determine where the delay occurs using the Activity Log. You need to check when SIP Ringing message comes from Patton to PBX and when it's send from PBX to the Yealink phone. This will show you where is the delay.
If you will see that the delay is coming from the Patton GW, you need to contact to the PSTN service provider of that customer and check the analog line settings.

The phones and the gateway are provisioned with the default templates and the phones are on current firmware 28.83.0.20. I did check the call logs as I turned on verbose logging and from what I can see the logging shows calling at 2:11:36 and I get the sendmsg at 2:11:42

What the clent is describing though is from the time they stop dialing its about 4-5 seconds before the call timer starts on the phone then about 5 seconds into the call timer being live then they hear ringing.

 

[leejor]

from what I can see the logging shows calling at 2:11:36 and I get the sendmsg at 2:11:42

So 2:11:36 is when the Invite was sent to 3CX? If so, at what time was the last digit dialled? Do the phones have an internal dialplan, or does the customer hit an end of dial-string key, to override any delay, while the set awaits additional digits?

The sendmsg is when the call is passed to the gateway? At what point after sending the Invite to the gateway is there a response? Which one? At that point (usually), audio is cut through, and the caller is awaiting ringback/busy/recording from the provider.

You didn't say if the gateway is connected to an ATA, or central office line equipment. Have you tried using an analogue set, on one of the PSTN lines, to see if there is any delay?

 

[YiannisH_3CX]

You could also try running a wireshark capture on the PBX to see the SIP messages and the time it takes the phone to send the Invite to the PBX and the PBX to the Patton device.

 

[Doberman_Tech]

So 2:11:36 is when the Invite was sent to 3CX? If so, at what time was the last digit dialled? Do the phones have an internal dialplan, or does the customer hit an end of dial-string key, to override any delay, while the set awaits additional digits?

The sendmsg is when the call is passed to the gateway? At what point after sending the Invite to the gateway is there a response? Which one? At that point (usually), audio is cut through, and the caller is awaiting ringback/busy/recording from the provider.

You didn't say if the gateway is connected to an ATA, or central office line equipment. Have you tried using an analogue set, on one of the PSTN lines, to see if there is any delay?

So it looks like the last digit was sent out at 2:11:36 and the the next time stamp for even the handoff was 2:11:42 based on the 3cx logs. The phones do not have an internal dial plan setup currently. They do have the default wait 4 seconds before timeout and dialing. I have tried adjusting that down but then they do not like the fact that if they hesitate it will just dial out.

The gateway is connected to a comcast modem that is handing out 2 fxs lines. I have not yet tried an analog phone off of one of them.

 

[leejor]

Do the sets have an "end of dial" key to speed up sending the digits? Reducing the time out isn't always a good idea, as, any hesitation will usually result in incorrect digits being sent.

The fact that the lines go into a Comcast ATA, may explain part of the delay, as it may have a time out to await all of the dialled digits.

 

[Doberman_Tech]

Okay so after doing some extensive testing If I dial direct off the Comcast ATA its about 5 seconds and the call connects. If I test direct off the desk phone it takes about 5 seconds for the ">>>>>>" to change to a timer. then after 5 seconds on the timer it then rings. When I did the above test I dialed the number and hit "send" on the phone. It doesn't seem to make much of a difference versus picking up the phone and dialing. Anyone have suggestions?

 

[leejor]

So what I'm hearing, is that the Comcast ATA is adding 5 seconds before you hear ringing, when a phone connected to a 'normal" PSTN line equipment should have ringing almost immediately after the last digit is pressed.

The other slight delay, that is going to happen, is when the gateway outpulses the DTMF to the Comcast ATA. In some cases that time can be shortened (risking the sending of unrecognised digits, in some cases), with a setting in the gateway. That delay can take 2 to 3 seconds, or even longer.

You might want to ask Comcast, if there is a setting, that they can change, to shorten that 5 second wait.

 

[cobaltit]

I've had the same issue with Comcast. We originally did an install using a Grandstream ATA and then after much fussing we switched to a Patton in hopes it would resolve the delay and still no go. The delay is not something Comcast can or cares to fix.

 

[Doberman_Tech]

I've had the same issue with Comcast. We originally did an install using a Grandstream ATA and then after much fussing we switched to a Patton in hopes it would resolve the delay and still no go. The delay is not something Comcast can or cares to fix.

So basically even if I call Comcast they won't do an thing with the delay?

 

[leejor]

The gateway is adding an additional delay, in your case. Comcast probably considers the 5 second delay it's ATA adds "acceptable", for the majority of it's customers which do not use a PBX and gateway (which makes the delay even greater).

It's not going to hurt to ask (the answer is automatically "NO", if you don't), but I would not hold my breath.

Have you considered going to VoIP trunking? You could add a second trunk group while leaving the Comcast trunks in place, even if you just used them for incoming, until moving over completely.