At the recent Voice on the Net show, we heard about some excellent capabilities for IP Centrex service. In fact, IP Centrex is not limited to services from the\u00a0incumbent local exchange carriers\u00a0- this was highlighted by the fact that one of the more intriguing demos was available in the AT&T booth for its as-yet-unannounced service.There\u2019s no question that IP Centrex is an excellent fit for many enterprises as they make the transition to voice over IP. But there are two major issues that must be addressed for IP Centrex to become the success that it should be, and we\u2019ll address the first of these in this newsletter.Frankly, IP Centrex needs a new name. In today\u2019s world, \u201cCentrex\u201d sounds old. By analogy, the \u201cAll New 2003 Edsel\u201d wouldn\u2019t exactly excite the automotive world. \u201cCentrex\u201d also implies \u201ccentralized.\u201d It implies a close association with the local central office. Indeed, traditional \u201cCentrex\u201d service was based on offering the same set of custom calling features that you would receive in a traditional PBX, only from a central-office configuration.There\u2019s a major difference between the fundamental architectures of \u201cCentrex\u201d and \u201cIP Centrex\u201d services. In many cases, it is somewhere between difficult and just short of impossible to extend traditional Centrex features across the WAN. If you have one set of features available as a user at the office, having that same profile and set of features follow you across the country is not trivial.However, with IP Centrex, the barrier of connection to a local switch is removed, so location independence becomes a given.We\u2019re not sure exactly how to convey this message. Perhaps the service should be called \u201cIP Distributex\u201d simply to emphasize this major advantage. But one thing is for sure - it\u2019s not a \u201ccentralized\u201d service.