Inbound call routing issue: $1 not working

(1/3) > >>

joshhighley:
SP2 is configured with voip.ms, which I have termination and a DID.

I have this for the inbound call routing:
{ph,SP2($1 > 5555555555)}
where 5555555555 is my cell phone number.  I've also enabled X_SpoofCallerID.  According to the admin guide (pgs 113-114), $1 is supposed to represent the caller number of the inbound call.  My intention is to simultaneously ring my cell phone and have it show the number of the caller.  The issue is that my cell phone is showing "Unavailable Number".  **However**, if I change $1 to a number, such as 1111111111, then it will show up correctly on my cell phone when the call is forwarded.  So, it appears that $1 is not working correctly, or at least not as I understand it.

Am I mis-understanding $1, or should I submit a support ticket?

obi-support2:
Can you try removing $1 >, that is just {ph,SP2(55555555555)}.

What is your obi's software version?

Thank you.

QBZappy:
joshhighley,

I was not able to get the caller number to pass using voip.ms. Best I could do was to pass caller name.

see thread:
http://www.obitalk.com/forum/index.php?topic=425.msg3134#msg3134


obi-support2,

What is "X_SpoofCallerID" supposed to spoof? Is there a way to get both Caller name and number to pass?

obi-support2:
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.


joshhighley:
when I removed the $1, the caller number was passed as I wanted.

For voip.ms users, note that I think you must clear out the caller id in their web configuration panel in the account settings (General tab I think) for them to accept the number from the obi.

Final issue is that when calling out, the caller number sent is the AuthUserName (6 digit id for voip.ms).  Is there anyway to set this? CallerIDName doesn't seem to do it.

Navigation

[0] Message Index

[#] Next page