Skip to content

Conversation

@junction1153b
Copy link
Contributor

This change restores RFC 3261 compliance for Remote-Party-ID header construction.

Previously, when the User-Agent string contained “Poly” or “Polycom,” FreeSWITCH intentionally omitted the sip: prefix in the RPID to accommodate legacy Polycom firmware display issues. Those early devices would incorrectly render the full SIP URI on-screen.

Modern Poly/Polycom firmware has resolved this behavior. To ensure proper interoperability with RFC-compliant SBCs (e.g., Sansay VSXi, Ribbon, BroadWorks) and strict SIP stacks, we now always include the sip: prefix in the RPID while retaining all other Polycom-specific logic and formatting.

…ents

This change restores RFC 3261 compliance for Remote-Party-ID header construction.

Previously, when the User-Agent string contained “Poly” or “Polycom,” FreeSWITCH intentionally omitted the sip: prefix in the RPID <addr-spec> to accommodate legacy Polycom firmware display issues. Those early devices would incorrectly render the full SIP URI on-screen.

Modern Poly/Polycom firmware has resolved this behavior. To ensure proper interoperability with RFC-compliant SBCs (e.g., Sansay VSXi, Ribbon, BroadWorks) and strict SIP stacks, we now always include the sip: prefix in the RPID while retaining all other Polycom-specific logic and formatting.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant