[asterisk-users] asterisk registrations by SER proxy

[Sammy Govind]

Hi again,

Asterisk could be aware of the registrations if the sipusers table is
shared with asterisk sip realtime, but then again the issue would remain
the same that asterisk want to authenticate the sip peer from
scratch..maybe try some Realtime configurations in sip.conf to avoid
authentications of clients having active register-expiry timer.

Already answered you prev. in other list to define a sip section for your
opensips

Regards,
Sammy.
On Mon, Dec 5, 2011 at 7:41 PM, Matt Hamilton <mistral9999 at hotmail.com>wrote:

>  I integrated Opensips with Asterisk Realtime (Asterisk sipusers/peers
> point to Opensips subscribe table via a view). Opensips handles the
> registrations. However, when a call comes in (INVITE is routed to
> Asterisk), it seems like Asterisk doesn't know about the user (or sees the
> users as not authorized), so can't create the SIP channel. (I use queues
> and conferencing also.)
>
> If I route the REGISTER to Asterisk after authorizing in Opensips,
> Asterisk does the authorization/registration again from scratch. In that
> case call goes through, but I end up duplicating the authorization process.
>
> I was hoping to take the load of handling registrations from Asterisk.  I
> know this is a very common scenario, but I'm not very clear about the
> process. Is it possible to make Asterisk be aware of those registrations
> made by the proxy server?
>
> Thanks,
> Matt
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> New to Asterisk? Join us for a live introductory webinar every Thurs:
>               http://www.asterisk.org/hello
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20111205/430321f2/attachment.htm>