Thanks Daniel....So no need to raise a issue in Jira?
Regards,
Kumaran T
On 10/16/2012 4:16 PM, Daniel Tacalau wrote:
Hi,
We discussed about this issue and come to the conclusion that Max
Sessions should include retrieved calls.
In order to do this the internal Max Session will be adjusted
as configured Max Session * 2. So, internally the value of Max Session
will be doubled; as a limitation the internal value will be capped to
1000.
I opened an issue in Pivotal Tracker "Park Server's option Max
Sessions should include retrieved calls"
https://www.pivotaltracker.com/story/show/37843695
Regards,
Daniel
On Tue, Oct 16, 2012 at 12:38 PM, Tony Graziano
<[email protected] <mailto:[email protected]>>
wrote:
I think #2 will not solve retrieving calls even if minimum is a
larger number.
On Oct 16, 2012 3:55 AM, "Daniel Tacalau" <[email protected]
<mailto:[email protected]>> wrote:
Hi,
IMO it's OK to have only one configuration option, i.e
MaxSession, for the park server sessions. Having more options
may be confusing for users.
I think we have two options:
1. Check how max session is used internally and fix it's usage
to also include retrieved calls.
2. Set a minimum limit in the Park Server configuration so
that users cannot set small values for MaxSession (i.e 7).
Either way we should improve MaxSession option description to
be clear what it is used for (parked calls, retrieved calls,
others?).
Joegen,
What do you think?
Regards,
Daniel
On Tue, Oct 16, 2012 at 10:12 AM, Kumaran
<[email protected]
<mailto:[email protected]>> wrote:
Hi All,
If we set Park Max Session =2 then we can't retrieve
the call park
if 2 calls placed in park..If we set to 1 then we can't
retrieve the
call at all...IMO Max session is to park the calls and not
related
retrieve the call...I think this behavior is seen because
once 2 call
parked and other user try to retrieve,it should fetch from
park
server..It consider already park session is full,so its
not allowing
user to retrieve the call....
Regards,
Kumaran T
_______________________________________________
sipx-dev mailing list
[email protected]
<mailto:[email protected]>
List Archive: http://list.sipfoundry.org/archive/sipx-dev/
_______________________________________________
sipx-dev mailing list
[email protected] <mailto:[email protected]>
List Archive: http://list.sipfoundry.org/archive/sipx-dev/
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426 <tel:434.984.8426>
sip: [email protected]
<mailto:[email protected]>
Helpdesk Customers: http://myhelp.myitdepartment.net
Blog: http://blog.myitdepartment.net
_______________________________________________
sipx-dev mailing list
[email protected] <mailto:[email protected]>
List Archive: http://list.sipfoundry.org/archive/sipx-dev/
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/
