Crazy Ring patterns, Callerid always shows out of area for all calls?
Sandia505:
Ring pattern sounds like: Ring, Ring, Pause, Ring, Pause. Pattern Repeats, Very little time between first 2 rings.
I attached a jpeg screen dump of the SP1 service screen, not sure it worked I may have to put the jpeg on my server and place a link here for you to see it.
Thanks!
Taoman:
Quote from: ianobi on March 23, 2016, 11:45:20 am
This can be done, but you will have to be prepared to dive into expert settings. If you wish me to show you how, then please post what is in this setting:
Voice Services > SP1 Service > X_InboundCallRoute
I have never been able to get this to work properly on 2 different Panasonic DECT phone models using 2 different OBi ATAs. This is why I recommended the OP set CidNoNameFormat to Show Caller Number. On Panasonic phones (when there is no incoming CNAM) you can set the CNAM display to show 7, 10, or an 11 digit number.
I think my syntax is correct so perhaps you can show me where I'm going wrong. This is what I'm using:
{(<1:>@@.):ph},{ph}
All of my DIDs don't include the leading "1" for incoming calls except Callcentric. So presumably the rule wouldn't work for any incoming calls except those from Callcentric. Correct? Except it doesn't work for Callcentric either. I still get the leading "1" displayed for all CC calls.
But, if I make the rule be {(<1xxx:>@@.):ph},{ph} (where xxx is local area code) it does work and only shows a 7-digit number.
Likewise, {(<xxx:>@@.):ph},{ph} works properly on all my other DIDs. It displays a 7-digit number as expected.
But I have never been able to remove just the leading "1" from any of my DIDs in the call display. Perhaps this is just a function of Panasonic DECT phones or am I missing something obvious?
Edit: Made another call to my Callcentric line using {(<1:>@@.):ph} and checked the Phone and Line Port status and could see the 1 was being stripped off before being sent so the problem is definitely with the Panasonic DECT phone. My guess is it has x number of characters it can display in that field and if you only send 10 it will add the 1. So by sending my line number plus * it overwrites where the 1 would otherwise normally display.
Sandia505:
It Always shows a 1 505 XXX XXXX on all devices, AT&T wireless, Nortel, as well as a Bellsouth Callerid box and a Uniden phone as well. Doesn't make any difference as to who the callerid unit is or that a 505 is a local calling number. ??? I am curious what the Red Exclamation points in specific fields are.
Taoman:
I came up with a better solution for me since I get calls on 3 of my 4 trunks. I prefaced the phone number with the line # which gets substituted for the leading "1" (at least on a Panasonic DECT phone) so I can easily see which line the call is coming in on. I had just been using different ring patterns to try and determine which line was actually ringing.
{(<?:X*>@@.):ph}
where X is the SP trunk number. So the end result displays like this where "3" is the line number:
3*555-555-1212
Taoman:
Quote from: Sandia505 on March 23, 2016, 02:24:59 pm
It Always shows a 1 505 XXX XXXX on all devices, AT&T wireless, Nortel, as well as a Bellsouth Callerid box and a Uniden phone as well. Doesn't make any difference as to who the callerid unit is or that a 505 is a local calling number. ??? I am curious what the Red Exclamation points in specific fields are.
Try changing your X_InboundCallRoute to the following:
{(353xxxx|353xxxx):aa},{(<1505:>@@.):ph},{(<1:>@@.):ph},{ph}
ianobi can correct any mistakes I might have made.
PS. A red exclamation mark means the field has/had been changed from the default setting.
Navigation
[0] Message Index
[#] Next page
[*] Previous page