Communication session addition via a host in deny new service mode
Communication servers hosting interactions between requesting devices and resources may require load sheading or maintenance and, as a result, be placed in Deny New Service (DNS) mode, whereby a subsequent session request is refused while existing sessions continue until concluded. However, an interaction comprising an existing session may be supplemented by a subsequent session, often utilizing a different application layer implementation. By providing the requesting device with an interaction identifier, a subsequent session made after the server has been placed in DNS mode, may be accepted and associated with the same resource associated with the existing session.
1. A system, comprising:
a processor; and
a network interface to a communications network; and
wherein the processor, upon receiving, via the network interface, a request for a new Session Initiation Protocol (SIP) session performs:
determining whether a server is in a Deny New Service (DNS) mode;
upon determining that the server is not in DNS mode, accepting the request;
upon determining that the server is in DNS mode, determining whether the request comprises an interaction identifier, wherein the interaction identifier is associated with a different SIP session;
upon determining that the server is in DNS mode and the request is devoid the interaction identifier, denying the request; and
upon determining that the server is in DNS mode and the request for the new SIP session does comprise the interaction identifier, accepting the request; and
wherein accepting the request comprises establishing the new SIP session between a requesting device and a resource device via the communications network.
2. The system of claim 1 , wherein the determining whether the request comprises the interaction identifier further comprises determining whether the interaction identifier is associated with the different SIP session comprising a currently active SIP session that has been previously established between the requesting device and the resource device.
3. The system of claim 2 , wherein the new SIP session and the currently active SIP session each utilize an application layer implementation and the application layer implementation is different between the new SIP session and the currently active SIP session.
4. The system of claim 3 , wherein one of the new SIP session and the currently active SIP session comprise the application layer implementation utilizing Hypertext Transfer Protocol (HTTP).
5. The system of claim 1 , wherein the processor, upon determining that the server is not in DNS mode, replies to the requesting device with the interaction identifier.
6. The system of claim 1 , wherein the request for the new SIP session comprises a callback Uniform Resource Locator (URL).
7. The system of claim 1 , wherein the server comprises disparate systems managed by signals provided, via the network interface, from the processor.
8. The system of claim 1 , wherein the server provides the interaction identifier to the requesting device.
9. The system of claim 1 , wherein determining whether the server is in the DNS mode comprises forwarding the request to the server and receiving a DNS reply in response.
10. The system of claim 1 , further comprising the processor, upon determining that the server is in DNS mode and the request is devoid of the interaction identifier, further determining whether the request comprises a priority greater than a previously determined threshold priority and, when the request comprises a priority greater than a previously determined threshold priority, accepting the request and, when the request does not comprise a priority greater than a previously determined threshold priority, denying the request.
11. A method, comprising,
issuing a first request for a first communication Session Initiation Protocol (SIP) session between a requesting device and a resource device via a network wherein the first communication SIP session is hosted by a server;
in response to the first request, receiving an interaction identifier;
in response to the first request, initiating the first communication SIP session comprising an exchange of computer encoded and decoded data between the requesting device and the resource device via the network;
at a later time, after the first communication SIP session has been initiated, issuing a second request for a second communication SIP session between the requesting device and the resource device via the network, the second request comprising the interaction identifier;
determining whether the server is in a Deny New Service (DNS) mode;
upon determining that the server is not in DNS mode, accepting the second request; and
upon determining that the server is in DNS mode, further determining whether the second request comprises an interaction identifier, wherein the interaction identifier is associated with a different SIP session, and denying the second request when the interaction identifier is absent and accepting the second request when the interaction identifier is present; and
wherein accepting the second request further comprises initiating the second communication SIP session comprising the exchange of computer encoded and decoded data between the requesting device and the resource device via the network.
12. The method of claim 11 , wherein first communication SIP session and the second communication SIP session each utilize an application layer implementation and the application layer implementation is different between the first communication SIP session and the second communication SIP session.
13. The method of claim 12 , wherein one of the first communication SIP session and the second communication SIP session comprise the application layer implementation utilizing Hypertext Transfer Protocol (HTTP).
14. The method of claim 11 , wherein at least one of the first request for the first communication SIP session and the second request for the second communication SIP session comprises a computer formatted message.
15. The method of claim 11 , wherein at least one of the first request for the first communication SIP session and the second request for the second communication SIP session comprises a priority indicia.
16. A method, comprising:
receiving, at a server, a first request for a first communication Session Initiation Protocol (SIP) session;
determining whether the server is in a Deny New Service (DNS) mode;
upon determining that the server is not in DNS mode, enabling the first communication SIP session;
upon determining that the server is in DNS mode, determining whether the first request comprises an interaction identifier, wherein the interaction identifier is associated with a different SIP session;
upon determining that the server is in DNS mode and the first request is devoid the interaction identifier, denying the first request; and
upon determining that the server is in DNS mode and the first request for the first SIP session does comprise the interaction identifier, accepting the first request; and
wherein accepting the first request comprises establishing the first SIP session comprising an exchange of computer encoded data between a requesting device, the requesting device providing the received first request, and a resource device utilizing a communications network.
17. The method of claim 16 , wherein determining whether the first request comprises the interaction identifier further comprises determining whether the interaction identifier is associated with the different SIP session comprising a currently active SIP session that has been previously established between the requesting device and the resource device.
18. The method of claim 17 , wherein the first communication SIP session and the currently active SIP session each utilize an application layer implementation and the application layer implementation is different between a new SIP session and the currently active SIP session.
19. The method of claim 18 , wherein one of the first SIP session and the currently active SIP session comprise the application layer implementation utilizing Hypertext Transfer Protocol (HTTP).
20. The method of claim 16 , the step of determining whether the server is not in DNS mode, further comprises replying to the first request with a callback Uniform Resource Locator (URL) comprising the interaction identifier.