2. Agenda
Classic Circuit Switched Telephony - PSTN
Audio Signal - Sample-based Coding
General Voip (why, advantages, QoS,...)
H.323 (overview, elements, standard, …)
3. Classic Circuit Switched Telephony -
PSTN Public Switched Telephone Network
POTS Plain Old Telephone Service -
Analog Telephony
ISDN Integraded Services Digital Network -
Digital Telephony
4. Classic Circuit Switched Telephony -
POTS Plain Old Telephone Service
Inventors
– Philipp Reise, Frankfurt 1861
– Alexander Graham Bell, Boston, 1876, patent
– Elisha Gray, 1876, 2 hours later
– Antonio Santi Giuseppe Meucci, 1854, presented in 1860, filed
patent in 1871, patent expired in 1874
main usage (assumed): concert broadcasting
voice coding and transmission: analog acoustic signal
transformed to (similar) analog electrical signal
5. Classic Circuit Switched Telephony -
POTS Plain Old Telephone Service
analog telephone connection (cont.):
dedicated link between partners
reserved bandwidth that cannot be used by other users =>
billing based on connection time and distance
signaling (call setup and teardown):
– in the beginning: point-to-point links
– later telephone wired to central office
6. Classic Circuit Switched Telephony -
ISDN Integrated Service Digital Network
transforming analog acoustic / electric signal to digital
values: PCM (Pulse Code Modulation)
8000 samples/s, each sample coded by 8 bits => 64 kbit/s
7. Classic Circuit Switched Telephony -
ISDN Integrated Service Digital Network
PCM (Pulse Code Modulation)- Standard ITU-T G.711
– sampling: discrete time values
Nyquist’s Theorem: 1/Ts >= B for for a good quality signal conversion
analog => digital
Human voice: 1 sample every 125 million/s => 8000 sample/s
Shannon’s theorem: Fsampling >= 2* Fmax
Phone Signal (including the range of human voice) : 300 – 3400 Hz, it’s
considered 4000 Hz (Fmax) => sampling rate: 2* 4000 Hz => 8000 Hz
8 bits / sample value => 8*8000 =>64 kbit/s
– quantisation: discrete sampling values
splitting the voltage range chosen in intervals associating a single
digital value per each internal. 8 bits => 28
= 256 intervals
8. Classic Circuit Switched Telephony -
ISDN Integrated Service Digital Network
An important step forward used in the ISDN technology
was the conversion of an analogue signal (human voice)
into a digital format, transporting it and, at the destination
party reconverting it again into the analogue format. This
coding approach is the one used in VOIP as well.
ISDN performs this anyway going on using mostly the
Circuit Switched Networks.
9. Classic Circuit Switched Telephony -
ISDN Integrated Service Digital Network
BRI Basic Rate Interface (144 Kbps bandwidth)
1 D channel 16 Kbps for signaling
2 B channels 64 Kbps
PRI Primary Rate Interface (2 Mbps bandwidth)
1 D channel 64 Kbps for signaling
30 B channels 64 Kbps
10. PSTN Public Switched Telephone Network
Both POTS and ISDN use the same connection philosophy:
circuit switched, so there’s a permanent reservation of the
network resources for the active or on-going
communications.
Both POTS and ISDN mostly use the same multiplexing
philosophy: TDM Time Division Multiplexing.
Both POTS and ISDN use the same addressing standard:
E.164, so the classical telephone numbers.
11. VOIP Voice Over IP - A Definition
VOIP stands for Voice Over Intenet Protocol and is a
technology to let voice go through IP packets and,
in definitive through Internet so a packed switched
network.
12. VOIP Voice Over IP - An overview
To COde/DECode the voice, even Voip started using the PCM seen in
ISDN with further improvements. So, at the source site, an ADC (Analog
Digital Converter) makes the voice digital.The IP network transports
packets having an header to control the communication and payload to
transport data. At the destination site, another ADC, reconvert the digital
packet into the analog voice.
14. Why VOIP ? - Business Aspects
single net infrastructure!! (companies, providers)
– Deutsche Telekom’s plan for 2012: PSTN will be totally replaced by
IP net
– USA: 30 % of telephone traffic is already VoIP
– the number of new VoIP providers is growing an growing monthly
cheap costs!! (users)
– removal of recurring cost of leased PSTN lines and associated
equipments and their maintenance
– usage based (time/distance) charges substituted by flat
monthly/annual charges (ISP connection)
– less taxes
15. Why VOIP ? (cont.)
universal VoIP account reachability!! (You can make a
call anywhere the Internet can reach)
availability of new applications!!
– click-to-dial feature: link on a web page or application:
click => call setup
– unified messaging (telephony, e-mail, sms, chat..etc)
– exchange of additional data:
audio and video conferences so multicast communication
shared applications
16. QoS in VOIP
VoIP goes through a network that was created to offer a best
effort service transport => queue time not controlled,
sometimes long:
– Packet loss => can be partially compensated by latest codecs
improving the voice compression phase and making shorter the voice
packet working on the headers (IP, UDP, RTP).
– Delay => calls may result in echo problems Jitter (delay variation)
compensated with a dejitter buffer => this buffer increases delay
when necessary.
Security, all the same risks as can be found with any IP
technology.
17. QoS in VOIP- Packet loss
40 bytes only for headers!! For a transmission rate of 20ms at 8kbps there’s a payload (compressed voice)
of 20 kbps. So 66% of the packet is busy for headers with a large quantity of redundant data => so a
possible solution, only the header of the 1st packet is complete, the header of the following packets
only contain the delta => the whole header can became 4-5 bytes!
18. QoS in VOIP - delay
The delay variation gives the jitter.
– optimal situation: no delay (=> no jitter):
19. QoS in VOIP - delay
The delay variation gives the jitter effect.
– constant delay (=> no jitter):
20. QoS in VOIP - delay
The delay variation gives the jitter effect.
– variable delay (=> jitter):
21. QoS in VOIP - delay
The delay variation gives the jitter effect.
– jitter can be compensated by playout buffering
– example: buffering time long.
and risk of buffer overflow
22. QoS in VOIP - delay
The delay variation gives the jitter effect.
– jitter can be compensated by playout buffering
– example: buffering time too short
23. QoS in VOIP - delay
The delay variation gives the jitter effect.
– jitter can be compensated by playout buffering
– example: optimal buffering time
24. QoS in VOIP - security
Security, all the same risks as can be found with
any IP technology
– typical solutions for data: IPSec, VPN
– encryption technology
At the end of March, Phillip Zimmerman, creator of the email
encryption technology PGP, announced that he had developed
Zfone, encryption for VoIP. It's currently only available on Mac
and Linux but Windows is coming.
25. QoS in VOIP - security
Secure Real Time Protocol (SRTP)
Described in RFC 3711, provides confidentiality,
message authentication, and protection for RTP and
RTCP traffic.
As side effect, the packet creation needs more time.
26. Major Standards on VoIP
Minimal functions to be achieved:
– Signaling (sets up association between
parties)
H.323
(ITU: International Telecommunication
Union)
SIP (Session Initiation Protocol)
(IETF: Internet Eng. Task Force)
Skype (company proprietary)
– Media transport (Voice and/or Video as
well)
RTP & RTCP
27. Standards on VoIP - Media transport
Audio/Video(real-time) vs. Data
Audio/Video:
– Analog in nature
– Delay sensitive
Data:
– Loss sensitive
– Error sensitive
28. Standards on VoIP - Media transport
TCP vs. UDP
TCP - Transmission Control Protocol
Connection oriented protocol.
– Handles sequencing and error detection,
ensuring that a reliable stream of data is
received by the destination application (packet
sequence numbers / acknowledgements /
resending).
– TCP – Signaling part with with upper layer
protocols.
UDP - User Datagram Protocol
Connectionless protocol as IP
– Does not attempt to perform any sequencing, or
to ensure data reliability.
– UDP – Media Transport Part with upper layer
protocols.
29. Standards on VoIP - Media transport
RTP (Real-time Transport Protocol)
provides end-to-end delivery services for data with real-time characteristics
(audio and video)
Address real time requirements including Jitter(variation in delay times
experienced by the individual packets making up the data stream), buffering
and playing out at a constant rate.
payload type identification=> allowing use of different coding schemes
sequence numbering=>to discover packet loss and re-ordering
time stamping=>allowing synchronization
Source identification=>a source may be identified independently of its IP
address
supports mixers and translators
it’s used both in H.323 and SIP, major VOIP standards
30. Standards on VoIP - Media transport
RTP header format
T version P padding X extension CSRC ct. Sender counter
M Marker Payload Type media code method
Sequence Number seq. number of the packet for a media transmission
Timestamp timestamp for syncronization
SSRC identifier of the sender CSRC list of senders
31. Standards on VoIP - Media transport
RTP header format - translator/mixer features
translator: coding transformation
mixer: mixing several audio streams into a single audio stream
32. Standards on VoIP - Media transport
RTCP (RTP Control Protocol)
RTCP functions:
– monitors and provides feedback on the quality of the transmission link for
data transported by the RTP packets (ie: if the bandwidth is lower than
usual, the sender may adapt the audio coding to a compression requiring
a lower data rate)
– support for multi-point communication(ie: information on leaving
conference members)
– identification of sources, Source DEScription:canonical name.(ie:for
communication conflict problems or program restart the SSRC identifier
might change, so the receiver asks for the CNAME (Canonical NAME) to
identify again the sender. It can be useful even to reorganize multiple
sessions (audio, video) with the same sender.
33. H.323 - a standard for VoIP
Recommendation H.323 published by the International
Telecommunications Union Telecommunications Sector (ITU-T)
is a standard for multimedia services over packet networks,
including rules to map the multimedia. communication services
over a variety of networks.
H.323 specifies:
– Components
– Protocols
– Procedures
34. H.323 - Components
Terminals
Multipoint Control Unit (MCU)
Gateway
Gatekeeper
Border Elements
Referred to as
“endpoints”
35. H.323 - Components
Terminals
An H.323 terminal is the communicating endpoint on the
network allowing the audio (and optionally even video)
bidirectional communication with another H.323 terminal,
gateway or MCU
Examples:
– Telephones
– Video phones
– IVR (Interactive Voice Responder) devices
– Voicemail Systems
– “Soft phones” (e.g.: NetMeeting®)
36. H.323 - Components
MCU (Multipoint Control Unit)
Responsible for managing multipoint conferences
(two or more endpoints engaged in a conference)
The MCU contains a Multipoint Controller (MC) that
manages the call signaling and may optionally have
Multipoint Processors (MPs) to handle media mixing,
switching, or other media processing
37. H.323 - Components
MCU (Multipoint Control Unit)
signaling and media data
signaling
media data
38. H.323 - Components
Gateway
Gateways interface H.323 to other not H.323
networks mapping the transmission format and the
communication procedures
The Gateway is composed of a :
– “Media Gateway Controller” (MGC) that handles call
signaling and other non-media-related functions
– “Media Gateway” (MG), that handles the media (multiplex,
rate matching, audio transcoding…)
39. H.323 - Components
Gateway
IP ISDN
Terminal
H.320
(ISDN)
Media Gateway Controller
signaling
Media Gateway
data
audio
video
Terminal
H.323
GatewayTerminal
H.323
Terminal
H.320
40. H.323 - Components
Gatekeeper
Mandatory Zone Management functions :
– Admission control. Check if an endpoint is allowed or
not to access to the system.
– Address translation (routing). It works as a location
server mapping telephone number/email addresses/alias
to IP addresses.
– Bandwidth control and resource reservation
41. H.323 - Components
Gatekeeper - The Zone
A Zone is a group of H.323 endpoints controlled by
one Gatekeeper
GK
GW
MCU
T1
Tn
PSTN
IP cloud
Router
43. H.323 - Protocols
Signaling (Everything that is not Media Data Transport)
H.225.0 Call signaling protocol and media stream packetization for packet-based
multimedia. It includes Q.931 and RAS.
– H.225 RAS (Registration, Admission and Status)
Gatekeeper discovery
Gatekeeper Registration
Admission control
– H.225 Call Signaling facility (derived from Q.931 ISDN control ch.)
setup, alert, connect, release complete, ...
H.245 provides “control” to the multimedia session that has been established - use
UDP
– Terminal capability exchange
– Master/Slave determinations
– Logical channel signaling
– Conference control (protocol for the MC channel in MCU)
46. H.323 - Procedures - basic call
Gatekeeper A Gatekeeper B
RRQ/RCF
ARQ
RRQ/RCF
LRQ
IP Network
Phone A
Gateway A Gateway B
H.225 (Q.931) Setup
H.225 (Q.931) Alert and Connect
H.245
RTP
ACF
LCF
V V
ARQ
ACF
Phone B
basic procedure: PCM (Pulse Code Modulation), used in ISDN:
• sampling: discrete time values. An analog signal can be represented by mean a set of digital values without a loss of signal quality if the recommendation of the Nyquist’s Theorem is satisfied.
The Nyquist Theorem states that the sampling step (the time interval Ts between 2 samples) for an analog signal having as max bandwidht B must satisfy the following expression: 1/Ts > B. This for the sampling step, afterwards there’s the Shannon’s theorem stating that an analog signal having a maximum frequency of Fmax, can be represented by means a sequence of samples calculated with a frequency at least 2*Fmax, so Fsampling >= 2* Fmax
examples:
• ISDN: 300 – 3400 Hz (Human Voice), it’s considered 4000 Hz => sampling rate: 8000 Hz
8 bits / sample value => 8*8000 =>64 kbit/s
• CD: 22000 Hz => sampling rate: 44000 Hz
16 bits / sample value => 700 kbit/s
2 channels for stereo: 1.4 Mbit/s
• quantisation: discrete sampling values
multiplexing (transmitting several logical channels on one physical channel)
TDM Time Division Multiplexing
FDM Frequency Division Multiplexing
Digital format can be better controlled: we can compress it, route it, convert it to a new better format, crypt it, and so on. Moreover a digital signal is is more noise -voice tolerant than its analogue version.
Essentially for landline voice communications there are 2 network infrastructures: IP and PSTN.
Technology is going to be more and more IP centric.
WHY VOIP?
Given that “There’s nothing wrong with TDM” Proven, reliable technology, Central Office engineers understand circuit switching, PSTN Equipments are less expensive than in the past (even if Inet equipment are anyway cheaper)
But it’s to be considered that…
Long term, industry direction is packet-based networks, Even legacy vendors are committed there are immediate opportunities: Cost savings, Improved services, New business / revenue generating opportunities.
If you do nothing, there will be more and more competitive pressure. E.g. “Non-geographical” service providers like Vonage/Skype/etc already offer cheap service bundles over any broadband Internet connection
Voice QoS more demanding than pure data QoS (ftp, email…)
Impact of QoS problems
Packet loss (line noise, unnatural sound), can be partially compensated by codecs: Sequence Numbering in the RTP packet (so let’s say an UDP rather “TCP oriented)” Differential PCM (DPCM), Adaptive DPMC (ADPMC). Moreover voice overheading => IP header (20 bytes)+UPD header (8 bytes) + (12 bytes) RTP header = 40 bytes only for headers!! For a transmission rate of 20ms at 8kbps there’s a payload (compressed voice) of 20 kbps. So 66% of the data packet is busy for headers => only the 1st header is complete, the following contain only the delta => the whole header can became 4-5 bytes!
8000 bit/s. To have bits in ms 8000/1000=8 bit/ms. 8*20ms=160 bit/ms => 20 bytes/ms (ms= milliseconds) 20 ms is the average time for prepare the packet.
Delay in the packet delivery may give echo problems, Jitter (delay variation) compensated with a dejitter buffer -> increases delay to have an equal delay for all packets and a more natural effects.
Jitter is variation in packet arrival time
Due to the nature of packet networks, packets can travel from a source to a destination using different paths resulting in different travel delay
Speech samples have to be played back at regular intervals (sampling rate). Otherwise, a severe degradation in the speech quality can take place
A delay jitter buffer is used to reorder the packets and absorb the delay jitter caused by the network.
The larger the buffer the better is the protection from delay jitter. However, this will result in larger delays
That`s exactly what adaptive playout algorithms do: they dynamically adjust the size of the jitter buffer depending on the delays experienced by already received packets.
Interestingly in the same Network Instruments survey only 29% of IT managers expressed concern over the security of VoIP calls. This is certainly one area when VoIP is improving and where the somewhat open nature of the technology is paying dividends. At the end of March, Phillip Zimmerman, creator of the email encryption technology PGP, announced that he had developed Zfone, encryption for VoIP. It's currently only available on Mac and Linux but Windows is coming. It is already possible to seemlessly integrate it in to exisiting VoIP solutions and it is hoped that it will become standard amongst most, if not all, solutions in time.
Sender behavior
- Determine cryptographic context to use
- Derive session keys from master key (via MIKEY)
- Encrypt the RTP payload
- If message authentication required, compute authentication tag and append
- Send the SRTP packet to the socket
Receiver behavior
- Read the SRTP packet from the socket.
- Determine the cryptographic context to be used
- Determine the session keys from master key (via MIKEY)
- If message authentication and replay protection are provided,check for possible replay and verify the authentication tag
- Decrypt the Encrypted Portion of the packet
- If present, remove authentication tag
- Pass the RTP packet up the stack
H323:
- ITU standard
- Takes a more telecommunications-oriented approach
- 90%+ of all Service Provider VoIP networks
- Used in MS Windows NetMeeting (the other party can keep the control of the PC, remote sysadmn)
SIP :
- IETF RFC2543
- Takes an Internet-oriented approach.
- Used in MS Windows Messenger on Windows XP.
Two major protocols in transport layer above IP – TCP & UDP
Enable the transmission of information between the correct processes (or applications) on host computers. These processes are associated with unique port numbers (for example, the HTTP application is usually associated with port 80)
TCP - Transmission Control Protocol – one of the protocols in the TCP/IP suite of protocols. Sits above IP in the protocol stack and provides for reliable transport of data (checks for missing packets and retransmits or requests retransmits) and provides flow control
TCP cannot support multicast !!
An additional small disadvantage is that TCP header islarger than a UDP header (40 bytes for TCP compared to 8 bytes). Also, TCP does not contain the necessary timestamp and encoding information needed by the receiving application, so that it cannot replace RTP. (Anyway it would not need the sequence number as TCP assures that no losses or reordering takes place.)
Problem: resending causes additional delay, so reliable but slow.
UDP – User Datagram Protocol - one of the protocols in the TCP/IP suite of protocols. Sits above IP in the protocol stack (at the same level as TCP) and provides for unreliable transport of data (no checking or flow control)
Problem: no sequence numbers, no timestamps, no resending, so not reliable but faster than tcp.
RTP:
- Provides end-to-end delivery services
- Runs on UDP
- Address real time requirements including Jitter(variation in delay times experienced by the individual packets making up the data stream)
- Buffering and playing out at a constant rate.
RTP - transports the digitized samples of real time information
- Sequence numbering : to discover packet loss and re-ordering
- Time stamping : allowing synchronization (ie:between audio and corresponding video, 2 different channels)
- Payload type identification : allowing use of different coding schemes
- Source identification : a source may be identified independently of its IP address
RTCP - provides feedback on the quality of the transmission link
RTP and RTCP do not reduce overall delay nor guarantees quality of service.
If such guarantees are required - Intserv (RSVP), Diffserv (DS byte)
Example for Mixer: if the senders x1…xn have an higher bandwidth and the receiver a lower one, instead of adapting down the communication, a mixer can “mix” the RTP data sources into a single RTC data stream compatible with the connection speed of the receiver
È una raccomandazione pubblicata dall’ITU-T (International Telecommunications Union Telecommunications Sector). La versione 1 è stata approvata nel 1996.
H.323 è standardizzato dall’ITU-T Study Group 16
La versione 5 dell’H.323 è stata approvata nel 2003
H.323 è uno standard che specifica i componenti, i protocolli, e i meccanismi per la trasmissione di dati multimediali su reti a commutazione di pacchetto senza garanzie di qualità del servizio
Elementi di un sistema H.323:
Terminal (Communicating endpoint on network)
Gateway (VoIP to PSTN/ISDN)
Gatekeeper (Address translation, (RAS) registration, admission control and status, work balance)
MCU (Multipoint Control Unit) (Conference control and data distribution)
Border Elements
Cornerstone technology for three transmission of real-time audio, video and data communications over packet-based networks.
H.323 is a collection of protocols for media transport, for signaling and for control.
H323 protocol is used, for example, by Microsoft Netmeeting to make VoIP calls.
This protocol allow a variety of elements talking each other:
1)Terminals, clients that initialize VoIP connection. Although terminals could talk together without
anyone else, we need some additional elements for a scalable vision.
2)Gatekeepers, that essentially operate:
a. address translation service, to use names instead IP addresses
b. admission control, to allow or deny some hosts or some users
c. bandwidth management
3) Gateways, points of reference for conversion TCP/IP - PSTN.
4) Multipoint Control Units (MCUs) to provide conference.
5) Proxies Server also are used.
h323 allows not only VoIP but also video and data communications.
Concerning VoIP, h323 can carry audio codecs G.711, G.722, G.723, G.728 and G.729 while for video it supports h261 and h263.
L’MCU fornisce il supporto per conferenze di più terminali H.323
Contiene un “Multipoint Controller” (MC) che gestisce la segnalazione di chiamata e (opzionalmente) un “Multipoint Processor” (MP) che processa l’audio/video (ad esempio mixing dei media, conversione tra codec, etc)
Conferenze :
- Centralizzate ogni partecipante invia flussi informazioni multimediali e segnalazione di controllo a MCU
- Decentralizzate ogni partecipante invia infomazioni multimediali agli altri in modo multicast mentre le informazioni di controllo (H.245) vengono inviate al MC del MCU
- Ibride (hybrid): video multicast fra partecipante, audio centralizzato all’ MP del MCU e informazioni di controllo (H.245) centralizzato all’ MC del MCU
- Miste (Mixed): dove alcuni partecipanti operano in modo centralizzato ed altri in modo misto
in small networks there may be no gatekeeper (=> each terminal needs its own mapping table)
Funzionalità opzionali:
- Call control signalling. Gestione della segnalazione H.225/Q.931 tra endpoint H.323.
- Call authorization. Concede o meno l’autorizzazione ad effettuare una chiamata utilizzando opportune policy (es. stato della sottoscrizione al servizio dell’endpoint)
- Bandwidth management. Processa le richieste di banda utilizzando policy (es. condizioni della banda in quel momento)
- Call management. Processa le richieste di chiamata usando policy (es. stato dell’endpoint)
- Gatekeeper management information (MIB).
- Bandwidth reservation. Riserva la banda per quei terminali che non sono in grado di farlo.
- Directory services.
Collezione di dispositivi H.323 gestiti da un unico gatekeeper.
Una chiamata tra due endpoint appartenti alla stessa zona passa da un unico gatekeeper.
Una chiamata tra due endpoint di due zone differenti coinvolge più gatekeeper.
There may be more than one physical Gatekeeper device that provides the logical Gatekeeper functionality for a zone
Single Administrative Domain
Collezione di zone che sono sotto un unico dominio amministrativo (es. Service Provider)
Border Element
Interfaccia di un Administrative Domain verso il Mondo esterno
H.225.0: Call signalling protocols and media stream packetization for packet-based multimedia (includes Q.931 and RAS)
H.450.x Supplementary services for multimedia:
1. Generic functional protocol for the support of supplementary services in H.323
2. Call transfer
3. Diversion
4. Hold
5. Park & pickup
6. Call waiting
7. Message waiting indication
H.235 Security and encryption for H-series multimedia terminals
RRQ: Registration Request / RCF: Registration Confirmation / RRJ: Registration Reject
L’utente indica al gatekeeper il proprio alias H323ID o indirizzo E.164, altrimenti il gatekeeper gli assegna automaticamente un alias e glielo comunica nel messaggio RCF
La registrazione è valida per un tempo pari a TimeToLive
La deregistrazione può essere iniziata dal gatekeeper o dall’utente
URQ: Unregister Request / UCF: Unregister Confirmation / URJ: Unregister Reject
Se il Gatekeeper non ha registrato l’utente richiesto inizia la procedura di localizzazione trasmettendo messaggio LRQ. Il messaggio LRQ può essere trasmesso in multicast o unicast (verso gatekeeper di riferimento). Il Gatekeeper che gestisce la zone con il Gateway, si occupa della traslazione di indirizzi da E.164 a IP.
LRQ: Location Request / LCF: Location Confirmation / LRJ: Locationn Reject
Nel messaggio Admission Request (ARQ), la terminazione descrive in ogni sua componente la chiamata che ha intenzione di effettuare e per la quale sta richiedendo l’accesso al servizio di comunicazione.
– Capacità trasmissiva richiesta (questo è ovviamente un limite superiore che il Gatekeeper potrà non rispettare),
– Identificativi della terminazione sorgente, di quella destinataria e della chiamata in generale (alcuni di questi indicativi, CRV, Call ID e Conference ID).
Nel messaggio ACF, il Gatekeeper inserirà l’indirizzo del canale logico da utilizzare per trasmettere i messaggi di segnalazione di chiamata
ARQ: Admission Request / ACF: Admission Confirmation / ARJ: Admission Reject
BRQ:Bandwidth ReQuest / BCF: Bandwidth ConFirm / BRJ: Bandwidth ReJect
DRQ: Disengage ReQuest / DCF: Disengage ConFirm