RETAIN not clear would be the consistent preference. Also assists in
removing and reinstalling packages if needed to manually without having to
backup/restore and restart services in production.

On Wed, Sep 12, 2012 at 8:28 AM, Kumaran <
[email protected]> wrote:

>  OK Tony....I notice only conference service will clear the old
> configuration once disabled but features like park,Acc code will be
> retained...So I thought raise a improved for consistency in features either
> remove features old configuration once that service is disabled or retain
> configuration if service is disabled and enabled...
>
> Regards,
> Kumaran T
>
>
> On 9/12/2012 5:47 PM, Tony Graziano wrote:
>
> It would be helpful to understand this:
>
>  When we disable a service like conference, does it remove the
> lines/services associated with it?
>
>  I.E. I create a conference "222". Later on I disable and create a user
> "222"? If I re-enable the service "222" should be not eligible because it
> belongs to conference service UNLESS it is disabled and remains in the DB
> so when I re-enable it the data is already/still populated.
>
>  IMO - The data to remain persistent (the data should be cleared). I can
> see disabling a service to troubleshoot something can create a lot of work
> to re-create it. We should not clear data upon disabling the service. When
> I try to create a user 222 it should throw an error that it exists.
>
> On Wed, Sep 12, 2012 at 7:54 AM, Kumaran <
> [email protected]> wrote:
>
>>   On 9/12/2012 5:20 PM, George Niculae wrote:
>>
>> On Wed, Sep 12, 2012 at 2:46 PM, Tony Graziano <
>> [email protected]> wrote:
>>
>>> It does not sound valid. Did you ensure the conference service was
>>> running and had restarted? Does projecting the server profile (not
>>> desirable, but helpful in troubleshooting) change this behavior?
>>>
>>>
>>  Well I guess we're not clearing out all items related to a particular
>> feature when it gets disabled. IMO think this is not something critical
>> that we need to address in 4.6 but can be improved later
>>
>>  George
>>
>>  OK George...I will raise a improvement that will make consistency in
>> features...
>>
>>
>> Regards,
>> Kumaran T
>>
>>
>>
>> _______________________________________________
>> sipx-dev mailing [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/
>>
>
>
>
>  --
> ~~~~~~~~~~~~~~~~~~
> Tony Graziano, Manager
> Telephone: 434.984.8430
> sip: [email protected]
> Fax: 434.465.6833
> ~~~~~~~~~~~~~~~~~~
> Linked-In Profile:
> http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
> Ask about our Internet Fax services!
> ~~~~~~~~~~~~~~~~~~
>
>  Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab
> 2013!
>  <http://sipxcolab2013.eventbrite.com/?discount=tony2013>
>
>
> LAN/Telephony/Security and Control Systems Helpdesk:
> Telephone: 434.984.8426
> sip: [email protected].**net<[email protected]>
>
>  Helpdesk Customers: 
> http://myhelp.myitdepartment.**net<http://myhelp.myitdepartment.net>
> Blog: http://blog.myitdepartment.net
>
>
> _______________________________________________
> sipx-dev mailing [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-dev/
>
>
>


-- 
~~~~~~~~~~~~~~~~~~
Tony Graziano, Manager
Telephone: 434.984.8430
sip: [email protected]
Fax: 434.465.6833
~~~~~~~~~~~~~~~~~~
Linked-In Profile:
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!
~~~~~~~~~~~~~~~~~~

Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab
2013!
<http://sipxcolab2013.eventbrite.com/?discount=tony2013>

-- 
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: [email protected]

Helpdesk Customers: http://myhelp.myitdepartment.net
Blog: http://blog.myitdepartment.net
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/

Reply via email to