[Spce-user] Rtp source address changes after in-dialog, Invite

[Philipp Rekers]

Hi all,
Hi Chris,

I think my problem I mentioned on Fri, 1 May 2020 19:54:41 +0200, might 
be the same. I have a "dual stack", IPv4 and IPv6 Sipwise server running 
with mr8.5.1. My provider send re-invites when g722 is active. When a 
customer is on IPv6 the reinvite contains the sipwise IPv4 address in 
SDP c=IN IP4 field instead of IPv6 address. As a workaround I disabled 
g722 - so I get no reinivites.

So the problem seems to be not a specific two IPv4 RTP interface 
problem, but a generally two RTP interface problem. Here is my network.yml:

---
hosts:
   self:
     dbnode: '1'
     eth0:
       dns_nameservers:
       - 185.xxx.xxx.xxx
       - 8.8.8.8
       gateway: 185.xxx.xxx.xxx
       hwaddr: ca:xx:xx:xx:xx:xx
       ip: 185.xxx.xxx.xxx
       netmask: 255.255.255.248
       type:
       - web_ext
       - sip_ext
       - rtp_ext
       - web_int
       - ssh_ext
       v6ip: 2Axx:xxxx:xxx:x:0:0:0:4
     interfaces:
     - lo
     - eth0
     lo:
       cluster_sets:
       - default
       ip: 127.0.0.1
       netmask: 255.255.255.0
       shared_ip: []
       shared_v6ip: []
       type:
       - sip_int
       - ha_int
       - aux_ext
       - ssh_ext
       - api_int
       - rtp_int
       - stor_int
       v6ip: ::1
       v6netmask: 128
     role:
     - proxy
     - lb
     - mgmt
     - rtp
     - db
     - storage
     status: online
     swraiddevices: []
     sysdescr: ''
     syslocation: ''
     sysname: ''


Best regards!
Philipp Rekers


> Message: 1
> Date: Tue, 1 Sep 2020 21:18:04 +1200
> From: Chris Hoffmann <chris021 at gmail.com>
> To: Walter Klomp <walter at myrepublic.net>, spce-user at lists.sipwise.com
> Subject: Re: [Spce-user] Rtp source address changes after in-dialog
> Invite
> Message-ID:
> <CAN8EJkxy1r1g-HZcqeurZ4xtBjQTCZdK9kfQrSLzGEz-Ysg+oQ at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi,
>
> As you can see from my supplied config I have 2 x RTP interfaces Already
> and as previously explained all calls work perfectly with the only
> exception being when I get a re-invite without SDP. At this point sipwise
> decides to send media and SDP with its rtp_int_ens192 address.
>
> I have my rtp_ext in my subscriber / domain and my rtp_int_ens192 
> listed on
> my peer.
>
> I think this must be some sort of RTP proxy bug, but would ideally like
> someone to confirm it so I can work out exactly which version I will need
> to migrate to.
>
> Thanks,
>
> Chris
>
> On Monday, August 31, 2020, Walter Klomp <walter at myrepublic.net> wrote:
>