Auto attendant not answering incoming PSTN call from phone in Circle of Trust
Jon9999:
I have my cell number (e.g., (9175551212) in my Circle of Trust, with the Match option unchecked. I can see that OBiTalk has correctly changed my LINE InboundCallRoute to {('jon'|x.9175551212):aa},{ph}.
Yet when I call my POTS number from my cell, it just rings the phone. The aa doesn't pick up.
I can see in my call log that the calls from my cell are coming through with CID of 'WIRELESS CALLER' 9175551212.
I've tried changing the LINE InboundCallRoute to {('jon'|@.9175551212):aa},{ph} but that doesn't work either.
The aa does pick up when I call from OBiON.
Any ideas?
-jon
ianobi:
Quote
I can see in my call log that the calls from my cell are coming through with CID of 'WIRELESS CALLER' 9175551212.
What matters here is exactly what is recorded in Status > Call History > Peer Number
Status > Call History > Peer Name is ignored by the OBi for routing purposes.
A rule such as @.9175551212 would match almost anything ending with digits 9175551212, if that is the Peer Number.
By the way, we are talking about "Trusted Callers" not "Circle of Trust". Yes, I know I'm being pedantic and it does not change anything about this question :)
Jon9999:
Darndest thing, Ian. Even though my incoming calls' CID is showing up correctly in Status>PHONE & LINE Status>Last Caller Info, and even thought the CID is displaying correctly on the phone connected to the PHONE port, the entries for Peer Name and Peer Number for the same call in Call History is completely blank. So that's why it's not matching the aa rule in the Line Port's Incoming Call Route. But why is the peer information not being captured in the log (or, presumably, in the rule engine) when it's there?
ianobi:
You are not the first person to have this problem!
The OBi110 defaults are set for standard North America CallerID detect, so you should be OK for most settings. That's assuming that you are using a fairly normal PSTN line. Some of us plug all sorts of weird stuff into our Line Ports - GSM devices, other ATAs etc.
Several settings can affect how the OBi110 detects CallerID from the Line Port. To give the OBi more time to detect CallerID try increasing:
Physical Interfaces -> LINE Port -> RingDelay
This might get annoying if increased too much as it delays ringing from incoming calls.
You could also try changing these settings:
Physical Interfaces->LINE Port->Ring Detection -> RingThreshold to 19.35-23.65 and/or RingValidationTime to 150.
In North America the CallerID is delivered between the first and second bursts of ringing. The OBi110 needs to actually detect that first burst of ringing and have enough time to process the information before it routes the call. If any of that fails, then it routes the call to the Phone Port as a default position.
azrobert:
If RingDelay is set too low you cannot test for CallerID in the InboundRoute(as ianobi described), but the OBi will start to display the CallerID as soon as it's available.
Navigation
[0] Message Index
[#] Next page