Search results

  1. nexVortex and DID Routing Failures

    I know that 3CX is receiving DID information from nexVortex on some level, because if I do not "verify the source by DID," the inbound calls to that DID fail completely. Thus, 3CX must be recognizing DID information from nexVortex... but 3CX's internal routing based on DID doesn't work. The...

  2. nexVortex and DID Routing Failures

    It is changed to the DID. 6155551234, etc...

  3. Your Forum doesn't allow searches of any 3 letter terms?

    "nexVortex DID" is not "too common." DID in general is not "too common." I'm not complaining, as much as I am voicing a concern. If most of your support is via this forum... and a large number of issues use "common" three letter acronyms/words... "filtering out" those acronyms/words is a problem.

  4. Your Forum doesn't allow searches of any 3 letter terms?

    Your Forum doesn't allow searches of any 3 letter terms? Like SIP? Or DID? Or Vox? Or URI? Or URL? Or Web? Or... PBX? Really? I mean seriously?

  5. nexVortex and DID Routing Failures

    DID routing does not work with nexVortex accounts/DID's? Version 7 and 8 DID's can be used to verify the source... but DID routing fails. Worked fine with Broadvox.
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom