News:

On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT

Main Menu

Softphone and Circle of Trust problem

Started by Obvdobi, October 21, 2011, 07:40:40 PM

Previous topic - Next topic

Obvdobi

The Softphone registered under my account cannot dial out numbers like the phone attached to the Obi device.
The phone at home is setup to turn 010-5555-5555 into 01186-10-5555-5555 by rule:
(1xxxxxxxxxx|<1615>[2-9]xxxxxx|<1>[2-9]xxxxxxxxx|<0:**201186>1[02-9]xx.|<0:**201186>[2-9]xx.|<**2>011xx.|<00:**2011>xx.|xx.|(Mipd)|[^*]@@.)

However, when I use Softphone, this rule does not apply. I guess it's related to Obitalk service's InboundCallRoute. The question is: how are the softphone associated with the obi device? by circle of trust?  When I dial out with this associated softphone, it will dial usual numbers correctly via SP1 as defined in InboundCallRoute:
{(2xxxxxxxx)>(xx.):sp1},{(2xxxxxxxx|2xxxxxxxx):aa},{ph}

I thought by changing it into:
{(2xxxxxxxx)>(<0:**201186>1[02-9]xx.|<0:**201186>[2-9]xx.|**2011xx.|<00:**2011>xx.|xx.):sp1},{(2xxxxxxxx|2xxxxxxxx):aa},{ph}

the call from the softphone will dial out international number by SP2 and US number by SP1. But none of the digits are translated properly. the number is dialed out by sp1 like "**201186....". sp2 is not used at all.

How can one use the same setup from Obi device for the softphone?

Also, if I add my friend in another country (with a different Obi account, no device, just a softphone account provided by Obi) to the circle of trust, how can she also use the same dialing rule defined in my Obi device?  Is it possible for her to do 1-stage dialing instead of going to AA and then dial out through 2-stage dialing?

RonR

#1
Calls from the PHONE Port are a two step process.  The first step evaluates input from the PHONE Port though the PHONE Port DigitMap, possibly transforming the entered number (as in your case, where **2 is prepended to various patterns).  The resulting number is then evaluated through the PHONE Port OutboundCallRoute, where transformation often occurs again (such as removing **2 before passing the number to SP2).  This two-step process does not occur from InboundCallRoute's.

When you use Circle-of-Trust from the OBiTALK Web Portal, a very minimal OBiTALK Service InboundCallRoute configuration is generated that doesn't use the normal trunk DigitMaps and doesn't support any trunk other than the PrimaryLine.

Since the PHONE Port OutboundCallRoute doesn't come into play from an InboundCallRoute, when you added **2 to dialed numbers, it simply went out the trunk with the rest of the number.

The following OBiTALK Service InboundCallRoute should mimic your PHONE Port behavior from both your (290000001) and your friend's (290000002) softphones:


Voice Service -> OBiTALK Service -> InboundCallRoute:

{(290000001|290000002)>(<0:01186>1[02-9]xx.|<0:01186>[2-9]xx.|011xx.|<00:011>xx.):sp2},
{(290000001|290000002)>(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1615>[2-9]xxxxxx):sp1},
{(290000001|290000002):aa},{ph}


See this post for a general purpose single-stage dialing configuration:

Single-Stage Dialing Through Any OBi Trunk

Obvdobi


RonR,

What a elegant solution! :)   Your single dialing tutorial is even better.  Thank you so much. I will have all my Obi and ObiOn apps to setup using your tutorial. It's much easier to add more apps or Obi(s) later.

BTW, I accidentally put my real Obi number in the post. Could you do me a favor to replace them with "2xxxxxxxx" ? Thanks, RonR!


Everton

Quote from: Obvdobi on October 22, 2011, 08:12:59 AM


BTW, I accidentally put my real Obi number in the post. Could you do me a favor to replace them with "2xxxxxxxx" ?

Ron cannot make any changes to your post, only YOU (and maybe the Moderators) can go back and "Modify" the post!

RonR

Quote from: Obvdobi on October 22, 2011, 08:12:59 AM
BTW, I accidentally put my real Obi number in the post. Could you do me a favor to replace them with "2xxxxxxxx" ?

Done.