Long Wait for Connection when Dialing

[cjtx82]

Whenever I dial the phone, it takes up to 30 seconds for it to connect and start actually calling the remote party. I tried this out calling to my cell phone just now and it took 18 seconds. My wife has complained about it and wants to switch back to V*****, can anyone help me speed the connect time up?

I use the Linksys PAP2, SouthCentral Server, TW cable internet access.

PS My Dishnetwork connection works fine and I even get CallerID on the TV with it.

Thanks!
ChuckJ

[KLH]

Try dialing the number and pressing the # key when done.
It should instantly start ringing.

[AzAmusements]

I have this same problem and the # key does not work. When this happens, it is sometimes rings on the other end but I can not hear it. The person answers normally. But most times the duration I wait is between 11 and 30 seconds as well.

[schaf921]

I have been having the same problem. I used to hang up when I heard silence for a few seconds thinking the call isn't connecting and then call the person back and they would ask why did I just call (caller ID). Since I just heard silence - I assumed no connection but apparently it rings on their end. Now I just wait to see if someone picks up or I get VM. Its sporadic so difficult to pin down when it happens for me

[KLH]

Out of curiosity, is this happening when you call other ViaTalk customers, or is it completely random?

[rocketman]

I have been having the same problem. I used to hang up when I heard silence for a few seconds thinking the call isn't connecting and then call the person back and they would ask why did I just call (caller ID). Since I just heard silence - I assumed no connection but apparently it rings on their end. Now I just wait to see if someone picks up or I get VM. Its sporadic so difficult to pin down when it happens for me

I have the same problem. Very annoying and sporadic. I do not know any other Viatalk customers to call ... this being the #1 reason I have not recommended them to anyone else.

[f1tech]

Ditto me... I do get the silence and then the person on the other side says hello. But not always. This happens when I call landlines or people using other VoIP providers like our regional cable company or V*****.

I have ViaTalk at home and in my office and I cannot say I have had the problem when I call one from the other.

[cjtx82]

I used the # sign after the number and that definitely helped. But the first time I tried it, there was no ringing on the phone, but my cell was ringing and the first time I heard anything was my cell's voicemail.

After the first time, it worked well for 4 consecutive times.

Anyway to put a suffix on all the numbers by default?

CJ

[Lunatic]

It seems like I had that problem as well awhile back among other problems. I set my Linksys to pick up an IP from my router via DHCP and set the dns info in my router from my ISP. ALso set the Linksys to be in the DMZ. Since then my service has been perfect. No problems whatsoever. I used to use Pa****8 and they had firmware upgrades for thier VOIP device. I dont know if there are any available for the Linksys device but it may be worth looking into.
Hope this helps.
Lunatic.

[hossnine]

I've had the same problem as well. The best luck I've had for getting around it is to dial all numbers as if they are long distance (1 + area code + number) rather than just the number (867-5309).

[sbradshaw]

I used the # sign after the number and that definitely helped. But the first time I tried it, there was no ringing on the phone, but my cell was ringing and the first time I heard anything was my cell's voicemail.

After the first time, it worked well for 4 consecutive times.

Anyway to put a suffix on all the numbers by default?

CJ

You can use the # sign. But you can also set something more globally by changing the value of the Interdigit Short Timer in the ATA. It may be too high for your liking. You can reduce that value (measured in seconds) to speed up the dialing. This field controls how long the ATA waits after the last digit you enter to determine if you are done entering numbers. A word of advise: a value too low may result in a busy signal if you pause too long between entering any 2 digits (as it will think you are done entering the entire phone number...and consider it to be invalid because you did not complete the number before the ATA tried sending it off).

Personally, I have this value set at 3 seconds which works good for me.

[spamoni]

When I signed up for service, I noticed that dialing 7 or 11 digit numbers worked great. when I dialed a 10 digit number a delay would happen for 15+ seconds. Researching the problem and testing my solution worked for me.

THe problem is with the Dial Plan on the PAP. The following Dial Plan is what I sent to viatalk and asked them to make it part of my updates being sent to the PAP. Once this was done, there was no more delay.

1. You can test it: Get the password to your PAP (Viatalk will provide).
2. Connect and locate the Dial Plan
3. Add |[2-9]xx[2-9]xxxxxxS0| to the plan and save it. (You can also cut and paste the dial Plan provided below)
4. Reset the PAP and then Test.

If it works for you - send it to Viatalk for correction...

I added the following information: |[2-9]xx[2-9]xxxxxxS0| and now it looks like this:

(*xx|*xxxxxxxxx|*xxxxxxxxxxxxx|*xxx|xxx|xxxx|[3469]11|0|00|[2-9]xxxxxx|[2-9]xx[2-9]xxxxxxS0|1xxx[2-9]xxxxxxS0|xxxxxxxxxxxx.|011xxxxxxxxxx)

[Brian188]

I think we are talking about 2 different issues here in this thread.

