Jump to content

Nexvortex E911


jlumby
 Share

Recommended Posts

I am trying to find a way to send a different outbound caller ID only when someone dials 911. According to Nexvortex, the way that they do E911 when you have multiple E911 locations with them is based upon the ANI you send out. The problem is since they require a SIP registration, the only way I can change the ANI is to send it out a different trunk, however I only have one trunk. The other thing I had thought about is to have it go through another PBXnSIP machine, however I would prefer not to need an additional machine to manage, and have found that as you get multiple PBXnSIP registrations to eachother, performance tends to degrade quickly, so I want to avoid that at all costs. What is the best way to acomplish this?

Link to comment
Share on other sites

I am trying to find a way to send a different outbound caller ID only when someone dials 911. According to Nexvortex, the way that they do E911 when you have multiple E911 locations with them is based upon the ANI you send out. The problem is since they require a SIP registration, the only way I can change the ANI is to send it out a different trunk, however I only have one trunk. The other thing I had thought about is to have it go through another PBXnSIP machine, however I would prefer not to need an additional machine to manage, and have found that as you get multiple PBXnSIP registrations to eachother, performance tends to degrade quickly, so I want to avoid that at all costs. What is the best way to acomplish this?

 

In 3.3 we introduced the "EPID" (endpoint identifier). When someone calls 911 on a emergency trunk, then the PBX will put the EPID into the contact. When the emergency center calls back, the call goes directly to the extension. even if there is usually an auto attendant in the middle.

 

This goes beyond what good old TDM was able to do. VoIP and SIP can do more than emulating circuits.

Link to comment
Share on other sites

In 3.3 we introduced the "EPID" (endpoint identifier). When someone calls 911 on a emergency trunk, then the PBX will put the EPID into the contact. When the emergency center calls back, the call goes directly to the extension. even if there is usually an auto attendant in the middle.

 

This goes beyond what good old TDM was able to do. VoIP and SIP can do more than emulating circuits.

 

This is nice, however how does it give them my E911 address since it is not sending the remote party ID that they are looking for, or does whatever I type in here override the normal remote party ID that I would be sending?

Link to comment
Share on other sites

This is nice, however how does it give them my E911 address since it is not sending the remote party ID that they are looking for, or does whatever I type in here override the normal remote party ID that I would be sending?

Does anyone know how this feature might apply to Nexvortex? They had never heard of it.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...