Here are the different messages used by the H225 RAS signaling which can occur between endpoints and GK.
- Gatekeeper Discovery : used by endpoints to register
- GRQ : Gatekeeper Request
- GCF : Gatekeeper Confirm
- GRJ: Gatekeeper Reject
- Registration/Unregistration : used by endpoints to register or unregister their address and their zone withtin the GK.
- RRQ : Registration Request
- RCF : Registration Confirm
- RRJ : Registration Reject
- URQ : Unregistration Request
- UCF : Unregistration Confirm
- URJ : Unregistration Reject
- Admission Control : These messages are used for all admission control and bandwidth management
- ARQ : Admission Request
- ACF : Admission Confirm
- ARJ : Admission Reject
- Bandwidth Control : these messages are used if you want to change the amount of bandwidth during a call
- BRQ : Bandwidth Request
- BCF : Bandwidth Confirm
- BRJ : Bandwidth Reject
- Endpoint Location : These messages are used to retrieve contact information ( also with Directory GK)
- LRQ : Location Request
- LCF : Location Confirm
- LRJ : Location Reject
- Status Information : They are used to retrieve a status information
- IRQ : Information Request
- IRR : Information Response Request
H225 call control signaling is on TCP/1720 and uses Q931 messages to establish, maintain and tear down calls. these messages are
- Setup Acknowledge
- Call Proceeding
- Progress Alerting
- User Information
- Release Complete
- Status Inquiry
So in general , here is the following reminder: While h225 call control signaling can be used for call setup, H245 must be used to determine a master/slave relationship, exchange terminal capabilities, logical channel signaling and DTMF relay.
We have already spoken about Gatekeeper signaling in this previous post but let’ be more general and see what are the common elements of H.323 stack.
We have H225 RAS ( Registration Admission and Status) which is used between the GK and H323 endpoints.
But under normal operation , we have also H225 which is the call control and signaling part of the H323 stack. So we use it to establish connections.
We have also H245 which is the negotiation part of the H323 stack. So it is during this stage that you can exchange capabilities/codecs, establish logical channels. It is in fact all settings for the transmission of the media.
- H225 RAS => UDP/1719
- GK Discovery => UDP/1718
The Multicast GK discovery uses IP Address 22.214.171.124
Here are some MGCP messages that you can see in the interaction between the Call Agent and the endpoint:
- EndpointConfiguration (EPCF) : A Call Agent sends this message to a gateway to specify signal encoding that will be received by an endpoint . A good example of these message will be the audio encoding using ulaw or alaw.
- CreateConnection (CRCX) : This command creates a connection between 2 endpoints. the connection is created based on parameters included with the commad such as codec , allowable bandwidth, use of echo cancellation, silence suppression , gain control, and so on.
- ModifyConnection (MDCX) : This is used to modify the parameters associated with a connection that was previously created.
- DeleteConnection (DLCX) : The Call Agent can send this command to inform a gateway that it should terminate a connection, and a gateway can send this command to indicate that a connection can no longer be sutained. In response to a DeleteConnection, an endpoint sends statistics associated with the connection.
- NotificationRequest (RQNT) : This is sent by the Call Agent to instruct a gateway to informit when specific events occur in an endpoint. Example : be on-hook/off-hook, tones,..
- Notify (NTFY) : An endpoint uses this command to inform a Call Agent when requested events occur
- AuditEndpoint (AUEP) : The Call Agent sends the AuditEndpoint command to the gateway to audit the status of an endpoint. The Call Agent can, for example, find out signal status, bearer information, …
- AuditConnection (AUCX) : The Call Agent sends this command to the gateway to find out the status of a connection. Connection status information that can be retrieved using this command includes Call ID, Connection Mode, and connection parameters
- RestartInProgress (RSIP) : The gateway sends this command to the Call Agent to inform the Call Agent that it is taking an endpoint or group of endpoints out of service or is returning an endpoint or group of endpoints to service.
Digit Manipulation is the process of modifying the called or calling party number. It can be configured in a number of different ways:
- Route Pattern
- Route Group Level
- Translation Pattern
- Translation Rules in VGW
The specific types of manipulatios are :
- Calling Party’s Extenal Phone Mask
- Calling Party Transform Mask
- Prefix Digits
- Discard Digits Instructions(DDI)
- Called Party Transform Mask
Although Digit Manipulation canbe done within a Route Group, it is applied when the the Route Groups are added to the Route List.
Recall also as seen in a previous post, that when digit manipulations are configured at both the Route Pattern and Route Group level, the manipulation configured at the Route Group level has priority over that configured at the Route Pattern level because it is processed later.
Translation patterns can be used also to manipulate the calling or called party numbers prior to call routing. It can be also used to modify elements such as CSS.
Here is a basic definition for the gatekeeper config:
zone local oks ksiazek.be 10.0.0.1 1719
zone prefix oks 1234*
gw-type-prefix 1#* default-technology
bandwidth total zone oks 1024
bandwidth session zone oks 128
The zone local defines the Gatekeeper’s name , the domain to which it belongs and its IP Address and the TCP port used.
The zone prefix specifies the Gatekeeper’s name and the prefix associated within the zone list.
The gw-type-prefix will help to route calls if the called number doesn’t correspond to an E.164 number.
The bandwidth total zone defines the maximum aggregate bandwidth that you can use within this specific zone.
The bandwidth session zone defines the maximum bandwidth available for a session in the zone ( so this is the bandwidth for a call)
No shut activates the Gatekeeper’ configuration.
Another QoS mechanism that is useful for slower link speeds is LFI which will fragment larger payload to specified fragment sizes and then interleave the smaller payloads in among the fragments, reducing then the serialization delay.
There are three primary LFI mechanisms supported by Cisco are as follows:
- Multitlink PPP (MLP) : used on PPP links
- FRF.12 : used on Voice over IP over Frame-Relay (VoIPovFR) links
- FRF.11 Annex C : used on voice ov Frame-Relay (VoFR) links
In MLP mode , then you define the maximum serialisation delay that you wnat on your link and under FRF.12, you define the maximum size of the fragment that you want on your link.