[Spce-user] multiple ethernet interfaces on SIPwise CE

[Bob Fryer]

Jon & Daniel,

Thank you for your timely replies, they were very much appreciated, even if it was to confirm the inevitable.

Just in case anyone else is reading this thread, we placed a "proxy" between Sipwise and the Carrier as it was an easy solution, and it worked as soon as we got the configuration right.

However, longer term we are looking at running two instances of mediaproxy as suggested by Daniel. I will run this up on the test system to look at this in more detail.

Again thank you for your replies.

Regards

Bob




-----Original Message-----
From: spce-user-bounces at lists.sipwise.com [mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Jon Bonilla (Manwe)
Sent: Wednesday, 26 June 2013 11:22 PM
To: spce-user at lists.sipwise.com
Subject: Re: [Spce-user] multiple ethernet interfaces on SIPwise CE

El Wed, 26 Jun 2013 11:25:23 +1000
"Bob Fryer" <bob at netintegrity.com.au> escribió:


>     extra_sockets:
> 
>       telcoprivateint: udp: 10.23.215.20:5060
> 
>  
> 
> and set this as selected in the Peer (outbound Socket)
> 
>  
> 
> ok we now have SIP flowing to the carrier. We can make a call out, 
> phone rings on other end, person picks up....all the SIP Signalling working.
> However no Voice either way.
> 
> Confirmed that RTP is using the eth1 interface and  not over the 
> private link(eth2). Main issue is that RTP negotiation in the SDP is 
> showing coming from the Eth1 interface and appears no way of overriding this.
> 
>  
> 
> Any proven ideas on correcting this issue?
> 
> Any confirmation that we generally understand the issue correctly? We 
> are not seasoned professionals with SIP but strong IP Networkng 
> skills, but have a reasonable handle on sip, but first time on 
> SIPwise. My wording may not be correct either as writing this quicker 
> than I would like.
> 

extra_sockets will help you in case the peer has firewalled the sip signaling but accepts the rtp traffic as offered in SIP. In case you need the rtp to go through the tunnel, you'd better set up that tunnel against your peer in a router and use it as default gateway.

I've seen this scenario in many operators sending traffic to BT, which asks for dedicated tunnel for SIP/RTP traffic.


>  
> 
> Any Assistance or thoughts would be appreciated, even if it is 
> confirmation that we have no choice but to place another SIP Proxy 
> between SIPwise and Private Peer.
> 

That's another choice, right.