Abstract: Packets of data can be processed by a chain or sequence of service functions which include both virtual and physical service functions. In one approach, the original header and/or payload of a packet is analyzed at a software switch to determine whether the packet should be processed by the chain. If such processing is indicated, a next service function to process the packet is identified. The packet is then forwarded to a virtualized or physical device which implements the next service function. A portion of the header, such as a MAC destination address, may be modified to direct the packet to the next function. Further, in some cases, a service function chain (SFC) header with a chain identifier may be added to, or removed from, the packet.

Abstract: Packets of data can be processed by a chain or sequence of service functions which include both virtual and physical service functions. In one approach, the original header and/or payload of a packet is analyzed at a software switch to determine whether the packet should be processed by the chain. If such processing is indicated, a next service function to process the packet is identified. The packet is then forwarded to a virtualized or physical device which implements the next service function. A portion of the header, such as a MAC destination address, may be modified to direct the packet to the next function. Further, in some cases, a service function chain (SFC) header with a chain identifier may be added to, or removed from, the packet.

Abstract: To provide for interoperability of Session Initiation Protocol (SIP) and H.323 for Secure Realtime Transport Protocol session establishment, a transmit key is received in a first protocol from a first endpoint. The transmit key is mapped from the first protocol to a second protocol and sent in the second protocol to a second endpoint to establish a secure communication session between the first endpoint and the second endpoint.

Abstract: A network node, configured for interfacing between a source network having a source telephony protocol and a packet network configured for sending and receiving data according to Internet Protocol, is configured for generating an IP based transport message for transport of normalized information describing a signaling message received from the source network according to the source telephony protocol. The network node is configured for generating a generic transparency descriptor having generic attributes for describing the signaling message. The generic attributes include a protocol name that specifies the source telephony protocol relative to a prescribed set of source telephony protocol types, and a message identifier that specifies the message type according to the source telephony protocol. Optional attributes specifying respective parameters based on the particular signaling message also may be generated.

Abstract: A method for sharing a call record between a first controller and a second controller is disclosed. The method comprises the step generating the call record in the first controller. For one embodiment, the call record comprises call parameters operable to establish a call connection between the first controller and a remote controller. The method also comprises the step of transferring the call record to the second controller. For one embodiment, the second controller performs as a stand-by controller and is able to take over the operations of the first controller in the event of failure of the first controller.

Abstract: A method for sharing a call record between a first controller and a second controller is disclosed. The method comprises the step generating the call record in the first controller. For one embodiment, the call record comprises call parameters operable to establish a call connection between the first controller and a remote controller. The method also comprises the step of transferring the call record to the second controller. For one embodiment, the second controller performs as a stand-by controller and is able to take over the operations of the first controller in the event of failure of the first controller.