SIP scanners
jazzy:
I use Obi100 and receive incoming calls from an IPKALL number, registered
with Getonsip. Receiving calls just fine, but now I want to add method #4
to thwart sip scanners.
I thought I understood what string to place in my inbound call routing.
So I did this:
X_InboundCallRoute: {>('my_auth_user_name'):ph}
the authusername I'm using comes right from my SIP credentials
from the SIP Credentials page on the Obi
and yes, authusername are alpha/numeric
Can this method work with my Getonsip account with the IPKall # ?
currently calls do not ring my Obi with this string in the Inboundcallroute.
Suggestions?
gderf:
I have
{>123456789:ph}
Where 123456789 is my_auth_user_name
jazzy:
My authusername is Alphanumric.
when I place this in the X inbound call route
{>('myauthusername28'):ph} the attached phone does not ring.
I'm getting myauthusername28 right from SP2 SIP credentials
authusername. Sp2 is using Getonsip (from an IPKALL # )
Does method #4 not work with authusernames from Getonsip?
gderf:
Why don't you try it without the parentheses and single quotes?
drgeoff:
Quote from: jazzy on February 03, 2014, 03:24:56 pm
My authusername is Alphanumric.
when I place this in the X inbound call route
{>('myauthusername28'):ph} the attached phone does not ring.
I'm getting myauthusername28 right from SP2 SIP credentials
authusername. Sp2 is using Getonsip (from an IPKALL # )
Does method #4 not work with authusernames from Getonsip?
Your format is correct so the next suspect is that the username you expect is not coming in. Have a look at your call history to see what is shown against an incoming call. Or perhaps call status during an incoming call call throw some light. Revert your InboundCallRoute to ph for those test calls.
Navigation
[0] Message Index
[#] Next page
[*] Previous page