One is the 7, 10, & 11 digit dialing. When dialing 10 digits instead of 11 there is long pause because your Pap 2 is waiting for the 11 digit, it then realizes you are done and dials out using the 10 and assuming a 1 to precede the 10 you dialed. You can change your dial plan as spamoni said or you use this one as well: (*xx|<:1AAA>[2-9]xxxxxx|1[2-9]xx[2-9]xxxxxxS0|<:1>[2-9]xx[2-9]xxxxxxS0|011xx.|1900xxxxxxx!)
Replace "AAA" with your area code. This dial plan allows for 7, 10, & 11 digit dialing, *codes such as *69, and international calling, it does not permit 900 # calling.

The other issue we are talking about here is not hearing the 'ringback' when the dialing is complete. I have heard this happen several times before, but never experienced it personally. I have heard that viatalk support is aware of this and if you open a ticket they can fix it, even if it is after a few go a rounds with their agents. Just try to be clear that it is the ringback that is the issue not that there is a delay after dialing.

[cjtx82]

The guys from Support set me up with this dial plan:

(*xx.|[3469]11S0|0|[2-9]xxxxxx|[2-9]xx[2-9]xxxxxxS0|1[2-9]xx[2-9]xxxxxxS0|011x.)

and it seems to do the trick.

I was told the plan you put out had the following problems:
(*xx|<:1972>[2-9]xxxxxx|1[2-9]xx[2-9]xxxxxxS0|<:1>[2-9]xx[2-9]xxxxxxS0|011xx.|1900xxxxxxx!)
will NOT allow you to dial 911 as a valid number, nor access *123 voicemail or *400 call broadcast, 411, or 0 to connect to an operator.

I don't know enough to tell the difference, but I thought I would pass that along to y'all!

They also fixed my MWI indicator that was a question on another thread!

Thanks for your help!
CJ

[Brian188]

Not sure about all of that, but I am able to dial 411, *123, and 0. I don't use broadcast, and I'll have to look into 911. Thanks for the heads up.

[spamoni]

As with Brian188, the Dial Plan I put out there works fine for all of the options provided... *123, 411 etc. But have not tested 911. Also note, I simply took the original Dial Plan provided by VT and added the 10 digit option

[littleminx]

okay but what about ViaTalk for Dummies;
as in what is an ATA and a PAP and how do i get to them to fix it?

[KLH]

An ATA is an Analog Telephone Adapter
A PAP is, um, well, I'm not sure what it is abbreviated for, but it is an Analog Telephone Adapter that ViaTalk uses made by Liksys.

To get them to fix it, just submit a ticket.

[littleminx]

thank you :)

confesses to remembering when telephones had party lines, rotary dials, and cords to the handset... ;)

[kyler13]

I had this similar problem, but noticed the interdigit short timer was set to 3. I counted my delay after dialing 10 digit numbers to be about 10 seconds. The interdigit long timer was set to 10. I set this down to 5 and voila it's only about 5 seconds now before it starts ringing.

[littleminx]

how would i go about doing this?

thanx :)

[littleminx]

oops sorry double posted somehow.

[kyler13]

how would i go about doing this?

thanx :)

Get your admin credentials from Viatalk by submitting a ticket. Pull up your ATA settings page by punching the router assigned IP into your web browser. Along the top you should see admin login. Do that. Also, switch to advanced view. Click on the Regional tab, and about half way down is the section called Control Timer Values (sec). "Interdigit long timer" is in there. My default was "10" and I tried "5" with success. Whatever you change it to, do "Save settings" at the bottom. That'll reboot your ATA. Then try dialing a 10 digit number and you should notice the shorter delay from last number dialed to ring. You can play with this time, but it'll eventually get set back to the default via provisioning, so if you find a value you like, submit a ticket asking tech support to permanently change. I'm not sure about the function of "interdigit short timer".

[kyler13]

Just found this:


Interdigit Long Timer: It specifies the default maximum time (in seconds) allowed
between dialed digits, when no candidate digit sequence is as yet complete. While,
Interdigit Short Timer specifies the default maximum time (in seconds) allowed
between dialed digits, when at least one candidate digit sequence is complete as dialed.


I interpret this as the long timer being applied during the entry of the first 6 digits, and the short timer thereafter. Oddly, I get the long timer delay when I dial 10 digits. Seems like a bug.

[littleminx]

Thank you! :)

[MagillaDKE]

When I signed up for service, I noticed that dialing 7 or 11 digit numbers worked great. when I dialed a 10 digit number a delay would happen for 15+ seconds. Researching the problem and testing my solution worked for me.

THe problem is with the Dial Plan on the PAP. The following Dial Plan is what I sent to viatalk and asked them to make it part of my updates being sent to the PAP. Once this was done, there was no more delay.

1. You can test it: Get the password to your PAP (Viatalk will provide).
2. Connect and locate the Dial Plan
3. Add |[2-9]xx[2-9]xxxxxxS0| to the plan and save it. (You can also cut and paste the dial Plan provided below)
4. Reset the PAP and then Test.

If it works for you - send it to Viatalk for correction...

I added the following information: |[2-9]xx[2-9]xxxxxxS0| and now it looks like this:

