asterisk users - May 2008 - How to do not use Asterisk internal DB for SIP register?

Hello,

We are using Asterisk Realtime and when registering SIP device in current
versions we noticed that:

1. Asterisk internal DB always holds info about registration, e.g.: "show
database" shows something like: 
	/SIP/Registry/106      :
193.138.yyy.xxx:62501:1800:106:sip:106 at 193.138.yyy.xxx:5060
2. None of the related settings in sip.conf (rtcachefriends, rtsavesysname,
rtupdate, rtautoclear, ignoreexpire) are affecting this behaviour, e.g.
"show database" ALWAYS holds registration info.
3. "fullcontact" field in DB is not populated when rtcachefriends is
off.

This behaviour totally ruins dynamic SIP registation when
"fullcontact"
should be put into external realtime database.

We are not using sip caching which ruins purpose for realtime.

Question would be:

How to do not use Asterisk internal DB for SIP register and have
"fullcontact" field populated in DB _WITHOUT_ rtcachefriends = yes?


Thank you for your future help.


Regards,
Mindaugas Kezys
http://www.kolmisoft.com

Hi,

I don't fully understand your set up, my understanding is that if you
use realtime with the cache settings off you should be fully reliant
on the external db and not use the Asterisk internal db at all.

However that aside in my case I take the registration traffic
completely away from Asterisk and let my customised SIP Registrar
handle it. The SIP Registrar updates the fullcontact and outboundproxy
fields on the realtime database and that provides Asterisk with all
the info it needs to contact the SIP accounts. It also lets Asterisk
concentrate on media operations which it is very good at and offloads
SIP registrations and NAT keep alives which it is poor at.

Regards,

Greyman.