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
domainName.data(), // sipProxyServers
NULL, // sipDirectoryServers
NULL, // sipRegistryServers
NULL, // authenicateRealm
NULL, // authenticateDb
NULL, // authorizeUserIds
NULL, // authorizePasswords
lineMgr, // lineMgr
SIP_DEFAULT_RTT, // sipFirstResendTimeout
TRUE, // defaultToUaTransactions
-1, // readBufferSize
OsServerTask::DEF_MAX_MSGS, // queueSize
FALSE // bUseNextAvailablePort
),
As per header documentation for PORT_DEFAULT in the SipUserAgent header
//! Constructor
/*! Sets up listeners on the defined ports and IP layer
* protocols for incoming SIP messages.
* \param sipTcpPort - port to listen on for SIP TCP messages.
* Specify PORT_DEFAULT to automatically select a port, or
* PORT_NONE to disable.
* \param sipUdpPort - port to listen on for SIP UDP messages.
* Specify PORT_DEFAULT to automatically select a port, or
* PORT_NONE to disable.
* \param sipTlsPort - port to listen on for SIP TLS messages.
* Specify PORT_DEFAULT to automatically select a port, or
* PORT_NONE to disable.
Unfortunately the only solution right now is you get that app away from
that port range or to get the port range away from the app :-(. I'll
see what I can do to expedite a fix.
Joegen
On Thursday, 04 November, 2010 11:07 PM, Joe Micciche wrote:
> -----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 wrote:
>> 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 {
>>>>> DatagramSocket sock = new DatagramSocket(i,
>>>>> localAddr);
>>>>> sock.close();
>>>>> } catch (Exception ex) {
>>>>> logger.error(String.format("Failed to bind to %s:%d",
>>>>> localAddr, i), ex);
>>>>> throw ex; ///<----- Simply comment this out and we
>>>>> are good to go.
>>>>> }
>>>>> }
>>>>>
>>>>>
>>>>> if everyone concur, we can patch this right away
>>>>>
>>>>>
>>>>>
>>>>> On Thursday, 04 November, 2010 11:08 AM, Joegen Baclor wrote:
>>>>>
>>>>>
>>>>>>> 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 there any other corresponding errors in the sipx bridge logs?
>>>>>>>>>
>>>>>>>>> -M
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>>>>>> Joe Micciche<[email protected]> 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 -> Services -> Media Relay:
>>>>>>>>> Standard error
>>>>>>>>> * log4j:WARN No appenders could be found for logger
>>>>>>>>> (org.sipfoundry.sipxrelay).
>>>>>>>>> * log4j:WARN Please initialize the log4j system properly.
>>>>>>>>> * Port range upper bound - Port range lower bound should be a
>>>>>>>>> multiple of 4
>>>>>>>>>
>>>>>>>>> sipxrelay.log shows: (x and xxx used to hide stuff)
>>>>>>>>> "2010-11-03T18:15:56.408000Z":1:JAVA:INFO:xxx.xxx.com:main:00000000:sipxrelay:"Checking
>>>>>>>>>
>>>>>>>>> port range 32000:65535"
>>>>>>>>> "2010-11-03T18:15:56.521000Z":2:JAVA:ERR:xxx.xxx.com:main:00000000:sipxrelay:"Failed
>>>>>>>>>
>>>>>>>>> to bind to /x.x.x.x:34977"
>>>>>>>>> java.net.BindException: Address already in use
>>>>>>>>> at java.net.PlainDatagramSocketImpl.bind0(Native Method)
>>>>>>>>> at
>>>>>>>>> java.net.PlainDatagramSocketImpl.bind(PlainDatagramSocketImpl.java:82)
>>>>>>>>>
>>>>>>>>> at java.net.DatagramSocket.bind(DatagramSocket.java:372)
>>>>>>>>> at java.net.DatagramSocket.<init>(DatagramSocket.java:211)
>>>>>>>>> at java.net.DatagramSocket.<init>(DatagramSocket.java:262)
>>>>>>>>> at
>>>>>>>>> org.sipfoundry.sipxrelay.SymmitronServer.start(SymmitronServer.java:1779)
>>>>>>>>>
>>>>>>>>> at
>>>>>>>>> org.sipfoundry.sipxrelay.SymmitronServer.main(SymmitronServer.java:1843)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> What else would be pertinent to help debug this? TIA for any
>>>>>>>>> pointers.
>>>>>>>>>
>>>>>>>>>
>> -- ==================================================================
>> Joe Micciche [email protected]
>> Red Hat, Inc. http://www.redhat.com
>> Senior Communications Engineer X(81) 44554
>> +1.919.754.4554 Key: 65F90FE1
>> ==================================================================
>>
>>
> _______________________________________________
> sipx-users mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>
>>>
> - --
> ==================================================================
> Joe Micciche [email protected]
> Red Hat, Inc. http://www.redhat.com
> Senior Communications Engineer X(81) 44554
> +1.919.754.4554 Key: 65F90FE1
> ==================================================================
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkzSzDYACgkQJHjEUGX5D+HR3ACfZh86n8RYZVX4FErBGxTnFfm7
> qREAnjQLQ+ZBzAtLqtc0jmmnup7dmfYI
> =w1CX
> -----END PGP SIGNATURE-----
>
>
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/
