Outbound CID Spoofing is it possible?
RonR:
VaHam,
From my read of the documentation, both of these should be identical:
{(1xxxxxxxxxx|xxxxxxx):sp2(14151234567>$2)}
{(1xxxxxxxxxx|xxxxxxx):sp2(14151234567>)}
and should set the CallerID to 14151234567 on an SP2 call to the 11 or 7 digit number resulting from the matched embedded DigitMap (1xxxxxxxxxx|xxxxxxx).
In another thread, the poster noted that $2 does not work as advertised, but was unable to get an explanation from the Obihai folks as to why.
RonR:
I don't believe that's correct. From the documentation:
$2 is an internal variable containing the called number of this inbound call, after any digit map transformation in the matched callee object of the matched peering object in the peering-list.
and
The target object inside an arg object is optional. If omitted, it implies the target $2, which means to call the original called number after applying any necessary digit map transformation implied by the rule. The preceding ‘>’ cannot be omitted if target is omitted but cid is not
'$2 is the term (Msp2)' doesn't make any sense to me, nor does its use in the manner you suggest.
VaHam:
Quote from: RonR on April 12, 2011, 10:28:34 am
I don't believe that's correct. From the documentation:
$2 is an internal variable containing the called number of this inbound call, after any digit map transformation in the matched callee object of the matched peering object in the peering-list.
and
The target object inside an arg object is optional. If omitted, it implies the target $2, which means to call the original called number after applying any necessary digit map transformation implied by the rule. The preceding ‘>’ cannot be omitted if target is omitted but cid is not
'$2 is the term (Msp2)' doesn't make any sense to me, nor does its use in the manner you suggest.
While I agree with your assessment of the $2's intended value I can tell you that it does not work however using (Msp2) as I showed above does in fact work! I won't fight with success :)
RonR:
I give up. The documentation says:
arg := cid > target
cid := spoofed-caller-number OR $1
target := number-to-call OR $2
Notes:
- number and number-to-call are literal strings, such as 14089991234
Putting a DigitMap (Msp2) in as a literal string doesn't make any sense.
VaHam:
Quote from: RonR on April 12, 2011, 02:33:11 pm
I give up. The documentation says:
arg := cid > target
cid := spoofed-caller-number OR $1
target := number-to-call OR $2
Notes:
- number and number-to-call are literal strings, such as 14089991234
Putting a DigitMap (Msp2) in as a literal string doesn't make any sense.
Fortunately is looks like because the Msp2 is enclosed in brackets () it gets interpreted as a variable rather than a literal string.
For some reason $2 does not seem to equate to (Msp2) as both you and I would have thought from the documentation.
I suspect the difference has to do with stripping off the leading **2 from the number to call. I am guessing that $2 includes the leading **2 and in processing the DigitMap for the Phone port (Msp2) gets the **2 stripped off.
Navigation
[0] Message Index
[#] Next page
[*] Previous page