(*xx|*xxxxxxxxx|*xxxxxxxxxxxxx|*xxx|xxx|xxxx|[3469]11|0|00|[2-9]xxxxxx|[2-9]xx[2-9]xxxxxxS0|1xxx[2-9]xxxxxxS0|xxxxxxxxxxxx.|011xxxxxxxxxx)

Based off my understanding of the plans. People who don't have 7 digit dialing should be able to get rid of "[2-9]xxxxxx|" in their dialing plans. I know my parents still have 7 digit dialing, but in my area we don't.

[hrtanya]

how would i go about doing this?

thanx :)

You can simply submit a support ticket requesting that we lower the Interdigit Long Timer.

[hrtanya]

Get your admin credentials from Viatalk by submitting a ticket. Pull up your ATA settings page by punching the router assigned IP into your web browser. Along the top you should see admin login. Do that. Also, switch to advanced view. Click on the Regional tab, and about half way down is the section called Control Timer Values (sec). "Interdigit long timer" is in there. My default was "10" and I tried "5" with success. Whatever you change it to, do "Save settings" at the bottom. That'll reboot your ATA. Then try dialing a 10 digit number and you should notice the shorter delay from last number dialed to ring. You can play with this time, but it'll eventually get set back to the default via provisioning, so if you find a value you like, submit a ticket asking tech support to permanently change. I'm not sure about the function of "interdigit short timer".

The Long Timer is the amount of time between you dialing the number and when the call is sent. If you take longer than 10 seconds to enter in the 7,10 or 11 digit number the call would go to a Busy signal.

The Short Timer is the amount of time between each digit you enter. If you take longer than 3 seconds between each digit the call would go to a Busy signal.

[Brian188]

The Long Timer is the amount of time between you dialing the number and when the call is sent. If you take longer than 10 seconds to enter in the 7,10 or 11 digit number the call would go to a Busy signal.

The Short Timer is the amount of time between each digit you enter. If you take longer than 3 seconds between each digit the call would go to a Busy signal.

That's not entirely correct.

The long timer is the amount of time the ATA waits before dialing if NO string in the dial plan is met.

The short timer is the amount of time the ATA waits before dialing if a string in the dial plan IS met.

For instance, lets assume my dial plan is only 1xx[2-9]xxxxxx

If I dial 555-1212 the adapter will wait 10 sec (interdigit long timer) before sending.

If I dial 1-555-555-1212 the adapter will wait 3 sec. (interdigit short timer) before it dials.

Dial plans can be further manipulated to include a specific setting for each timer. For instance if my DP was 1xx[2-9]xxxxxxS0 when I dial 11 digits starting with a 1 the short timer is set to 0 (that's what the S0 is) and the adapter would not wait at all to dial. [S=Short Timer, 0= Zero sec. - L= Long timer - T=Initial Timeout]

By the way I am speaking about Linksys PAP2 models, and Cisco SPA models only.

[MagillaDKE]

Why are so many dial plans different? Wouldn't the same functionality be on each dialplan?

I know some of them are "optimized" for speed dialing (I don't use it), but just curious. I've read a ton of threads regarding different dialplans as well as bothered sbradshaw directly a few times.

Thanks.

Can someone post their current PAP2T (or PAP2) dial plan from ViaTalk? I'm just curious.

[Brian188]

Why are so many dial plans different? Wouldn't the same functionality be on each dialplan?

I know some of them are "optimized" for speed dialing (I don't use it), but just curious. I've read a ton of threads regarding different dialplans as well as bothered sbradshaw directly a few times.

Thanks.

Can someone post their current PAP2T (or PAP2) dial plan from ViaTalk? I'm just curious.

There are so many things you can do with a DP. that why you will see so many different ones. You can set up speed dialing as you said, short cuts, IP dialing, etc. You are really only limited by your imagination and the 400+ character limit of the field. Having said that this is my DP:

(*xx|*xx.|[49]11S0|0|00|<:AREACODE>[2-9]xxxxxxS1|[2-9]xx[2-9]xxxxxxS1|1[2-9]xx[2-9]xxxxxxS0|011x.|1900xxxxxxx!|<611:18666267150>S0|<511:LOCALNUMBER>S0|<811:LOCALNUMBER>S0)

This allow for *code dialing (*69, *72, *400, etc.), 4 and 911 dialing though VT, operator, and int'l operator, 7, 10, & 11 digit dialing, international dialing, dialing 611 for VT, dialing 511 for road conditions, dialing 811 for call before you dig, and it disallows 1-900 numbers.

There is a lot more I could do with this DP but choose not to. As I said there is so much you can do, that is why you'll see people doing different things, to suit their calling patterns.

[bubbanc]

What if I have my dial plan setup correctly, I try to call someone and it never rings and nobody answers. Hang up, try to call again, it rings and someone answers.

[Brian188]

What if I have my dial plan setup correctly, I try to call someone and it never rings and nobody answers. Hang up, try to call again, it rings and someone answers.

Sounds like a NAT or firewall problem. Is the adapter in the DMZ, or ports forwarded? If so, how often does the adapter register?