new Caller-ID spoofing inquiry over SIP for Obi 110
rob613:
This forum shows an old topic somewhat similar to this, but over PSTN.
I would like to get some guidance for how to use Caller-ID spoofing over a SIP forward that I am testing.
I have enabled the spoofing (field X_SpoofCallerID) in both the ITSP profiles for SIP.
My inbound call route is the following:
{(Mtesting):vg3(9991234)},{(Mreject):sp1(2125551234)}...
As I will explain, what else should I put near vg3 to enable spoofing the call with the Caller-ID of the call that matches my "testing" digit map?
My VG3 uses the technique listed in another thread for tf.callwithus.com for toll-free calls.
When I receive a call on my PSTN line that matches a known set of Caller-ID's, I want to forward them through to a specific SIP URI, such as my softphone. This forwarding is working but I want to do it so that the call will come through with the original call's Caller-ID, not the caller ID of my SP service.
My forward is working via the LINE port InboundCallRoute. Within the parameter I am calling out through a VG because I am using a different SIP configuration than my normal SP configuration.
By using a digitmap for the set of CID's that I want to match and forward I suspect that I can use a backreference, and that I will need to use the > character within the forward rule.
And since this is receiving CID with Name on my PSTN line, and I am spoofing a SIP call to a SIP extension, is there anything more I need to do so that the CID-Name field will be populated within the SIP header? Are there any other SIP header fields I can fill out to try to distinguish that this is my PSTN line's received calls?
When I am home I am likely to answer these calls on my regular phone handset, but if I am away, but have a SIP phone with me and online, I think I should be able to easily answer my ringing PSTN line from a remote location with this technique. Question: will the Obi take my PSTN line off hook only when the SIP call answers?
And for calls that I want to reject, I already have another rule in place (discussed in another thread), for calls from known telemarketers who have been told to not call my PSTN line again. I still enjoy this when the Obi spares me from having to answer such calls. I would like to add the CID spoofing capability there as well.
QBZappy:
rob613,
Quote from: rob613 on November 21, 2012, 09:48:23 am
..., not the caller ID of my SP service.
You may need to find a CID spoofing friendly service provider. Most SPs prevent CID spoofing. I know that voipms, and a few others allow it.
tmetro:
Quote from: QBZappy on November 21, 2012, 09:53:25 am
You may need to find a CID spoofing friendly service provider.
This can be true if you are using a VoIP provider to gateway to PSTN. In that case you are dependent on the VoIP provider to permit you to spoof a CID, which they in turn send as part of the PSTN call.
To clarify, in this situation Rob is making a connection from an OBi to a SIP end-point, and the only party involved in the spoofing is the OBi.
-Tom
QBZappy:
rob613,
This might help:
http://www.obitalk.com/forum/index.php?topic=530.msg3269#msg3269
Re: Inbound call routing issue: $1 not working
Quote from: obi-support2 on March 31, 2011, 03:01:36 pm
OBi passes both, name and number, from the original call, if X_SpoofCallerID is yes.
ITSP however might not take it, and may reject the call all together. That's why
this is option depending on your ITSP.
However, using the SP2(xyz > abc) syntax in an InboundCallRoute, it can only spoof the number; we currently don't have a syntax for spoofing a name this way.
Also, even when we spoof it, the ITSP can selectively take the name or number part as they please and present the call to the final destination.
You have more control if the "ITSP" is a PBX (like Asterisk) for example. I do not expect this option to be very useful for a general commercial ITSP.
tmetro:
Quote from: rob613 on November 21, 2012, 09:48:23 am
I have enabled the spoofing (field X_SpoofCallerID) in both the ITSP profiles for SIP.
I didn't see mention of that in the documentation as being necessary in order to use CID spoofing in the InboundCallRoute. That's not to say it isn't, as the documentation could be deficient.
The impression I get from the documentation for X_SpoofCallerID is that it is used when the OBi is gatewaying a call from PSTN to a VoIP outbound trunk line. It isn't clear whether this is orthogonal to the InboundCallRoute rules, or whether it merely establishes a default behavior.
Quote
My inbound call route is the following:
{(Mtesting):vg3(9991234)},{(Mreject):sp1(2125551234)}...
Lets simplify. Only one of these is relevant to the question at hand:
{(Mtesting):vg3(9991234)}
Quote
As I will explain, what else should I put near vg3 to enable spoofing the call with the Caller-ID of the call that matches my "testing" digit map?
...forwarding is working but I want to do it so that the call will come through with the original call's Caller-ID, not the caller ID of my SP service.
...that I will need to use the > character within the forward rule.
Right, so the expression becomes:
{(Mtesting):vg3($1>9991234)}
At least that's what the administrator's guide leads me to believe. The documentation for InboundCallRoute says:
Code:
terminal := PHx OR AAx OR LIx(arg) OR SPx(arg) OR PPx(arg)
arg := cid > target
cid := spoofed-caller-number OR $1
target = number-to-call OR $2
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
$1 is an internal variable containing the value of the caller number of this inbound call,
after any digit map transformation in the matched caller object of the matched peering
object in the peering-list.
But my understanding is that you've tried this, and it didn't work.
-Tom
Navigation
[0] Message Index
[#] Next page