Caller ID format
ianobi:
Smee,
It is possible to transform incoming CallerID. For example:
Voice Services > SP1 Service > X_InboundCallRoute:
{(<1:>@@.):ph},{ph}
An incoming call with CallerID of 12345678912 will have the leading "1" removed before the CallerID is sent to the phone by the rule {(<1:>@@.):ph}.
An incoming call with CallerID of 2345678912 or any other CallerID not starting with "1" will be sent to the phone unchanged by the rule {ph}.
Smee:
Quote from: ianobi on June 03, 2013, 09:21:08 am
Smee,
It is possible to transform incoming CallerID. For example:
Voice Services > SP1 Service > X_InboundCallRoute:
{(<1:>@@.):ph},{ph}
An incoming call with CallerID of 12345678912 will have the leading "1" removed before the CallerID is sent to the phone by the rule {(<1:>@@.):ph}.
An incoming call with CallerID of 2345678912 or any other CallerID not starting with "1" will be sent to the phone unchanged by the rule {ph}.
Wow, thanks. This certainly makes the display on my Uniden phone display to where at least it is readable. After applying the above, I now see my number formatted as 123-456-7890. Many thanks for the tip!! I applied it to all three of my Obi100s. ;D
Smee
jcrouch:
Quote from: ianobi on June 03, 2013, 09:21:08 am
Smee,
It is possible to transform incoming CallerID. For example:
Voice Services > SP1 Service > X_InboundCallRoute:
{(<1:>@@.):ph},{ph}
An incoming call with CallerID of 12345678912 will have the leading "1" removed before the CallerID is sent to the phone by the rule {(<1:>@@.):ph}.
An incoming call with CallerID of 2345678912 or any other CallerID not starting with "1" will be sent to the phone unchanged by the rule {ph}.
Waahoo!!!!!! That is perfect! Thank you so much.
GregoryZ:
Ianobi,
Surprise!! Guess who is still around and reading your posts? :) :)
Here is a question for your expert knowledge.....
Quote from: ianobi on June 03, 2013, 09:21:08 am
Smee,
It is possible to transform incoming CallerID. For example:
Voice Services > SP1 Service > X_InboundCallRoute:
{(<1:>@@.):ph},{ph}
An incoming call with CallerID of 12345678912 will have the leading "1" removed before the CallerID is sent to the phone by the rule {(<1:>@@.):ph}.
An incoming call with CallerID of 2345678912 or any other CallerID not starting with "1" will be sent to the phone unchanged by the rule {ph}.
So how would this look if I removed the "1" but added the "**1" to show the line number the call came in on?
I was looking at your post on "Caller ID format": http://www.obitalk.com/forum/index.php?topic=6045.msg38612#msg38612, and wanted to combine the two ideas.
-G
ianobi:
GregoryZ,
Glad to see that are still with us - it's always a pleasure to hear from you :)
It should be quite easy to achieve what you describe. The original rule:
Voice Services > SP1 Service > X_InboundCallRoute:
{(<1:>@@.):ph},{ph}
The "1" on the left of the colon is replaced by the "nothing" on the right of the colon. This rule will replace "1" with "**1":
Voice Services > SP1 Service > X_InboundCallRoute:
{(<1:**1>@@.):ph},{ph}
For sp2:
Voice Services > SP2 Service > X_InboundCallRoute:
{(<1:**2>@@.):ph},{ph}
My very cheap dect phones seem ok with displaying "*", but there have been reports of phones that will only display numbers for CallerID.
The OP in this thread wanted 10 digits so his phone would display the format xxx-xxx-xxxx. I'm not sure how the CallerID will be formatted for a number such **12345678912. I think it will vary depending on the type of phone. Mine just outputs the string **12345678912 with no dashes or spaces. However, I am using UK style CallerID, so it would be interesting to hear how this works with North American style CallerID.
Navigation
[0] Message Index
[#] Next page
[*] Previous page