by Olivier | Mar 2, 2010 | CUCM, H.323, Non classé, SIP, Written Theory |
A MTP can bridge tohether two full-duplex voice stram and if necessary convert between G711 ulaw and alaw as well as different sample sizes. So as the MTP bridge is handling each stream independently, H.323 supplementary services can be supported. In other words, MTP will enhance H.323v1 with all these supplementary services(Call Park, Hold , Transfer , Conferencing,…).
Pay attention also that you can use MTP in order to provide the translation between the out-of-band DTMF tones used by SCCP and SIP in-band (payload type) DTMF tones.
by Olivier | Mar 2, 2010 | CUCM, H.323, IOS, Non classé, Written Theory |
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.
by Olivier | Mar 2, 2010 | CUCM, Lab, Non classé, SIP, Written Theory |
Since Call Manager 4.X, SIP Trunks can be used for connectivity with SIP Networks and devices via a SIP Proxy Servers.
A SIP Proxy can handle SIP Request , Authentication and Authorization of users and will implement policies and features
by Olivier | Mar 2, 2010 | H.323, IOS, Lab, Non classé, Written Theory |
Here is a basic definition for the gatekeeper config:
!
gatekeeper
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
no shutdown
!
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.
by Olivier | Feb 25, 2010 | H.323, IOS, Lab, Non classé, Written Theory |
Endpoints which are using multicast discovery will use the multicast adress 224.0.1.41 for GRQ
by Olivier | Feb 25, 2010 | H.323, IOS, Lab, Non classé, Written Theory |
In H.323 , you can play with the caller id (not the case with MGCP , see previous post).
By default,Caller ID is disabled on all FXS ports.
So in order to enable it , you must go under the voice-port and activate it as it is shown in the below config
!
voice-port 2/0
caller-id enable
!
Recent Comments