[Spce-user] Signalling and RTP on different Ips?

Jon Bonilla jbonilla at sipwise.com
Mon Jan 9 07:14:42 EST 2012

El Mon, 09 Jan 2012 11:18:43 +0100
Andreas Granig <agranig at sipwise.com> escribió:

> Hi,
> On 01/09/2012 10:48 AM, Israel Padron wrote:
> > I´m going to start playing with SipProviderCE, and I have a question,
> > it´s possible to do a sip trunk to another host sepparating the
> > signalling and the rtp? I mean send the signalling to op public ip, and
> > the rtp to another public ip. If yes, how can be this done?
> The SIP trunk just needs to properly announce its RTP IP in the SDP body
> of the INVITE or 200 message as usual. There is nothing to configure on
> the SPCE, since media is negotiated during the SIP session establishment.
> Andreas

I think Israel means using one IP for Sip and another Ip for mediaproxy.

Israel: By default no, the system uses the same ip for both. The one you
configure in config.yml as networking-->eaddress

You'll need to use customtt files to customize your spce system if you want
mediaproxy to listen a different ip address.


Quickly, without any warranties, I'd say that you need to change this file:


You'll need to change (hardcode) the ADDRESS parameter and set it to the
desired IP. Please, do create a customtt template for making this change
persistent instead of directly editing the file.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20120109/0ef4fd8d/attachment-0001.asc>

More information about the Spce-user mailing list