I did next: 1. Only Kamailio take care about registration. My Asterisk dont know nothing about who is registered and who is not. Asterisk just forward calls to Kamailio and care about response. 2. All calls from Kamailio are accepted from Asterisk as authorized calls - by IP of Kamailio. 3. I did couple of tricks to handle some problems with reentrant ACK/BYE messages. But as I see - this is in your future. I can suggest to follow same strategy - keep registration in Kamailio only, and let Asterisk to do its specific job.
On Tue, Apr 23, 2013 at 6:28 AM, Henning Bragge <henning.bra...@oskall.com>wrote: > Hi, > > I'm totally new to Kamailio and I attempt to add Kamailio functionality to > an already working Asterisk implementation. > > I have been following this link: > http://kb.asipto.com/asterisk:realtime:kamailio-3.3.x-asterisk-10.7.0-astdb > > Everything seems to work with an exception of encountering NAT issues. The > location table in Kamailio reports the local NAT address, instead of the > public address, where then Asterisk reports UNREACHABLE status. > > I have installed and started RTPproxy as adviced in the above link - no > changes. > > Best regards, > > Henning Bragge > > _______________________________________________ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users@lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users > >
_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
