AAM 6.2 unable to transfer to mailbox from a vector in CM

[ayrscott]

Need some help...I have a vector that contains a messaging step to a mailbox. When AAM answers the call it says please enter the mailbox number. However, if I call the station directly or call the DID for that station, I get the personal greeting.

Any ideas?

[sheasley]

This issue could have several causes:
1. The vector may be referenced in the SIP history info, but not administered in the Public Unknown table - SOLN233201
2. The transfer from the vector may have a leading + in the called party ID - SOLN232601
3. The transfer from the vector may not be sending the correct extension length
If you perform a ‘collect system log files’ from the application server and then grep the InfoBridge.log file for ‘PhoneUtils’ it will display the data used for integration, like the pilot number, calling party, and called party. This log also displays results from the lookups against these.

[ayrscott]

After checking the call records it appears that on calls coming from the vector are passing the messaging hunt group extension number and not the extension defined in the messaging step. Incoming calls to the extension or the DID work fine.

[ayrscott]

A few more details......This only occurs when a call has been placed in queue and then not answered then transferred to the RONA VDN and placed in queue again and not answered then sent to the vector step for messaging.

[jmertz]

In our vectors for our 6.2 system we can accomplish this one of two ways.


1. using the messaging command

Examples:

messaging skill 99 for extension active

messaging skill 99 for extension 7100

99 is our voice mail hunt group


2. Use the route to command

route-to number 2222 with cov n if unconditionally


2222 is the extension for the aura messaging server


Both the active in the messaging command and the route to will look for the leading number but replacing active with an extension should always work unless something in the trunk routing isn't configured correctly.

Or that has been our experience in the past.

[ayrscott]

Originally Posted by jmertz

In our vectors for our 6.2 system we can accomplish this one of two ways.


1. using the messaging command

Examples:

messaging skill 99 for extension active

messaging skill 99 for extension 7100

99 is our voice mail hunt group


2. Use the route to command

route-to number 2222 with cov n if unconditionally


2222 is the extension for the aura messaging server


Both the active in the messaging command and the route to will look for the leading number but replacing active with an extension should always work unless something in the trunk routing isn't configured correctly.

Or that has been our experience in the past.

I have made all past this but appreciate the help.....

I have actually figured out the fix to this......While looking through solutions for other issues with SIP trunking,I found a problem with the SIP trunk not passing the extension number. I added a wait step for 2 seconds hearing music before the messaging step in the vector and that corrected the problem.

[marzahn]

It's interesting to me how long this trick has been around. When I was fairly new where I am now, I moved my new employer from Rolm to Definity 8.x. One of the first confrernces I attended had a vector work session where I learned to ". . . always start a vector with a wait time 2 seconds. . . " statement.

Thank you,
Bill Marzahn
Telecommunications Administrator


Neighborhood Health Plan of Rhode Island
299 Promenade Street
Providence, RI 02908-5720
401-459-6677 (Direct "Find-me" Line)
401-709-7177 (Facsimile)
www.nhpri.org and on Facebook

Ranked the #4 Medicaid Health Insurance Plan in America by NCQA*
* National Committee for Quality Assurance 2013-2014 Health Insurance Plan Rankings - Medicaid

[arahamanshar]

Good to know that the issue is now fixed.

Abdul Rahaman Shariff

[marzahn]

Originally Posted by ayrscott

I have made all past this but appreciate the help.....

I added a wait step for 2 seconds hearing music before the messaging step in the vector and that corrected the problem.

We recently contracted with a consultant to "clean up" and add funtionality to our vectors. One of the things I learned was that current good practice in vector writing allows the following first vector step . . .

01 wait-time 0 secs hearing ringback

This has worked quite well for us since implementatoin earlier this year.