Results 1 to 10 of 27

Thread: *67 issue

Threaded View

Previous Post Previous Post   Next Post Next Post
  1. #11
    Join Date
    Feb 2007
    Location
    Irvine CA
    Posts
    1,542,128,044

    Default Re: *67 issue

    The reason we handle it server side and do not use the ATA is that since we don't get the raw data if the ATA manipulates it, it affects other features and can cause issues with either it not working properly and transmitting the CID or calls to fail if it's not sent out to a carrier with a correct ANI.

    We tried that back in the early days with the 502s and it was a mess with people saying calls not completing randomly (since it didn't come in a proper format or completely stripped the ANI altogether). If we make any system changes, we can't account for what the device does to correct it.

    Then if a firmware update is or a new device is used in the future, it could change how it sends it and all the fun starts over again with needing to redesign how our system takes the info from it and call accounting, etc.

    We try not to rely on the devices for anything unless we absolutely have to to keep things flexible and consistent in terms of delivering service vs it potentially having issues if we ever make any changes.
    Last edited by VOIPoTim; 06-09-2009 at 12:27 PM.
    Timothy Dick
    Founder/CEO
    VOIPo.com

    Interact with VOIPo: Twitter, Facebook

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •