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!

Avaya CM6 to FreePBX

Status
Not open for further replies.

Fezzerooney

Technical User
Nov 10, 2011
25
GB
1. Has anyone got any idea how to get the MWI working from FreePBX to CM?
(At the moment you dial 83xxx/82xxx from the Avaya and ASM converts it back to 33xxx or 22xxx as it routes to FreePBX/Asterisk)
2. Is there a better way than using a coverage path and remote coverage number to get the calls to it?
(I've tried hunt group with SIP adjunct and it just reads the Voicemail Handle rather than the extension number of the phone.)

HUNT GROUP

Group Number: 1 ACD? n
Group Name: Asterisk Queue? n
Group Extension: 21000 Vector? n
Group Type: ucd-mia Coverage Path:
TN: 1 Night Service Destination:
COR: 0 MM Early Answer? n
Security Code: Local Agent Preference? n
ISDN/SIP Caller Display: mbr-name


HUNT GROUP





Message Center: sip-adjunct

Voice Mail Number Voice Mail Handle Routing Digits
(e.g., AAR/ARS Access Code)
80999 80999


















 
SIP MWI on CM wants a SIP notify message

For call answer, CM will send a SIP message TO:voicemail pilot#@domain.com, FROM:personwhocalled@domain.com and there will be history-info and diversion headers, of which the most recent is "who's phone didn't answer to result in this call going to voicemail?" Avaya Aura Messaging can be configured to look at either History-info or Diversion for this task.

If you can trigger your voicemail to use the diversion or history headers to know who to answer for, that'd help!

Here's some headers from a SIP INVITE to a AAM for a call that was sent to voicemail:
Diversion: <sip:678@domain.com>;reason="unknown"
History-Info: <sip:678@domain.com>;index=1
History-Info: "Joe User" <sip:678@domain.com?Reason=SIP%3Bcause%3D480%3Btext%3D%22Temporarily%20Unavailable%22&Reason=Redirection%3Bcause%3DNO|
RMAL%3Bavaya-cm-reason%3D%22cover-no-reply%22%3Bavaya-cm-vm-address-digits%3D*996472530780%3Bavaya-cm-vm-address-handle%3Dsip:VMPilotNumberGoesHere%40domain.com>;index=1

AAM can answer with things like "Joe User" is "On the phone" or "not available" or "doesn't like you and doesn't want to be disturbed" etc...

Now, for MWI, the Notify will be sent by your voicemail server to say 1234@domain.com with a message in there to say "MWI ON" or "MWI OFF". You would need to take the numbers in the "notify" message and have SM route that to CM for CM to turn the lamp on.
And if you're doing digit manipulations to get calls over to voicemail, you'd likely need to manipulate them back on the return to CM with some adaptation to make sure CM gets the right extension @domain.com in the notify to light the lamp.

Or, use H323 and QSIG - that's way easier!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top