Prepend CID info to show which line the call is coming in on

<< < (2/2)

azrobert:
You can add a "1" prefix to the CallerID with the following X_InboundCallRoute:
{(<1>@@.):ph},{ph}

Add a "1" for SP1, "2" for SP2.....

My phone only allows a numeric CallerID. If I add "L1" the CallerID displays blank.


Update:

giqcass,

I tried "{(<**1>@@.):ph},{ph}" and it worked.
My phone won't allow me to add a alpha character, but allowed *
I assume every phone is different, so just try.

Shale:
Quote from: azrobert on May 27, 2013, 03:06:38 pm

I tried "{(<**1>@@.):ph},{ph}" and it worked.


Would "{(<**1>@.):ph}" have worked also?

giqcass:
Anything other then 0-9 seems to upset my phone.  With an outgoing dial plan we don't need to prepend ** anyway.  I will probably create a country code for each of my service providers then set my outgoing dial plan to dial each separate service provider based on the call plan.  This is an excellent solution for my needs.  Thanks for the help.  

I think I might use the following "Country codes"
SP1 = No Change
SP2 = 02
SP3 = 03
SP4 = 04
BT1 = 09

I have been thinking about whether this might mess up international dialing.  I believe it will work fine.

ianobi:
Shale,

My original rule for this was:

Voice Services > SP1 Service > X_InboundCallRoute:
{(<**1>(@@.|?)):ph}

Your rule {(<**1>@.):ph} does the same in a more concise way. It allows for an incoming call with CallerID or with no CallerID and prepends **1 to either. If there was no CallerID then that incoming call will now have a CallerID of **1.

It's a personal choice whether or not you wish to accept calls with no CallerID. In azrobert's example {(<**1>@@.):ph},{ph} only calls with some sort of CallerID will have **1 prepended.

In my original post I decided to allow incoming calls with CallerID or no CallerID, but also used the "oleg method" to defeat scanners like so:
Quote

If we are using the “oleg method” to defeat scanners and assuming that my AuthUserName is 1212121, then the rule would be:

{(<**1>(@@.|?))>(1212121):ph}

Some of this is personal choice and some must be decided by what your dect phone etc will display - I have some problems with that myself.

If you want to see all the possibilities of what the OBi can prepend to a CallerID, then fork the call to a softphone like PhonerLite and it will display the full transformed CallerID during ringing and it can be viewed using the debug feature. I have successfully prepended words such as "family" or "business" but getting a phone to display that plus the original CallerID is either impossible or just hard to read!

Navigation

[0] Message Index

[*] Previous page