Increase RTP port range

[Dave May]

We ran out of available sessions on our sipXecs OpenACD server this
morning, so we increased the max-sessions from 1000 to 1500.
Predictably (at least in hindsight, that is), we then ran out of RTP
ports as the total number of channels in use went over 1000.



2012-07-26 08:25:02.389178 [CRIT] sofia_glue.c:1048 No RTP ports
available!



sipXecs changes the FreeSWITCH RTP range from its default of 16384-32768
to 11000-12998. Is there an underlying reason for this change, and are
there any known issues with changing it back to FS defaults in
/etc/sipxpbx/freeswitch/switch.conf.xml.vm?



Thanks,



Dave.



Dave May, ICCE

Manager, Information Technology

PATLive

800.659.7807 phone & fax

***@patlive.com <mailto:***@patlive.com>



Hosted Communications | Friendly Service www.patlive.com
<http://www.patlive.com/>

[Joegen Baclor]

You left out the most vital piece of information. How many calls do you
have physically active in space time? Is it about a 1000?

Post by Dave May
We ran out of available sessions on our sipXecs OpenACD server this
morning, so we increased the max-sessions from 1000 to 1500.
Predictably (at least in hindsight, that is), we then ran out of RTP
ports as the total number of channels in use went over 1000.
2012-07-26 08:25:02.389178 [CRIT] sofia_glue.c:1048 No RTP ports
available!
sipXecs changes the FreeSWITCH RTP range from its default of
16384-32768 to 11000-12998. Is there an underlying reason for this
change, and are there any known issues with changing it back to FS
defaults in /etc/sipxpbx/freeswitch/switch.conf.xml.vm?
Thanks,
Dave.
*Dave May, ICCE*
Manager, Information Technology
PATLive
800.659.7807 phone & fax
Hosted Communications | Friendly Service www.patlive.com
<http://www.patlive.com/>
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

[Dave May]

Sorry, there were approximately 800 inbound calls connected to 200
agents when the max-sessions limit was reached. Increasing max-sessions
to 1500 allowed the number of incoming calls to increase to 900, but
that resulted in a slew of the RTP errors listed below as well as
reports of one-way audio/dead air issues.



Dave.



From: Joegen Baclor [mailto:***@ezuce.com]
Sent: Thursday, July 26, 2012 12:34 PM
To: Discussion list for users of sipXecs software
Cc: Dave May
Subject: Re: [sipx-users] Increase RTP port range



You left out the most vital piece of information. How many calls do you
have physically active in space time? Is it about a 1000?


On 07/27/2012 12:19 AM, Dave May wrote:

We ran out of available sessions on our sipXecs OpenACD server
this morning, so we increased the max-sessions from 1000 to 1500.
Predictably (at least in hindsight, that is), we then ran out of RTP
ports as the total number of channels in use went over 1000.



2012-07-26 08:25:02.389178 [CRIT] sofia_glue.c:1048 No RTP ports
available!



sipXecs changes the FreeSWITCH RTP range from its default of
16384-32768 to 11000-12998. Is there an underlying reason for this
change, and are there any known issues with changing it back to FS
defaults in /etc/sipxpbx/freeswitch/switch.conf.xml.vm?



Thanks,



Dave.



Dave May, ICCE

Manager, Information Technology

PATLive

800.659.7807 phone & fax

***@patlive.com <mailto:***@patlive.com>



Hosted Communications | Friendly Service www.patlive.com
<http://www.patlive.com/>








_______________________________________________
sipx-users mailing list
sipx-***@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/

[Joegen Baclor]

11000-12998 <- This value only allows you 500 channels. RTP proxy
requires two ports for each leg. The main reason I could think of why
it was changed is to make sure that media relay rtp port range does not
conflict with freeswitch port range.

Post by Dave May
Sorry, there were approximately 800 inbound calls connected to 200
agents when the max-sessions limit was reached. Increasing
max-sessions to 1500 allowed the number of incoming calls to increase
to 900, but that resulted in a slew of the RTP errors listed below as
well as reports of one-way audio/dead air issues.
Dave.
*Sent:* Thursday, July 26, 2012 12:34 PM
*To:* Discussion list for users of sipXecs software
*Cc:* Dave May
*Subject:* Re: [sipx-users] Increase RTP port range
You left out the most vital piece of information. How many calls do
you have physically active in space time? Is it about a 1000?
We ran out of available sessions on our sipXecs OpenACD server
this morning, so we increased the max-sessions from 1000 to 1500.
Predictably (at least in hindsight, that is), we then ran out of
RTP ports as the total number of channels in use went over 1000.
2012-07-26 08:25:02.389178 [CRIT] sofia_glue.c:1048 No RTP ports
available!
sipXecs changes the FreeSWITCH RTP range from its default of
16384-32768 to 11000-12998. Is there an underlying reason for
this change, and are there any known issues with changing it back
to FS defaults in /etc/sipxpbx/freeswitch/switch.conf.xml.vm?
Thanks,
Dave.
*Dave May, ICCE*
Manager, Information Technology
PATLive
800.659.7807 phone & fax
Hosted Communications | Friendly Service www.patlive.com
<http://www.patlive.com/>
_______________________________________________
sipx-users mailing list
List Archive:http://list.sipfoundry.org/archive/sipx-users/