Systems and methods for mapping a URI to a plurality of endpoints for a SIP communication

1. A method for providing unauthenticated client access to session initiation protocol (SIP) communication services provided by an Ethernet device comprising a proxy and a conference bridge, comprising:

receiving, by a device installed as an Ethernet adapter, a SIP call request from a first client, the SIP call request comprising a first uniform resource identifier (URI), the first URI comprising a SIP alias;

determining, by the device, that the first client has not been authenticated;

identifying, by the device, that the first URI comprises a SIP alias;

proxying, by the device, the SIP call request to an endpoint associated with the SIP alias, responsive to the identification of the first URI as a SIP alias;

receiving, by the device, a second SIP call request from the first client, the SIP call request comprising a third URI; and

blocking, by the device, the second SIP call request.

2. The method of claim 1 , further comprising determining that the SIP alias corresponds to a conference bridge address, and wherein proxying the SIP call request is performed responsive to the determination that the SIP alias corresponds to the conference bridge address.

3. The method of claim 2 , further comprising determining that the conference bridge address is an address for an active conference session, and wherein proxying the SIP call request is performed responsive to the determination that the conference bridge address is an address for the active conference session.

4. The method of claim 1 , wherein determining that the first client has not been authenticated comprises determining that the first client has not registered an address with a registrar of the device.

5. The method of claim 1 , wherein determining that the first client has not been authenticated comprises determining that the first client lacks authorization to register an address.

6. The method of claim 1 , wherein identifying that the first URI comprises a SIP alias comprises retrieving a registration record associated with the first URI from a registrar of the device.

7. The method of claim 6 , further comprising identifying an explicit alias indicator in the retrieved registration record.

8. The method of claim 6 , further comprising identifying that the first URI is associated with a plurality of addresses.

9. The method of claim 6 , further comprising identifying that the first URI is associated with an address of a conference bridge.

10. The method of claim 6 , further comprising identifying that the first URI is associated with a second URI.

11. The method of claim 1 , wherein blocking the second SIP call request comprises blocking the request, responsive to determining that the third URI corresponds to an internal extension.

12. The method of claim 1 , wherein blocking the second SIP call request comprises blocking the request, responsive to determining that the third URI does not correspond to an active conference session.

13. The method of claim 1 , wherein blocking the second SIP call request comprises blocking the request, responsive to determining that a number of requests received from the first client exceeds a predetermined threshold.

14. The method of claim 1 , further comprising adding the first client to a blacklist.

15. A system providing unauthenticated client access to session initiation protocol (SIP) communication services provided by an Ethernet device comprising a proxy and a conference bridge, comprising:

a device installed as an Ethernet adapter, comprising an Ethernet interface for receiving a SIP call request from a first client, the SIP call request comprising a first uniform resource identifier (URI), the first URI comprising a SIP alias;

wherein the device is configured for:

determining that the first client has not been authenticated,

identifying that the first URI comprises a SIP alias, and

proxying the SIP call request to an endpoint associated with the SIP alias, responsive to the identification of the first URI as a SIP alias; and

wherein the Ethernet interface is further configured for receiving a second SIP call request from the first client, the SIP call request comprising a third URI; and the device is further configured for blocking the second SIP call request.

16. The system of claim 15 , wherein the device further comprises a conference bridge, and wherein the device is configured for determining that the SIP alias corresponds to a conference bridge address, and wherein proxying the SIP call request is performed responsive to the determination that the SIP alias corresponds to the conference bridge address.

17. The system of claim 16 , wherein the device is further configured for determining that the conference bridge address is an address for an active conference session, and wherein proxying the SIP call request is performed responsive to the determination that the conference bridge address is an address for the active conference session.

18. The system of claim 15 , wherein the device comprises a registrar, and wherein the device is configured for determining that the first client has not registered an address with the registrar of the device.

19. The system of claim 15 , wherein the device is configured for determining that the first client lacks authorization to register an address.

20. The system of claim 15 , wherein the device comprises a registrar, and wherein the device is configured for retrieving a registration record associated with the first URI from the registrar of the device.

21. The system of claim 20 , wherein the device is configured for identifying an explicit alias indicator in the retrieved registration record.

22. The system of claim 20 , wherein the device is configured for identifying that the first URI is associated with a plurality of addresses.

23. The system of claim 20 , wherein the device comprises a conference bridge, and wherein the device is configured for identifying that the first URI is associated with an address of the conference bridge.

24. The system of claim 20 , wherein the device is configured for identifying that the first URI is associated with a second URI.