# US 2014/0156858 A1 · System and method for geographic sip scaling > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2014/0156858 A1 - Document ID: US20140156858A1 - Status: Published application - Kind: A1 - Application number: 14/176,473 - Filed: 2014-02-10 - Published: 2014-06-05 - Earliest claimed: 2011-02-02 - Assignees: Junction Networks Inc. - Applicants: Junction Networks, Inc. - Inventors: John RIORDAN; Eric TAMME - Web page: https://patentgrep.com/patent/US20140156858A1 ## CPC - H04L 61/2564: {for a higher-layer protocol, e.g. for session initiation protocol [SIP]} - H04L 61/2589: over a relay server, e.g. traversal using relay for network address translation [TURN] - H04L 65/1045: Proxies, e.g. for session initiation protocol [SIP] - H04L 65/1073: Registration or de-registration - H04L 65/1104: Session initiation protocol [SIP] - H04L 65/80: Responding to QoS - H04L 61/4511: using domain name system [DNS] - H04L 61/4535: using an address exchange platform which sets up a session between two nodes, e.g. rendezvous servers, session initiation protocols [SIP] registrars or H.323 gatekeepers - H04L 2101/385: Uniform resource identifier for session initiation protocol [SIP URI] - H04L 2101/69: using geographic information, e.g. room number - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Described herein are aspects relating to a system and method for scaling a session initiation protocol communication system that allows components of the system to be distributed and/or scaled across multiple and different hardware, networks, systems, and locations. ## Claims ### Claim 1 A method for processing a session initiation protocol (SIP) request, comprising: receiving a SIP request from a user agent (UA) comprising an identifier of a different UA; obtaining the lookup information of the different UA based on a request to a registrar comprising the identifier; and generating a routing header for the SIP request based at least in part on whether the lookup information includes a path header for the different UA. ### Claim 2 (depends on 1) The method of claim 1, wherein generating the routing header comprises including information from the path header in the routing header where the lookup information includes the path header. ### Claim 3 (depends on 2) The method of claim 2, wherein the information comprises an internet protocol (IP) address of a proxy server related to the different UA. ### Claim 4 (depends on 1) The method of claim 1, wherein generating the routing header comprises including information regarding the different UA in the routing header where the lookup information does not include the path header. ### Claim 5 (depends on 4) The method of claim 4, wherein the information comprises an internet protocol (IP) address of the different UA or a related network address translation (NAT) device received from the registrar in the location information. ### Claim 6 (depends on 1) The method of claim 1, further comprising: receiving UA contact information from the UA including at least one of a SIP uniform resource identifier (URI) or an internet protocol (IP) address of the UA; and transmitting at least a portion of the UA contact information to the registrar for retrieval by other proxy servers. ### Claim 7 (depends on 6) The method of claim 6, further comprising creating a UA path header that includes the portion of the UA contact information, wherein the transmitting comprises transmitting the UA path header to the registrar. ### Claim 8 (depends on 1) The method of claim 1, further comprising: appending the routing header to the SIP request; and transmitting the SIP request based at least in part on an internet protocol (IP) address in the routing header. ### Claim 9 (depends on 8) The method of claim 8, wherein obtaining the lookup information comprises obtaining lookup information for a plurality of different UAs related to the identifier, wherein appending comprises appending a plurality of routing headers to a plurality of instances of the SIP request, and wherein transmitting comprises transmitting the plurality of instances of the SIP request to the plurality of different UAs. ### Claim 10 (depends on 9) The method of claim 9, further comprising: receiving a response to one of the plurality of instances of the SIP request from one of the plurality of different UAs; and cancelling one or more of the plurality of instances of the SIP request related to a remaining portion of the plurality of different UAs. ### Claim 11 A method for processing a session initiation protocol (SIP) request, comprising: receiving a request for lookup information of a first user agent (UA) from a second proxy server related to a second UA; determining the lookup information for the first UA based on a path header received from a first proxy server related to the first UA; and transmitting at least a portion of the lookup information to the first proxy server based on whether the first proxy server is the second proxy server. ### Claim 12 (depends on 11) The method of claim 11, wherein the transmitting comprises including the path header with the portion of the lookup information where the first proxy server is different from the second proxy server. ### Claim 13 (depends on 11) The method of claim 11, further comprising removing the path header from the portion of the lookup information where the first proxy server is the second proxy server. ### Claim 14 A system for processing a session initiation protocol (SIP) request, comprising: a registrar for receiving a request for lookup information of a first user agent (UA) from a second proxy server related to a second UA; and a database for storing the lookup information for the first UA based on a path header received from a first proxy server related to the first UA, wherein the registrar determines the lookup information from the database based at least in part on an identifier of the first UA specified in the request, and transmits at least a portion of the lookup information to the first proxy server based on whether the first proxy server is the second proxy server. ### Claim 15 (depends on 14) The system of claim 14, wherein the registrar includes the path header in transmitting the portion of the lookup information where the first proxy server is different from the second proxy server. ### Claim 16 (depends on 14) The system of claim 14, wherein the registrar removes the path header from the portion of the lookup information where the first proxy server is the second proxy server.