Learning about ..... dial plans!
ianobi:
I won’t try to address all of your issues in this post as some more facts are needed.
Crucial to to how OBi digit maps work, is knowing the following setting:
Physical Interfaces -> PHONE Port -> PrimaryLine
Default for an OBi110 is “PSTN Line”. Primary Line is the service you can use without any ** codes. You may well have changed it when you set up your service providers, which is fine, but we need to know.
I would set your Phone Port DigitMap to this:
Physical Interfaces > PHONE Port > DigitMap:
([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|000|**0|***|#|**1(Msp1)|**2(Msp2)|**8(Mli)|**9(Mpp)|(Mpli))
“000” is needed here to make it a special case. When you dial “000” it will go out to PSTN via the Phone Port OutboundCallRoute with no need to reference any other digit maps.
Msp1 and Msp2 are referenced within the Phone Port DigitMap, so probably do not need to be added. If you made your Primary Line “SP1 Service”, then (Mpli) is automatically replaced by (Msp1).
If you can find your local OBi web page, then look at Status > Call History. This will show what you dialled and where the call was routed for each call. The web page is normally found by dialling ***1, but not in this case! The ip address can be found in “System Status” if you go in via the OBi Dashboard, follow prompts to Expert Configuration.
I cannot see why 775 does not work, but maybe Call History will shed some light on that.
Here’s some more homework :)
http://www.obitalk.com/forum/index.php?topic=513.msg3001#msg3001
Only read the first post in that thread!
Edit: I just noticed that you say that sp1 is the Primary Line. I must read more carefully!!
ianobi:
OK, so I had some time between watching the cricket (IPL). Pom here, I know an Aussie will understand :D So here's my attempt at a dial plan for you:
Physical Interfaces > PHONE Port > PrimaryLine: SP1 Service
Voice Service > Auto Attendant > PrimaryLine: SP1 Service
Service Providers > ITSP Profile A > General > DigitMap:
(<**2>775S4|<**2>x.8888888|<02>[2-9]xxxxxxx|0[2-9]xxxxxxxx|0011xx.|1[258]1|000|18xxx.|13xxx.)
Service Providers > ITSP Profile B > General > DigitMap:
(<02>[2-9]xxxxxxx|0[2-9]xxxxxxxx|0011xx.|775S4|000|18xxx.|13xxx.)
Physical Interfaces > PHONE Port > DigitMap:
([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|000|**0|***|#|**1(Msp1)|**2(Msp2)|**8(Mli)|**9(Mpp)|(Mpli))
Physical Interfaces > PHONE Port > OutboundCallRoute:
{([1-9]x?*(Mpli)):pp},{(<#:>|000):li},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}
Notes:
18xxx. & 13xxx. lengthened to prevent clashes with three-digit numbers.
<**2>775S4 This uses your Primary Line to redirect 775 to sp2 by prepending **2 to 775. The S4 adds a four second delay to prevent clashing with someone dialling a longer number that starts 775. If no other numbers start 775, then the S4 is not needed.
<**2>x.8888888 To be honest, I did not really understand what this is for, but it redirects to sp2 the same way as 775.
000 goes directly to PSTN.
Using the Primary Line to do the redirecting means that the Phone Port DigitMap and OutboundCallRoutes can be left at default, except for the 911 to 000 change in your case. If you wish to dial 000 via sp1 or sp2 you will need to dial **1000 or **2000. OBi devices to not provide "fail over". If the PSTN line fails, then dialling 000 will result in "no service available" message. Automatic failover can be achieved in some circumstances using trunk groups, but that's way too complex for this post!
In your posts the digit maps etc had a lot of spaces in them. They are best avoided as they can cause problems.
Let me know how it goes. Feel free to question or complain if my dial plan does not work :)
Colic:
Thanks for the reply - let me comment with my thoughts so they can be corrected and I can learn more!
Quote from: ianobi on April 17, 2013, 08:04:21 am
I would set your Phone Port DigitMap to this:
Physical Interfaces > PHONE Port > DigitMap:
([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|000|**0|***|#|**1(Msp1)|**2(Msp2)|**8(Mli)|**9(Mpp)|(Mpli))
I had ultimately intended SP1 to take most calls, but SP2 (lower quality but cheaper) to take special numbers (1300 etc). So Im thinking if I only reference Mpli (ie Sp1) and Msp1 doesnt contain those numbers, then this digimap will fail to recognise them. Or should I make both Msp1 and 2 the same and reply on the outbound call routing to do that for me?
Quote
“000” is needed here to make it a special case. When you dial “000” it will go out to PSTN via the Phone Port OutboundCallRoute with no need to reference any other digit maps.
But Assuming the outbound call route directs it to PSTN, right?
Quote
I cannot see why 775 does not work, but maybe Call History will shed some light on that.
Yes Im in to call history (not via ***1 yet!) but it tells me little more except the call number was 775, it was routed to sp2 but gave an error "End Call (400 Bad Request(Bad Content-Length (larger than datagram)))." The same digit sequence to the same SP on my Android connects every time.. Hmmm.
Quote
Here’s some more homework :)
http://www.obitalk.com/forum/index.php?topic=513.msg3001#msg3001
Only read the first post in that thread!
I was a bad boy and started reading the rest, then thought better of it! I should probably stay clear of this until I get the basics, but if I get that inital post right, you are saying that if my phone port digitmap were to only say {nn.} and my phone outbound call route only said {1234:sp1} , and the sp1 digitmap only said {5678} then when I dial 1234 the call would be connected?
How do I reach that bizarre conclusion - well from myh interpretation of your comment
Quote
In reality, the ITSPA, ITSPB, LINE, and OBiTALK DigitMaps only come into play because they're actually part of the PHONE Port DigitMap through indirect references: (Msp1), (Msp2), (Mli), (Mpp), and (Mpli).
and since in my example I havent referenced any of the sp1 (or other come to that) digitmaps, then the Phone port digitmaps do not come into play. If I have understood you correctly.
Colic:
Quote
OK, so I had some time between watching the cricket (IPL). Pom here, I know an Aussie will understand
[\quote]
Funnily enough, I originated from the Mother Country 20 or so yeas ago, so I find it convenient to take whichever side fits the moment!! But I digress .....
Quote
18xxx. & 13xxx. lengthened to prevent clashes with three-digit numbers.
Lesson #1 learned :)
Quote
<**2>775S4 This uses your Primary Line to redirect 775 to sp2 by prepending **2 to 775.
Ah right, yes that makes sense thanks.
Quote
<**2>x.8888888 To be honest, I did not really understand what this is for, but it redirects to sp2 the same way as 775.
Yes, well it was supposed to be for testing with two SPs, but now I understand more it isnt needed, and didnt make much sense (it did at the time!), so youre right to be confused.
Re spaces, I made the mistake of reading the manual (It may contain extra white spaces for readability), but you cant beat practical experience! Thanks.
Onwards I go - I need to sort this 775 next, then I might be back!!
=============================
.. I am back! Im almost having fun now, failure of 775 (as above) was resolved by turning off ALG SIP in my router, after which the Obi correctly took its router reserved IP address which it refused to do before.
Anyway, having made great progress, Im now trying to get an incoming call to the AA to translate the number and then use auto call back as follows:
{(<**1>(0418666623)):aa($1)},{(<**1>(0294727444:0418666623)):aa},{ph}
0418666623 works, AA calls back as expected.
0294727444 does not, and goes straight to ph.
What is wrong with the above substitution? (yes the number comes in as 0294727444 but its really from 0418666623 but via a SIP who overstamps 0294727444 onto the CLID).
ianobi:
I won’t go back over all the issues in the past couple of posts as I think you have moved on. The important thing to remember with outgoing calls is that it is a two-stage process. Consider if you dial 775 from the Phone Port: In stage one the Phone Port DigitMap using this rule from (Mpli) <**2>775 prepends **2 to make the number **2775. Now in stage two **2775 is processed throught the Phone Port OutboundCallRoute and this rule {(<**2:>(Msp2)):sp2} removes the **2, matches 775 in (Msp2) and routes the call to sp2.
The Phone Port DigitMap and Phone Port OutboundCallRoute will do most of the work for you if you get the Service Providers > ITSP Profile A/B > General > DigitMap and Line Port DigitMaps right.
If you wanted to use sp2 for 13 and 18 numbers then you could change your (Mpli) by changing (Msp1) Like so:
Service Providers > ITSP Profile A > General > DigitMap:
(<**2>775S4|<02>[2-9]xxxxxxx|0[2-9]xxxxxxxx|0011xx.|1[258]1|000|<**2>18xxx.|<**2>13xxx.)
Onwards to the InboundCallRoutes:
If the incoming CallerID is 0294727444 and you want the call back to go to 0418666623 using sp1, then the correct syntax is:
{(0294727444):aa(**10418666623)},{ph}
As you want both CallerIDs to call back to number 0418666623 you could combine to this:
{(0418666623|0294727444):aa(**10418666623)},{ph}
If SP1 Service is set for the auto attendant primary line (see previous post), then you could drop the **1 as the auto attendant will use its primary line by default unless you tell it differently.
Glad to see you got the 775 problem sorted.
Navigation
[0] Message Index
[#] Next page
[*] Previous page