Caller treatment in a SIP network

• US 8,139,746 B2
• Filed: 12/31/2008
• Issued: 03/20/2012
• Est. Priority Date: 03/20/2001
• Status: Active Grant

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: Verizon Business Global LLC (Verizon Communications Inc.)
• Inventors: Gallant, John K., McMurry, Kathleen A.
• Primary Examiner(s): Addy, Thujuan K
• Application Number:
  US12/347,643
• Publication Number:
  US 20090110174A1
• Time in Patent Office: 1,175 Days
• Field of Search: 379/210.02, 379/142.01, 379/201.01, 379/114.05, 379/218.01, 379/196, 379/211.02, 379/207.13, 379/142.05, 370/352, 370/260
• US Class Current: 379/210.02
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• 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
• CPC Class Codes: H04M 7/0078 Security; Fraud detection; Fraud prevention

Abstract

In a SIP network, SIP servers are provisioned with information used to authenticate subscribers and entities that will be placing calls. This information can be used during call establishment to allow or deny calls, as well as to determine the appropriate party to bill if the call involves a charge, such as a long distance charge. In addition to allowing calls between authenticated and trusted entities, there is a need for the SIP server to allow certain kinds of calls that involve non-trusted users or entities. If non-trusted entities where not recognized, trusted users and entities within the SIP network would not be able to receive calls from users or entities not know to the SIP server that is providing them services.

Claims

1. A method, comprising:

receiving, at a server device, a packetized request from a calling party to initiate a communication;

determining, at the service device, whether the calling party is trusted, including identifying the calling party using a header in the packetized request; and

processing, at the server device, the packetized request based on determining whether the calling party is trusted, where processing the packetized request includes;

when the calling party is trusted, routing the communication to a called party, and

when the calling party is not trusted;

determining whether the called party will accept the communication from the calling party that is not trusted,

when the called party will accept the communication from the calling party that is not trusted, routing the communication to the called party, and

when the called party will not accept the communication from the calling party that is not trusted, responding to the calling party that the communication cannot be completed.

2. The method of claim 1, where responding to the calling party that the communication cannot be completed includes forwarding a denial-of-call message to the calling party.

3. The method of claim 1, where processing the packetized request further includes, when the calling party is not trusted:

determining whether the communication is billable; and

when the communication is not billable and when the called party will accept the communication from the calling party that is not trusted, routing the communication to the called party.

4. The method of claim 3, where processing the packetized request further includes:

when the communication is billable, determining whether billing information is available for the calling party; and

when billing information is not available for the calling party, responding to the calling party that the communication cannot be completed.

5. The method of claim 1, where determining whether the calling party is trusted includes:

identifying, in the request, seed data for an authentication algorithm;

receiving a message from the calling party, the messaging including a result of the seed data being used in the authentication algorithm; and

processing the result in the message.

6. The method of claim 1,

where the packetized request includes one or more authentication credentials of the calling party, and

where determining whether the calling party is trusted includes validating the one or more authentication credentials of the calling party.

7. The method of claim 1, where at least a portion of the communication is over a session initiation protocol (SIP) based network.

8. The method of claim 7, where the server device includes an SIP server and the calling party includes a SIP client.

9. A method comprising:

receiving, by a computer device and from a calling party, a request to initiate a call;

determining, by the computer device, whether to route the call to a called party, where the determining includes;

determining to route the call when the request includes information indicating that the calling party is trusted,

determining to route the call when the calling party is not trusted and when the calling party is verified, where verifying the calling party includes sending a message comprising seed data to the calling party and receiving a response from the calling party that includes a result of using the seed data in an authorization algorithm, and

determining to route the call when the calling part is not trusted and when the called party indicates that the communication will be accepted from the calling party that is not trusted; and

when the communication is not routed, responding, by the computer device, to the calling party that the communication cannot be completed.

10. The computer readable medium method of claim 9, further comprising:

determining whether the communication is billable,

where determining whether to route the call to a called party further includes determining to not route the communication when the calling party is not trusted and when the communication is not billable.

11. The method of claim 10, where determining whether the communication is billable includes determining whether billing information is available for the calling party, and

where determining whether to route the call to a called party further includes:

determining to not route the communication when the billing information is not available for the calling party.

12. The method of claim 9, where determining to route the call when the request includes information indicating that the calling party is trusted includes:

validating the information in the request.

13. A server device comprising:

a processor to;

receive a request to initiate a call from a calling party to a called party;

determine, in response to receiving the request, whether the calling party is served by the server device, where determining whether the calling party is served by the server device includes resolving whether the request includes a proxy authorization for the calling party;

in response to resolving that the request does not includes the proxy authorization for the calling party, resolve whether the calling party is a trusted party, and

in response to resolving either that the request includes the proxy authorization for the calling party or that the calling party is a trusted party, process the request to initiate the call to the called party.

14. The server device of claim 13, where the processor, when deciding whether the calling party is the trusted party, is further to:

forward a message to request additional information from the calling party;

receive the additional information from the calling party in response to the request for the additional information; and

process the received additional information.

15. The server device of claim 14, where the message includes seed data, and where the additional information from the calling party includes a result of using the seed data in an authentication algorithm.

16. The server device of claim 13, where the processor, when determining whether the calling party is served by the server device, is further to:

identify a host associated with the calling party, the host being identified based on data in the request; and

determine whether the host is served by the server device.

17. The server device of claim 13, where the processor is further to:

determine whether the call is billable when the calling partying is not the trusted party;

when the call is determined to be billable, determine whether billing information is known for the calling party; and

deny the request when the call is determined to be billable and the billing information is not known for the calling party.

18. The server device of claim 13, where the processor, when determining whether the calling party is served by the server device, is further to:

locate one or more authentication credentials of the calling party in the request; and

validate the one or more authentication credentials of the calling party.

19. The server device of claim 13, where at least a portion of the call is over a session initiation protocol (SIP) based network, and where the server device includes a SIP server and the calling party is associated with a SIP client.

20. The server device of claim 13, where the processor is further to:

resolve whether the called party accepts the call from the calling party that is not the trusted party, and

in response to resolving that the called party accepts the call from the calling party that is not the trusted party, process the request to initiate the call to the called party.