System and method for enabling DTMF detection in a VoIP network

• US 8,271,049 B2
• Filed: 01/24/2011
• Issued: 09/18/2012
• Est. Priority Date: 03/02/2006
• Status: Active Grant

• Current Assignee: Tango Networks Incorporated
• Original Assignee: Tango Networks Incorporated
• Inventors: Silver, Andrew, Lewis, Lathan, Landgren, Patricia
• Primary Examiner(s): Afshar, Kamran
• Assistant Examiner(s): DEAN, JR, JOSEPH E
• Application Number:
  US13/012,332
• Publication Number:
  US 20110116498A1
• Time in Patent Office: 603 Days
• Field of Search: 455/401, 455/567
• US Class Current: 455/567
• CPC Class Codes: H04L 12/66 Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
• CPC Class Codes: H04L 65/00 Network arrangements, protocols or services for supporting real-time applications in data packet communication real-time or near real-time messaging, e.g. instant messaging [IM] H04L51/04; selective video distribution H04N21/00
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/102 Gateways arrangements for connecting between networks having differing types of switching systems, e.g. gateways, H04L12/66
• CPC Class Codes: H04L 65/1023 Media gateways
• CPC Class Codes: H04L 65/1033 Signalling gateways
• CPC Class Codes: H04L 65/104 in the network
• CPC Class Codes: H04L 65/1053 IP private branch exchange [PBX] functionality entities or arrangements circuit switched PBXs H04M3/00
• 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/1095 Inter-network session transfer or sharing
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 65/1106 Call signalling protocols; H.323 and related
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04M 15/00 Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
• CPC Class Codes: H04M 15/57 for integrated multimedia messaging subsystem [IMS]
• CPC Class Codes: H04M 15/63 based on the content carried by the session initiation protocol [SIP] messages
• CPC Class Codes: H04M 15/8292 Charging for signaling or unsuccessful connection
• CPC Class Codes: H04M 2203/1091 Fixed mobile conversion
• CPC Class Codes: H04M 2215/208 : IMS, i.e. Integrated Multimedia messaging Subsystem
• CPC Class Codes: H04M 3/42042 : Notifying the called party of information on the calling party details within substation equipment H04M1/57, signalling details H04Q3/72
• CPC Class Codes: H04M 3/42068 : where the identifier is used to access a profile
• CPC Class Codes: H04M 3/42102 : Making use of the called party identifier
• CPC Class Codes: H04M 3/42314 : in private branch exchanges
• 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/0075 : Details of addressing, directories or routing tables
• CPC Class Codes: H04M 7/009 : in systems involving PBX or KTS networks
• CPC Class Codes: H04Q 2213/13034 : A/D conversion, code compression/expansion
• CPC Class Codes: H04Q 2213/1307 : Call setup
• CPC Class Codes: H04Q 2213/13091 : CLI, identification of calling line
• CPC Class Codes: H04Q 2213/13098 : Mobile subscriber
• CPC Class Codes: H04Q 2213/13109 : Initializing, personal profile
• CPC Class Codes: H04Q 2213/13176 : Common channel signaling, CCS7
• CPC Class Codes: H04Q 2213/1318 : Ringing
• CPC Class Codes: H04Q 2213/13196 : Connection circuit/link/trunk/junction, bridge, router, gateway
• CPC Class Codes: H04Q 2213/13204 : Protocols
• CPC Class Codes: H04Q 2213/1322 : PBX
• CPC Class Codes: H04Q 2213/13224 : Off-net subscriber, dial in to/out from network, teleworking
• CPC Class Codes: H04Q 2213/13296 : Packet switching, X.25, frame relay
• CPC Class Codes: H04Q 2213/13348 : Channel/line reservation
• CPC Class Codes: H04Q 2213/13384 : Inter-PBX traffic, PBX networks, e.g. corporate networks
• CPC Class Codes: H04Q 2213/13389 : LAN, internet
• CPC Class Codes: H04Q 2213/13405 : Dual frequency signaling, DTMF
• CPC Class Codes: H04Q 2213/13407 : Detection of data transmission mode
• CPC Class Codes: H04Q 3/0025 : Provisions for signalling
• CPC Class Codes: H04Q 3/0045 : involving hybrid, i.e. a mixture of public and private, or multi-vendor systems
• CPC Class Codes: H04Q 3/62 : for connecting to private branch exchanges
• CPC Class Codes: H04Q 3/72 : Finding out and indicating number of calling subscriber
• CPC Class Codes: H04W 28/0289 : Congestion control load shedding arrangements in network planning H04W16/08; performing reselection for handling the traffic H04W36/22; wireless traffic scheduling H04W72/12
• CPC Class Codes: H04W 4/16 : Communication-related supplementary services, e.g. call-transfer or call-hold
• CPC Class Codes: H04W 4/20 : Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
• CPC Class Codes: H04W 40/00 : Communication routing or communication path finding
• CPC Class Codes: H04W 40/02 : Communication route or path selection, e.g. power-based or shortest path routing
• CPC Class Codes: H04W 40/22 : using selective relaying for reaching a BTS [Base Transceiver Station] or an access point
• CPC Class Codes: H04W 40/30 : for proactive routing
• CPC Class Codes: H04W 76/10 : Connection setup
• CPC Class Codes: H04W 76/12 : Setup of transport tunnels
• CPC Class Codes: H04W 76/19 : Connection re-establishment
• CPC Class Codes: H04W 76/20 : Manipulation of established connections
• CPC Class Codes: H04W 76/22 : Manipulation of transport tunnels
• CPC Class Codes: H04W 76/28 : Discontinuous transmission [DTX]; Discontinuous reception [DRX]
• CPC Class Codes: H04W 76/30 : Connection release
• CPC Class Codes: H04W 8/12 : between location registers or mobility servers
• CPC Class Codes: H04W 8/26 : Network addressing or numbering for mobility support
• CPC Class Codes: H04W 80/00 : Wireless network protocols or protocol adaptations to wireless operation
• CPC Class Codes: H04W 84/16 : WPBX [Wireless Private Branch Exchange]
• CPC Class Codes: H04W 88/16 : Gateway arrangements
• CPC Class Codes: H04W 92/02 : Inter-networking arrangements
• CPC Class Codes: H04W 92/06 : between gateways and public network devices
• CPC Class Codes: H05K 999/99 : dummy group

