Outbound CID Spoofing is it possible?
RonR:
Quote from: VaHam on April 12, 2011, 03:01:02 pm
For some reason $2 does not seem to equate to (Msp2) as both you and I would have thought from the documentation.
I've never thought that $2 equates to (Msp2). $2 is supposed to an internal varialble that holds the number to be called, which is the result of the DMP evaluating the (<**2:>(Msp2)) to the left of the colon, using the value returned by the DMP when it evaluated the number dialed though the PHONE Port DigitMap.
Page 116:
- $2 is an internal variable containing the called number of this outbound call, after any digit map transformation in the matched callee object
VaHam:
Quote from: RonR on April 12, 2011, 03:22:51 pm
Quote from: VaHam on April 12, 2011, 03:01:02 pm
For some reason $2 does not seem to equate to (Msp2) as both you and I would have thought from the documentation.
I've never thought that $2 equates to (Msp2). $2 is supposed to an internal varialble that holds the number to be called, which is the result of the DMP evaluating the (<**2:>(Msp2)) to the left of the colon, using the value returned by the DMP when it evaluated the number dialed though the PHONE Port DigitMap.
Page 116:
- $2 is an internal variable containing the called number of this outbound call, after any digit map transformation in the matched callee object
I should have said $2 should equate to the result of Msp2 having been applied as I think we both surmised from the documentation. But that does not appear to be the case. However enclosing the Msp2 in brackets (which apparently makes it be interpreted as a variable) does in fact give us the correct value.
I know what the manual says; but from my testing it does not work that way. Perhaps someone else who actually has the capability of testing this can confirm my tests; but for me I can tell you that is works as I stated above and not as the manual states!
RonR:
Have you also tried?:
{(<**2:>(Msp2)):sp2(14151234567>)}
Note the trailing '>' above.
With ITSPx -> X_SpoofCallerID checked.
And testing it by making a call as **2 + number to see if the correct number is called and if the expected CallerID is displayed (using the desired CallerID in place of 14151234567, of course).
VaHam:
Quote from: RonR on April 12, 2011, 04:03:27 pm
Have you also tried?:
{(<**2:>(Msp2)):sp2(14151234567>)}
Note the trailing '>' above.
With ITSPx -> X_SpoofCallerID checked.
And testing it by making a call as **2 + number to see if the correct number is called and if the expected CallerID is displayed (using the desired CallerID in place of 14151234567, of course).
Yes I have and no it doesn not work!
UPDATE: I was wrong this does work!
RonR:
Ok, I just wanted to make sure all those aspects went into the test at the same time.
What part(s) failed? Wrong number called? Wrong CallerID?
Navigation
[0] Message Index
[#] Next page
[*] Previous page