800 calling through SipBroker (via CallCentric)

<< < (9/12) > >>

azrobert:
How are you using a Star Code to block CID?

I dialed *67188842...... and still got direct access to my account.

You could setup 2 VGs. One with your real CID and the other with no or a phony CID.

giqcass:
Currently I have a second Google Voice account.  I did not sign up for Google Voice with that account.  Therefore I don't have a number for that account.  When you make calls with a Gtalk account with no number attached you get a generic outbound CID.  I then set that account up on Simonics and sent them an email to allow no registration access to my account.  I set that up as a voice gateway and remapped my obi to send *67 calls out the Voice gateway.

Here is where I explained the process originally.
http://www.obitalk.com/forum/index.php?topic=5451.0

I got the idea from all of those people that had been complaining about having the incorrect outgoing CID because they set there account up wrong.  For billing reasons it's impossible to block CID to toll free numbers.

azrobert:
Quote from: mo832 on April 08, 2014, 01:00:55 pm

Now, disregarding all of the special alternatives we have tried, can you help me figure out why my setup was still requiring the **1 even though the codes seemed to take care of it automatically via Primary Line? If I have a logic error somewhere, I would like to find it now before it becomes an issue, if ever.


I took another look at this and found the problem.

ITSP B DigitMap
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*#]@@.)

Phone Port OutboundCallRoute
{([1-9]x?*(Mpli)):pp},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**9:>(Mpp)):pp},{(Mvg8):vg8},{(Mpli):pli}

First, the OutboundCallRoute processes left to right. {(Mpli):pli} is the rule that routes calls to the Primary Line (SP1)

[^*#]@@. is the rule causing the problem.
This rule will match a dialed number where the 1st character is NOT an * or # followed by 1 or more characters.

**275*18005551212 will match {(<**2:>(Msp2)):sp2} and be routed to SP2.

**2 will match <**2:>
and
75*18005551212 will match (Msp2)

You can fix the routing problem by removing "|[^*#]@@."

mo832:
Thank you azrobert, you are da man!

Regarding that last string that should be removed, will that eliminate any functionality?

I remember another string suggested by RonR that is a better choice. It was supposed to be used for SIP dialing "anything@anything". But how can you dial characters from a phone?

azrobert:
I don't know what that rule is for. Removing it shouldn't cause problems.

I removed all rules I don't use.
My SP1 DigitMap looks like this:
(1xxxxxxxxxx|<1>xxxxxxxxxx|<1480>xxxxxxx)

I removed (Mipd). It allows you to dial IP addresses and I don't need it.
I also removed "xx.". It checks for any number of digits.
This can slow down dialing and should be removed if not needed.
When you dial 18005551212 the OBi will wait a couple seconds before routing the dialed number to a trunk because of "xx.". It doesn't know if you will dial additional digits, so it waits.
The call will be routed immediately without "xx.".
I even removed "011xx.". We only call about 5 international numbers and I setup speed dials for them.

RonR did some fancy coding. For an example he would build a URI in the Phone Port DigitMap like "userdi@somewhere.dyndsn.com" and then check for it in the OutboundallRoute with @@.

Navigation

[0] Message Index

[#] Next page

[*] Previous page