System and method for communication diversion notification

1. A node comprising:

a transceiver configured to send, to an application server, a subscription message requesting notification when a communication for the node is diverted to another node, the subscription message containing a message body with criteria for the notification,

wherein the transceiver is further configured to receive, according to the subscription message, a notification message about a communication diversion, the notification message containing an Extensible Markup Language (XML) document with information related to the criteria, the information including a diversion reason element and a reason code associated with the diversion reason element, and

wherein the criteria of the subscription message specifies at least one of: an identity of an originating party of the communication; a time range for diversion notification; and a reason for diversion.

2. The node of claim 1 , wherein the reason code is a numeric value.

3. The node of claim 1 , wherein the subscription message is a SIP SUBSCRIBE request.

4. The node of claim 1 , wherein the criteria includes a time zone indicator.

5. The node of claim 1 , wherein the node is a user agent.

6. The node of claim 1 , wherein the reason code corresponds to a code specified in Internet Engineering Task Force (IETF) Request for Comments (RFC) 4458.

7. The node of claim 1 , wherein the notification message is a SIP (Session Initiated Protocol) NOTIFY request.

8. The node of claim 1 , wherein the criteria requests notification of some but not all communication diversions.

9. The node of claim 1 , wherein the XML document is an XML event package.

10. An application server comprising:

a transceiver configured to receive a subscription request from a node, the subscription request including a filter criteria for at least one specific reason to be notified; and

a processor configured to match a redirection reason of a communication diversion to the filter criteria,

wherein the transceiver is further configured to send a diversion notification message to the node, the diversion notification message containing an Extensible Markup Language (XML) document with a diversion reason element and a reason code associated with the diversion reason element, and

wherein the filter criteria of the subscription request specifies at least one of: an identity of an originating party of the communication; a time range for diversion notification; and a reason for diversion.

11. The application server of claim 10 , wherein the criteria is specifiable by a user to specify a time range for diversion notification.

12. The application server of claim 11 , wherein the subscription request comprises a time zone indicator, and wherein the application server is configured to send diversion notifications based on the time zone indicator and a current time zone of the node.

13. The application server of claim 10 , wherein the processor is further configured to map a cause param parameter to the diversion reason element.

14. The application server of claim 13 , wherein the reason code corresponds to a numeric code specified in Internet Engineering Task Force (IETF) Request for Comments (RFC) 4458.

15. The application server of claim 14 , wherein the mapping of the cause param parameter and the diversion reason element is one of:

Communication forwarding busy, the Cause value “486” as defined by RFC 4458 shall be used;

Communication forwarding no reply, the Cause value “408” as defined by RFC 4458 shall be used;

Communication forwarding unconditional, the Cause value “302” as defined by RFC 4458 shall be used;

Communication deflection (Immediate response), the Cause value “480” as defined by RFC 4458 shall be used;

Communication Forwarding Not Logged in, The Cause value “404” as defined by RFC 4458 shall be used;

Communication deflection during alerting, the cause value “487” as defined by RFC 4458 shall be used; or

Communication Forwarding on Subscriber Not reachable, the cause value “503” as defined by RFC 4458 shall be used.

16. The application server of claim 10 , wherein the communication diversion is a first communication diversion or a subsequent communication diversion.

17. The application server of claim 10 , wherein the diversion notification message is a SIP (Session Initiated Protocol) NOTIFY request with a body containing the XML document.

18. The application server of claim 10 , wherein the criteria requests notification of some but not all communication diversions.

19. The application server of claim 10 , wherein the XML document is an XML event package.

20. A non-transitory computer-readable medium storing instructions which are configured to cause an application server to perform operations comprising:

receiving a subscription request from a node, the subscription request including a filter criteria for at least one specific reason to be notified; and

matching a redirection reason of a communication diversion to the filter criteria,

wherein the transceiver is further configured to send a diversion notification message to the node, the diversion notification message containing an Extensible Markup Language (XML) document with a diversion reason element and a reason code associated with the diversion reason element, and

wherein the filter criteria of the subscription request specifies at least one of: an identity of an originating party of the communication; a time range for diversion notification; and a reason for diversion.

21. The non-transitory computer-readable medium of claim 20 , wherein the criteria is specifiable by a user to specify a time range for diversion notification.

22. The non-transitory computer-readable medium of claim 20 , wherein the instructions are further configured to cause the application server to perform an operation of mapping a cause param parameter to the diversion reason element.

23. The non-transitory computer-readable medium of claim 22 , wherein the reason code corresponds to a numeric code specified in Internet Engineering Task Force (IETF) Request for Comments (RFC) 4458.

24. The non-transitory computer-readable medium of claim 23 , wherein the mapping of the cause param parameter and the diversion reason element is one of:

Communication forwarding busy, the Cause value “486” as defined by RFC 4458 shall be used;

Communication forwarding no reply, the Cause value “408” as defined by RFC 4458 shall be used;

Communication forwarding unconditional, the Cause value “302” as defined by RFC 4458 shall be used;

Communication deflection (Immediate response), the Cause value “480” as defined by RFC 4458 shall be used;

Communication Forwarding Not Logged in, The Cause value “404” as defined by RFC 4458 shall be used;

Communication deflection during alerting, the cause value “487” as defined by RFC 4458 shall be used; or Communication Forwarding on Subscriber Not reachable, the cause value “503” as defined by RFC 4458 shall be used.

25. The non-transitory computer-readable medium of claim 20 , wherein the communication diversion is a first communication diversion or a subsequent communication diversion.

26. The non-transitory computer-readable medium of claim 20 , wherein the diversion notification message is a SIP (Session Initiated Protocol) NOTIFY request with a body containing the XML document.

27. The non-transitory computer-readable medium of claim 21 , wherein the subscription request comprises a time zone indicator, and wherein the application server is configured to send diversion notifications based on the time zone indicator and a current time zone of the node.

28. The non-transitory computer-readable medium of claim 20 , wherein the criteria requests notification of some but not all communication diversions.

29. The non-transitory computer-readable medium of claim 20 , wherein the XML document is an XML event package.