Bad idea #1 :
Allow for other processes to grab ports in the range reserved for sipXrelay
and deal with it on the fly. Reason: Posted already. FAIL configtest if port
range is specified in ephemeral range.
Bad idea #2:
A single port to multiplex all RTP traffic. Would fail for firewalls that
ran
A fixed port would probably work best from a firewall perspective.
On May 23, 2011 11:58 AM, "Mircea Carasel" wrote:
> On Mon, May 23, 2011 at 2:37 PM, George Niculae wrote:
>
>> Hi All,
>>
>> I'm investigating http://track.sipfoundry.org/browse/XX-9189 so I'm
>> resurrecting
>> http://thread.gma
On Mon, May 23, 2011 at 2:37 PM, George Niculae wrote:
> Hi All,
>
> I'm investigating http://track.sipfoundry.org/browse/XX-9189 so I'm
> resurrecting
> http://thread.gmane.org/gmane.comp.telephony.pbx.sipfoundry.general/30441
> discussion...
>
> I managed to recreate the issue on my machine by
Hi All,
I'm investigating http://track.sipfoundry.org/browse/XX-9189 so I'm
resurrecting
http://thread.gmane.org/gmane.comp.telephony.pbx.sipfoundry.general/30441
discussion...
I managed to recreate the issue on my machine by specifying the UDP
range 31000 - 44000 and restarting prompted service
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Just to follow up, it seems that if sipregistrar binds to a lower port
than sipxrls, I can set NAT to use all ports up to the sipxrls random
high port - apparently sipregistrar binding to a high UDP port does not
cause Media Relay to fail with "Port in
It's not a mystery. The client user agent for RLS is set to grab a
random port.
mClientUserAgent(
PORT_DEFAULT, // sipTcpPort
PORT_DEFAULT, // sipUdpPort
PORT_DEFAULT, // sipTlsPort
NULL, // publicAddress
NULL, // defaultUser
bindIp, // defaultSipAddress
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
http://track.sipfoundry.org/browse/XX-9189
I'm mystified why this just started happening - any ideas? And while I
have a workaround, it is quite crippling to my user base to restrict the
RTP range.
joe
On 11/04/2010 10:41 AM, Joegen Baclor wrote:
>
Hey Joe,
Go ahead and create a jira ticket. We've received some info from Ranga
that this might have some undesired complications in other parts of the
code. We will investigate further and update the issue tracker accordingly.
Joegen
On Thursday, 04 November, 2010 09:49 PM, Joe Micciche wro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joegen, do you want me to open a case for this or have you already?
> This is a one liner fix in the relay code.
>
> for (int i = config.getPortRangeLowerBound(); i < config
> .getPortRangeUpperBound(); i++) {
> try {
>
On Wed, Nov 3, 2010 at 11:13 PM, Joegen Baclor wrote:
> This is a one liner fix in the relay code.
>
> for (int i = config.getPortRangeLowerBound(); i < config
> .getPortRangeUpperBound(); i++) {
> try {
> DatagramSocket sock = new DatagramSocket(i, loca
This is a one liner fix in the relay code.
for (int i = config.getPortRangeLowerBound(); i < config
.getPortRangeUpperBound(); i++) {
try {
DatagramSocket sock = new DatagramSocket(i, localAddr);
sock.close();
} catch (Except
AFAIK, not being able to bind to all ports in the range must not result
to a process shutdown of the symmitron. This exception should be benign
and the media relay should just go grab the next available port. Do you
concur?
On Thursday, 04 November, 2010 04:02 AM, Matt White wrote:
Are the
I'm not sure if the symptoms match exactly, but I ran into a problem like this
last year, where the ports were not being released properly. See
http://forum.sipfoundry.org/index.php?t=msg&goto=43359&S=6a0a2c7c1ad6dd91dd6f5ea6aad822f6&srch=Error+message+from+sipxBridge#msg_43359
My problem was d
On 11/03/2010 04:04 PM, sipx-users-requ...@list.sipfoundry.org wrote:
> Date: Wed, 03 Nov 2010 16:02:43 -0400
> From: "Matt White"
> Subject: Re: [sipx-users] sipX Media Relay died
> To:
> Message-ID: <4cd187a202f1c...@firewall.thesummit-grp.com>
> Con
To follow up, sipxrls is binding to a udp port that is on the range of
our RTP (UDP) ports; which then prevents Media Relay from starting.
As a test I've defined 31000 - 44000 for RTP, started services and Media
Relay fails.
netstat -lnpu:
udp0 0 10.11.45.10:35265 0.0.0.0:*
Are there any other corresponding errors in the sipx bridge logs?
-M
>>> Joe Micciche 11/03/10 3:05 PM >>>
Not sure what happened but Media Relay died yesterday. No changes were
made to the system.
sipXconfig (4.2.1-018971.dhubler 2010-08-21T04:59:18 build34) on
CentOS5.5 iso.
Under Servers ->
Not sure what happened but Media Relay died yesterday. No changes were
made to the system.
sipXconfig (4.2.1-018971.dhubler 2010-08-21T04:59:18 build34) on
CentOS5.5 iso.
Under Servers -> Services -> Media Relay:
Standard error
* log4j:WARN No appenders could be found for logger
(org.sipfound
17 matches
Mail list logo
