Microsoft Teams SBCs send # character unescaped

[davemidd]

It was confirmed to me (in support ticket #‎31034933) that the Microsoft SBCs send the # character in a Request-URI un-escaped. i.e. it is sent as a '#' rather than '%23'.

e.g. If the Teams user dials #123, we receive over the Direct Routing trunk:

INVITE sip:#[email protected]:5081;user=phone;transport=tls SIP/2.0.

instead of:

INVITE sip:%[email protected]:5081;user=phone;transport=tls SIP/2.0.

This is in violation of RFC-3261. (See Section 25 Augmented BNF for the SIP Protocol, Sub-section 25.1 Basic Rules). This RFC exception should be documented on this page.

Regards, David

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: fe63a384-d262-ea29-c793-6266228035bf
• Version Independent ID: a1bc23e7-3241-bc8b-7e41-d34941d9f4ff
• Content: Teams phone system direct routing: Definitions and RFC standards - Microsoft Teams
• Content Source: Teams/direct-routing-protocols.md
• Service: msteams
• GitHub Login: @CarolynRowe
• Microsoft Alias: crowe

[get-itips]

Hello @davemidd How are you? Unfortunately, we have no access to support cases information. I'll try to confirm this, thanks

[CarolynRowe]

Looping in @FilippSe

[get-itips]

@FilippSe Can you help clarify here? Thank you!

[FilippSe]

Under investigation at the moment

[get-itips]

Thanks @FilippSe

[get-itips]

@FilippSe How are you? Any update on the investigation? Thanks

[scanum]

@FilippSe Wanted to check here if there is any update on this investigation? Thanks!