[asterisk-dev] [Code Review] Remove need forregistration strings in sip.conf

[Nick Lewis]

>Out of curiosity, how does this 
>work with realtime peers?
>Will there be some syntax telling 
>asterisk "pre-load peers named 
>AAA and BBB" to force their 
>registration (given they have 
>register=yes in options) ?

Hmmm dunno. To be honest I am not very familiar with realtime. I guess
if realtime only loads in response to an incoming invite then it is not
going to work. Previous versions supported peer callbackextension so
maybe there is already a solution or maybe callbackexten was not valid
in realtime. 

Perhaps at startup the database could be searched for realtime peers
with register=yes and have them temporarily loaded just to do the
sip_register(). Once they are in the sip_registry list then they may be
safe. Can you make a suggestion

-- N_L

-----Original Message-----
From: asterisk-dev-bounces at lists.digium.com
[mailto:asterisk-dev-bounces at lists.digium.com] On Behalf Of Dmitry
Andrianov
Sent: 17 June 2010 19:40
To: Asterisk Developers Mailing List; DavidVossel
Subject: Re: [asterisk-dev] [Code Review] Remove need forregistration
strings in sip.conf

Out of curiosity, how does this work with realtime peers?
Will there be some syntax telling asterisk "pre-load peers named AAA and
BBB" to force their registration (given they have register=yes in
options) ?

-----Original Message-----
From: asterisk-dev-bounces at lists.digium.com
[mailto:asterisk-dev-bounces at lists.digium.com] On Behalf Of Nick Lewis
Sent: Thursday, June 17, 2010 7:02 PM
To: David Vossel
Cc: Asterisk Developers; Nick Lewis
Subject: Re: [asterisk-dev] [Code Review] Remove need for registration
strings in sip.conf


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/718/
-----------------------------------------------------------

(Updated 2010-06-17 10:01:52.894512)


Review request for Asterisk Developers and David Vossel.


Changes
-------

Addressed comments from dvossel


Summary
-------

This change adds the ability to specify the sip registration expiry and
registrar host to the peer configuration items. This permits all
registration details that are available to the registration string to be
also available to the peer definitions. The users of sip.conf can enable
registration by setting register=yes in the peer and do not need to
concern themselves with the strange format of the registration strings

Suggest inclusion in 1.8


Diffs (updated)
-----

  trunk/channels/chan_sip.c 268968 
  trunk/channels/sip/config_parser.c 268968 
  trunk/channels/sip/include/sip.h 268968 
  trunk/configs/sip.conf.sample 268968 

Diff: https://reviewboard.asterisk.org/r/718/diff


Testing
-------

Compile, run and confirm in cli sip show registry


Thanks,

Nick


-- 
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev

-- 
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev

______________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
______________________________________________________________________

_____________________________________________________________________
This message has been checked for all known viruses by Star Internet delivered through the MessageLabs Virus Control Centre.
_____________________________________________________________________
Disclaimer of Liability
ATL Telecom Ltd shall not be held liable for any improper or incorrect use of the  information described and/or contained herein and assumes no responsibility for anyones use  of the information. In no event shall ATL Telecom Ltd be liable for any direct, indirect,  incidental, special, exemplary, or consequential damages (including, but not limited to,  procurement or substitute goods or services; loss of use, data, or profits; or business  interruption) however caused and on any theory of liability, whether in contract, strict  liability, or tort (including negligence or otherwise) arising in any way out of the use of  this system, even if advised of the possibility of such damage.

Registered Office: ATL Telecom Ltd, Fountain Lane, St. Mellons Cardiff, CF3 0FB
Registered in Wales Number 4335781

All goods and services supplied by ATL Telecom Ltd are supplied subject to ATL Telecom Ltd standard terms and conditions, available upon request.