Crazy Ring patterns, Callerid always shows out of area for all calls?
ianobi:
@ Taoman - Looks like you have a good understanding of how to transform incoming CallerIDs. {(<1:>@@.):ph} was my original post several years ago when people were complaining that their phones were only designed to display ten digit numbers. I used the "@@." rather than "xx." as my incoming CallerIDs sometimes contain letters as well as numbers. For conventional incoming calls containing only digits, then {(<1:>xx.):ph} would work fine for removing the leading "1".
@ Sandia505 - Taoman's suggested InboundCallRoute should work fine for you:
{(353xxxx|353xxxx):aa},{(<1505:>@@.):ph},{(<1:>@@.):ph},{ph}
The first rule sends incoming calls with that CallerID to your Auto Attendant.
{(<1505:>@@.):ph} matches incoming calls with CallerIDs with the first four digits being 1505, removes the leading 1505 and sends the remaining seven digits to the Phone Port as a seven digit CallerID.
{(<1:>@@.):ph} matches incoming calls with CallerIDs with the first digit being 1, removes the leading 1 and sends the remaining ten digits to the Phone Port as a ten digit CallerID.
{ph} matches any other CallerID and sends it unchanged to the Phone Port.
I cannot see any reason for your crazy ring pattern. Maybe try a simple corded phone as a test?
Sandia505:
ianobi, Thanks so much for the detailed callerid info, implemented and works perfectly, now shows 7 digit local number.
I did want to ask you what the red exclamation point are at the ends of certain fields. (see previous attachment)
Gonna see where I can pick up a standard corded phone, everything I currently have is wireless or straight callerid boxes. (wish I had kept my old trimline)
What is your thoughts of completely removing everything from Obi, performing a factory reset on the 200 and try putting everything back in hopes of resolving the ring issue or am I asking for trouble doing this?
Best regards, :D
Dan
Taoman:
Quote from: ianobi on March 24, 2016, 02:42:29 am
I used the "@@." rather than "xx." as my incoming CallerIDs sometimes contain letters as well as numbers.
Thanks. I was wondering about that. I don't think NANP allows non-numerical characters in the CallerID number. I take it the UK does?
ianobi:
@ Dan - Here's the official line from Obihai:
Quote
Inside the OBi Expert Configuration pages, you will notice its resemblance to the OBi device web page menu, look and layout. To the right of the configurable parameter value field, there may be a red exclamation mark (!). When this mark is present, it means the parameter value next to where it appears has an OBi Expert configuration database entry that is different than the OBiTALK database entry. If the Device Default and OBiTALK boxes are left unchecked, then the OBi will use this setting in its active configuration.
I have loads of red "!" - nothing to worry about.
I would not try the factory reset just yet. The corded phone test would be my first step - it may be nothing to do with the OBi. You could try changing the ring profile from A to B, save, then change it back again to see if that resets something.
ianobi:
@ Taoman - The UK system is similar to NANP, it only uses digits. However, it is an "open" system which allows for variable length numbers, which can make OBi digit maps more difficult.
I'm thinking back a couple of years now, but I think someone in the US was under the impression that his voip or PSTN provider was including "-" symbols. That seems unlikely, more likely his phone was introducing those in its display. My need for "@@." is more to do with my direct ip calling where I can invent CallerIDs, which sometimes include letters.
In the US it would be fine to be more precise. If your Call History shows all calls coming in are eleven digits starting with "1", then this:
{(<1:>@@.):ph}
could be rewritten as
{(<1:>xxxxxxxxxx):ph}
Navigation
[0] Message Index
[#] Next page
[*] Previous page