MM SIP 5.2

[voippbx]

CM 5.2 and MM 5.2 Exchange backend. Issue - transferred caller directly to vmail doesn't show in exchange where the call came from only 'EXTERNAL CALLER'.

I call from the outside (PSTN) to a DID user. They pickup and press transfer VMAIL HUNT GROUP NUMBER then * # # then the 4 digit user's mailbox. I leave message then check the users mailbox to see it shows Message from "EXTERNAL CALLER'. ??? Should it not show caller ID? If I call directly and leave voicemail or if I dial and let it ring it works both ways. The only time it fails is if we use the Transfer * # #?

Any thoughts?

 

[KenMeans]

What TUI are they using?

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[voippbx]

Audix

 

[KenMeans]

This may help.


e. Called party information is not identified by MM in certain
call scenarios such as when using vectoring. This was
corrected in Avaya CM 3.1.4 and CM 4.0.1; corresponding
changes were made in the minimum required MM release as
noted in Section 2.0.
If you are integrating to an Avaya CM 3.1.4 (or later) or CM
4.0.1 (or later) you need to activate the necessary features in the
Modular Messaging System to support these releases. On MM
go to C:\Avaya_Support\Registry_Keys on each MAS and
double-click on the file “CalledPartyAlgorithm-New1.reg.”
Once done the selection takes effect immediately; no processes
need to be restarted. This will change the way MM reads the SIP
History Information records used to integrate the call.
IMPORTANT: Please note that this should only be done if
BOTH Avaya CM and MM are at these release
levels or higher. If either MM or Avaya CM is
on an earlier release, this should not be done.
Should you want/need to re-enable the original functionality
double-click on the file “CalledPartyAlgorithm-Orig.reg” on
each MAS.

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)