My application processes data under the assumption that the following field contains a phone number:
entities
participants
calls
other
addressNormalized
However, when extracting the value from this field, we sometimes encounter an email address instead. I would like to know what kind of values can be present in the addressNormalized field.
Is this normal behavior? If so, could you please explain the reason and the specifications behind this?
I read the documentation but had difficulty understanding it, so I'm asking here.
(string) The normalized address. This field is acquired from the Address Normalization Table. The addressRaw could have gone through some transformations, such as only using the numeric portion, before being run through the Address Normalization Table.
Thank you for your assistance.
Please let me know if this version meets your requirements.
I don't understand what you mean by an email address in the addressNormalized field.
An address involved in a call could be a "tel:" based address or a "sip:" based address.
The sip: address can contain a number@host or a user@host.
If this is what you mean by email address (sip:user@host), then yes, such format can populate the addressNormalized field. An example would be an agent with a SIP Phone registered with a username format, or another example can be the voicemail participant of a call (I mean participant with purpose=voicemail), ...
Thank you for your response. I now understand the point you were making.
The "email address" we are retrieving does indeed follow the sip:user@host format. To clarify, are we obtaining the addressNormalized field from the From or To headers in the SIP messages?
Yes, that's the principle.
I mean normalized identity from the SIP session (being in To/From header or maybe other headers like for P-Asserted-Identity, ...).