[Spce-user] Hair-pinning through SPCE - Loss of RTP Traffic
gary at netdiverse.com
Mon Jul 14 19:34:41 EDT 2014
That solved it.
I really appreciate your assistance.
This message was sent from my mobile phone. Please excuse any typos or
On Jul 14, 2014 4:02 AM, "Andrew Pogrebennyk" <apogrebennyk at sipwise.com>
> On 14/07/14 06:29, Gary Nieboer wrote:
> > There is no NAT between the FreePBX and SPCE, The FreePBX and SPCE each
> > use their own IP address for media and signaling.
> > There are two carrier peers involved which both use different IP
> > addresses for media and signaling. There is also no NAT between the
> > carriers and SPCE. The signaling comes from a single IP at each
> > carrier, but a range of IPs for the media. The carriers' proxies
> > cannot reach the FreePBX IP address. Only the SPCE can reach both
> > FreePBX and Carriers without NAT.
> using different IPs for the signaling and media is not a problem.
> I think you should make a trace and compare it with rtp.log.
> > config.yml has the following line:
> > nattest_exception_ips ~
> > Is the above variable for potential media proxy IP address(es) or
> > signaling proxy IP address(es)
> those are signaling source IP addresses.
> > How do I define a range of IP addresses? Let's say I want to include
> > 10.0.0.0 - 126.96.36.199
> Ranges are not supported, but honestly speaking it's not needed. This
> option is usually needed only when sip:provider is deployed in private
> LAN behind SBC which is relaying the signaling and media from public
> internet to the sp:pro.
> > How do I define a list of unique IP addresses? Let's say I want to
> > include 10.5.6.7 10.11.12.13 and 188.8.131.52
> This is a list, one IP per line
> - 10.2.0.10
> - 10.2.0.12
> Or put on a single line:
> nattest_exception_ips: [10.2.0.10, 10.2.0.12]
> > Thanks for your assistance.
> > -Gary
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Spce-user