"SIP Trunking" is the term everyone seems to understand --martin
-----Original Message----- From: Lawrence, Scott (BL60:9D30) Sent: Monday, February 23, 2009 10:32 AM To: Steinmann, Martin (BL60:2500) Cc: [email protected] Subject: Re: [sipX-dev] Service names - again On Fri, 2009-02-20 at 19:37 -0500, Martin Steinmann wrote: > I have to come back to service names as there are some inconsistencies > in the way it ended up. > > > > 1) In the services table we have an entry called "Configuration" > and in the list of server roles it is called "Management". I prefer > "Management" > > 2) In the list of server roles there is an entry called > "Conference", but the service table has no reference to conference. I > propose to rename "Media Engine" to "Media & Conferencing" > > 3) The list of server roles mentions "Border Controller", but the > services table calls it "SIP Trunk". I prefer "SIP Trunking" for both > places The "SIP Trunk" is the thing provided by the ITSP. The "Border Controller" is the sipXecs that talks to the SIP Trunk. > 4) The services table has an entry for "ACD", the list of server > roles calls it "Call Center" and the drop-down main navigation calls > it "ACD Call Center". I prefer "ACD Call Center" for all three places > > 5) The list of server roles has an entry for "Conference". The > main navigation drop-down calls it "Conferencing". I prefer > "Conferencing" A service is not a role - it's a part of a role (sometimes the only part). Doesn't using different names help make that distinction? _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
