Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Feb 23, 2009 VoicePulse will cease to function w/ 3CX

Discussion in '3CX Phone System - General' started by Cloverlick, Feb 6, 2009.

Thread Status:
Not open for further replies.
  1. Cloverlick

    Joined:
    Jul 17, 2007
    Messages:
    10
    Likes Received:
    0
    Specifically, DID Routing will cease to function, thus making the service completely worthless.

    VoicePulse, yet again, is "upgrading" their servers. (They seem to make some "groundbreaking" change to their infrastructure once every 12-18 months... and manage to render our configuration worthless, every time.)

    Currently, their connection servers are connect01.voicepulse.com, connect02 and connect03.

    As of February 23 (pursuant their last email), these servers will be shut-off, and jfk-primary.voicepulse.com & jfk-backup.voicepulse.com will be the "new" servers.

    I the "new" servers are not only "new," they are configured differently for DID delivery.

    When we tried switching over, DID Routing fails completely...

    And again... all we're doing is changing from "connect01..." to "jfk-primary..." as per their instructions.

    In short, it fails. When we switch back, it works.

    This is the response from VoicePulse...

    ------------------------------------------
    [VoicePulse] has confirmed that we are sending the correct information to your server. The DID is appearing in the Request URI as it should be. I believe the problem is that your 3CX system is looking in the wrong place for the DID. It is looking in the "To" field to route the calls when it should be looking in the RURI for the necessary information. The "To" field is going to contain only the username for your PBX login credentials, not the DID.

    [VoicePulse] would recommend that you contact Pronexus, the developers of the 3CX system, and ask them if you can configure 3CX to look for the information in the Request URI. Once your server is reading the information from the RURI instead of the "To" field in the SIP header, your system should be able to route the calls correctly.
    ------------------------------------------

    We tried making the changes they recommended above.

    It still fails.

    We're open to suggestions... and I can't imagine we're the only group in the world using both 3CX w/ VoicePulse. (However, we may be the last.)

    We are using 3CX v.5.

    On a related note... nothing makes us "happier" than having groups that we're paying money... make random changes to systems, that AREN'T broken.... causing us to spend time, effort, money and resources to FIX problems, caused by other people.
     
  2. discovery1

    discovery1 Member

    Joined:
    Aug 4, 2008
    Messages:
    355
    Likes Received:
    0
    Maybe it's time for an upgrade to version 7?
    The newer versions allow you more control over the fields in the incoming requests.

    You could always set up a trial using the free version of 7.x to see if you can get VoicePulse working before purchasing the latest version.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. mchung

    Joined:
    Nov 6, 2009
    Messages:
    1
    Likes Received:
    0
    Is it still the case that VoicePulse and 3CX are still not compatible with each other?

    This wiki entry [1] seems to indicate that there's some form of working support. Additionally, on the VoicePulse side of things, I can confirm that it's getting some form of status update from our 3CX system, but phone calls aren't being properly handled.

    [1]: http://sites.google.com/a/3cx.com/3cx-wiki/voip-provider/3rd-party-supported/working-voip-providers
     
Thread Status:
Not open for further replies.