Single-Stage Dialing Through Any OBi Trunk
mish:
@ianobi - I did what you suggested.
PSTN line is the default line for the Phone port on Obi110.
Created a speed dial at #5 using the Obitalk website. If I press 5, then the phone connected to Obi110 rings.
Also created InboundCallRoute in Obi110:
{(290123456|300123456|500123456)>(Mpli):pli},{ph}
Did this because I am calling from Obi100 for testing purposes. Obi202 is where I need the capability.
Then I dialled 5*9812312345. However, all that happens is that ph rings. But the call does not go through to the PSTN line.
Obi110 log shows this:
Peer Name Obi100
Peer Number 300123456
Obi100 where I called 5*9812312345 from shows this
Terminal ID PHONE1 OBiTALK1
Peer Name
Peer Number 5*19812312345 5*19812312345
Notice, the 1 that is prefixed to the number by Obi100. I am thinking that this must be done in SP1 of the Obi100 that I am using to call. I wonder if I can say that if a number begins with 5* then let anything that comes after that pass through without modification.
---
As to trying to resolve the basic functioning of this setup, wondering if
Some outbound call rule also needs to change? If so, in Obi110's Phone Port?
In the PHONE Port and Auto Attendant DigitMap's, change [1-9]x?*(Mpli) to [1-9]x?*@@.
In the PHONE Port and Auto Attendant OutboundCallRoute's, change {([1-9]x?*(Mpli)):pp} to {([1-9]x?*@@.):pp}
ianobi:
You could make the changes to the outbound rules, but in the OBi100 not the OBi110. It will stop the 1 being prepended to outgoing numbers. So long as the number arriving at the OBi110 is in a format accepted by Mpli then it should be sent to pli.
In case there is any doubt regarding the OBi110 Primary Line use this rule:
{(290123456|300123456|500123456)>(Mli):li},{ph}
I think you are very close! Let me know how you get on. I cannot log in here for next 24 hours, but I will be back!
ianobi:
I just re-read RonR's original post:
Quote
Note: Replace pli above (2 places) with the OBi's PHONE Port -> PrimaryLine trunk name (sp1,sp2,li,pp,tg1) as the OBi won't do it for you.
Looks like using pli does not work in InboundCallRoutes. I did not know that :-[
The suggested change to
{(290123456|300123456|500123456)>(Mli):li},{ph}
Is probably all that is required to fix it.
mish:
@ianobi - Success at last! The change you suggested worked. Further, I had to change the digit map of ITSP A because parsing of that digitmap was prefixing a 1 to the number. Now it works!
Thank you! Before I received your reply, I had already tried a lot of options. Had changed pli to li, but not Mpli to Mli!
One more question: If I do not want PSTN line to be the default line, and if I change the default line, this routing should still work right, because the inbound route in Obi110 now seems to explicitly point to li, and has nothing to do with pli. Right?
------
And one more question: :)
What do these lines achieve?
Quote
In the PHONE Port and Auto Attendant DigitMap's, change [1-9]x?*(Mpli) to [1-9]x?*@@.
In the PHONE Port and Auto Attendant OutboundCallRoute's, change {([1-9]x?*(Mpli)):pp} to {([1-9]x?*@@.):pp}
ianobi:
Mish,
I believe that you are correct about changing the Primary Line, the (Mli):li rule should still work. I cannot test that here, maybe you would :)
Let’s look at the outgoing side of what you have done:
Speed dial 5 = the Obi110 number 290123456
You dialled from your Obi100: 5*9812312345
Phone Port DigitMap rule [1-9]x?*(Mpli) decides that is a valid number. It means any one or two digit number followed by a star, then a number that fits Mpli DigitMap.
Phone Port OutboundCallRoute rule {([1-9]x?*(Mpli)):pp} routes that number to the OBiTALK trunk.
The format going out to the OBiTALK trunk must be something like:
300123456 5*9812312345
I’m guessing that the Obi servers know that 5* coming from 300123456 means use the speed dial 5 number to route the call to 290123456 and strips out the 5*. So, 9812312345 is sent to 290123456 along with the “from” info 300123456
Using these default rules, only numbers matching Mpli in the sending Obi can be sent using this method.
RonR suggests changing the rules to:
Phone Port DigitMap rule [1-9]x?*@@. This means any one or two digit number followed by a star followed by anything.
Phone Port OutboundCallRoute rule {([1-9]x?*@@.):pp} routes that number to the OBiTALK trunk.
I like RONR’s better as it allows us to send any numbers we wish – or letters!
Now let’s look at the incoming side – the “target” OBi110 in this case.
OBiTALK InboundCallRoute:
{(290123456|300123456|500123456)>(Mli):li},{ph}
If the number coming in from any of the callers in the list matches Mli, then that number will be sent out to line.
(290123456 does not need to be in its own list)
I see no reason why this should not work, if all the DigitMaps are different from each other:
{(300123456|500123456)>(Mli):li},{(300123456|500123456)>(Msp1):sp1},{(300123456|500123456)>(Msp2):sp2},….more here…{ph}
In practice the caller numbers are best put in a User Defined Digit Map, which if called “cot” then the rules would be:
{(Mcot)>(Mli):li},…more here…
If anyone would like to take on the testing of some of this, or already knows it works, then please let us know .
I’m sorry this has been long and rambling, but my thinking and my typing are not always in synch. Did I answer the question?? ::)
Navigation
[0] Message Index
[#] Next page
[*] Previous page