Abstract:
Various embodiments provide an apparatus and method for handling dynamic payloads in a heterogeneous network. An example embodiment includes a first node interface to receive a first request for data communication from a first node, the first request being coded in a first protocol and including information identifying a first payload type. The example embodiment includes a second node interface to receive a second request for data communication from a second node, the second request being coded in a second protocol and including information identifying a second payload type. The first node interface of the example embodiment configures a message coded in the first protocol to include the information identifying the second payload type and to send the message to the first node.
Abstract:
In one embodiment, a method includes receiving at a protocol translator a first message from a first endpoint to a second endpoint. The first message includes a list of media capabilities of the first endpoint. The method also includes transmitting from the protocol translator a second message to the second endpoint including a media capabilities request header and receiving at the protocol translator a response message from the second endpoint. The response message includes a response header including a list of the media capabilities of the second endpoint.
Abstract:
We describe a system embodiment comprising generating a Secure Real-Time Transport Protocol (SRTP) encapsulated packet and including a secure media indicator into the SRTP encapsulated packet. The method further comprises inserting the SRTP encapsulated packet into an SRTP voice stream associated with an active call between a source and a destination endpoint and indicating an end-to-end secure call between the source and destination endpoints responsive to the secure media indicator.And we describe a method embodiment comprising transmitting a request message from a source endpoint to a destination endpoint participating in an active call and setting a secure media flag in the request message at each node in a signaling path associated with the active call. The method further comprises returning a response message from the destination endpoint to the source endpoint responsive to the request and indicating an end-to-end secure call between the two endpoints.
Abstract:
Various embodiments provide a method and apparatus for providing secure blast calls. An example embodiment includes a secure blast call apparatus including a blast component to determine if a secure or a non-secure call connection is needed and to blast a call connection invite to a plurality of destination endpoints; and a connection component to determine if a responding destination endpoint is a secure or a non-secure destination endpoint, to establish a connection with a secure destination endpoint if a secure call connection is needed, and to establish a connection with a non-secure destination endpoint if a non-secure call connection is needed.
Abstract:
In a particular embodiment, a disconnect message with a progress indicator may be received in a PSTN protocol at a gateway. The gateway determines if the disconnect message includes a progress indicator. The gateway then generates a SIP message with a reason indicator that indicates the SIP message is mapped from a disconnect message that includes the progress indicator. The SIP message is then sent to a second gateway. The second gateway determines that the SIP message should be interworked to a disconnect message. The second gateway uses the reason indicator in the SIP message to determine this. Accordingly, the second gateway sends a disconnect with progress indicator to a second PBX. This allows the second PBX the option to either listen to an in-band announcement or to disconnect without listening to the in-band announcement.
Abstract:
In one embodiment, a session is refreshed using a message that is simplified for refresh purposes. The refresh message that is used is a message used for another purpose in a protocol (e.g., SIP). For example, a reINVITE message may be used as a refresh message. If the reINVITE message is used for its intended purpose, the reINVITE message may be used to change the characteristics of a session. This reINVITE message includes an SDP and full header such that the parameters can be properly changed. However, the reINVITE message may be used to refresh a session. This may be referred to as a simple refresh message. But, the simple refresh message does not include an SDP or any other message body. The simple refresh message includes only a reduced header. This reduces time spent building and parsing the simple refresh message.
Abstract:
In one embodiment, a first end device associated with a first user and a second end device associated with a second user may be participating in a call. During the call, the second user may wish to transfer the call to a third user. The second user has the choice of using a blind transfer or a consult transfer. In one embodiment, a gateway determines interworking information that is needed to interwork an H.450.2 message for the H.323 protocol to a SIP REFER message, and vice versa, to allow the call transfer.
Abstract:
Embodiments of the present invention provide techniques for refreshing a session. A session is refreshed using a refresh message that is enhanced for a refresh. For example, the refresh message does not include an SDP or any other message body. The message includes only a reduced header. This reduces time spent building and parsing the refresh message. Also, less bandwidth is used in sending the refresh messages.
Abstract:
In a particular embodiment, a network device receives, from a first device, a first call request for a second device. The network device may then send the first call request to a redirect server, which can determine where to send the call. The network device receives a response from the redirect server indicating an address to redirect the call request to. The network device then determines a redirect ID for the redirect. The network device sends a message to the first device with the redirect ID where the message indicates that a redirection occurred to the third device. The network device then receives a second call request from the first device that includes the redirect ID. The network device determines if the call was part of a previous redirect. If so, the second call request is sent to the address associated with the redirect ID.
Abstract:
In a particular embodiment, interworking between an H.323 protocol and SIP protocol for a call forward/redirection is provided. A first user may call a second user. The second user may have set preferences that cause a call redirection/forward to another end device. The end device may be associated with the second user or another user. Different preferences for the call forward/redirection may be provided. For example, a call may be forwarded all the time, when the second end device is busy, when there is no answer, etc. The redirection may then be performed using a gateway. When end devices communicate using SIP and H.323, the gateway provides interworking to provide the call forward/redirection. For example, the gateway maps a 3xx message in SIP to an H.450.3 message in the H.323 protocol, and vice versa, to provide the call forward/redirection.