Re: [reSIProcate-users] phone compatible RTC setup

[Scott Godin <sgodin@xxxxxxxxxxxxxxx>]

You would need to manually add a route for each user with a non-dialable AOR.  ie:

sip:1234@xxxxxxxxxx -> sip:user@xxxxxxxxxx

Since you are using MySQL you could probably craft up a SQL statement to do this for you.  Just keep in mind that the route table is only read on startup, so you would need to trigger a restart of the proxy when the table is updated.

Scott

Scott

On Tue, Jun 16, 2015 at 9:19 AM, Wolfgang Rosenauer <wolfgang.rosenauer@xxxxxxxxxx> wrote:

Hi,

I'm using repro basically as outlined on http://rtcquickstart.org/.
The system works pretty much with JS communicator and WebRTC but now I'm
wondering if the voice part can be "hardware compatible".

What I mean is:
My users have now SIP addresses equal their email addresses which is no
problem for the JS communicator solution.
I'm wondering if I can use the same setup to connect SIP phones to it as
well.
So one of the first things would be routes reflected by numbers.
All my users are read from MySQL. Can I also get a route configuration
using numbers from the database?
How would that work?


Thanks,
 Wolfgang
_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/