Abstract

A method, mobile terminal, and system for selectively establishing an outgoing caller ID on a mobile terminal served by a wireless network, for identifying a line called on a mobile terminal, and for directing a call from a mobile terminal to a network subscriber based on accessed information of the subscriber in the subscriber'"'"'s network.

Claims

1. A method, comprising:

configuring a packet engine in a bearer stream between a first telephone device and a second telephone device;

determining, by the packet engine, via a buffer and an inter-digit timer utilized by the packet engine, a start and a stop of patterns associated with dual-tone multi-frequency digits in order to differentiate a feature invocation digit pattern from the dual-tone multi-frequency digits; and

reporting, by the packet engine, a dual-tone multi-frequency event to the call server in response to determining the start and a stop of patterns associated with the dual-tone multi-frequency digits.

2. The method as specified in claim 1, further comprising using, by the call server, IPTables port mappings to anchor the bearer stream.

3. The method as specified in claim 1, further comprising providing, by the call server, a mid-call service based on the reported dual-tone multi-frequency digit.

4. The method as specified in claim 1, wherein the packet engine is implemented as a software-only entity.

5. The method as specified in claim 1, further comprising deploying the packet engine on a common hardware platform as the call server.

6. The method as specified in claim 1, further comprising deploying the packet engine on a separate hardware platform from the call server.

7. The method as specified in claim 1, further comprising statically linking the packet engine into a process of the call server.

8. The method as specified in claim 1, wherein the packet engine is scalable.

9. The method as specified in claim 1, wherein the packet engine supports control by multiple call servers in the Voice over Internet Protocol network.

10. The method as specified in claim 1, wherein the call server controls multiple packet engines in the Voice over Internet Protocol network.

