Re: [reSIProcate-users] How to direct some SIP traffic towards IP addresses other than the outbound proxy ?

[Scott Godin <sgodin@xxxxxxxxxxxxxxx>]

You can use a different profile (without an outbound proxy set) for subscriptions then for other traffic. 

 https://www.resiprocate.org/DUM_Configuration_and_Profiles

Scott

On Tue, Feb 18, 2014 at 2:59 PM, Julio Cesar Esteves Cabezas <jcabezas@xxxxxxxxxxxxx> wrote:

Hi,

The question:
  How can we intercept and handle, in the code, SUBSCRIBE/NOTIFY SIP
messages sent from an UA built upon recon/DUM/resip, before sending them in
wire to achieve directing them to specific IP addresses (peer UAs) other
than that of the configured outbound proxy (an SBC) ?

  The "conventional" SIP traffic (registration, calls) must still be
directed towards the outbound proxy.

The background:
  We are deploying a system with a SBC that mediates all SIP traffic.
  The UAs are built upon recon/dum/resiprocate and use heavily exchange
SUBSCRIBE/NOTIFY to share "realtime" communication state between them.
  But the SBC CPU is being overloaded by that SUBSCRIBE/NOTIFY traffic.
  So, we intend to make the SUBSCRIBE/NOTIFY traffic peer-to-peer between
UAs.
  We have system support to inform each UA of the IP addresses of its
subscription peers.

Best regards,
Julio.

_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/