"Domain.com" is valid from both a CNAM perspective and a SIP display name perspective. My guess is this is an issue in the voicemail-to-email code on the destination ITSP.
-- Nabeel Jafferali X2 Networks Inc. On Mon, Dec 15, 2014 at 11:30 PM, Mark Brown <t...@marknmel.com> wrote: > > Hi Taug'ers > > Perhaps someone with a telephony background can answer me a question > related to call id. > > If I send a call with id as "Domain.com<905-555-1212>" (domain and number > altered for the purpose of this email)... > My question - is the "dot" in Domain.com a valid character? I also use > mixed case, just like the example (if that matters) > I'm with Primus/Unlimitel here - using an IAX trunk - with the CID being > tweaked by an asterisk 1.8 machine on this end. Basically - this has worked > for years - with no issues that I was aware of... > > I ran into a snag when placing a call to another VoIP ITSP tonight, and > attempting to leave voicemail. The voicemail is recorded successfully, > however I have configured with that ITSP to deliver voicemail as email - > but the target email accounts also happen to be on "Domain.com" and are > never delivered to those email accounts on that domain, when my Calling > number is Primus/Unlimitel. > > Some datapoints: > > * Calls/voicemail from my mobile phone with a with different CID are > sent successfully. Emails successfully delivered. > * I set my CID to be "DomainCom" on Primus/Unlimitel, and I can work > around the problem this way too. Emails successfully delivered. > * If I disable the voicemail to email integration at the other ITSP, > messages are saved on their voicemail server. (no email - but > voicemail waiting...) > > I don't know if it's a goofy regex in their softswitch, voicemail server, > or I'm sending bad data as a part of my CID string. > > I'm trying to rule out the latter.... (but if I'm doing something silly - > I'd like to fix that too...) > > Any ideas on this one? Any documents I could reference? > > Many thanks in advance.... > > /Mark >
