SIP. D50444 revision 1.1
|
|
- Alice Cornelia Wilkins
- 8 years ago
- Views:
Transcription
1 SIP D50444 revision 1.1 May 2008
2 TABLE OF CONTENTS INTRODUCTION...5 WHAT IS SIP?...6 Components...6 User Agent...6 Proxy Server...6 Registrar...7 Redirect Server...7 Requests for Comments...7 SIP Messages...9 SIP Requests...9 SIP Responses...9 Session Description Protocol (SDP)...11 TANDBERG SIP TERMINALS...12 TANDBERG MXP Endpoints...13 Software F2-F6 SIP Server Interaction...13 F2-F6 Call Flow (Site A calls Site B)...13 F2-F6 Audio...14 F2-F6 Video...14 Jitter and Latency...15 RFC Support...16 TANDBERG MXP Personal Series Endpoints...18 L2-L5 SIP Server Interaction...18 L2-L5 Call Flow (Site A calls Site B)...18 L2-L5 Audio...19 L2-L5 Video...19 Jitter and Latency...19 RFC Support...20 TANDBERG SIP INFRASTRUCTURE...22 TANDBERG MPS 200/ J3-J4 SIP Server Interaction...24 J3-J4 Call Flow (MPS calls Site A)...24 J3-J4 Audio...25 J3-J4 Video...25 Jitter and Latency...25 RFC Support...26 TANDBERG Codian 4500 Series MCU...28 Software 2.2(1.0) SIP Server Interaction...28 Software 2.2(1.0) Call Flow...28 Software 2.2(1.0) Audio...29 Software 2.2(1.0) Video...29 Jitter and Latency...30 RFC Support...30 TANDBERG Codian 4200 Series MCU...31 Software 2.2(1.0) SIP Server Interaction...31 Software 2.2(1.0) Call Flow...31 Software 2.2(1.0) Audio...32 Software 2.2(1.0) Video...32 Jitter and Latency...33 RFC Support...33 D50444 Page 2
3 TANDBERG Codian 3500 Series IP Gateway...34 Software 1.1(1.1) SIP Server Interaction...34 Software 1.1(1.1) Call Flow...34 Software 1.1(1.1) Audio...35 Software 1.1(1.1) Video...35 Jitter and Latency...36 RFC Support...36 TANDBERG 3G Gateway...37 R2-R3 SIP Server Interaction...37 R2-R3 Call Flow (Gateway calls Site A call initiated from 3G side)...37 R1-R3 Audio...38 R1-R3 Video...38 Jitter and Latency...38 TANDBERG Video Portal...39 V2-V3 SIP Server Interaction...39 V2-V3 Call Flow (Video Portal calls Site A call initiated from 3G side)...39 V2-V3 Audio...40 V2-V3 Video...40 Jitter and Latency...40 TANDBERG Content Server...41 S3 SIP Server Interaction...41 S3 Call Flow (Content Server calls Site A)...41 S3 Audio...42 S3 Video...42 Jitter and Latency...42 RFC Support...42 TANDBERG Codian 2200 Series IPVCR...44 Software 2.2(1.0) SIP Server Interaction...44 Software 2.2(1.0) Call Flow...44 Software 2.2(1.0) Audio...45 Software 2.2(1.0) Video...45 Jitter and Latency...46 RFC (Request for Comment) Support...46 TANDBERG Video Communication Server...47 TANDBERG SIP Server Traversal Interaction...47 TANDBERG SIP Server Non-Traversal Interaction...47 TANDBERG VCS Control to VCS Expressway Traversal Interaction...48 TANDBERG VCS Control to VCS Expressway Call Flow...49 STUN Client-to-VCS Expressway Interaction...50 STUN Relay...51 RFC (Request for Comment) Support...51 LIST OF TERMS...52 REFERENCES...54 D50444 Page 3
4 DOCUMENT REVISION HISTORY Rev 1.0 Rev 1.1 Initial Version Minor Revision; Added References D50444 Page 4
5 INTRODUCTION Session Initiation Protocol (SIP) is an application layer protocol for creating, terminating, and modifying of multimedia sessions with one or more participants, developed by the Internet Engineering Task Force (IETF). SIP is independent of the multimedia session handled and of the mechanism used to describe the session. The IETF also designed SIP to be independent of the underlying transport layer. SIP is similar to H.323 and shares some of the same protocols, such as TCP, UDP, and others. With the ascent of the Internet as a rival to the circuit-switched telephony network, a signaling protocol was needed to set up and terminate connections, in order to assimilate telephony services with the technology of IP. A motivating goal for SIP was to provide a signaling and call setup protocol for IPbased communications that can support some of the call processing functions and features present in the public switched telephony network. This document is intended to discuss SIP from both a general and TANDBERG-specific point of view. Varying levels of depth will be included within the document in order to provide a complete view of the technology and how it is implemented. In addition, deployment scenarios will be discussed, such as firewall traversal, and how those deployments will interact with other IP network components (e.g. firewalls). D50444 Page 5
6 WHAT IS SIP? Session Initiation Protocol (SIP) is an application layer IETF standard protocol for initiating interactive user sessions that involve multimedia elements such as video, voice, chant, and others. SIP can establish multimedia sessions, and modify, or terminate them. SIP is based on the Web protocol HTTP, and like HTTP, SIP is a text-based, request-response protocol, utilizing TCP and/or UDP as the transport mechanism for the session messages. The SIP protocol itself is only responsible for establishing a session between two end points of a conversation, utilizing several other protocols to establish the communication services over that connection. Session Description Protocol (SDP), for example, describes the media content of the session, including the audio, video and data capabilities of the endpoint, media ports to be used for connections as well as any other information that would be pertinent to the media connections between the end points Components The SIP protocol defines several entities. Each entity has a specific function and participates in SIP communication as a client (initiates requests), as a server (responds to requests), or as both. One physical device can have the functionality of more than one logical SIP entity. An example, is a network server working as a Proxy server, can also function as a Registrar at the same time. User Agent A User Agent (UA) is an application that interfaces between the user and he SIP network. User Agents initiate and terminate sessions by exchanging requests and responses. User Agents operate in two fashions, but also may function as both. When send SIP messages, the UA acts as a User Agent Client (UAC), and when receiving messages, it acts as a User Agent Server (UAS). User Agent Client (UAC) A User Agent Client (UAC) is an application that initiates SIP requests to a User Agent Server (UAS). A UAC can be a program or a device that interacts with a user. The UAC determines the information essential for the request; the protocol, the port, and IP address of the UAS to which the request is being sent. User Agent Server (UAS) The User Agent Server (UAS) is a server application that accepts the request from a UAC and generates accept, reject, or redirect responses on behalf of the user. Proxy Server SIP Proxy servers are elements that route SIP requests to UAS and SIP responses to UAC. A SIP Proxy server acts as both a UAC and UAS. A request may travel several Proxy servers before it reaches the far end UAC. Each Proxy server will make routing decisions, modifying the request before forwarding it to the next Proxy. Responses will route through the same set of Proxy servers by the requests in reverse order. SIP defines 3 types of Proxy servers: Call Stateful Proxy Call Stateful proxies need to be informed of all SIP transactions and therefore are always in the path taken by SIP messages traveling between users. These Proxy servers store state information from the moment the session is established until the moment it ends. D50444 Page 6
7 Stateful Proxy A Stateful proxy stores state related to a given transaction until the transaction concludes. Forking proxies are good examples of stateful proxies as they send SIP messages to several places and store state about the SIP message transaction until all location have returned a response. Stateless Proxy A Stateless Proxy forgets all information once a request or response has been processed. A stateless proxy forwards every request it receives downstream and every response it receives upstream. Registrar A SIP Registrar contains the location of all UA s within a domain. A Registrar acts as the front end to the location service for a domain, reading and writing mappings based on the contents on REGISTER requests. This location service is then queried by a Proxy server that is responsible for that domain. A Registrar is usually co-located with a Proxy server or a Redirect server. Redirect Server A Redirect Server accepts a SIP request, maps the address and returns a list of possible locations to the client that initiated the request. Unlike Proxy Servers, Redirect Servers do not pass the request on to others. Proxy Servers will make subsequent attempts for the user rather than sending new contact info to the user. Requests for Comments Requests for Comments (RFC) documents are a series of memoranda encompassing new research, innovations, and methodologies applicable to Internet technologies. Many RFC s are the standards on which the Internet is formed. The first proposed version of SIP was defined in RFC 2543 and was further defined in RFC Besides the basic specifications, a number of extensions to SIP have been defined in other RFC s and internet drafts. Below are several examples of SIP RFC s and drafts. RFC 1889 RFC 2190 RFC 2327 RFC 2396 RFC 2429 RFC 2617 RFC 2782 RFC 2833 RFC 2976 RFC 3016 RFC 3047 RFC 3261 RFC 3262 RFC 3263 RFC 3264 RTP: A Transport protocol for Real-time Applications RTP Payload Format for H.263 Video Streams SDP: Session Description Protocol Uniform Resource Identifiers (URI): Generic Syntax RTP Payload Format for the 1998 Version of ITU-T Rec. H.263 Video (H.263+) Digest Authentication DNS RR for specifying the location of services (DNS SRV) RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals The SIP INFO Method RTP Payload Format for MPEG-4 Audio/Visual Streams RTP Payload Format for ITU-T Recommendation G SIP: Session Initiation Protocol Reliability of Provisional Responses in SIP Locating SIP Servers An Offer/Answer Model with SDP D50444 Page 7
8 RFC 3311 RFC 3327 RFC 3361 RFC 3420 RFC 3515 RFC 3550 RFC 3581 RFC 3605 RFC 3711 RFC 3840 RFC 3880 RFC 3890 RFC 3891 RFC 3892 RFC 3944 RFC 3960 RFC 3984 RFC 4028 RFC 4145 RFC 4566 RFC 4568 RFC 4574 RFC 4582 RFC 4583 RFC 4585 RFC 4587 RFC 4629 RFC 4796 UPDATE method SIP Extension Field for Registering Non-Adjacent Contacts DHCP Option for SIP Servers Internet Media Type message/sipfrag Refer method RTP: A Transport Protocol for Real-Time Applications Symmetric Response Routing RTCP attribute in SDP The Secure Real-time Transport Protocol (SRTP) Indicating User Agent Capabilities in SIP Call Processing Language (CPL): A Language for User Control of Internet Telephony Services A Transport Independent Bandwidth Modifier for SDP The SIP "Replaces" Referred-By Mechanism H.350 Directory Services Early Media RTP Payload Format for H.264 Video Session Timers in SIP TCP-Based Media Transport in the SDP SDP: Session Description Protocol SDP: Security Descriptions for Media Streams The Session Description Protocol (SDP) Label Attribute The Binary Floor Control Protocol Format for Binary Floor Control Protocol (BFCP) Streams Extended RTP Profile for RTCP-Based Feedback RTP Payload Format for H.261 Video Streams RTP Payload Format for ITU-T Rec. H.263 Video The Session Description Protocol (SDP) Content Attribute draft-ietf-xcon-bfcp-connection-04.txt draft-levin-mmusic-xml-media-control-03.txt draft-ietf-sipping-cc-transfer-06.txt draft-kristensen-avt-rtp-h264-extension-00.txt D50444 Page 8
9 SIP Messages SIP is a text based protocol; and has well defined messages that are used for communications. There are two types of messages. A SIP message can be either a request from a UAC to an UAS, or a response from a UAS to a UAC. SIP Requests There are several types (methods) of SIP Requests. The most commonly used are listed below. INVITE Indicates a client is being invited to participate in a session (RFC 3261) ACK Confirms that the client has received a final response to s request (RFC 3261) BYE Terminates a session (RFC 3261) CANCEL Cancels any pending searches but does not terminate any sessions accepted (RFC 3261) OPTIONS Queries the capabilities of servers (RFC 3261) REGISTER Registers the address listed in the To header field with a SIP server (RFC 3261) PRACK Provisional Acknowledgement (RFC 3262) SUBSCRIBE Subscribes for an event of Notification from the Notifier (RFC 3265) NOTIFY Notify the subscriber of a new Event (RFC 3265) PUBLISH Publishes a Event to the server (RFC 3903) INFO Sends mid-session information that does not modify message state (RFC 2976) REFER Ask recipient to issue SIP request (call transfer) (RFC 3515) MESSAGE The MESSAGE is used to transport instant messages using SIP (RFC 3428) UPDATE SIP Responses The UPDATE method is used to modify the state of a session with out changing the state of the dialog (RFC 3311) SIP Response messages contain numeric response codes. The SIP response code set is partly based on HTTP response codes. There are six classes of response: 1xx Informational Responses 100 Trying: Extended search being performed Ringing Call Is Being Forwarded Queued Session Progress D50444 Page 9
10 2xx Successful Responses 200 Ok 202 Accepted 3xx Redirection Responses 300 Multiple Choices 301 Moved Permanently 302 Moved Temporarily 305 Use Proxy 380 Alternative Service 4xx Client Failure Responses 400 Bad Request 401 Unauthorized 404 Not Found 405 Method Not Allowed 406 Not Acceptable 407 Proxy Authentication Required 408 Request Timeout 409 Conflict 412 Conditional Request Failed 413 Request Entity Too Large 414 Request URO Too Long 415 Unsupported Media Type 420 Bad Extension 480 Temporarily Unavailable 481 Call/Transaction Does Not Exist 482 Loop Detected 483 Too Many Hops 484 Address Incomplete 485 Ambiguous 486 Busy Here 487 Request Terminated 488 Not Acceptable Here D50444 Page 10
11 5xx Server Failure Responses Server Internal Error Not Implemented: The SIP request method is not implemented Bad Gateway Service Unavailable Server Time-out SIP Version Not Supported Message Too Large Precondition Failure 6xx Global Failure Responses Busy Everywhere Decline Does Not Exist Anywhere Not Acceptable Session Description Protocol (SDP) SDP (RFC 4566) is intended for describing multimedia sessions for the purposes of session announcement, session invitation, and other forms of multimedia session initiation. SDP does not provide the content of the media form itself but simply provides a negotiation between two end points to allow them to agree on a media type and format. An SDP description contains session-level information and media-level information. The session-level information applies to the whole session; for instance, the originator of the session or the session name. The media-level information applies to a particular media stream; for instance, the codec used for encoding the audio stream or the port number the video stream is headed. An announcement consists of a session-level section followed by zero or more media-level sections. The session-level part starts with a `v=' line and continues to the first media-level section. The media description starts with an `m=' line and continues to the next media description or end of the whole session description. In general, session-level values are the default for all media unless overridden by an equivalent media-level value. D50444 Page 11
12 TANDBERG SIP TERMINALS TANDBERG provides a wide variety of form factors based upon the same software and hardware platform. The products range from the personal space, to set tops, up to the executive boardroom plasma-based systems. There are even form factors available for the healthcare industry, distance education, judicial market and first responders. While these form factors may look quite different, they all share the same core technology that makes TANDBERG endpoints the most feature rich in the world. MXP Platform Software Version Released Release Notes F2 February 2005 D50327 F3 July 2005 D50359 F4 January 2006 D50402 F5 July 2006 D50443 F6 May 2007 D50476 Personal Series Software Version Released Release Notes L2 April 2005 D50343 L3 October 2005 D50388 L4 April 2006 D50433 L5 November 2007 D50505 Please consult the appropriate section for details on a particular version of software. D50444 Page 12
13 TANDBERG MXP Endpoints Software F2-F6 SIP Server Interaction Function Port Type Direction SIP Messages 5060 UDP/TCP Endpoint SIP Registrar/Proxy SIP Messages 5061 TLS (TCP) Endpoint SIP Registrar/Proxy Note: Only one of the transport types (UDP, TCP or TLS) is used at any one time. F2-F6 Call Flow (Site A calls Site B) Endpoint A TANDBERG VCS Endpoint B EndptA VCS Protocol Type VCS EndptB Endpt Defined 5060 SIP Request UDP/TCP 5060 Endpt Defined Endpt Defined 5061 SIP Request TCP (TLS) 5061 Endpt Defined 2326 N/A Media (Audio) UDP/RTP N/A N/A Media (Audio) UDP/RTCP N/A N/A Media (Video) UDP/RTP N/A N/A Media (Video) UDP/RTCP N/A N/A Media (Dual UDP/RTP N/A 2330 Streams) 2331 N/A Media (Dual UDP/RTCP N/A 2331 Streams) 2332 N/A Media (FECC) UDP/RTP N/A N/A Media (FECC) UDP/RTCP N/A 2333 Note: Only one of the transport types (UDP, TCP or TLS) is used at any one time. D50444 Page 13
14 For SIP registration and call setup/control signaling, TANDBERG F2-F6 software listens for SIP Requests and SIP Responses on the default trusted SIP ports (5060 for TCP and UDP or 5061 for TLS over TCP). TANDBERG F2-F5 software uses a pool of 160 UDP ports (2326:2485) for all media (both RTP and RTCP). When connecting to far end systems that support symmetrical RTP, the ports are used in increments of 8 per call (e.g. the first call will use either ports or , depending on call direction). All calls with systems that do not support symmetrical RTP, however, will require 16 ports per call. After the first call is connected, the endpoint will use the next consecutive 8 ports for the subsequent call and so on until all calls are disconnected. Once all calls are disconnected, the ports will reset to the beginning. The port allocation behavior has changed a bit in F6. While the same port range is used (UDP ports 2326:2485 inclusive), the port range will continue to increment once all active calls are disconnected. Only when the top of the range is reached will the ports to be allocated for the next call reset to the beginning of the range. For example, upon startup, the MXP will allocate ports for the first call. Whether or not that call disconnects prior to the next call being connected, call 2 will utilize ports This incremental allocation will continue until port 2485 is reached, at which time the ports will reset to the beginning of the range. The TANDBERG endpoint also uses symmetrical RTP ports, thereby reducing the number of ports needed per call. Symmetrical RTP functionality allows the same port to be used for both incoming and outgoing audio streams. However, when the logical channels are opened, the start range for the UDP ports could begin at 2326 or 2334, depending on who initializes the open logical channel commands. F2-F6 Audio Audio Length (ms) Audio size IP UDP RTP G ms 160 bytes 20 bytes 8 bytes 12 bytes 200 bytes G ms 160 bytes 20 bytes 8 bytes 12 bytes 200 bytes G.722.1_24 20ms 60 bytes 20 bytes 8 bytes 12 bytes 100 bytes G.722.1_32 20ms 80 bytes 20 bytes 8 bytes 12 bytes 120 bytes G ms 40 bytes 20 bytes 8 bytes 12 bytes 80 bytes AAC-LD 20ms 160 bytes 20 bytes 8 bytes 12 bytes 200 bytes F2-F6 Video Total Video Video size (max) IP UDP RTP Total (max) H bytes* 20 bytes 8 bytes 12 bytes 1440 bytes H.263/+/ bytes* 20 bytes 8 bytes 12 bytes 1440 bytes H bytes* 20 bytes 8 bytes 12 bytes 1440 bytes * The dataport command h323mtu < > can be used to change the maximum video payload size to any value between 500 and 1400 bytes. D50444 Page 14
15 Jitter and Latency Latency can be defined as the time between a node sending a message and receipt of the message by another node. The TANDBERG systems can handle any value of latency, however, the higher the latency, the longer the delay in video and audio. This may lead to conferences with undesirable delays causing participants to interrupt and speak over each other. Jitter can be defined as the difference in latency. Where constant latency simply produces delays in audio and video, jitter can have a more adverse effect. Jitter can cause packets to arrive out of order or at the wrong times. TANDBERG systems can manage packets with jitter up to 100ms; packets not received within this timeframe will be considered lost packets. If excessive packet loss is detected, the TANDBERG systems will make use of IPLR TF (see document D50165, TANDBERG and IPLR, for more information) or downspeeding (flow control) to counteract the packet loss. F2 software introduced a new dynamic jitter buffer that can increase in value depending on the performance of the network. To minimize introduced latency, this buffer will begin at 20ms and continue to 100ms if sufficient packet loss is occurring. F3 software introduced RTP time stamping into the audio packets in order to help reduce lip sync issues that may occur over an SIP call. This operation has also been slightly modified to improve as much as possible within the F4, F5 and F6 software releases. To further improve lip sync with high resolution images (including XGA, w720p and other high resolution video formats), F3 software has changed the behavior of image buffering prior in order to attempt to place information on the wire as fast as possible. Prior to this adjustment in behavior, the MXP endpoint would attempt to maintain a consistent packet size when placing the information on the wire, which would result in video being buffered internally to ensure that the entire packet could be filled prior to transmission. This potential buffering created a potential lip sync issue at the far end of the SIP call as the time between the actual capture of the visual image and placing the information on the wire was not a constant and, therefore, the far end system cannot adjust for any time differences between the arrival of the video information and the arrival of the audio information. The endpoint will now, by default, not buffer the high resolution images prior to transmission, which will ensure a constant time delta between the arrival of the video and audio information to the far end, allowing for an adjustment as necessary and improved lip sync. This change in behavior, though, can cause the MXP to send out consecutive packets that have a relatively large difference in size. For example, one packet can come out at 1400 bytes while the packet behind that can be sent out at 800 bytes followed by a 1200 byte packet and so on. Some QoS configurations improperly handle the large adjustments in packet size, thereby dropping packets within the QoS buffer and causing packet loss in the call. If, for any reason, it is necessary to disable this behavior, it can be done through the API command xconfiguration AllowLatency: <On/Off> (requires the latest minor release of F4 software, at a minimum). When this setting is On, the MXP will buffer the traffic prior to placing it on the wire; Off (default) will not buffer any video internally. D50444 Page 15
16 RFC Support The following RFC s are supported in the MXP product line as of software version F6.3. RFC 1889 RFC 2190 RFC 2327 RFC 2396 RFC 2429 RFC 2617 RFC 2782 RFC 2833 RFC 2976 RFC 3016 RFC 3047 RFC 3261 RFC 3262 RFC 3263 RFC 3264 RFC 3311 RFC 3361 RFC 3420 RFC 3515 RFC 3550 RFC 3581 RFC 3605 RFC 3711 RFC 3840 RFC 3890 RFC 3891 RFC 3892 RFC 3960 RFC 3984 RFC 4028 RFC 4145 RFC 4566 RFC 4568 RFC 4574 RTP: A Transport protocol for Real-time Applications RTP Payload Format for H.263 Video Streams SDP: Session Description Protocol Uniform Resource Identifiers (URI): Generic Syntax RTP Payload Format for the 1998 Version of ITU-T Rec. H.263 Video (H.263+) Digest Authentication DNS RR for specifying the location of services (DNS SRV) RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals The SIP INFO Method RTP Payload Format for MPEG-4 Audio/Visual Streams RTP Payload Format for ITU-T Recommendation G SIP: Session Initiation Protocol Reliability of Provisional Responses in SIP Locating SIP Servers An Offer/Answer Model with SDP UPDATE method DHCP Option for SIP Servers Internet Media Type message/sipfrag Refer method RTP: A Transport Protocol for Real-Time Applications Symmetric Response Routing RTCP attribute in SDP The Secure Real-time Transport Protocol (SRTP) Indicating User Agent Capabilities in SIP A Transport Independent Bandwidth Modifier for SDP The SIP "Replaces" Referred-By Mechanism Early Media RTP Payload Format for H.264 Video Session Timers in SIP TCP-Based Media Transport in the SDP SDP: Session Description Protocol SDP: Security Descriptions for Media Streams The Session Description Protocol (SDP) Label Attribute D50444 Page 16
17 RFC 4582 RFC 4583 RFC 4585 RFC 4587 RFC 4629 RFC 4796 The Binary Floor Control Protocol Format for Binary Floor Control Protocol (BFCP) Streams Extended RTP Profile for RTCP-Based Feedback RTP Payload Format for H.261 Video Streams RTP Payload Format for ITU-T Rec. H.263 Video The Session Description Protocol (SDP) Content Attribute draft-ietf-xcon-bfcp-connection-04.txt draft-levin-mmusic-xml-media-control-03.txt draft-ietf-sipping-cc-transfer-06.txt draft-kristensen-avt-rtp-h264-extension-00.txt D50444 Page 17
18 TANDBERG MXP Personal Series Endpoints L2-L5 SIP Server Interaction Function Port Type Direction SIP Messages 5060 UDP/TCP Endpoint SIP Registrar/Proxy SIP Messages 5061 TLS (TCP) Endpoint SIP Registrar/Proxy Note: Only one of the transport types (UDP, TCP or TLS) is used at any one time. L2-L5 Call Flow (Site A calls Site B) TANDBERG VCS Endpoint A EndptA VCS Protocol Type VCS EndptB Endpt Defined 5060 SIP Request UDP/TCP VCS Defined 5060 Endpt Defined 5061 SIP Request TCP (TLS) 5061 Endpt Defined 2326 N/A Media (Audio) UDP/RTP N/A N/A Media (Audio) UDP/RTCP N/A N/A Media (Video) UDP/RTP N/A N/A Media (Video) UDP/RTCP N/A N/A Media (Dual UDP/RTP N/A 2330 Streams) 2331 N/A Media (Dual UDP/RTCP N/A 2331 Streams) 2332 N/A Media (FECC) UDP/RTP N/A N/A Media (FECC) UDP/RTCP N/A 2333 Note: Only one of the transport types (UDP, TCP or TLS) is used at any one time. D50444 Page 18
19 For SIP registration and call setup/control signaling, TANDBERG L2-L5 software listens for SIP Requests and SIP Responses on the default trusted SIP ports (5060 for TCP and UDP or 5061 for TLS over TCP). TANDBERG L2-L4 software uses a pool of 32 UDP ports (2326:2357) for all media (both RTP and RTCP). When connecting to far end systems that support symmetrical RTP, the ports are used in increments of 8 per call (e.g. the first call will use either ports or , depending on call direction). All calls with systems that do not support symmetrical RTP, however, will require 16 ports per call. After the first call is connected, the endpoint will use the next consecutive 8 ports for the subsequent call and so on until all calls are disconnected. Once all calls are disconnected, the ports will reset to the beginning. The port allocation behavior has changed a bit in L5. While the same port range is used (UDP ports 2326:2485 inclusive), the port range will continue to increment once all active calls are disconnected. Only when the top of the range is reached will the ports to be allocated for the next call reset to the beginning of the range. For example, upon startup, the MXP will allocate ports for the first call. Whether or not that call disconnects prior to the next call being connected, call 2 will utilize ports This incremental allocation will continue until port 2485 is reached, at which time the ports will reset to the beginning of the range. All versions of L software use bi-directional UDP ports, thereby reducing the number of ports required to connect an SIP call. L2-L5 Audio Audio Length (ms) Audio size IP UDP RTP G ms 160 bytes 20 bytes 8 bytes 12 bytes 200 bytes G ms 160 bytes 20 bytes 8 bytes 12 bytes 200 bytes G.722.1_24 20ms 60 bytes 20 bytes 8 bytes 12 bytes 100 bytes G.722.1_32 20ms 80 bytes 20 bytes 8 bytes 12 bytes 120 bytes L2-L5 Video Total Video Video size (max) IP UDP RTP Total (max) H bytes* 20 bytes 8 bytes 12 bytes 1440 bytes H.263/+/ bytes* 20 bytes 8 bytes 12 bytes 1440 bytes H bytes* 20 bytes 8 bytes 12 bytes 1440 bytes * for L1 L5 software, the API command xconfig rtp mtu: < > can be used to change the maximum video payload size to any value between 400 and 1400 bytes. Jitter and Latency Latency can be defined as the time between a node sending a message and receipt of the message by another node. The TANDBERG systems can handle any value of latency, however, the higher the latency, the longer the delay in video and audio. This may lead to conferences with undesirable delays causing participants to interrupt and speak over each other. Jitter can be defined as the difference in latency. Where constant latency simply produces delays in audio and video, jitter can have a more adverse effect. Jitter can cause packets to arrive out of order or at the wrong times. TANDBERG systems can manage packets with jitter up to 100ms; packets not received within this timeframe will be considered lost packets. If excessive packet loss is detected, the TANDBERG systems will make use of IPLR TF (see document D50165 for more information) or downspeeding (flow control) to counteract the packet loss. D50444 Page 19
20 Introduced in L2, the 150MXP software supports a dynamic jitter buffer that can increase in value depending on the performance of the network. To minimize introduced latency, this buffer will begin at 20ms and continue to 100ms if sufficient packets are arriving outside the current jitter buffer range. L3 software introduced RTP time stamping into the audio packets in order to help reduce lip sync issues that may occur over an SIP call. RFC Support The following RFCs are supported in the MXP Personal Series product line as of software version L5.0. RFC 1889 RFC 2190 RFC 2327 RFC 2396 RFC 2429 RFC 2617 RFC 2782 RFC 2833 RFC 2976 RFC 3016 RFC 3047 RFC 3261 RFC 3262 RFC 3263 RFC 3264 RFC 3311 RFC 3361 RFC 3420 RFC 3515 RFC 3550 RFC 3581 RFC 3605 RFC 3711 RFC 3840 RFC 3890 RFC 3891 RFC 3892 RFC 3960 RTP: A Transport protocol for Real-time Applications RTP Payload Format for H.263 Video Streams SDP: Session Description Protocol Uniform Resource Identifiers (URI): Generic Syntax RTP Payload Format for the 1998 Version of ITU-T Rec. H.263 Video (H.263+) Digest Authentication DNS RR for specifying the location of services (DNS SRV) RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals The SIP INFO Method RTP Payload Format for MPEG-4 Audio/Visual Streams RTP Payload Format for ITU-T Recommendation G SIP: Session Initiation Protocol Reliability of Provisional Responses in SIP Locating SIP Servers An Offer/Answer Model with SDP UPDATE method DHCP Option for SIP Servers Internet Media Type message/sipfrag Refer method RTP: A Transport Protocol for Real-Time Applications Symmetric Response Routing RTCP attribute in SDP The Secure Real-time Transport Protocol (SRTP) Indicating User Agent Capabilities in SIP A Transport Independent Bandwidth Modifier for SDP The SIP "Replaces" Referred-By Mechanism Early Media D50444 Page 20
21 RFC 3984 RFC 4028 RFC 4145 RFC 4566 RFC 4568 RFC 4574 RFC 4582 RFC 4583 RFC 4585 RFC 4587 RFC 4629 RFC 4796 RTP Payload Format for H.264 Video Session Timers in SIP TCP-Based Media Transport in the SDP SDP: Session Description Protocol SDP: Security Descriptions for Media Streams The Session Description Protocol (SDP) Label Attribute The Binary Floor Control Protocol Format for Binary Floor Control Protocol (BFCP) Streams Extended RTP Profile for RTCP-Based Feedback RTP Payload Format for H.261 Video Streams RTP Payload Format for ITU-T Rec. H.263 Video The Session Description Protocol (SDP) Content Attribute draft-ietf-xcon-bfcp-connection-04.txt draft-levin-mmusic-xml-media-control-03.txt draft-ietf-sipping-cc-transfer-06.txt draft-kristensen-avt-rtp-h264-extension-00.txt D50444 Page 21
22 TANDBERG SIP INFRASTRUCTURE TANDBERG provides several infrastructure products aimed at addressing different needs. These products include a distributed MCU, centralized MCU, gateway, gatekeeper and firewall traversal technology. While these form factors may look quite different, they all share the same core technology that makes TANDBERG infrastructure the most feature-rich solution available on the market today. TANDBERG MPS Software Version Released Release Notes J3 January 2006 D50414 J4 July 2007 D50489 TANDBERG Codian 4500 MCU Software Version Released Release Notes 2.2(1.0) December 2007 N/A TANDBERG Codian 4200 MCU Software Version Released Release Notes 2.2(1.0) December 2007 N/A TANDBERG Codian IP Gateway 3500 Software Version Released Release Notes 1.1(1.1) December 2007 N/A TANDBERG Entrypoint Software Version Released Release Notes EP1 March 2007 D50477 TANDBERG 3G Gateway Software Version Released Release Notes R2 April 2006 D50436 R3 June 2007 D50495 D50444 Page 22
23 TANDBERG Video Portal Software Version Released Release Notes V2 April 2006 D50437 V3 June 2007 D50496 TANDBERG Content Server Software Version Released Release Notes S3 January 2008 D50510 TANDBERG Codian IPVCR 2200 Software Version Released Release Notes 2.2(1.0) December 2007 N/A TANDBERG Video Communication Server Software Version Released Release Notes X1 August 2007 D50491 Please consult the appropriate section for details on a particular version of software. D50444 Page 23
24 TANDBERG MPS 200/800 The TANDBERG MPS is a card-based chassis ideal for medium to large enterprise needs or centralized deployment architecture. J3-J4 SIP Server Interaction Function Port Type Direction SIP Messages 5060 UDP/TCP MPS SIP Registrar/Proxy SIP Messages 5061 TLS (TCP) MPS SIP Registrar/Proxy Note: Only one of the transport types (UDP, TCP or TLS) is used at any one time. J3-J4 Call Flow (MPS calls Site A) TANDBERG VCS MPS Site A MPS VCS Protocol Type VCS Site A MPS Defined 5060 SIP Request UDP/TCP VCS Defined 5060 Endpt Defined 5061 SIP Request TCP (TLS) 5061 Endpt Defined 2326 N/A Media (Video) UDP/RTP N/A N/A Media (Video) UDP/RTCP N/A N/A Media (Dual UDP/RTP N/A 2330 Streams) 2329 N/A Media (Dual UDP/RTCP N/A 2331 Streams) 2330 N/A Media (Audio) UDP/RTP N/A N/A Media (Audio) UDP/RTCP N/A 2327 Note: Only one of the transport types (UDP, TCP or TLS) is used at any one time. For SIP registration and call setup/control signaling, the MPS listens for SIP Requests and SIP Responses on the default trusted SIP ports (5060 for TCP and UDP or 5061 for TLS over TCP). All SIP traffic will flow between the System Controller card on the MPS and the far end system. The MPS uses a pool of 4626 UDP ports (2326:6951) for all media (both RTP and RTCP). The ports are used in increments of 8 per call (e.g. the first call will use ports ). After the first call is connected, the MPS will use the next consecutive 8 ports for the subsequent call and so on until all calls are disconnected. Once all calls are disconnected, the ports will reset to the beginning. All UDP Media content will flow directly between the specific media blade on the MPS and the endpoint connected. D50444 Page 24
25 The port allocation behavior has changed a bit in J4. While the same port range is used (UDP ports 2326:6951 inclusive), the port range will continue to increment once all active calls are disconnected. Only when the top of the range is reached will the ports to be allocated for the next call reset to the beginning of the range. For example, upon startup, the MPS will allocate ports for the first call. Whether or not that call disconnects prior to the next call being connected, call 2 will utilize ports This incremental allocation will continue until port 6951 is reached, at which time the ports will reset to the beginning of the range. Similar to the MXP endpoints running F2 or later, the TANDBERG MPS (all versions of software) uses bi-directional UDP ports, so the number of ports required is reduced in comparison to older versions of the TANDBERG endpoints software. J3-J4 Audio Audio Length (ms) Audio size IP UDP RTP G ms 160 bytes 20 bytes 8 bytes 12 bytes 200 bytes G ms 160 bytes 20 bytes 8 bytes 12 bytes 200 bytes G.722.1_24 20ms 60 bytes 20 bytes 8 bytes 12 bytes 100 bytes G.722.1_32 20ms 80 bytes 20 bytes 8 bytes 12 bytes 120 bytes G ms 40 bytes 20 bytes 8 bytes 12 bytes 80 bytes AAC-LD 20 ms 160 bytes 20 bytes 8 bytes 12 bytes 200 bytes J3-J4 Video Total Video Video size (max) IP UDP RTP Total (max) H bytes* 20 bytes 8 bytes 12 bytes 1440 bytes H.263/+/ bytes* 20 bytes 8 bytes 12 bytes 1440 bytes H bytes* 20 bytes 8 bytes 12 bytes 1440 bytes * with all versions of the MPS software, the dataport command xconfig RTP MTU: < > can be used to change the maximum video payload size to any value between 1200 and 1400 bytes. Jitter and Latency Latency can be defined as the time between a node sending a message and receipt of the message by another node. The TANDBERG systems can handle any value of latency, however, the higher the latency, the longer the delay in video and audio. This may lead to conferences with undesirable delays causing participants to interrupt and speak over each other. Jitter can be defined as the difference in latency. Where constant latency simply produces delays in audio and video, jitter can have a more adverse effect. Jitter can cause packets to arrive out of order or at the wrong times. TANDBERG systems can manage packets with jitter up to 200ms; packets not received within this timeframe will be considered lost packets. If excessive packet loss is detected, the TANDBERG systems will make use of IPLR TF (see document D50165 for more information) or downspeeding (flow control) to counteract the packet loss. To further improve lip sync with high resolution images (including XGA, w720p and other high resolution video formats), J3 software has changed the behavior of image buffering prior in order to attempt to place information on the wire as fast as possible. Prior to this adjustment in behavior, the MPS would attempt to maintain a consistent packet size when placing the information on the wire, which would result in video being buffered internally to ensure that the entire packet could be filled prior to transmission. This potential buffering created a potential lip sync issue at the far end of the SIP call as the time between the actual capture of the visual image and placing the information on the wire was not a constant and, therefore, the far end system cannot adjust for any time differences between the arrival of the video information and the arrival of the audio information. D50444 Page 25
26 The MPS will now, by default, not buffer the high resolution images prior to transmission, which will ensure a constant time delta between the arrival of the video and audio information to the far end, allowing for an adjustment as necessary and improved lip sync. This change in behavior, though, can cause the MPS to send out consecutive packets that have a relatively large difference in size. For example, one packet can come out at 1400 bytes while the packet behind that can be sent out at 800 bytes followed by a 1200 byte packet and so on. Some QoS configurations improperly handle the large adjustments in packet size, thereby dropping packets within the QoS buffer and causing packet loss in the call. If, for any reason, it is necessary to disable this behavior, it can be done through the API command xconfiguration SystemUnit TrafficShaping: <On/Off> (requires the latest minor release of J3 software, at a minimum). When this setting is On, the MPS will buffer the traffic prior to placing it on the wire; Off (default) will not buffer any video internally. RFC Support The following RFCs are supported in the MPS as of software version J4.2. RFC 1889 RFC 2190 RFC 2327 RFC 2396 RFC 2429 RFC 2617 RFC 2782 RFC 2833 RFC 2976 RFC 3016 RFC 3047 RFC 3261 RFC 3262 RFC 3263 RFC 3264 RFC 3311 RFC 3420 RFC 3515 RFC 3550 RFC 3581 RFC 3605 RFC 3840 RFC 3890 RFC 3891 RFC 3892 RFC 3960 RTP: A Transport protocol for Real-time Applications RTP Payload Format for H.263 Video Streams SDP: Session Description Protocol Uniform Resource Identifiers (URI): Generic Syntax RTP Payload Format for the 1998 Version of ITU-T Rec. H.263 Video (H.263+) Digest Authentication DNS RR for specifying the location of services (DNS SRV) RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals The SIP INFO Method RTP Payload Format for MPEG-4 Audio/Visual Streams RTP Payload Format for ITU-T Recommendation G SIP: Session Initiation Protocol Reliability of Provisional Responses in SIP Locating SIP Servers An Offer/Answer Model with SDP UPDATE method Internet Media Type message/sipfrag Refer method RTP: A Transport Protocol for Real-Time Applications Symmetric Response Routing RTCP attribute in SDP Indicating User Agent Capabilities in SIP A Transport Independent Bandwidth Modifier for SDP The SIP "Replaces" Referred-By Mechanism Early Media D50444 Page 26
27 RFC 3984 RFC 4028 RFC 4145 RFC 4566 RFC 4574 RFC 4582 RFC 4583 RFC 4585 RFC 4587 RFC 4629 RFC 4796 RTP Payload Format for H.264 Video Session Timers in SIP TCP-Based Media Transport in the SDP SDP: Session Description Protocol The Session Description Protocol (SDP) Label Attribute The Binary Floor Control Protocol Format for Binary Floor Control Protocol (BFCP) Streams Extended RTP Profile for RTCP-Based Feedback RTP Payload Format for H.261 Video Streams RTP Payload Format for ITU-T Rec. H.263 Video The Session Description Protocol (SDP) Content Attribute draft-ietf-xcon-bfcp-connection-04.txt draft-levin-mmusic-xml-media-control-03.txt draft-ietf-sipping-cc-transfer-06.txt draft-kristensen-avt-rtp-h264-extension-00.txt D50444 Page 27
28 TANDBERG Codian 4500 Series MCU The TANDBERG Codian 4500 series of MCUs are stand alone appliances supporting up to 40 ports per chassis. Multiple chassis can be combined through cascading either in a distributed or centralized architecture if an increase in capacity is required. Note: The Codian products allocate random ports in the range of to It is possible to change the fixed ports on which the Codian products receive and establish connections under the Network > Services portion of the management interface. Software 2.2(1.0) SIP Server Interaction Codian 4500 Function Port Type Direction SIP Messages 5060 UDP/TCP 4500 SIP Registrar/Proxy Note: Only one of the transport types (UDP or TCP) is used at any one time. Software 2.2(1.0) Call Flow TANDBERG VCS 4500 Site A Codian 4500 VCS Protocol Type VCS Site A 49152: SIP Request UDP/TCP VCS Defined : SIP Request UDP/TCP 5060 Endpt Defined 49152:65535 N/A Media (Video) UDP/RTP N/A Endpt Defined 49152:65535 N/A Media (Video) UDP/RTCP N/A Endpt Defined 49152:65535 N/A Media (Dual UDP/RTP N/A Endpt Defined Streams) 49152:65535 N/A Media (Dual UDP/RTCP N/A Endpt Defined Streams) 49152:65535 N/A Media (Audio) UDP/RTP N/A Endpt Defined 49152:65535 N/A Media (Audio) UDP/RTCP N/A Endpt Defined Note: Only one of the transport types (UDP, TCP or TLS) is used at any one time. D50444 Page 28
29 For SIP registration and call setup/control signaling, the Codian 4500 will use a random port within the range of to Because the same port range is shared by multiple services (i.e. FTP data, H.323 media/call signaling/control and SIP media/call signaling/control), ports are allocated at the time they are needed for each particular service; ports used for logical channels are only allocated when necessary. Logical channels and signaling channels are opened up at different times of a SIP call; ports may or may not be consecutive within a single call. For example, a standard SIP call (media only) may occupy ports 49172/49173 TCP and 49166/49167 and 49160/49161 UDP due to the number of connections that are opened up around the same time. All random ports are allocated from the top of range down, beginning with the ports in the 65xxx grouping. Software 2.2(1.0) Audio Audio Length (ms) Audio size IP UDP RTP G ms 160 bytes 20 bytes 8 bytes 12 bytes 200 bytes G ms 160 bytes 20 bytes 8 bytes 12 bytes 200 bytes G ms 48 bytes 20 bytes 8 bytes 12 bytes 88 bytes G ms 20 bytes 20 bytes 8 bytes 12 bytes 60 bytes AAC-LC_48 20ms 180 bytes 20 bytes 8 bytes 12 bytes 220 bytes AAC-LC_56 20ms 210 bytes 20 bytes 8 bytes 12 bytes 250 bytes AAC-LC_64 20ms 240 bytes 20 bytes 8 bytes 12 bytes 280 bytes AAC-LC_96 20ms 400 bytes 20 bytes 8 bytes 12 bytes 440 bytes AAC-LD_48 20ms 120 bytes 20 bytes 8 bytes 12 bytes 160 bytes AAC-LD_56 20ms 140 bytes 20 bytes 8 bytes 12 bytes 180 bytes AAC-LD_64 20ms 160 bytes 20 bytes 8 bytes 12 bytes 200 bytes AAC-LD_96 20ms 240 bytes 20 bytes 8 bytes 12 bytes 280 bytes Siren14 20ms 120 bytes 20 bytes 8 bytes 12 bytes 160 bytes G Annex C 20ms 120 bytes 20 bytes 8 bytes 12 bytes 160 bytes Software 2.2(1.0) Video Total Video Video size (max) IP UDP RTP Total (max) H bytes* 20 bytes 8 bytes 12 bytes 1440 bytes H.263/+/ bytes* 20 bytes 8 bytes 12 bytes 1440 bytes H bytes* 20 bytes 8 bytes 12 bytes 1440 bytes * with 2.2(1.0) software, the maximum mtu used for video payload can be adjusted between 400 and 1400 bytes through the web interface control under Settings > Conferences > Maximum transmitted video packet size. D50444 Page 29
30 Jitter and Latency Latency can be defined as the time between a node sending a message and receipt of the message by another node. The TANDBERG systems can handle any value of latency, however, the higher the latency, the longer the delay in video and audio. This may lead to conferences with undesirable delays causing participants to interrupt and speak over each other. Jitter can be defined as the difference in latency. Where constant latency simply produces delays in audio and video, jitter can have a more adverse effect. Jitter can cause packets to arrive out of order or at the wrong times. The TANDBERG Codian 4500 MCU incorporates variable, independent jitter buffers for the audio and video streams of the call. The audio stream has a dynamic jitter buffer of 40ms up to and including 240ms, while the dynamic jitter buffer used for the video stream begins at 30ms and can increase when deemed necessary by an increase in jitter for the active SIP call. The maximum size of the jitter buffer is determined by the bandwidth of the call in question; for a call connected at 384kbps, the jitter buffer can equate to a full 2 seconds, while a 2Mbps call will equate to a jitter buffer of approximately 350ms. The Codian 4500 MCU utilizes RTP time stamping between the audio and video streams to ensure they remain synchronized throughout the call. RFC Support The following RFC s are supported in the Codian 4500 MCU product line as of software version 2.2(1.0). RFC 2190 RFC 2327 RFC 2617 RFC 2833 RFC 2976 RFC 3261 RFC 3264 RFC 3265 RFC 3555 RFC 3984 RFC 4573 RTP Payload Format for H.263 Video Streams SDP: Session Description Protocol Digest Authentication RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals The SIP INFO Method SIP: Session Initiation Protocol An Offer/Answer Model with SDP Session Initiation Protocol (SIP)-Specific Event Notification MIME Type Registration of RTP Payload Formats RTP Payload Format for H.264 Video MIME Type Registration for RTP Payload Format for H.224 draft-levinmmusic-xml-schema-media-control D50444 Page 30
31 TANDBERG Codian 4200 Series MCU The TANDBERG Codian 4200 series of MCUs are stand alone appliances supporting up to 40 ports per chassis. Multiple chassis can be combined through cascading either in a distributed or centralized architecture if an increase in capacity is required. Note: The Codian products allocate random ports in the range of to It is possible to change the fixed ports on which the Codian products receive and establish connections under the Network > Services portion of the management interface. Software 2.2(1.0) SIP Server Interaction Codian 4200 Function Port Type Direction SIP Messages 5060 UDP/TCP 4200 SIP Registrar/Proxy Note: Only one of the transport types (UDP, TCP or TLS) is used at any one time. Software 2.2(1.0) Call Flow TANDBERG VCS 4200 Site A Codian 4200 VCS Protocol Type VCS Site A 49152: SIP Request UDP/TCP VCS Defined : SIP Request UDP/TCP 5060 Endpt Defined 49152:65535 N/A Media (Video) UDP/RTP N/A Endpt Defined 49152:65535 N/A Media (Video) UDP/RTCP N/A Endpt Defined 49152:65535 N/A Media (Dual UDP/RTP N/A Endpt Defined Streams) 49152:65535 N/A Media (Dual UDP/RTCP N/A Endpt Defined Streams) 49152:65535 N/A Media (Audio) UDP/RTP N/A Endpt Defined 49152:65535 N/A Media (Audio) UDP/RTCP N/A Endpt Defined Note: Only one of the transport types (UDP, TCP or TLS) is used at any one time. D50444 Page 31
32 For SIP registration and call setup/control signaling, the Codian 4200 will use a random port within the range of to Because the same port range is shared by multiple services (i.e. FTP data, H.323 media/call signaling/control and SIP media/call signaling/control), ports are allocated at the time they are needed for each particular service; ports used for logical channels are only allocated when necessary. Logical channels and signaling channels are opened up at different times of a SIP call; ports may or may not be consecutive within a single call. For example, a standard SIP call (media only) may occupy ports 49172/49173 TCP and 49166/49167 and 49160/49161 UDP due to the number of connections that are opened up around the same time. All random ports are allocated from the top of range down, beginning with the ports in the 65xxx grouping. Software 2.2(1.0) Audio Audio Length Audio IP UDP RTP Total (ms) size G ms 160 bytes 20 bytes 8 bytes 12 bytes 200 bytes G ms 160 bytes 20 bytes 8 bytes 12 bytes 200 bytes G ms 48 bytes 20 bytes 8 bytes 12 bytes 88 bytes G ms 20 bytes 20 bytes 8 bytes 12 bytes 60 bytes AAC-LC_48 20ms 180 bytes 20 bytes 8 bytes 12 bytes 220 bytes AAC-LC_56 20ms 210 bytes 20 bytes 8 bytes 12 bytes 250 bytes AAC-LC_64 20ms 240 bytes 20 bytes 8 bytes 12 bytes 280 bytes AAC-LC_96 20ms 400 bytes 20 bytes 8 bytes 12 bytes 440 bytes AAC-LD_48 20ms 120 bytes 20 bytes 8 bytes 12 bytes 160 bytes AAC-LD_56 20ms 140 bytes 20 bytes 8 bytes 12 bytes 180 bytes AAC-LD_64 20ms 160 bytes 20 bytes 8 bytes 12 bytes 200 bytes AAC-LD_96 20ms 240 bytes 20 bytes 8 bytes 12 bytes 280 bytes Siren14 20ms 120 bytes 20 bytes 8 bytes 12 bytes 160 bytes G Annex C 20ms 120 bytes 20 bytes 8 bytes 12 bytes 160 bytes Software 2.2(1.0) Video Video Video IP UDP RTP Total size (max) (max) H bytes* 20 bytes 8 bytes 12 bytes 1440 bytes H.263/+/ bytes* 20 bytes 8 bytes 12 bytes 1440 bytes H bytes* 20 bytes 8 bytes 12 bytes 1440 bytes * with 2. 2(1.0) softwa re, the maximum mtu used for video payload can be adjusted between 400 and 1400 bytes through the web interface control under Settings > Conferences > Maximum transmitted video packet size. D50444 Page 32
Session Initiation Protocol (SIP) The Emerging System in IP Telephony
Session Initiation Protocol (SIP) The Emerging System in IP Telephony Introduction Session Initiation Protocol (SIP) is an application layer control protocol that can establish, modify and terminate multimedia
More informationNAT TCP SIP ALG Support
The feature allows embedded messages of the Session Initiation Protocol (SIP) passing through a device that is configured with Network Address Translation (NAT) to be translated and encoded back to the
More informationSIP : Session Initiation Protocol
: Session Initiation Protocol EFORT http://www.efort.com (Session Initiation Protocol) as defined in IETF RFC 3261 is a multimedia signaling protocol used for multimedia session establishment, modification
More informationSIP A Technology Deep Dive
SIP A Technology Deep Dive Anshu Prasad Product Line Manager, Mitel June 2010 Laith Zalzalah Director, Mitel NetSolutions What is SIP? Session Initiation Protocol (SIP) is a signaling protocol for establishing
More informationAlcatel OmniPCX Enterprise R11 Supported SIP RFCs
Alcatel OmniPCX Enterprise R11 Supported SIP RFCs Product & Offer Large & Medium Enterprise Ref: 8AL020033225TCASA ed3 ESD/ Mid & Large Enterprise Product Line Management October 2013 OmniPCX Enterprise
More informationAV@ANZA Formación en Tecnologías Avanzadas
SISTEMAS DE SEÑALIZACION SIP I & II (@-SIP1&2) Contenido 1. Why SIP? Gain an understanding of why SIP is a valuable protocol despite competing technologies like ISDN, SS7, H.323, MEGACO, SGCP, MGCP, and
More informationSIP Trunking. Service Guide. www.megapath.com. Learn More: Call us at 877.634.2728.
Service Guide Learn More: Call us at 877.634.2728. www.megapath.com What is MegaPath SIP Trunking? SIP Trunking enables your business to reduce costs and simplify IT management by combining voice and Internet
More informationIxLoad: Advanced VoIP
IxLoad: Advanced VoIP IxLoad in a typical configuration simulating SIP endpoints Aptixia IxLoad VoIP is the perfect tool for functional, performance, and stability testing of SIPbased voice over IP (VoIP)
More informationVoIP with SIP. Session Initiation Protocol RFC-3261/RFC-2543. Tasuka@Tailyn.com.tw
VoIP with SIP Session Initiation Protocol RFC-3261/RFC-2543 Tasuka@Tailyn.com.tw 1 Legacy Telephone 2 Legacy Telephone 2 Legacy Telephone 2 Legacy Telephone 2 Legacy Telephone 2 Legacy Telephone 2 Legacy
More informationSIP: Protocol Overview
SIP: Protocol Overview NOTICE 2001 RADVISION Ltd. All intellectual property rights in this publication are owned by RADVISION Ltd. and are protected by United States copyright laws, other applicable copyright
More informationEE4607 Session Initiation Protocol
EE4607 Session Initiation Protocol Michael Barry michael.barry@ul.ie william.kent@ul.ie Outline of Lecture IP Telephony the need for SIP Session Initiation Protocol Addressing SIP Methods/Responses Functional
More informationTECHNICAL CHALLENGES OF VoIP BYPASS
TECHNICAL CHALLENGES OF VoIP BYPASS Presented by Monica Cultrera VP Software Development Bitek International Inc 23 rd TELELCOMMUNICATION CONFERENCE Agenda 1. Defining VoIP What is VoIP? How to establish
More informationChapter 10 Session Initiation Protocol. Prof. Yuh-Shyan Chen Department of Computer Science and Information Engineering National Taipei University
Chapter 10 Session Initiation Protocol Prof. Yuh-Shyan Chen Department of Computer Science and Information Engineering National Taipei University Outline 12.1 An Overview of SIP 12.2 SIP-based GPRS Push
More informationSIP Essentials Training
SIP Essentials Training 5 Day Course Lecture & Labs COURSE DESCRIPTION Learn Session Initiation Protocol and important protocols related to SIP implementations. Thoroughly study the SIP protocol through
More informationTSIN02 - Internetworking
TSIN02 - Internetworking Lecture 9: SIP and H323 Literature: Understand the basics of SIP and it's architecture Understand H.323 and how it compares to SIP Understand MGCP (MEGACO/H.248) SIP: Protocol
More informationThis specification this document to get an official version of this User Network Interface Specification
This specification describes the situation of the Proximus network and services. It will be subject to modifications for corrections or when the network or the services will be modified. Please take into
More informationVIDEOCONFERENCING. Video class
VIDEOCONFERENCING Video class Introduction What is videoconferencing? Real time voice and video communications among multiple participants The past Channelized, Expensive H.320 suite and earlier schemes
More informationMedia Gateway Controller RTP
1 Softswitch Architecture Interdomain protocols Application Server Media Gateway Controller SIP, Parlay, Jain Application specific Application Server Media Gateway Controller Signaling Gateway Sigtran
More informationChapter 2 PSTN and VoIP Services Context
Chapter 2 PSTN and VoIP Services Context 2.1 SS7 and PSTN Services Context 2.1.1 PSTN Architecture During the 1990s, the telecommunication industries provided various PSTN services to the subscribers using
More informationVA Enterprise Standard: VIDEO CODEC/RECORDING
DEPARTMENT OF VETERANS AFFAIRS (VA) OFFICE OF INFORMATION AND TECHNOLOGY (OIT) VA SERVICE DELIVERY ENGINEERING (SDE) ENTERPRISE SYSTEMS ENGINEERING (ESE) VA Enterprise Standard: VIDEO CODEC/RECORDING Version
More informationUnit 23. RTP, VoIP. Shyam Parekh
Unit 23 RTP, VoIP Shyam Parekh Contents: Real-time Transport Protocol (RTP) Purpose Protocol Stack RTP Header Real-time Transport Control Protocol (RTCP) Voice over IP (VoIP) Motivation H.323 SIP VoIP
More informationSession Initiation Protocol
TECHNICAL OVERVIEW Session Initiation Protocol Author: James Wright, MSc This paper is a technical overview of the Session Initiation Protocol and is designed for IT professionals, managers, and architects
More informationVoice over IP (VoIP) Overview. Introduction. David Feiner ACN 2004. Introduction VoIP & QoS H.323 SIP Comparison of H.323 and SIP Examples
Voice over IP (VoIP) David Feiner ACN 2004 Overview Introduction VoIP & QoS H.323 SIP Comparison of H.323 and SIP Examples Introduction Voice Calls are transmitted over Packet Switched Network instead
More informationWhite paper. SIP An introduction
White paper An introduction Table of contents 1 Introducing 3 2 How does it work? 3 3 Inside a normal call 4 4 DTMF sending commands in sip calls 6 5 Complex environments and higher security 6 6 Summary
More informationA Comparative Study of Signalling Protocols Used In VoIP
A Comparative Study of Signalling Protocols Used In VoIP Suman Lasrado *1, Noel Gonsalves *2 Asst. Prof, Dept. of MCA, AIMIT, St. Aloysius College (Autonomous), Mangalore, Karnataka, India Student, Dept.
More informationEncapsulating Voice in IP Packets
Encapsulating Voice in IP Packets Major VoIP Protocols This topic defines the major VoIP protocols and matches them with the seven layers of the OSI model. Major VoIP Protocols 15 The major VoIP protocols
More informationinternet technologies and standards
Institute of Telecommunications Warsaw University of Technology 2015 internet technologies and standards Piotr Gajowniczek Andrzej Bąk Michał Jarociński multimedia in the Internet Voice-over-IP multimedia
More informationBest Practices for Role Based Video Streams (RBVS) in SIP. IMTC SIP Parity Group. Version 33. July 13, 2011
Best Practices for Role Based Video Streams (RBVS) in SIP IMTC SIP Parity Group Version 33 July 13, 2011 Table of Contents 1. Overview... 3 2. Role Based Video Stream (RBVS) Best Practices Profile... 4
More informationApplication Note. Onsight Mobile Collaboration Video Endpoint Interoperability v5.0
Application Note Onsight Mobile Collaboration Video Endpoint Interoperability v5. Onsight Mobile Collaboration Video Endpoint Interoperability... 3 Introduction... 3 Adding Onsight to a Video Conference
More informationApplication Note. Firewall Requirements for the Onsight Mobile Collaboration System and Hosted Librestream SIP Service v5.0
Application Note Firewall Requirements for the Onsight Mobile Collaboration System and Hosted Librestream SIP Service v5.0 1 FIREWALL REQUIREMENTS FOR ONSIGHT MOBILE VIDEO COLLABORATION SYSTEM AND HOSTED
More informationMultimedia & Protocols in the Internet - Introduction to SIP
Information and Communication Networks Multimedia & Protocols in the Internet - Introduction to Siemens AG 2004 Bernard Hammer Siemens AG, München Presentation Outline Basics architecture Syntax Call flows
More informationSession Initiation Protocol (SIP) 陳 懷 恩 博 士 助 理 教 授 兼 計 算 機 中 心 資 訊 網 路 組 組 長 國 立 宜 蘭 大 學 資 工 系 Email: wechen@niu.edu.tw TEL: 03-9357400 # 340
Session Initiation Protocol (SIP) 陳 懷 恩 博 士 助 理 教 授 兼 計 算 機 中 心 資 訊 網 路 組 組 長 國 立 宜 蘭 大 學 資 工 系 Email: wechen@niu.edu.tw TEL: 03-9357400 # 340 Outline Session Initiation Protocol SIP Extensions SIP Operation
More informationVoice over IP Fundamentals
Voice over IP Fundamentals Duration: 5 Days Course Code: GK3277 Overview: The aim of this course is for delegates to gain essential data networking and Voice over IP (VoIP) knowledge in a single, week-long
More informationReview: Lecture 1 - Internet History
Review: Lecture 1 - Internet History late 60's ARPANET, NCP 1977 first internet 1980's The Internet collection of networks communicating using the TCP/IP protocols 1 Review: Lecture 1 - Administration
More informationSIP Messages. 180 Ringing The UA receiving the INVITE is trying to alert the user. This response MAY be used to initiate local ringback.
SIP Messages 100 Trying This response indicates that the request has been received by the next-hop server and that some unspecified action is being taken on behalf of this call (for example, a database
More informationSIP: Ringing Timer Support for INVITE Client Transaction
SIP: Ringing Timer Support for INVITE Client Transaction Poojan Tanna (poojan@motorola.com) Motorola India Private Limited Outer Ring Road, Bangalore, India 560 037 Abstract-The time for which the Phone
More informationDistrict of Columbia Courts Attachment 1 Video Conference Bridge Infrastructure Equipment Performance Specification
1.1 Multipoint Control Unit (MCU) A. The MCU shall be capable of supporting (20) continuous presence HD Video Ports at 720P/30Hz resolution and (40) continuous presence ports at 480P/30Hz resolution. B.
More informationApplication Note. Onsight Connect Network Requirements V6.1
Application Note Onsight Connect Network Requirements V6.1 1 ONSIGHT CONNECT SERVICE NETWORK REQUIREMENTS... 3 1.1 Onsight Connect Overview... 3 1.2 Onsight Connect Servers... 4 Onsight Connect Network
More informationSession Initiation Protocol (SIP)
SIP: Session Initiation Protocol Corso di Applicazioni Telematiche A.A. 2006-07 Lezione n.7 Ing. Salvatore D Antonio Università degli Studi di Napoli Federico II Facoltà di Ingegneria Session Initiation
More informationSIP Basics. CSG VoIP Workshop. Dennis Baron January 5, 2005. Dennis Baron, January 5, 2005 Page 1. np119
SIP Basics CSG VoIP Workshop Dennis Baron January 5, 2005 Page 1 Outline What is SIP SIP system components SIP messages and responses SIP call flows SDP basics/codecs SIP standards Questions and answers
More informationSIP Trunking Manual 05.15. Technical Support Web Site: http://ws1.necii.com (registration is required)
SIP Trunking Manual 05.15 Technical Support Web Site: http://ws1.necii.com (registration is required) This manual has been developed by NEC Unified Solutions, Inc. It is intended for the use of its customers
More informationDialogic Diva SIPcontrol Software
Dialogic Diva SIPcontrol Software converts Dialogic Diva Media Boards (Universal and V-Series) into SIP-enabled PSTN-IP gateways. The boards support a variety of TDM protocols and interfaces, ranging from
More informationSIP (Session Initiation Protocol) Technical Overview. Presentation by: Kevin M. Johnson VP Engineering & Ops
SIP (Session Initiation Protocol) Technical Overview Presentation by: Kevin M. Johnson VP Engineering & Ops Page 1 Who are we? Page 2 Who are we? Workforce Automation Software Developer Page 3 Who are
More informationAn Introduction to VoIP Protocols
An Introduction to VoIP Protocols www.netqos.com Voice over IP (VoIP) offers the vision of a converged network carrying multiple types of traffic (voice, video, and data, to name a few). To carry out this
More informationInternet Working 15th lecture (last but one) Chair of Communication Systems Department of Applied Sciences University of Freiburg 2005
15th lecture (last but one) Chair of Communication Systems Department of Applied Sciences University of Freiburg 2005 1 43 administrational stuff Next Thursday preliminary discussion of network seminars
More informationThis presentation discusses the new support for the session initiation protocol in WebSphere Application Server V6.1.
This presentation discusses the new support for the session initiation protocol in WebSphere Application Server V6.1. WASv61_SIP_overview.ppt Page 1 of 27 This presentation will provide an overview of
More informationOverview of Voice Over Internet Protocol
Overview of Voice Over Internet Protocol Purva R. Rajkotia, Samsung Electronics November 4,2004 Overview of Voice Over Internet Protocol Presentation Outline History of VoIP What is VoIP? Components of
More informationInternet Services & Protocols Multimedia Applications, Voice over IP
Department of Computer Science Institute for System Architecture, Chair for Computer Networks Internet Services & Protocols Multimedia Applications, Voice over IP Dipl.-Inform. Stephan Groß Room: GRU314
More informationVoice over IP & Other Multimedia Protocols. SIP: Session Initiation Protocol. IETF service vision. Advanced Networking
Advanced Networking Voice over IP & Other Multimedia Protocols Renato Lo Cigno SIP: Session Initiation Protocol Defined by IETF RFC 2543 (first release march 1999) many other RFCs... see IETF site and
More informationVoIP. What s Voice over IP?
VoIP What s Voice over IP? Transmission of voice using IP Analog speech digitized and transmitted as IP packets Packets transmitted on top of existing networks Voice connection is now packet switched as
More informationIP-Telephony SIP & MEGACO
IP-Telephony SIP & MEGACO Bernard Hammer Siemens AG, Munich Siemens AG 2001 1 Presentation Outline Session Initiation Protocol Introduction Examples Media Gateway Decomposition Protocol 2 IETF Standard
More information159.334 Computer Networks. Voice over IP (VoIP) Professor Richard Harris School of Engineering and Advanced Technology (SEAT)
Voice over IP (VoIP) Professor Richard Harris School of Engineering and Advanced Technology (SEAT) Presentation Outline Basic IP phone set up The SIP protocol Computer Networks - 1/2 Learning Objectives
More informationIP-Telephony Real-Time & Multimedia Protocols
IP-Telephony Real-Time & Multimedia Protocols Bernard Hammer Siemens AG, Munich Siemens AG 2001 1 Presentation Outline Media Transport RTP Stream Control RTCP RTSP Stream Description SDP 2 Real-Time Protocol
More informationFirewall Support for SIP
Firewall Support for SIP The Firewall Support for SIP feature integrates Cisco IOS firewalls, Voice over IP (VoIP) protocol, and Session Initiation Protocol (SIP) within a Cisco IOS-based platform, enabling
More informationInternet Services & Protocols Multimedia Applications, Voice over IP
Department of Computer Science Institute for System Architecture, Chair for Computer Networks Internet Services & Protocols Multimedia Applications, Voice over IP Dr.-Ing. Stephan Groß Room: INF 3099 E-Mail:
More informationSIP Trunking Quick Reference Document
SIP Trunking Quick Reference Document Publication Information SAMSUNG TELECOMMUNICATIONS AMERICA reserves the right without prior notice to revise information in this publication for any reason. SAMSUNG
More informationLehrstuhl für Informatik 4 Kommunikation und verteilte Systeme
Chapter 2: Representation of Multimedia Data Chapter 3: Multimedia Systems Communication Aspects and Services Multimedia Applications and Communication Protocols Quality of Service and Resource Management
More informationThe use of IP networks, namely the LAN and WAN, to carry voice. Voice was originally carried over circuit switched networks
Voice over IP Introduction VoIP Voice over IP The use of IP networks, namely the LAN and WAN, to carry voice Voice was originally carried over circuit switched networks PSTN (Public Switch Telephone Network)
More informationHow To Use A Pbx On A Network With A Ppl (Ipo) On A Pnet On A Microsoft Ip On A Pc Or Ip On An Ip On Ip On Pc Or Mac On A Cell Phone On A 2G
Technical Specification IP phone IP230 Interfaces Ethernet: Headset: 2 x RJ 45 interface 10/100-BASE-TX (auto negotiation) with internal 2 port switch and Power over LAN, Class 1 (IEEE 802.3af) RJ-45 interface
More informationContents. Specialty Answering Service. All rights reserved.
Contents 1. Introduction to Session Internet Protocol... 2 2. History, Initiation & Implementation... 3 3. Development & Applications... 4 4. Function & Capability... 5 5. SIP Clients & Servers... 6 5.1.
More informationSpecial Module on Media Processing and Communication
Special Module on Media Processing and Communication Multimedia Communication Fundamentals Dayalbagh Educational Institute (DEI) Dayalbagh Agra PHM 961 Indian Institute of Technology Delhi (IITD) New Delhi
More informationImplementing Intercluster Lookup Service
Appendix 11 Implementing Intercluster Lookup Service Overview When using the Session Initiation Protocol (SIP), it is possible to use the Uniform Resource Identifier (URI) format for addressing an end
More informationVOICE over IP H.323 Advanced Computer Network SS2005 Presenter : Vu Thi Anh Nguyet
VOICE over IP H.323 Advanced Computer Network SS2005 Presenter : Vu Thi Anh Nguyet 1 Outlines 1. Introduction 2. QoS in VoIP 3. H323 4. Signalling in VoIP 5. Conclusions 2 1. Introduction to VoIP Voice
More informationIxLoad Voice SIP Key Features
IxLoad Voice SIP Key Features IxLoad Voice SIP is the perfect tool for functional, performance, and stability testing of SIP-based voice over IP (VoIP) network components. Because IxLoad supports SIP,
More informationVoIP QoS. Version 1.0. September 4, 2006. AdvancedVoIP.com. sales@advancedvoip.com support@advancedvoip.com. Phone: +1 213 341 1431
VoIP QoS Version 1.0 September 4, 2006 AdvancedVoIP.com sales@advancedvoip.com support@advancedvoip.com Phone: +1 213 341 1431 Copyright AdvancedVoIP.com, 1999-2006. All Rights Reserved. No part of this
More informationMaster Kurs Rechnernetze Computer Networks IN2097
Chair for Network Architectures and Services Institute for Informatics TU München Prof. Carle, Dr. Fuhrmann Master Kurs Rechnernetze Computer Networks IN2097 Prof. Dr.-Ing. Georg Carle Dr. Thomas Fuhrmann
More informationNetwork Considerations for IP Video
Network Considerations for IP Video H.323 is an ITU standard for transmitting voice and video using Internet Protocol (IP). It differs from many other typical IP based applications in that it is a real-time
More informationOnline course syllabus. MAB: Voice over IP
Illuminating Technology Course aim: Online course syllabus MAB: Voice over IP This course introduces the principles and operation of telephony services that operate over Internet Protocol (IP) networks
More informationInternet Technology Voice over IP
Internet Technology Voice over IP Peter Gradwell BT Advert from 1980s Page 2 http://www.youtube.com/v/o0h65_pag04 Welcome to Gradwell Gradwell provides technology for every line on your business card Every
More informationGrandstream Networks, Inc.
Grandstream Networks, Inc. GVC3200/GVC3200 Conferencing System for Android TM Application Note: Preliminary Interoperability Test between GVC3200/GVC3200 and Other Video Conference Systems Index INTRODUCTION...
More informationPart II. Prof. Ai-Chun Pang Graduate Institute of Networking and Multimedia, Dept. of Comp. Sci. and Info. Engr., National Taiwan University
Session Initiation Protocol oco (SIP) Part II Prof. Ai-Chun Pang Graduate Institute of Networking and Multimedia, Dept. of Comp. Sci. and Info. Engr., National Taiwan University Email: acpang@csie.ntu.edu.tw
More informationConferencing Using the IP Multimedia (IM) Core Network (CN) Subsystem
GPP X.S00-0 Version.0 Version Date: May 00 Conferencing Using the IP Multimedia (IM) Core Network (CN) Subsystem Revision: 0 COPYRIGHT GPP and its Organizational Partners claim copyright in this document
More informationIxLoad VoIP SIP, MGCP Features
IxLoad VoIP SIP, MGCP Features Aptixia IxLoad can test the performance of VoIP networks and devices by emulating SIP and MGCP user agents. IxLoad can be used to: Test the scalability and performance of
More informationReceiving the IP packets Decoding of the packets Digital-to-analog conversion which reproduces the original voice stream
Article VoIP Introduction Internet telephony refers to communications services voice, fax, SMS, and/or voice-messaging applications that are transported via the internet, rather than the public switched
More informationIndepth Voice over IP and SIP Networking Course
Introduction SIP is fast becoming the Voice over IP protocol of choice. During this 3-day course delegates will examine SIP technology and architecture and learn how a functioning VoIP service can be established.
More informationVOICE OVER IP (VOIP) TO ENTERPRISE USERS GIOTIS KONSTANTINOS
VOICE OVER IP (VOIP) TO ENTERPRISE USERS GIOTIS KONSTANTINOS Master of Science in Networking and Data Communications THESIS Thesis Title Voice over IP (VoIP) to Enterprise Users Dissertation submitted
More informationLifeSize UVC Multipoint Deployment Guide
LifeSize UVC Multipoint Deployment Guide May 2014 LifeSize UVC Multipoint Deployment Guide 2 LifeSize UVC Multipoint LifeSize UVC Multipoint is a software MCU optimized for conferences that mix high definition
More informationBroadband Telephony. Terminal Equipment Requirements and Specifications
Broadband Telephony Terminal Equipment Requirements and Specifications TABLE OF CONTENTS 1 Introduction... 3 1.1 Scope... 3 1.2 Intended audience... 3 1.3 Notice... 3 1.4 Definitions... 3 2 BBT Service
More informationOverview of VoIP Systems
2 Overview of VoIP Systems In their simplest form, Voice over IP protocols simply enable two (or more) devices to transmit and receive real-time audio traffic that allows their respective users to communicate.
More informationNTP VoIP Platform: A SIP VoIP Platform and Its Services
NTP VoIP Platform: A SIP VoIP Platform and Its Services Speaker: Dr. Chai-Hien Gan National Chiao Tung University, Taiwan Email: chgan@csie.nctu.edu.tw Date: 2006/05/02 1 Outline Introduction NTP VoIP
More informationVegaStream Information Note Considerations for a VoIP installation
VegaStream Information Note Considerations for a VoIP installation To get the best out of a VoIP system, there are a number of items that need to be considered before and during installation. This document
More informationDeveloping Higher Density Solutions with Dialogic Host Media Processing Software
Telecom Dialogic HMP Media Server Developing Higher Density Solutions with Dialogic Host Media Processing Software A Strategy for Load Balancing and Fault Handling Developing Higher Density Solutions with
More informationSession Initiation Protocol (SIP)
Session Initiation Protocol (SIP) Introduction A powerful alternative to H.323 More flexible, simpler Easier to implement Advanced features Better suited to the support of intelligent user devices A part
More informationBasic Vulnerability Issues for SIP Security
Introduction Basic Vulnerability Issues for SIP Security By Mark Collier Chief Technology Officer SecureLogix Corporation mark.collier@securelogix.com The Session Initiation Protocol (SIP) is the future
More informationMODELLING OF INTELLIGENCE IN INTERNET TELEPHONE SYSTEM
MODELLING OF INTELLIGENCE IN INTERNET TELEPHONE SYSTEM Evelina Nicolova Pencheva, Vessela Liubomirova Georgieva Department of telecommunications, Technical University of Sofia, 7 Kliment Ohridski St.,
More informationTechnical Manual 3CX Phone System for Windows
Technical Manual 3CX Phone System for Windows This technical manual is intended for those who wish to troubleshoot issues encountered with implementing 3CX Phone System. It is not intended to replace the
More informationVoice Over IP. Priscilla Oppenheimer www.priscilla.com
Voice Over IP Priscilla Oppenheimer www.priscilla.com Objectives A technical overview of the devices and protocols that enable Voice over IP (VoIP) Demo Packet8 and Skype Discuss network administrator
More informationProvisioning and configuring the SIP Spider
Provisioning and configuring the SIP Spider Administrator Guide Table of Contents 1. Introduction... 3 2. Manual Provisioning... 4 3. Automatic Provisioning... 5 3.1 Concept... 5 3.2 Preparing the configuration
More informationAN IPTEL ARCHITECTURE BASED ON THE SIP PROTOCOL
AN IPTEL ARCHITECTURE BASED ON THE SIP PROTOCOL João Paulo Sousa Instituto Politécnico de Bragança R. João Maria Sarmento Pimentel, 5370-326 Mirandela, Portugal + 35 27 820 3 40 jpaulo@ipb.pt Eurico Carrapatoso
More informationOffice Communications Server 2007 Videoconferencing Interoperability
Office Communications Server 2007 Videoconferencing Interoperability Microsoft Corporation Published: July 31, 2008 Executive Summary Microsoft Office Communications Server 2007 is the first Microsoft
More informationFor internal circulation of BSNL only
E1-E2 E2 CFA Session Initiation Protocol AGENDA Introduction to SIP Functions of SIP Components of SIP SIP Protocol Operation Basic SIP Operation Introduction to SIP SIP (Session Initiation Protocol) is
More informationHow To Set Up A Cisco Expressway Trunk On A Cnet Cnet Trunk On An Unidenm (Cisco Vcnet) Vcntl On A Uniden Mt.Net (Cnet Trunk) On A Multi
Cisco Unified Communications Manager with Cisco Expressway (SIP Trunk) Deployment Guide Cisco Expressway X8.2 Unified CM 8.6.x, 9.x January 2015 Contents Introduction 4 Deployment scenario 4 Configuring
More informationVoice over IP. Presentation Outline. Objectives
Voice over IP Professor Richard Harris Presentation Outline Brief overview of VoIP and applications Challenges of VoIP IP Support for Voice Protocols used for VoIP (current views) RTP RTCP RSVP H.323 Semester
More informationBest Practices for SIP Security
Best Practices for SIP Security IMTC SIP Parity Group Version 21 November 9, 2011 Table of Contents 1. Overview... 33 2. Security Profile... 33 3. Authentication & Identity Protection... 33 4. Protecting
More informationVoice-Over-IP. Daniel Zappala. CS 460 Computer Networking Brigham Young University
Voice-Over-IP Daniel Zappala CS 460 Computer Networking Brigham Young University Coping with Best-Effort Service 2/23 sample application send a 160 byte UDP packet every 20ms packet carries a voice sample
More informationUnified Communications Drive Protocol Convergence
Unified Communications Drive Protocol Convergence November 2009 1 INTRODUCTION With the emergence of the Unified Communications 1 (UC) concept, enterprises, service providers and other organizations started
More informationSIP, Session Initiation Protocol used in VoIP
SIP, Session Initiation Protocol used in VoIP Page 1 of 9 Secure Computer Systems IDT658, HT2005 Karin Tybring Petra Wahlund Zhu Yunyun Table of Contents SIP, Session Initiation Protocol...1 used in VoIP...1
More informationETM System SIP Trunk Support Technical Discussion
ETM System SIP Trunk Support Technical Discussion Release 6.0 A product brief from SecureLogix Corporation Rev C SIP Trunk Support in the ETM System v6.0 Introduction Today s voice networks are rife with
More informationVOIP-211RS/210RS/220RS/440S. SIP VoIP Router. User s Guide
VOIP-211RS/210RS/220RS/440S SIP VoIP Router User s Guide Trademarks Contents are subject to revise without prior notice. All trademarks belong to their respective owners. FCC Warning This equipment has
More informationApplication Note. Onsight Connect Network Requirements v6.3
Application Note Onsight Connect Network Requirements v6.3 APPLICATION NOTE... 1 ONSIGHT CONNECT NETWORK REQUIREMENTS V6.3... 1 1 ONSIGHT CONNECT SERVICE NETWORK REQUIREMENTS... 3 1.1 Onsight Connect Overview...
More information