Akshata Saralaya wrote:
> Martin Steinmann wrote:
>>
>> How about with the titles below?
>>
>>
>>
>> - If there is only one section (group), only use the main
>> title and no group titles
>>
>> - Remove the designation “Engine” from the Media Server
>>
> +1
>>
>> - Make sure capitalization is consistent
>>
>> - Remove all references to sipX and freeswitch
>>
>>
>>
>> --martin
>>
>>
>>
>>
>>
>
> The services shows;
> sipxproc :
> {"FreeSWITCH"=>"Running", -------------Media Engine
> "sipXmrtg"=>"Running",
> "SIPRegistrar"=>"Running",
> "ParkServer"=>"Running",
> "ConfigAgent"=>"Disabled",
> "CallResolver"=>"Running",
> "ACDServer"=>"Disabled",
> "SIPStatus"=>"Running",
> "ConfigServer"=>"Running",
> "CallResolver-Agent"=>"Disabled",
> "SipXbridge"=>"Disabled",
> "MediaServer"=>"Running",----------------Voicemail
> "sipXivr"=>"Running",
> "PageServer"=>"Running",
> "CFSServer"=>"Running",
> "PresenceServer"=>"Disabled",
> "ResourceListServer"=>"Running",
> "SipXrelay"=>"Running",
> "SIPXProxy"=>"Running"}
>
> I my opinion it will avoid confusion with Freeswitch and Media Server if
> we use different and clear distinguished names.
> Media Server is right from the beginning recognized for Voicemail. If we
> use same name for FreeSWITCH (i.e. Media Engine) parameter, I feel it
> will be confusing. So the Titles could be;
>
These are not the names displayed by sipXconfig.
These are internal names displayed by a low level tool (sipxproc). I think
we decided not to touch them this time around with the possible exception
described here: <http://permalink.gmane.org/gmane.comp.voip.sipx.devel/15075>
Also sipXconfig UI should not use the word "server" to describe "service".
Server is a machine on which the service runs.
I will just make all Service pages to have the same title as the Services
to which they refer: "Voicemail", "SIP Proxy" etc. We solved this issue
once, does not make sense to solve it differently just because we are
talking about a different page.
D.
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
