Like the subject says - do you have a 10+ second delay when dialing a 7 digit telephone number?
Printable View
Like the subject says - do you have a 10+ second delay when dialing a 7 digit telephone number?
Just tried. PAP2T - 28 seconds. Second try was 33 seconds.
Got a delay? Please send support@voipo.com a traceroute to your SIP server.
Possibly a dial string issue for those who are having this problem.
VOIPoDylan,
Will do. How do I determine what my SIP server is? I looked in vPanel and on the PAP2T and do not see anything.
Ticket JMW-878775
I used to have an issue, but not anymore. I have a 502.
Totally a 7 digit dialing issue. Workaround for me was (as I worked with the voipo team months ago to get resolved) to dial the 7 digits, then #. Call goes right through. Using GS 502, NATed behind WRT54g w/ Tomato 1.23.
Best Voip quality service I have ever seen -- last 5 weeks have been tough though.
-bird
This is one feature I like with the grandstreams: if the SIP server supports 484 responses ("Incomplete Address"), the grandstream can be set to use the Early Dial feature, whereby every digit pressed results in sending an invite to the SIP server with the number collected so far. If the SIP server sends back a 484, the GS will keep collecting digits until it gets a success or failure response. This is nice since it doesn't require dialplan juju in the ATA and dialing 7 digits works instantly :) I have my asterisk server set up this way.
1bird2,
IMHO, that is 8 digit dialing. If they advertise 7 digit dialing, then it should work in a reasonable manner. A couple of seconds delay is no biggie, but 30 seconds seems silly.
I will update here with the outcome after they work on my ticket.
The only post dial delay I have is if I dial a 7 digit number.
Since we have multiple NPAs in our area, we never dial 7 digits. Just a learned habit.
Besides, everything works so well, I would not want to change anything.
Depending on the box you are using, there are dial plans that will virtually eliminate those delays.
I have the ten second delay and using a GS 502, but I thought that was normal. I can easily cut the delay down considerably by dialing a # after the 7 digits.
I really have not noticed this as we have many area codes in my city, so i always just dial the 10 digit. But when trying there is a slight delay. Adding a 7 digit dialing plan to the overall dialing plan does fix this issue as others have stated.
the latter. you dial a number, and it is N seconds until you hear ringback.
I don't know what a DTMF is, but I'm talking about the silence between hitting the last number and hearing the ring.
dtmf are the touch tones.
I am not saying that adding a # to the end of 7 digits is 7 digit dialing. I am saying two things:
1. This is a workaround to shorten the time one hears ringback tone from the time one dials the last digit of 7 digits + #. Again, this is a workaround.
2. Opening a support ticket with a description of this problem will be resolved by the support team -- I do not have to perform this 7 digit dial + # anymore.
Hope that clarifies my post.
Hope this helps!!!
-bird
Support re-provisioned my PAP2T just had me reboot. The delay now is down to 10 seconds. What should it be? I would prefer 3 or 4 seconds.
Edit: Support just changed it to be 4-5 seconds. For future reference, Brandon said he changed the "interdigit short timer & dial plan".
Delay (with 7 digit dialing) is about 10 seconds. That said, I'm pretty conditioned to 10 digit dialing, so it's not really an issue. However, it's good to know that the dialing rules can be adjusted.
Thought I'd update to note that only *some* 7 digit calls take that long. For grins, I called my cell phone this morning, and it only took 5 seconds from last digit to ring. *shrug*
It's about five seconds for me on the Linksys.
Update: I had to have Brandon add 1 or 2 seconds back into my delay, since my fax machine wants a nice long dial-tone before it starts dialing. If it is too short, it gets a busy signal before the dialing starts. Oye!