[Spce-user] New type sip_ext_incoming available in network.yml

Jon Bonilla (Manwe) manwe at sipdoc.net
Fri May 13 11:40:49 EDT 2016


El Thu, 12 May 2016 19:30:57 +0200
Alex Lutay <alutay at sipwise.com> escribió:

> On 05/12/2016 06:38 PM, Jon Bonilla (Manwe) wrote:
> ...
> > Anyway I wouldn't have pushed this to version 3.8.X.  It changes the system
> > behaviour and may cause issues after upgrade which should be transparent
> > IMHO.  
> 
> AFAIK, the default behaviour is not changed as sip_ext_incoming is not
> defined in network.yml by default. Isn't it?
> 


But you stop being able to rceive incoming SIP traffic via the defined
extra_sockets, right?

I understtod that now extra_sockets is for outgoing traffic only and if you
want to receive traffic you need to declare it via sip_ext_incoming. So if you
have peers sending incoming traffic to the extra socket that wouldn't work any
longer. isn't it?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: Firma digital OpenPGP
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160513/59fb8f6f/attachment-0001.sig>


More information about the Spce-user mailing list