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