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 John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

NEC SV9100 Voicemail to email issue

ngstan

IS-IT--Management
Nov 8, 2021
37
US
We recently switched our email system over to Microsoft 365. I'm using a third-party SMTP provider (SMTP2GO) to send voicemails from the NEC SV9100 to the recipient's email since the 9100 doesn't support Microsoft OAuth. Everything has been working well until recently when I've started seeing bounced emails. The error message is: "550 Multiple From addresses are not allowed without a Sender address". After discussing this with the SMTP provider, we discovered the issue. The SV9100 is pulling the caller ID name into the from line of the email. The bounced emails all contain a comma "LAST NAME, FIRST NAME" which is interpreted by Microsoft as being multiple from addresses. Most of our voice mails don't have commas but I'm seeing a few each day now and I'm worried that customers will become irritated that they're not being called back because our customer service folks aren't receiving those voice mails.

Is there anyway to get the SV9100 to not pull the caller ID into the from address? Thanks!
 
Turn off caller ID to VM in the trunk settings. Otherwise office 365 needs to fix their sh*t. I've seen this all over. I have one customer that has a 365 relay and has never had an issue and another ....it's silly.
 
Turn off caller ID to VM in the trunk settings. Otherwise office 365 needs to fix their sh*t. I've seen this all over. I have one customer that has a 365 relay and has never had an issue and another ....it's silly.
Found it under 14-01-22. I just tested it and it appears like that should work but really stinks not having the name or at least the phone number in the voice mail email. The from becomes 'outside caller' and the number in the body is 'unavailable'. Everything has been working great until recently so Microsoft must have changed something. Or I guess it's possible the carrier is changing their caller ID format to add commas. I have a ticket with them but probably nothing they can do. Thanks for the info!
 

Part and Inventory Search

Sponsor

Back
Top