Browse Prior Art Database

SIP URI fixing by implicit domain dialing/routing mechanism

IP.com Disclosure Number: IPCOM000242069D
Publication Date: 2015-Jun-17
Document File: 2 page(s) / 47K

Publishing Venue

The IP.com Prior Art Database

Related People

Benoit TRINITE: AUTHOR

Abstract

The proposed solution is to detect dynamically invalid SIP URI and fix it. Automatic completion done by endpoints in such a way can be used without any restriction and with the best possible user experience. The solution works without configuration and without deployment based pattern, and allows interworking with third parties.

This text was extracted from a Microsoft Word document.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 80% of the total text.

In SIP world, it is very common to attach an endpoint to a domain or directly to a SIP Server (a proxy or a B2BUA). In such case, and to simplify user experience, endpoint provides automatic completion with implicit host part when dialing a URI, i.e. if one dials an incomplete identity (that contains only the user part), the endpoint will automatically build the requested URI by combining the requested identity completed by its own domain or SIP Server name or address as host part.

For example,

-         when dialing an internal number like 1000, endpoints concatenate this dialed destination with an implicit host part and in this case, the resulting URI is correct: 1000@mydomain.fr

-         when dialing user plain identity like benoit.trinite, endpoints concatenate this dialed destination with an implicit host part and in this case, the resulting URI is correct: benoit.trinite@mydomain.fr

There are issues with this automatic URI completion which can lead to invalid and/or incomplete URI.

For example,

-         when dialing an IP address like 135.117.167.221, certain endpoints will concatenate this dialed destination with an implicit host part and in this case, the resulting URI is wrong : 135.117.167.221@mydomain.fr

-         when dialing a complete URI like meetingroom1.mycompany.fr, certain endpoints will concatenate this dialed destination with an implicit host part and in this case, the resulting URI is wrong : meetingroom1.mycompany.fr@mydomain.fr

The proposed solution is to detect dynamically invali...