I have a peculiar issue and I wonder if anyone else has had this issue or experienced anything similar. 

At the tail end of migrating a company to Microsoft Teams voice, most of the issues have been rectified apart from two numbers. When ever we assign these numbers to a user, they cannot call out, assign a number and they work. 

Immediately think its the SIP Provider, as in other cases the number has not been ported correctly. However from the investigation it seems on the INVITE as the number leaves teams, it is incorrect. On the offending number the P-ASSERTED-IDENTITY is showing as (tel:)

The working example given shows this as a SIP Record.

The CONTACT header is different. My Carrier has assured me the number is set up correctly and it this is coming from Teams

​I have a peculiar issue and I wonder if anyone else has had this issue or experienced anything similar.  At the tail end of migrating a company to Microsoft Teams voice, most of the issues have been rectified apart from two numbers. When ever we assign these numbers to a user, they cannot call out, assign a number and they work.  Immediately think its the SIP Provider, as in other cases the number has not been ported correctly. However from the investigation it seems on the INVITE as the number leaves teams, it is incorrect. On the offending number the P-ASSERTED-IDENTITY is showing as (tel:)The working example given shows this as a SIP Record. The CONTACT header is different. My Carrier has assured me the number is set up correctly and it this is coming from Teams   Read More

​