[Spce-user] No audio with RTP Proxy activated

Robert Cuaresma rcuaresma at telcon.es
Tue Jun 28 10:19:17 EDT 2016


Dear all,

I have an issue with RTP Proxy activated with "Plain SDP Option" on SPCE v2.8. I will try to explain it:

- The SPCE is working behind NAT with Public IP configured on "Advertised IP" parameter in "Network.yml" file.
- Subscribers (Asterisk PBX) are in the same LAN of SPCE (172.16.20.x).
- IP of the SipWise eth0 is 172.16.20.2
- Advertised IP configured on network.yml file is XX.XX.144.197 (Public IP Natted to SipWise)

On the Peering Server configuration I have configured "Never" on RTP-Proxy parameter and it works fine and have audio on both ways, but if I configure "Always with plain SDP" I have no audio on both ways.

I traced the two scenarios and I saw some differences on SDP that can be the problem but I don't know how to solve it:

Scenario A) Peer Server with RTP-Proxy OFF: (Works fine. Audio on both ways)
Packet from SipWise (172.16.20.2) to Asterisk PBX (172.16.20.18)
Session Description Protocol
    Session Description Protocol Version (v): 0
    Owner/Creator, Session Id (o): Sonus_UAC 16711 1779 IN IP4 XX.XX.162.77 (Public IP Address of Peering Server)
    Session Name (s): SIP Media Capabilities
    Connection Information (c): IN IP4 XX.XX.162.75 (Public IP Address of Peering Server)
    Time Description, active time (t): 0 0
    Media Description, name and address (m): audio 27528 RTP/AVP 18 101
    Media Attribute (a): direction: passive
    Media Attribute (a): rtpmap:18 G729/8000
    Media Attribute (a): fmtp:18 annexb=no
    Media Attribute (a): rtpmap:101 telephone-event/8000
    Media Attribute (a): fmtp:101 0-15
    Media Attribute (a): sendrecv
    Media Attribute (a): ptime:20

Scenario B) Peer Server with RTP-Proxy ON Always with Plain SDP (No audio on both ways)
Packet from SipWise (172.16.20.2) to Asterisk PBX (172.16.20.18)
Session Description Protocol
    Session Description Protocol Version (v): 0
    Owner/Creator, Session Id (o): Sonus_UAC 27951 31561 IN IP4 XX.XX.144.197 (Advertised IP on SipWise network.yml)
    Session Name (s): SIP Media Capabilities
    Connection Information (c): IN IP4 XX.XX.144.197 (Advertised IP on SipWise network.yml)
    Time Description, active time (t): 0 0
    Media Description, name and address (m): audio 39266 RTP/AVP 18 101
    Media Attribute (a): direction: passive
    Media Attribute (a): rtpmap:18 G729/8000
    Media Attribute (a): fmtp:18 annexb=no
    Media Attribute (a): rtpmap:101 telephone-event/8000
    Media Attribute (a): fmtp:101 0-15
    Media Attribute (a): sendrecv
    Media Attribute (a): ptime:20
    Media Attribute (a): rtcp:39267

I think that on Scenario B, the Connection Information will be contain the private IP address (172.16.20.2) of the SipWise eth0 instead of "Advertised IP" configured on "Network.yml". I'm correct? On affirmative case, how can I solve this?

Thanks!

Robert Cuaresma.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160628/d994e5ca/attachment.html>


More information about the Spce-user mailing list