Outbound CID Spoofing is it possible?
VaHam:
Quote from: RonR on April 12, 2011, 04:16:50 pm
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?
Ok I went back to make sure the error code was the usual 407. And I must correct myself; it seems that the
{(<**2:>(Msp2)):sp2(4151234567>)} syntax does also work just fine. I know I attempted to try this case in earlier testing before I hit on the one which worked; so I must have made some other mistake back then.
So now the document makes a little more sense when it states:
"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 not the cid."
The $2 is equal to the value of (Msp2) but can be specified by simply leaving it blank in which case it defaults to the same value as (Msp2). The syntax I used probably caused the Msp2 algorithms to be called twice.
By "preceding", in the documentation, it is applying to the target and whether the default target is used or not the > must follow the spoofed-caller-number.
What is interesting here is that since (Msp2) also work then other DigitMaps can probably be used here as well I would assume to include user DigitMaps. This may provide for other interesting possibilities. Perhaps the digitmap for the called number could be different than the original dialed number by use of user defined digitmaps.
Again I think one example of the spoofing in the documentation could have avoided all the discussion in this thread :)
RonR:
{(<**2:>(Msp2)):sp2(14151234567>)} was the only suggestion I made because it's exactly what the documentation calls for.
I still think you have some misconceptions about $2 and Msp2, but this has gone on long enough already. I certainly agree the documentation could be improved. Occasional input from the Obihai folks would also go a long way to clarify things.
VaHam:
Quote from: RonR on April 12, 2011, 10:23:38 am
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.
Well I will have to agree with the poster in the other thread that $2 does not work and therefore the two cases you cite above are not in fact equal.
But either {(<**2:>(Msp2)):sp2(4151234567>)} OR {(<**2:>(Msp2)):sp2(4151234567>(Msp2))} does achieve my goal of having my GV cid shown on my second provider instead of it's own cid, since my second provider is on SP2. That way no matter which one I use to dial out on; if the called party just returns the call they will go back to my GV number.
Encino_Stan:
Quote from: VaHam on April 12, 2011, 09:13:31 pm
Well I will have to agree with the poster in the other thread that $2 does not work and therefore the two cases you cite above are not in fact equal.
But either {(<**2:>(Msp2)):sp2(4151234567>)} OR {(<**2:>(Msp2)):sp2(4151234567>(Msp2))} does achieve my goal of having my GV cid shown on my second provider instead of it's own cid, since my second provider is on SP2. That way no matter which one I use to dial out on; if the called party just returns the call they will go back to my GV number.
You say you can show your google voice cid over either sp1 or sp2. But I would like my sp2 number to show on sp1. However, since sp1 is my gv number it is my understanding that I cannot do that, since gv doesn't support spoofing. Is this correct?
jimates:
Correct, you can't change the number that shows up when calling using google voice.
Navigation
[0] Message Index
[#] Next page
[*] Previous page