METHOD AND SYSTEM FOR PROVIDING CALL SCREENING IN A PACKET-SWITCHED NETWORK

• US 20110158132A1
• Filed: 03/03/2011
• Published: 06/30/2011
• Est. Priority Date: 09/22/2005
• Status: Active Grant

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: Verizon Services Organization Incorporated (Verizon Communications Inc.)
• Inventors: Robbins, David C.
• Granted Patent: US 8,447,019 B2
• Time in Patent Office: Days
• US Class Current: 370/260
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1076 Screening of IP real time communications, e.g. spam over Internet telephony [SPIT]
• CPC Class Codes: H04L 65/1096 Supplementary features, e.g. call forwarding or call holding systems providing special services or facilities to telephony subscribers H04M3/42
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04M 1/27 Devices whereby a plurality of signals may be stored simultaneously
• CPC Class Codes: H04M 11/04 with alarm systems, e.g. fire, police or burglar alarm systems
• CPC Class Codes: H04M 7/006 Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP) , including next generation networks with a packet-switched transport layer H04L65/00 takes precedence; aspects not specific to the type of network H04M3/00; special services in those networks H04M3/42

Abstract

Embodiments of the invention provide systems and methods for determining whether a call in a packet-switched network to a first destination is to be forwarded, forwarding the call to a second destination based on a determination that the call is to be forwarded, notifying the first destination that the call has been forwarded, receiving a request from the first destination to screen the call, and enabling the first destination to screen the call.

Claims

1-19. -19. (canceled)

20. A system, comprising:

at least one non-transitory computer readable media for storing codes; and

at least one programmable processor configured execute the codes to perform;

receiving a call to a first destination from a caller;

determining whether a call forwarding is active at the first destination;

forwarding the call to a second destination based at least in part on the determination that the call forwarding is active;

notifying the first destination that the call has been forwarded;

determining whether the first destination wants to screen the call within a predetermined time period; and

enabling the first destination to screen the call based at least in part on the determination that the first destination wants to screen the call, wherein enabling the first destination to screen the call comprises creating a conference between the caller, the first destination, and the second destination.

21. The system according to claim 20, wherein forwarding the call to a second destination comprises transmitting a request to the second destination to create a dialog with the second destination.

22. The system according to claim 20, wherein notifying the first destination that the call has been forwarded comprises transmitting a notification message to the first destination, wherein the notification message comprises at least one of an identification of a dialog with the caller, an address associated with the second destination, and the predetermined time period.

23. The system according to claim 20, wherein determining whether the first destination wants to screen the call comprises receiving a notification of a detected device control condition at the first destination.

24. The system according to claim 20, wherein enabling the original destination to screen the call further comprises receiving a request at an address associated with the first destination.

25. The system according to claim 24, wherein the request comprises at least one of an identification of a dialog with the caller and a session description.

26. The system according to claim 20, wherein enabling the original destination to screen the call further comprises creating a dialog with the first destination.

27. The system according to claim 20, wherein creating a conference between the caller, the first destination, and the second destination comprises assigning a conference uniform resource identifier (URI) to the conference between the caller, the first destination, and the second destination.

28. The system according to claim 27, wherein creating a conference between the caller, the first destination, and the second destination further comprises transmitting a conference message to the first destination, wherein the conference message comprises at least one of the conference uniform resource identifier (URI) and a parameter associated with the conference.

29. The system according to claim 20, wherein the at least one processor is further configured to execute the codes to perform:

receiving a request to create a two-way media session with the first destination.

30. The system according to claim 29, wherein the request to create the two-way media session comprises a request that enables the first destination to transmit audio data to at least one of the second destination or a caller associated with the call.

31. The system according to claim 20, wherein the at least one processor is further configured to execute the codes to perform:

determining whether the first destination wants to eject the second destination from the call.

32. The system according to claim 31, wherein determining whether the first destination wants to eject the second destination from the call comprises receiving a refer request from the first destination, wherein the refer request comprises at least one of an address associated with the second destination and an indication to eject the second destination from the call.

33. A method, comprising:

receiving a call to a first destination from a caller;

determining whether a call forwarding is active at the first destination;

forwarding the call to a second destination based at least in part on the determination that the call forwarding is active;

notifying the first destination that the call has been forwarded;

determining whether the first destination wants to screen the call within a predetermined time period; and

enabling the first destination to screen the call based at least in part on the determination that the first destination wants to screen the call, wherein enabling the first destination to screen the call comprises creating a conference between the caller, the first destination, and the second destination.

34. The method according to claim 33, wherein forwarding the call to a second destination comprises transmitting a request to the second destination to create a dialog with the second destination.

35. The method according to claim 33, wherein notifying the first destination that the call has been forwarded comprises transmitting a notification message to the first destination, wherein the notification message comprises at least one of an identification of a dialog with the caller, an address associated with the second destination, and the predetermined time period.

36. The method according to claim 33, wherein determining whether the first destination wants to screen the call comprises receiving a notification of a detected device control condition at the first destination.

37. The method according to claim 33, wherein enabling the original destination to screen the call further comprises receiving a request at an address associated with the first destination.

38. The method according to claim 37, wherein the request comprises at least one of an identification of a dialog with the caller and a session description.

39. The method according to claim 33, wherein enabling the original destination to screen the call further comprises creating a dialog with the first destination.

40. The system according to claim 33, wherein creating a conference between the caller, the first destination, and the second destination comprises assigning a conference uniform resource identifier (URI) to the conference between the caller, the first destination, and the second destination.

41. The method according to claim 40, wherein creating a conference between the caller, the first destination, and the second destination further comprises transmitting a conference message to the first destination, wherein the conference message comprises at least one of the conference uniform resource identifier (URI) and a parameter associated with the conference.

42. The method according to claim 33, further comprising receiving a request to create a two-way media session with the first destination.

43. The method according to claim 42, wherein the request to create the two-way media session comprises a request that enables the first destination to transmit audio data to at least one of the second destination or a caller associated with the call.

44. The method according to claim 33, further comprising determining whether the first destination wants to eject the second destination from the call.

45. The method according to claim 44, wherein determining whether the first destination wants to eject the second destination from the call comprises receiving a refer request from the first destination, wherein the refer request comprises at least one of an address associated with the second destination and an indication to eject the second destination from the call.