Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Ringing a hunt group DN over a gateway SIP trunk - adding a 2nd hunt group extension

Status
Not open for further replies.

smalltownguy

IS-IT--Management
Aug 22, 2013
56
US
This is my thread from last summer, where we set up a hunt group at one location, and configured two remote locations to dial to the DN attached to the hunt group:


I would like to set up a 2nd hunt group DN, and I cannot seem to get the mapping to work correctly. Inside the local store the hunt group works fine, but the remote stores are telling me "invalid number" when they dial the last digit of the DN.

Here's how things are set up:

* Home store uses 4 digit DN's, 2221 is the receptionist set. (22 prefix)
* One remote store uses 4 digit DN's, 2321 is the receptionist (23 prefix)
* Other remote store uses 4 digit DN's 2421 is the receptionist (24 prefix)
* The hunt group is located at the home store. It's using 2761, and is currently working across the IP trunks. Currently using target line 170.
* The next hunt group I'd like to set up would be 2762, and that is the one I can't get set up correctly. I have it set up using target line 171.
Both of the remote stores have the ability to dial 2761 no problem, but I cannot get them to dial 2762. They both have entries on the IP trunk routing table to send "27" to the local IP address of the home store.

What am I doing wrong? Does my second hunt group DN (2762) need to be on the same target line 170?

 
Okay, I believe I have figured this out. The step I missed from my last post from June 2014 was the part where I quoted:

"Then I added the extension in the calling plan locally and the calls started going through."

That part confused me at first, until I finally found what I needed in the Dialing Plan of the remote store.

Telephony> Dialing Plan> Routing> Destination Codes

In the Destination Codes table, I found where I had entered the specific DN of the hunt group I'd created at the home store. Defining that DN gave the remote store a valid DN # to send down to the main store's system. I added the new DN # of the new hunt group I created (2762) and copied all of the First Route and Absorbed Length settings. Then the calls started going through.



 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top