Callerid lost when routing via PP?
obi-support2:
This is a limitation in 1.1 and 1.2 releases.
The OBi does not pass the original caller's number so that the called OBi can recognize the call is from a member in the circle-of-trust.
In release 1.3 (coming-soon), there will be an enhancement to show the original caller's number at the called OBi, but still uses the calling OBi's number for circle-of-trust matching.
jimates:
"show the original caller's number at the called OBi"
Great. I am pretty sure that will satisfy my needs, and many others, where I only want to see the original callers number when forking calls to another endpoint, without any additional call management.
"but still uses the calling OBi's number for circle-of-trust matching"
If I understand that correctly, the caller id of the last device passing the call (not the id of the original call) is the caller id that will be used for COT at the next endpoint.
krpan:
Thank you for info obi-support2, I'll definitely look forward to 1.3 :)
On another note, in my attempts to find ways to work around the soon to be dealt with limitation ;D I observed that when used in appropriate places in InboundCallRoute, $1 and $2 are treated as literals instead of being substituted with caller id and called id respectively (as per information on pages 113-114 in admin documentation)
I.e. According to documentation the following should work if used in InboundCallRoute of SP1 (SP1 and SP2 are setup as SIP accounts):
{(xx.):sp2($1>$2)}
instead OBi tries to make a call via SP2 using literal $2 as called id and using literal $1 as CID. The only place I've seen $1 substituted appropriately and not treated as a literal value was in AA digit map :(
QBZappy:
obi-support2,
Looking forward for this feature that many considered basic to have. Well done. (dance of joy)
+1
yhfung:
Quote from: krpan on May 26, 2011, 08:51:55 pm
On another note, in my attempts to find ways to work around the soon to be dealt with limitation ;D I observed that when used in appropriate places in InboundCallRoute, $1 and $2 are treated as literals instead of being substituted with caller id and called id respectively (as per information on pages 113-114 in admin documentation)
I.e. According to documentation the following should work if used in InboundCallRoute of SP1 (SP1 and SP2 are setup as SIP accounts):
{(xx.):sp2($1>$2)}
instead OBi tries to make a call via SP2 using literal $2 as called id and using literal $1 as CID. The only place I've seen $1 substituted appropriately and not treated as a literal value was in AA digit map :(
Please note that if you want to pass caller or callee IDs to other parties via SP1 or SP2 provided the VoIP providers allow you to do so, otherwise all the information sent by OBi device to the providers are disregarded.
YH
Navigation
[0] Message Index
[#] Next page
[*] Previous page