CircleNet would like to introduce ourselves to the Obi world
Sam_from_CircleNet:
vtsnaab,
Thanks! We always like to hear good things about ourselves ::). Also your right about Nitzan, in some ways we are competitors but I can tell he cares about his customers. Future9 is a solid company.
Sam
dial.tone:
Quote from: azrobert on April 23, 2014, 08:13:32 pm
Quote from: zorlac on April 23, 2014, 07:46:54 pm
Now I just need to figure out a plan for SP1 on the wife's line.
Unfortunately there is quite a pregnant pause (before it starts ringing) dialing out on SP2 via Circlenet & that won't fly for the wife.
See my comments here:
http://www.obitalk.com/forum/index.php?topic=7742.msg50188#msg50188
And my next post in the same thread on international calls.
Quote from: azrobert on April 20, 2014, 06:10:26 pm
. . .If your Phone Port Primary Line is SP1, then the SP1 DigitMap is the parm that needs to be examined for problems. It is found at Service Providers -> ITSP Profile A -> General.
This is the default SP1 DigitMap for a OBi110:
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*#]@@.)
. . .
Here is my recommended DigitMap for most people:
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.S3|<1aaa>xxxxxxx)
aaa is you local area code for 7 digit dialing.
BACKGROUND: With Circlenet setup for outbound calling on a Voice Gateway, and, in my case, Callcentric setup for inbound calls, then there are TWO places for digitmaps, one under the ITSP Profile and the other under the Voice Gateway.
Callcentric provides the following specific digitmap sequence for its setup at Service Providers -> ITSP Profile A or B or C or D -> General:
(*xx.|**275*x.|[3469]11|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*#]@@.)
The other digitmap, located at Voice Services -> Gateways and Trunk Groups -> Voice Gateway1 or 2 or . . ., was specified in Reply 60 to this thread as follows:
(1xxxxxxxxxx|<1>xxxxxxxxxx|<1919>xxxxxxx|011xxxxxx.S3)
QUESTION: Which digitmap should be changed, the Callcentric one or the Voice Gateway one? It seems like it would be the Voice Gateway one, since that is the one affecting outgoing calls. No? Actually, for those of us who use Callcentric as an inbound-only provider, does the Callcentric digitmap even matter?
azrobert:
The short answer is VG DigitMap for outbound calls.
Read on if you want to know how things work,
You can do some fancy stuff with an OBi. The scope of my following answer is limited to outbound calls from the phone port and inbound calls directed to a phone port.
Inbound calls are not affected by any DigitMap. The Inbound Call Route for the trunk directs the call to a phone port.
After you dial an outbound number the Phone Port DigitMap gets control.
The DigitMap validates the dialed number.
It can also modify the dialed number like adding a country code, area code or stripping off a prefix.
If the number does not match a rule in the Phone Port DigitMap you will get a Busy signal.
If the dialed matches a rule, it is passed to the Phone Port OutboundCallRoute.
Each entry in the OutboundCallRoute has a DigitMap or a literal.
If a dialed number matches an entry, it is routed out the specified trunk.
If there no match, you get a message something like "No Routes Available".
All trunk DigitMaps are totally IRRELIVANT unless they are referenced by the Phone DigitMap or OutboundCallRoute.
Most of the rules in the Phone Phone DigitMap or OutboundCallRoute are for special cases.
I'm only including what is need for calls to the Primary Line.
Phone DigitMap
((Mpli))
Phone Out Route
{(Mpli):pli}
Mpli points to the Points to the Primary line DigitMap (usually ITSP A DigitMap)
pli points to the Primary Line (usually sp1)
You would get the same results using Msp1 and sp1
If you dial 18005551212 it matches a rule in the ITSP A DigitMap, then matches the rule in the Out Route as is routed out SP1.
I 1st setup a VG like this:
Phone DigitMap
(8xxxxxxxxxx|(Mpli))
VG1 DigitMap
(<8:1>xxxxxxxxxx)
Phone Out Route
{(Mvg1):vg},{(Mpli):pli}
If you dial 88005551212 it passes the Phone DigitMap.
It matches VG1 DigitMap (Mvg1)
The number is changed to 18005551212 and routed out VG1.
If I did this:
Phone DigitMap
((Mvg1)|(Mpli))
The dialed number would pass the Phone DigitMap.
The number would be changed to 18005551212 in the Phone DigitMap.
It would NOT match Mvg1 in the Phone Out Route and would be routed out SP1.
Edit:
After GV was removed from SP1, I suggested this:
VG1 DigitMap
(1xxxxxxxxxx)
When you dial 18005551212 it matched the Primary Line DigitMap and is passed to the Phone Out Route.
It doesn't matter that GV was removed from the Primary Line and SP1 is not used.
Maybe you should change the Phone DigitMap, so it's not confusing:
Phone DigitMap
((Mvg1)|(Mpli))
The dialed number will match both Mvg1 and Mpli in the Phone Out Route.
Processing moves left to right, so it will match Mvg1 first and be routed out vg1
dial.tone:
Here is the Voice Gateway Digitmap I'm using and I'm still getting a 10-second delay when dialing a local, 7-digit number within my area code (where "aaa" in the digitmap is replaced with my area code). 10-digit and 11-digit numbers go right through without delay. I don't see any open-ended rules to trigger a 10-second delay. Any suggestions on how to make 7-digit calls go right through? What should I look for?
(1xxxxxxxxxx|011xx.S3|<1aaa>xxxxxxx)
azrobert:
The Phone Port DigitMap determines how long the OBi waits.
You have to look at all the DigitMaps the Phone DigitMap refers to, which probably includes the ITSP A DigitMap (primary line).
You don't get a 10 second delay with 11 digit numbers?
Maybe I don't totally understand how the delay is determined?
Ianobi, please chime in.
Edit:
Since 10 digits still work, you must have the 10 digit rule in the Primary Route's DigitMap.
You would need to remove the 10 digit rule and xx. from the Primary route's DigitMap to get zero delay on 7 digits.
Navigation
[0] Message Index
[#] Next page
[*] Previous page