Page 116 of the OBi Device Administration Guide states:
$2 is an internal variable containing the called number of this outbound call, after any digit map transformation in the matched callee object
$2 is not expanded, however, and is passed as the literal '$2' in the following OutboundCallRoute rule:
{(Mpli):pp(3*$2)}
Speed Dial 3 is used and the targeted OBi receives the call, but with a payload of '$2' instead of the called number.
14 days and no response from Obihai.
Quote from: RonR on September 12, 2011, 10:22:01 PM
Page 116 of the OBi Device Administration Guide states:
$2 is an internal variable containing the called number of this outbound call, after any digit map transformation in the matched callee object
$2 is not expanded, however, and is passed as the literal '$2' in the following OutboundCallRoute rule:
{(Mpli):pp(3*$2)}
Speed Dial 3 is used and the targeted OBi receives the call, but with a payload of '$2' instead of the called number.
This problem was
not corrected and is 100% reproducible in Software Version : 1.3.0 (Build: 2575)
Obihai support,
Will this reproducible bug also be fixed in an upcoming maintenance release?
Quote from: RonR on September 12, 2011, 10:22:01 PM
Page 116 of the OBi Device Administration Guide states:
$2 is an internal variable containing the called number of this outbound call, after any digit map transformation in the matched callee object
$2 is not expanded, however, and is passed as the literal '$2' in the following OutboundCallRoute rule:
{(Mpli):pp(3*$2)}
Speed Dial 3 is used and the targeted OBi receives the call, but with a payload of '$2' instead of the called number.
Obihai support,
This problem has changed and is 100% reproducible in Software Version : 1.3.0 (Build: 2586).
Instead of $2 being incorrectly passed as the literal '$2', $2 is now discarded and no called number is passed to the targeted OBi.