11. The method as specified in claim 1, wherein the packet engine comprises a user space process and a kernel module.

12. The method as specified in claim 11, further comprising:

receiving, by the user space process, commands from the call server;

sending, by the user space process, commands to the call server; and

utilizing, by the user space process, IPTables to create port mappings within an IP stack.

13. The method as specified in claim 12, wherein the kernel module determines which Real-time Transport Protocol packets of the bearer stream received from the IP stack include dual-tone multi-frequency digits.

14. The method as specified in claim 13, further comprising:

examining, by the kernel module, headers of each Real-time Transport Protocol packet; and

checking a Payload Type field for an indication of whether the Real-Time Transport Protocol packet contains a dual-tone multi-frequency event.

15. The method of claim 14, wherein the dual-tone multi-frequency event is encoded per IETF RFC 2833, the method further comprising sending, by the kernel module, the Real-Time Transport Protocol packet to the user space process for further application level processing.

16. The method as specified in claim 14, wherein the kernel module comprise a Linux kernel module operating as an extension to a Linux kernel, and wherein the Linux kernel module facilitates examination of incoming Real-time Transport Protocol packets.

17. A server, comprising:

a user space module configured to receive and send commands from and to the Voice over Internet Protocol network; and

a kernel module configured to receive a bearer stream comprising Real-time Transport Protocol packets from an IP stack, wherein the kernel module utilizes an inter digit timer to determine a start and a stop of patterns associated with the dual-tone multi-frequency digits in order to differentiate a feature invocation digit pattern from the dual-tone multi-frequency digits;

wherein the user space module reports a dual-tone multi-frequency event to the call server in response to determining the start and a stop of patterns associated with the dual-tone multi-frequency digits.

18. The packet engine as specified in claim 17, wherein the kernel module comprise a Linux kernel module, and wherein the Linux kernel module examines headers of each Real-time Transport Protocol packet and checks a Payload Type field, wherein the Payload Type field indicates whether the Real-time Transport Protocol packet contains a dual-tone multi-frequency event.

19. The packet engine as specified in claim 18, wherein the dual-tone multi-frequency event is encoded per IETF RFC 2833, and the Linux kernel module sends the Real-Time Transport Protocol packet to the user space module for further application level processing.

20. The packet engine as specified in claim 18, wherein the Linux kernel module operates as an extension to a Linux kernel and facilitates examination of incoming Real-time Transport Protocol packets.

21. A server, comprising:

a first module configured to establish a Voice over Internet Protocol call session; and

a second module configured to detect digit events within an active Voice over Internet Protocol call session, wherein the second module utilizes a buffer and an inter digit timer to determine a start and a stop of patterns associated with the digit events in order to differentiate a feature invocation digit pattern from the digit events.

22. The call server as specified in claim 21, wherein the Voice over Internet Protocol call server is configured to operate as an intermediate node on a signaling path of the call session.

23. The call server as specified in claim 21, wherein the Voice over Internet Protocol call server is further configured to provide mid-call services as a function of detected digit events originated by a party to the call session.

24. The call server as specified in claim 21, wherein the Voice over Internet Protocol call server comprises a packet engine comprising a user space module configured to receive and send commands from and to a Voice over Internet Protocol network, and wherein the user space module is configured to utilize Linux IPTables to create port mappings within an IP stack.

25. The call server as specified in claim 24, wherein the packet engine further comprises a Linux kernel module adapted to receive Real-time Transport Protocol packets of the call session.

26. The call server as specified in claim 25, wherein the Linux kernel module examines headers of each Real-time Transport Protocol packet and checks a Payload Type field, wherein the Payload Type field indicates whether the Real-time Transport Protocol packet contains at least one digit event.

27. The call server as specified in claim 26, wherein the digit events are encoded per IETF RFC 2833, and the Linux kernel module sends the Real-Time Transport Protocol packet to the user space module for further application level processing.

28. The call server as specified in claim 26, wherein the Linux kernel module operates as an extension to a Linux kernel and facilitates examination of incoming Real-time Transport Protocol packets.