Avaya Support Forums  

Go Back   Avaya Support Forums > Messaging

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 06-21-2012, 09:13 AM
boothg boothg is offline
Aspiring Member
 
Join Date: Jun 2012
Posts: 2
boothg has 10 reputation points
Default MM Dial by name Call ID.

Hi,
I have an issue whereby when a caller goes to voicemail and selects dial by name, they select the name they require and then it dials the extension.
On the display of the extension, if caller id is not sent, the display shows the following nummber. 000-000-0000. Does anyone know where I can change this number, the customer would prefer to not see a number.
It is MM 5.2 MAS with Exchange SIP integration to CM.
Thanks in advance
Gary
Reply With Quote
  #2  
Old 08-13-2012, 02:26 AM
dineshan dineshan is offline
Hot Shot
.
 
Join Date: Mar 2010
Posts: 10
dineshan has 10 reputation points
Default

Hi Gary,

I don't think there is any configuration that you can do on the MM. Maybe a code change, but that would probably impact all calls, with or without Caller-IDs. If that is the request you may need to open an SR, and if the Backbone Engineer finds it as a product enhancement, it would probably go as a GRIP.

Thanks,
Girish
Reply With Quote
  #3  
Old 08-14-2012, 09:58 AM
csteinh csteinh is offline
Member
 
Join Date: Mar 2010
Posts: 6
csteinh has 10 reputation points
Default

Check the "Asserted ID" value on the PBXs>SIP tab from VMSC to see if there is any value entered. It's most likely empty. This field can be used to display a number under certain call scenarios.

Here is some additional info from the MM 5.2 SP3 patch 2 release notes:

Effect of this Patch on Outcalls

After the installation of this patch, there will be a change in the calling number which gets displayed for outcalls from the MM system. The outcalls which are affected include all client outcalls and Call Me outcalls.

For a non-multi-site configuration: The phone being called will display, as the calling number, the P-Asserted-Identity value configured for the PBX in the VMSC (VMSC>PBX's>(the desired PBX)>SIP). If the P-Asserted-Identity value is not configured, then the phone being called will display the calling number as "0000000000", "unknown", or something similar.

For a multi-site configuration: The phone number being called will display, as the calling number, the P-Asserted-Identity value configured for the PBX in the VMSC (VMSC>PBX's>(the desired PBX)>SIP). If the P-Asserted-Identity value is not configured, then the phone being called will display, as the calling number, the value configured for the hunt group for the site in the VMSC (VMSC>Sites>Configure). If the hunt group value is not configured, then the phone being called will display the calling number as "0000000000", "unknown", or something similar.
Effect of this Patch on Transfers

After the installation of this patch, there may be a change in the calling number which gets displayed for transfers (including auto-attendant transfers and Find Me). If the original call into the system does not include caller ID-related information, the behavior will be as follows:

For both non-multi-site and multi-site configurations: The phone being called will display, as the calling number, the P-Asserted-Identity value configured for the PBX in the VMSC (VMSC>PBX's>(the desired PBX)>SIP). If the P-Asserted-Identity value is not configured, then the phone being called will display the calling number as "0000000000", "unknown", or something similar.



Chuck
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
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

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 03:59 AM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.