SOLVED: Expert settings - CID prefix?
Taoman:
Quote from: QuantiumTech on April 25, 2016, 09:48:12 am
Any idea what I might be doing wrong or what else I might try?
Yes, listen to anything ianobi tells you. ;D Only reason I learned how to do this was because of him.
QuantiumTech:
Thanks so much for the help, ianobi!
With no modifications, the phone connected to my Obi200 shows
UNKNOWN CALLER
15205551456
Using your suggested string, my phone shows "UNKNOWN CALLER" with a blank line below it.
If I change <**1> to just <1>, I get "UNKNOWN CALLER" with a line below it showing the phone number - with an extra 1 prepended to the phone number. (now we're getting somewhere!) That extra 1 at the beginning, however, causes the separating dashes to be omitted.
If I change <1> to <H>, I get "Private Caller" - which, based on what you said, I think probably means that my phone is freaking out over any non-numeric character in the phone number line.
If I try to use <3->, it shows "UNKNOWN CALLER" and the phone number (no dashes) - with a 3 prepended. (The dash appears to be ignored.)
I thought maybe if I used some sort of text delimiter around an alpha character... so I tried <'H'> That gave me the same result as using the default value - "UNKNOWN CALLER" followed by the phone number. Interestingly, it does restore the separating dashes in the phone number: 1-520-555-1466 so basically it's ignoring everything within the "<>"
I got the exact same result when trying to use double quotes instead of single quotes as text delimiters. I also tried back ticks (``) as text delimiters- again, same result.
I'm giving up (for now) on using alpha characters and just trying to get "3" plus a dash or star or space or any sort of separator between it and the phone number that follows. However, it would be really nice to use an alpha prefix as opposed to numeric and I'm wondering... so far, everything I'm doing is only affecting the lower line (where the phone number is displayed) - is there any way to modify the UPPER line (which actually is alphanumeric)?
QuantiumTech:
No matter what I do, I can't seem to get any separation between the prepended 3 and the rest of the phone number. All the below have the exact same result:
<3>
<3->
<3 >
If I include a star or a # or anything non-numeric (other than dash or space), it goes back to showing "UNKNOWN CALLER" with a blank line below it.
To some extent, the whole purpose of this exercise is to not only allow my office manager to know which number is being called - so she can answer with the appropriate greeting - but also to be able to pop the last seven digits of the phone number into the search field of our customer database. Having the caller ID shown as 3-15205551466 is only marginally better than 315205551466. Yes, the prepended 3 does tell her which business is being called, but the omitted dashes make it much harder to get the last 7 digits for the database search. If there's a way to prepend "H-" to the upper line, it would be a much, much better solution as the letter prefix is much more intuitive (all 4 of my businesses start with a different letter) but also, the dashes would be displayed in the phone number.
ianobi:
Quote
With no modifications, the phone connected to my Obi200 shows
UNKNOWN CALLER
15205551456
I'm guessing that your phone is attempting to show:
CNAME
CallerID
There's some guesswork here as we have no knowledge of what your phone is capable of displaying. OBi devices cannot modify CNAME. If a CNAME is sent, then it will forward it to the Phone Port exactly as it receives it from the telco or SIP provider or GV. I do not know much about GV, but I'm assuming that it does not send CNAME. I don't know if your phone may add in CNAME if it has a number in its database.
All we can do from an OBi point of view is to transform CallerID. It appears that your phone will not display letters in the CallerID (lower line), I guess that this is not unusual. If you only require the final seven digits of the incoming CallerID to be displayed, then you could experiment with something like this:
{(<xxxx:1111>xxxxxxx):ph}
This will replace the first four digits of an eleven digit number with 1111 followed by the remaining seven digits unchanged. This may be more obvious on the phone display.
Getting late in my part of the world, so I'm signing off for today. If you wish to carry on experimenting, then I'm happy to help if I can tomorrow.
QuantiumTech:
Quote from: ianobi on April 25, 2016, 12:34:50 pm
I do not know much about GV, but I'm assuming that it does not send CNAME. I don't know if your phone may add in CNAME if it has a number in its database.
I have no idea about what GV does or does not do with CNAME but my phone definitely adds it when it's in my phone's database.
Quote
All we can do from an OBi point of view is to transform CallerID. It appears that your phone will not display letters in the CallerID (lower line), I guess that this is not unusual. If you only require the final seven digits of the incoming CallerID to be displayed, then you could experiment with something like this:
{(<xxxx:1111>xxxxxxx):ph}
This will replace the first four digits of an eleven digit number with 1111 followed by the remaining seven digits unchanged.
PERFECT! I really just wanted to replace the first digit, so I used {(<x:3>xxxxxxxxxx):ph}
and now it replaces the "1" (before the area code) with a 3 - and I still get the separator dashes! Tremendously helpful, ianobi! Thank you!!!
Navigation
[0] Message Index
[#] Next page
[*] Previous page