SIP ATA (Analog Terminal Adapters – Mitel TA7100 Family) / AG4124 Analog Gateway Terminals

SIP ATA (Analog Terminal Adapters – TA7100 family)

AG4124 Analog Gateway Terminals

A number in the SIPInvite “From” header

• Device: No configuration required.
• MX-ONE: Program extension and number conversion.
• NG911 Portal: Program a Location (civic address) to match the A number defined in MX-ONE.

Note that this setup is not recommended in case of forking extensions, because the user can be logged in more than one place using the same extension. For example, a user has a phone logged on in his/her desk and he or she can do a login in another phone in a conference room. When an emergency call is established, the A number will be sent, however, the systems do not know if that was done from the desktop or the conference room.

For such cases, IP address setup is better.

SIP ATA (Analog Terminal Adapters – TA7100 family)

AG4124 Analog Gateway Terminals

IP domain or IP Address

• Device: The SIP phone shall have a valid IP address.
• MX-ONE: Program a Location ID to match the IP domain or IP Address in the ip_domain command.
  Note:

  A callback number needs to be configured either in the MX-ONE or NG911 portal.

  In MX-ONE use the emergency_ location command to add the callback number.

• NG911 Portal: Program a Location (civic address) to match the Location ID defined in MX-ONE.

The customer needs to be considerate of IP Domain usage as it is possible that an IP subnet may refer to more than one dispatchable location as required by the RAY BAUM’S Act and in that scenario a single IP domain may not be granular enough to meet the legal requirements.

SIP ATA (Analog Terminal Adapters – TA7100 family)

AG4124 Analog Gateway Terminals

DIR

• Device: No configuration required.
• MX-ONE: Program a Location ID to match the DIR in the emergency location database.
  Note:

  callback number needs to be configured either in the MX-ONE or NG911 portal.

• NG911 Portal: Program a Location (civic address) to match the Location ID defined in MX-ONE.

Note that this setup is not recommended if the customer is using Free seating (Hot Desking (VDP) or Logon XML). This is because, the Location ID will be associated with the Directory Number and if a user who normally sits in the site 1 in Los Angeles moves to site 2 in New York and registers the SIP phone there via VDP or Logon XML, the location will still be associated with Los Angeles. For such cases, IP address setup is better.

SIP ATA (Analog Terminal Adapters –TA7100 family)

AG4124 Analog Gateway Terminals

LIM

• Device: No configuration required.
• MX-ONE: Program a Location ID to match the LIM in the emergency location database.
  Note:

  A callback number needs to be configured either in the MX-ONE or NG911 portal.

• NG911 Portal: Program a Location (civic address) to match the Location ID defined in MX-ONE.

Note that this setup reduces the amount of configuration needed in MX-ONE. However, it must be complaint with the local laws regarding the square/foot search area that will be done by the Emergency Response Team.

The customer needs to be considerate of LIM usage as it is possible that an LIM or LIMs may refer to more than one dispatchable location as required by the RAY BAUM’S Act and in that scenario a single LIM may not be granular enough to meet the legal requirements. Note that this setup is not recommended if the customer is using HLR redundancy or Free seating (Hot Desking (VDP) or Logon XML). This is because, the Location ID will be associated with the Directory Number and if a user who normally sits in the site 1 in Los Angeles moves to site 2 in New York and registers the SIP phone there via VDP or Logon XML, the location will still be associated with Los Angeles. For such cases, IP address setup is better.

Service Node 1 (LIM 1) is located in the building 1 and Service Node 2 (LIM 2) is located in the building 2. User extension's 1000 is normally registered in the Service Node 1 located in the site1 (Home Location). In case of Service Node 1 goes down, the extension 1000 will be registered in the Service Node 2(Visitor Location) using the HLR mechanism, which is in the building 2. In such case, MX-ONE will send the location ID associated with Service Node 2 (LIM 2) instead of Service Node1 (LIM 1), then the Emergency Response Team will not be able to locate the user.