Does SIP scanner method #4 work with ringto?

(1/3) > >>

noHatNoCattle:
I can't receive calls after implementing the fix for SIP scanners shown below:

Change the (Voice Services)SPn Service->X_InboundCallRoute: from {ph}, if that is what it currently is, to {>('Insert your AuthUserName here'):ph}

Has anyone got this fix to work using ringto??

The SIP scanner fix is described in method #4 in the link below.

https://www.obitalk.com/forum/index.php?topic=5467.msg35387#msg35387

azrobert:
First, use format {>username:ph}
No quotes or parentheses.
If you want an explanation, ask.

Sometimes the username sent is not the same as AuthUserName.
Here is a trick you can do to determine the username.
Temporarily add {sp1($2@192.168.1.199)}, to the beginning of your InboundCallRoute, then call your provider number.
$2 is a variable that contains the username.
The call will fail because of the dummy IP address.

The OBi call history will show the username.
Log into your OBi using the Web interface.
In your internet browser enter the IP address of your OBi.
UserID is admin
Click Status
Click Call History

You will see the OBi trying to route the call to username@192.168.1.199

noHatNoCattle:
Thanks for the reply azrobert.

When I login via the browser using the OBI IP address, what do I put in for username and password?  Here's the dialog on the screen:

A username and password are being requested by http://xxxxxxxx. The site says: "admin@OBi110"

username: ?
password: ?

gderf:
username: admin
password: admin

noHatNoCattle:
Thanks gderf and azrobert !!  Phone works now with new InboundCallRoute set (no ticks or parenthesis).  Now time will tell if the SIP scanner calls stop.

Navigation

[0] Message Index

[#] Next page