Home Forums HAast (High Availability for Asterisk) General HAast OEM Edition UA / unique ID is wrong

Tagged: , , ,

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • teliumcustomer18
    Post count: 1

    We have a home built app which tracks calls across the various HAast clusters, linking call quality with information from our gateway. This worked well with the unlimited edition of HAast, but since switching to the OEM edition our app no longer works. (None of the unique call id’s from asterisk match what is seen at our gateway). What is wrong?

    Avatar photoTelium Support Group
    Post count: 258

    To understand what is going wrong you need to understand a bit more about the HAast CC module. The CC module acts like an SBC or proxy, in that all external UA’s (or services/devices) connect to the CC module, and the CC module connects to Asterisk. Each “session” is actually split into two sessions.

    In the event of cluster failover the UA sessions move to the other node, while the Asterisk sessions are rebuilt. The CC module rebuilds conferences, queues, calls in progress, etc. on Asterisk and then bridges it back to the matching outside UA session.

    With the Unlimited edition the call UniqueID found in asterisk matches what was seen at your gateway. With the OEM edition the call UniqueID found in Asterisk will be different that was is seen at your gateway (the CC module is bridging two separate sessions). In order to for your app to get the UniqueID (or any Asterisk variable) you must use the CC module API and ask it to provide a mapping between the external and internal session variables.

    HAast OEM uniqueid session

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.