Last Caller Number / *69 Call Return
RonR:
obi-support2,
Is there some reason you're ignoring my posts to you?
RonR:
Obihai,
I would really appreciate the courtesy of a reply. I will summarize my questions and concerns again.
Assuming the default PHONE Port CallReturnDigitMaps, is this an accurate description of the workings of $LCN, *69, and PHONE Port -> LastCallerNumber?:
The OBi processes the number and trunk name (sp1, sp2, li, pp) of the last incoming call to the PHONE Port through the CallReturnDigitMaps, matching the trunk name to one of the rules. The matching rule's embedded DigitMap then causes **n to be added, except in the case where the call came in the PrimaryLine (pli), and the result is stored in $LCN. *69 Call Return calls the number stored in $LCN using the PHONE Port OutboundCallRoute. $LCN is also used to display PHONE Port -> LastCallerNumber.
If this is not accurate, please provide the correct description.
Currently, *69 and LastCallerNumber do not appear to be working correctly.
Regardless of what PrimaryLine is set to:
Only calls coming in from a SIP trunk get **n added and get returned on the same trunk.
Calls coming in from a Google Voice or OBiTALK trunk do not get **n added and get returned on the PrimaryLine trunk.
*69 fails if the last caller number was from an OBiTALK trunk and PrimaryLine is not set to OBiTALK Service.
*69 fails if the last caller number was from a Google Voice trunk and PrimaryLine is set to OBiTALK Service.
There are probably failure scenarios involving the LINE Port, but I don't have CallerID and cannot test them.
If $LCN, *69, and PHONE Port -> LastCallerNumber were handled properly as I described above, I believe all scenarios would work correctly, returning the call on the same trunk it came in on, regardless of what PrimaryLine is set to.
PLEASE respond to this post.
obi-support2:
I only use default, and it's all working as expected, including PSTN calls.
We will have someone check on your cases and report back on Monday.
Thank you.
obi-support2:
We can duplicate the problem with Google Voice on SP1/2; and this is a bug we need to fix.
-----
To explain how it works, let's consider the default CallReturnDigitMaps:
{pli:(xx.)},{sp1:(<**1>xx.)},{sp2:(<**2>xx.)},{li:(<**8>xx.)},{pp:(<**9>xx.)}
The pli in first rule is replaced with the configured primary line upon system start.
If there is a conflict with another rule later in the list, the rule that comes first (left-to-right order) will be used by OBi. So if primary line is OBiTALK service, the **9 prefix will not be added, and so on.
For incoming calls on any trunk, the OBi first applies the CallReturnDigitMap for that trunk to come up with a mapped number. If no rule is found for that trunk, the original caller number is used as the mapped number. OBi then applies the PHONE Port DigitMap on the mapped number and
stores the mapped result as the LastCallerNumber status parameter on the PHONE Port web page.
When you dial *69, OBi uses the stored number directly for call routing. In other words, PHONE Port DigitMap is applied when the call return number is stored; not when *69 is dialed.
-----
The bug is, when SP1/2 is configured as Google Voice, the OBi fails to find the corresponding CallReturnDigitMap, and therefore no prefix is added; hence *69 in that case always try to use the primary line. If your GV trunk is also your primary line, then you won't notice the difference.
(For SIP, everything works as expected).
----
If you would like to try out patch to fix this issue, please send an email to
supprt@obihai.com and include your OBi number. We can push the patch to your unit.
Thank you for reporting this issue.
OBIHAI Support Team
RonR:
Quote from: obi-support2 on May 16, 2011, 12:56:45 pm
If you would like to try out patch to fix this issue, please send an email to supprt@obihai.com and include your OBi number. We can push the patch to your unit.
Yes, I would like the update. I sent an email a couple of hours ago, but the update is still not available.
Thanks,
Ron
Navigation
[0] Message Index
[#] Next page
[*] Previous page