Home | Register |    
 
Forums         |        Articles          |      Software          |      Portals          |      Resource          |      Wiki      |    White Papers         
 
Go Back   PBX Info :: Your Free PBX, PABX and Telephone Information Resource > PBX SYSTEMS > AVAYA > Definity Support
   SEARCH  
     
User Name Password      
Save ?
Definity Support Definity Servers Support

Tags: , , ,


Post New Thread  Reply
 
LinkBack Thread Tools Display Modes
Old 11-20-2004, 09:30 AM   #1 (permalink)
zeromeg
Junior Member

Activity Longevity
0/20 17/20
Today Posts
0/0 ssssssss2
Rep Power: 0zeromeg is on a distinguished road

Total Points:
Donate

I have a customer whom their services vendor has installed a T1 for. They and the provider have configured the circuit to provide 4 digits and function as DID.

Per the forum and suggestions provided by people I configured the T1 with the channels being Tie and functioning like DID. The customer's extensions are 6300-6359. The provider ported yesterday and the DID 6300-6359 are working just fine. However, the services vendor also specified to port the customers main phone number which the last 4 are 7777. When they ported, the main# would just ring and ring. I renumbered as a test one of the unused ports of the VM to 7777 and the voice mail would transfer the call to the operator.

The provider configured it so that instead of 7777 being passed that it now sends 6377 to get it in the range. That worked to get the operator to be answering all incoming calls but they want the attendant to answer all incoming calls to 7777. Can I just setup at this point 6377 in VM as associated to an auto attendant to get this to work or is there something else I should do? I was at first thinking of setting up 6377 as an adjunct and then doing forwarding to the vm group.

Any help as always is appreciated!

Thanks in advance.
zeromeg is offline   sendpm.gif Reply With Quote
Old 11-20-2004, 10:57 PM   #2 (permalink)
TouchToneTommy
Junior Member

Activity Longevity
6/20 20/20
Today Posts
0/0 sssssss12
Location: California's Central Coast
Rep Power: 6TouchToneTommy is on a distinguished road

Total Points:
Donate
Country:

Merlin Legend, T1 (DID) and Merlin Messaging

You're on the right track. renumber an adjunct to 6377 and then cover it to voice mail. Don't know which voice mail you're using. For Merlin Messaging, you just assign an auto attendnat to it. For Merlin Mail, it's handled by the mailbox's Class of Service. Don't know about Audix, it's not my bag. Right now, since 6377 doesn't match anything, it defaults to ringing at the Operator's console. When they were sending 7777, it probably ended up matching calling group 777, which had no members or overflow, thus the continual ring. When you made a VM port match 7777, the call arrived without mode codes, which confused the voice mail port, and its fall back is to transfer to the operator.
TouchToneTommy is offline   sendpm.gif Reply With Quote
Old 11-21-2004, 05:36 AM   #3 (permalink)
zeromeg
Junior Member

Activity Longevity
0/20 17/20
Today Posts
0/0 ssssssss2
Rep Power: 0zeromeg is on a distinguished road

Total Points:
Donate

Thanks! There is always more than one way to do something on these systems so I like to talk it out loud to others to get feedback. I figured that it's just like setting up a delay for an attendant and the best way to do it. I didn't want to do the forwarding. I don't mind doing it for side functions but not something as primary as the calls coming in.
zeromeg is offline   sendpm.gif Reply With Quote
Post New Thread  Reply



Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On

Tags   |   Advertise    |    Media Partners   |    Admin   |   About us   |   Contact Us   |   RSS   


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.0.0
Copyright PBXINFO LLC 2006