Aooa, could you explain what the different parts of your dial plan string do?So I went back to the factory default spa2102 dial plan
and modified it to the following
I started to try dialing local and long distance #s.. what I noticed is that I do not need to dial 1 in front of long distance #s - I'm in toronto, and I'm calling BC with just the 10 digit number... why is that? If this is the case, then technically, I don't need the section 1[2-9]xx[2-9]xxxxxxS0.. right?
I gave the answer in the 1st 'code' box in post #79 above.Aooa, could you explain what the different parts of your dial plan string do?
I think it would immediately match, so 'S0' is probably redundant, but it won't do any harm to leave it there. Note that you must have e911 enabled @ voip.ms for this to be accepted.For the 911 - I notice the samples on the web doesn't add S0, is there any point in adding S0 or as soon as 911 match it will dial it right away and skip trying to match with the rest of the dial plan?
To reduce processing time (delays), it's beneficial to have the shortest, most-efficient dial plan possible. For that reason, I'd recommend using a single [2-9]xxxxxxSO, since it will automatically match to not only your local area codes, but also long-distance ones.I'm in GTA so for me, local area codes are 416, 905, 647.. other area codes would be long distance and should require a 1 in front.. based on this, is it better to individually add 416xxxxxxx, 905xxxxxxx, 647xxxxxxx or keep it generic with [2-9]xx[2-9]xxxxxx.. guess benefit with generic is to accomodate future new local area codes..
I guess so, hence I'm not completely sure why they'd extend that to xxxxxxxxxxxx. in your original dial plan.if I wanted to mimic a regular POTS line that has no restriction, would it be just (x.)?
Yes it will match both strings, but given the choice of a full match to x11 and only a partial match to the longer string, I'd expect the software to go with the full match and start dialing (string matching is about length AND character matching). However, adding 'SO' will simply force your preference - you don't want to delay those 911 calls!if I'm understanding how dial plans work correctly.. if I dial 311, 411, 611, or 911, doesn't that match both 11 and [2-9]xx[2-9]xxxxxxS0 strings?
I know there's no area code 311,411,611,911 but technically it still match the [2-9]xx part of the 2nd string and the system would wait to see if user presses the next set of digits [2-9]xxxxxx or not before dialing?
This is one of the reasons I'm leaving it in. Others being;...for the 1[2-9]xx[2-9]xxxxxxS0 - I just realized that if I take this out, then if someone else in the house who is used to dialing long distance with a 1 in front won't be allowed to dial out...
That did the trick.For some reason you can't set Caller ID Number with most ATAs; you need to set outgoing Caller ID from within "Manage Sub Accounts" (or "Account Settings" for the main account) on VoIP.ms' website.
You CAN however set Caller ID Name with your ATA.
Tried setting it to the Toronto server but it made no difference.Mot_guy,
not sure if the issue with receiving call is the same issue I had but in your voip.ms account, did you set you DID Point of Presence to the correct server? When I setup my account it was set to the US server which did not allow me to receive any calls, once I set it to the correct Toronto server, I had no problem receiving calls..
Did your device register properly? Check the Account Information page (if you're using the main account) or the Sub Accounts Diagnostic page (if you're using a sub account). It should tell you whether or not your device is registered, what sever it's registered to, and when the next registration is expected.mot_guy said:Now if I could figure out why I can place calls but not receive any.
What you tried should work. Did you enter the full 10-digit number with no punctuation? If you check the regional tab, are the Distinctive Ring Patterns all different?holymoly said:I just plunked in two numbers in Ring1Caller and Ring2Caller. Don't think it did a thing?
Yep, you sure got to keep an eye on those pesky house guests But why stop there? Why not set a password using your dial plan?!?aooa said:i guess it's a good way to prevent your house guest from calling long distance without you knowing