![]() ![]() ![]() |
|
dteirney: While trying to track down any potential configuration issues that might be preventing incoming DTMF tones from working I found the document from 2talk.co.nz that documents the configuration settings for the SPA112 (the ATA I'm using). http://blog.2talk.co.nz/spa122.html
Some of the settings are different to those in the provisioning file, especially around the call progress tones and ring patterns.
I doubt they have anything to do with my DTMF problem, but how important are those settings to be correct? I'm not sure whether the provisioning file is correct or the document from 2talk.
Regards,
Old3eyes
Just a quick follow-up to this thread as it is stickied to the top of the page!
First, the original post and the linked page by @sbiddle are really helpful and his original work in this area is much appreciated.
However, as I have seen from a few of his posts across this forum, the dial plan listed on his page is now outdated and doesn't allow dialing numbers to the new expanded number ranges (e.g. vodafone's expanded range and number of digits). I believe @sbiddle has suggested that a more generic call plan is a safer bet and more 'future proof'. If anyone has one that they would like to post here, that would be great!
If I find more specific information, I'll return here.
Just wanted to get a post here now to ensure any other users trying configure VOIP should know that dial plan referenced by the OP has some flaws for today's expanded number ranges.
spacedog:
Just a quick follow-up to this thread as it is stickied to the top of the page!
First, the original post and the linked page by @sbiddle are really helpful and his original work in this area is much appreciated.
However, as I have seen from a few of his posts across this forum, the dial plan listed on his page is now outdated and doesn't allow dialing numbers to the new expanded number ranges (e.g. vodafone's expanded range and number of digits). I believe @sbiddle has suggested that a more generic call plan is a safer bet and more 'future proof'. If anyone has one that they would like to post here, that would be great!
If I find more specific information, I'll return here.
Just wanted to get a post here now to ensure any other users trying configure VOIP should know that dial plan referenced by the OP has some flaws for today's expanded number ranges.
Just been on 2talks page and the Dial plan they have on there for a Linksys device is
([2-9]xxxxxx|0[34679][2-9]xxxxxx|0210xxxxxxx|021[12]xxxxxx|021[3-9]xxxxx|02[0279]xxxxxxx|0204xxxxxxx|0240xxxxxx|024[1-9]xxxxxxx|0282[4-5]xxxxxx|050xxxxxxx|070xxxxxxx|080xxxxxxx|00xxxxxxx.|01[08]|017xx|12[356]|[19]11|*55|*88|023xxxxxxxx|01[1234569]x.|02[56]x.|028[013456789]x.|0282[0123467890]|0282[01236789]|05[1-9]x.|08[1-9]x.|0[34679][0-1]x.|1[03456789]x.|11[023456789]x.|12[0124789]x.|*[012346789]x.|*5[012346789]x.)
Dont know if it is up to date with Vodafones no range but do notice it does have Skinny numbers in it.
Thanks @kfella2000. I've tested that Dial Plan and it seems to be working well now for me. I also contacted Hero and they provided the same dial plan to me. It's working fine both for my 2Degrees VoIP service and with Hero so far so I think this seems to be a good one for at least the current range of numbers. Not sure how future-proof it is or if there is a better more future proof kind of dial plan as had been suggested by @sbiddle in other posts in the year's past
I stopped changes and supporting my hosted config because at one point I was getting up to half a dozen or so people most days who were iTalk or 2talk users looking for support because they couldn't get any elsewhere.
I don't see any need for such a solution these days as everybody who's using VoIP should be using a fully auto provisioned endpoint - it's the only way to guarantee compatibility with each SIP soft switch particularly with around 30 or so settings required on a SPA112 to make it fully compatible with PTC specs and to ensure it works properly.
Yeah I totally get where you are coming from, but there are power users like myself that have to keep muddling through this as copper dies out and everything moves to VoiP.
My business has to rely on a complex blended environment of aging DSL, limited copper facility, FemtoCel's, and rural WirelessISP service. There is no integrated autoprovisioned endpoint solution to keep my business connected and running so I simply must employ SIP ATA adapters to get the extra lines we need.
And at home a FritzBox simply doesn't offer all the functions I need (or want) so I run dd-wrt. Anyways, understand your position and appreciate your help in the past @sbiddle. Your regional provisional settings still seem pretty good, too! The good news is that it does seem possible to still do what I'm doing and the dialplan above is good enough for today and, hopefully, a few more years. I'm sure I'm not the only user with unique/rural setups/deployments that has to forge on their own into the great wilderness of the 'unsupported' (and this post is for those folks).
|
![]() ![]() ![]() |