Outbound CID Spoofing is it possible?
RonR:
VaHam,
I assume from your posts that you're probably experimenting with an OutboundCalRoute rule something like this?:
{(<**2:>(Msp2)):sp2(14151234567>)}
If so, are you testing it by dialing **2 + number. That's the only way this particular rule would match and attempt to set your CallerID. If your VoIP provider is on SP2 and your PrimaryLine is set to SP2, dialing without **2 does go out SP2, but not via this rule. Sorry if you already know and understand this.
I don't have a VoIP provider that permits setting CallerID, so I can't try anything here.
QBZappy:
VaHam,
I think there is some confusion over what you think "spoofed caller number" means and what the Admin manual definition of it is.
In the context of the user we expect that term to mean passing our Caller ID info to the party receiving our call.
In the case of the manual (P115-116) I believe it means to pass a "spoofed" telephone number over the digimap to replace the digits which were dialed.
Good examples of spoofed caller number
http://www.obitalk.com/forum/index.php?topic=339.0
{(<411:18002464411>):sp1},
In this context dialing 411 will be replaced (or spoofed) with 18002464411 over SP1
I think they could have used another term to express that concept. It has a dual meaning, which would obviouly create some confusion.
Any other takes on this.
RonR:
QBZappy,
I more inclined to think you're confused. :)
CallerID spoofing is not the same as number substitution in a DigitMap.
From the OBi Device Administration Guide:
terminal := PHx OR AAx OR LIx(arg) OR SPx(arg) OR PPx(arg) (arg object is optional)
arg := cid > target
- spoofed-caller-number is a literal string, such as 14081112233, to be used as the caller number for making a new call on the specified trunk
More notes on the arg, cid, and target objects:
- The cid object inside an arg object is optional. If omitted, it implies no caller-ID spoofing when making the call on the specified trunk. The succeeding ‘>’ can be omitted is cid is omitted
- 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
- arg object is optional. If omitted, it implies the arg with the target $2 and no cid. If arg is omitted, the succeeding parentheses ( ) can be omitted also.
QBZappy:
RonR,
Quote from: RonR on April 11, 2011, 10:20:06 pm
From the OBi Device Administration Guide:
- spoofed-caller-number is a literal string, such as 14081112233, to be used as the caller number for making a new call on the specified trunk
Is this not an example of above mentioned statement?
Example:
{(<411:18002464411>):sp1},
In this context dialing 411 will be replaced (or spoofed) with 18002464411 (<-literal string) over SP1 (Trunk)
QBZappy:
RonR,
Quote from: RonR on April 11, 2011, 10:20:06 pm
CallerID spoofing is not the same as number substitution in a DigitMap.
I didn't say that it was.
I reread that section of the manual (P115-116) and that is the impression I get of what they are trying to convey.
However I can see how you could interpret this to mean Celler ID spoofing.
{(<**2:>(Msp2)):sp2(14151234567>)}
Note the Admin guide uses the term "spoofed-caller-number" as opposed to spoofed caller ID. I think there it is subtle difference in meaning.
Navigation
[0] Message Index
[#] Next page
[*] Previous page