Dial plan explanation
SteveInWA:
Quote from: MarkObihai on April 29, 2014, 07:56:41 am
One of our OBi users in Australia has written an excellent tutorial on digit maps - "OBi Digitmaps Unravelled" - that I have attached to this post.
Thunderbird1 has been a regular contributor on the Australian Whirlpool forum in the discussion thread on the OBi202, found here:
http://forums.whirlpool.net.au/forum-replies.cfm?t=2215053
Hi Mark:
So, I looked at your link. It's a 29-page and growing thread. I gave up after reading a few of those 29 pages. The "tutorial" is a 17-page textbook. This is a good example of how incredibly complex the dial plan rules can be...endless, endless threads here, on DSLReports, and now on Whirlpool. I think there are probably less than 3-5 human beings outside of Obihai that really understand (and can explain!) how to make a simple, efficient dial plan. Having two different places in the configuration for dial plan rules that interact with each other (Phone port and Service Provider) makes it much worse.
Here is another (10-page) thread, going on for years, that just makes my head hurt.
http://www.obitalk.com/forum/index.php?topic=34.0
The "programming language" knowledge needed is just too steep. I understand that it offers powerful configuration options, but less than 10% of users need that.
Relying on the ITSPs to create optimized dial plans for their services is also a bad idea, since most of them have no clue, either.
What is really needed, is a GUI, check-the-boxes tool integrated right into the Obitalk portal, to optimize dial plans. Something similar to what RonR created and posted over on DSL reports, but built into the portal, not standalone.
Ostracus:
Ah, it's the kind of knowledge we'll need if we are ever going to conquer FTL. ;D
SteveInWA:
Adding to my comment "Relying on the ITSPs to create optimized dial plans for their services is also a bad idea, since most of them have no clue, either."
Ideally, if Obihai is going to be successful with their authorized service provider program, they should consult with each authorized SP to design an optimized dial plan for that provider as a starting point (e.g. which string reaches that SP's voicemail box, and how to handle international calls), then provide the user with the GUI check-box interface to tweak it (for example, if a user wants outbound calls or inbound calls to route to some other SP or VG, or if they want to use some other route for E911, and on and on).
No mere mortal should have to figure this out when signing up with an ITSP. Can you imagine if Comcast required you to know C++ and Ruby on Rails to set up your channel list?
Dmitry:
I have a question regarding numbering plan for international dialing and 911:
Current setup:
line 1: with GoogleVoice, used for all inbound and US domestic (including Canada) outbound calls
line 2: VoiP provider, used for outbound only for international calls.
For example, if I need to dial UK, I dial **2-011-44-xxx-yyyyyyy where **2 - second line prefix, 011 - international dialing prefix, 44 - UK country code.
I need to create numbering plan such as every dialing sequence that starts 011 will be replaced by **2011 and
if 911 dialed from Line 1, I want the call to be forwarded to predefined number (provided by gv911.com), for example, 1-222-333-4444 on line 1.
ianobi:
Assuming that sp1 is your Primary Line, then:
Service Providers > ITSP Profile A > General > DigitMap:
(<**2>011xx.S3|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*#]@@.)
If your voip provider fails, then you should still be able to force 011 calls via GV by dialling **1 before the number.
911 is best routed at a higher level, that is in the Phone Port OutboundCallRoute, then it will not be affected by any future digit map changes.
Replace any existing rule containing “911” in the Phone Port OutboundCallRoute with:
Physical Interfaces > PHONE Port > OutboundCallRoute:
... existing rules here ... ,{(<911:12223334444>):sp1}, … existing rules here …
Navigation
[0] Message Index
[#] Next page
[*] Previous page