The following features were added to IMG release 10.3.2:
The following features are in the baseline Controlled Introduction release.
The GCEMS file name convention has changed to include the version number:
IMG_10.x.x.xx.bin (example: IMG_103.2.30.bin)
The IMG User Interface (ClientView, EventView) file name convention has changed to include the version number:
IMGUserInterface_10.x.x.xx.bin (example: IMGUserInterface_10.3.2.20.bin)
The scripts to start and stop the GCEMS have been renamed as follows:
StartIMG now named StartGCEMS
StopIMG now named StopGCEMS
This feature allows you to search text/data within a configuration based on different criteria. Search can be performed in forward or backward direction. You can search on partial strings (ex. a search on "IM" will find "IMG"). Wildcards are not supported.
See ClientView Search Capabilities.
The flexibility and usability of the ClientView data import process has been improved. The Import Manager gives you the ability to define the behavior at certain critical decision points during import: specifically, when duplicate objects or error conditions are encountered.
At the start of the import process, the Import Manager will present choices for how duplicate objects and error conditions are to be handled. The Import Manager will then process the imported file based on these selections.
See Importing Data.
The IMG supports the following for SNMP:
Ability to monitor Ethernet, DS1 and DS3 interfaces using industry standards MIBs
Get and Trap commands (SETs are not be supported)
Support for industry standard MIBs among common Network Management tools.
The Multi Router Traffic Grapher (MRTG) is a tool to monitor the traffic load on network links. MRTG generates HTML pages containing PNG images which provide a Live visual representation of this traffic.
See An Overview of MRTG.
Symmetric NAT Traversal
The IMG now supports Symmetric NAT Traversal for H.323, as well as for SIP.
H323 uses the Symmetric NAT Traversal information internally. No Symmetric NAT Traversal information is shared with other gateways or endpoints.
Forward Call Indicators contain information relating to the characteristics of the connection, signaling path and called party sent in the forward direction. This is a mandatory parameter in IAM messages, which is used in countries that offer CUG (closed user group) service. Using the FCI Override pane, you can configure the IMG to send or ignore various indicators.
See Configuring FCI Override and the FCI Override pane reference.
You can send a Continuity Check request on a CIC or a group of CICs. See the Circuit Group pane.
You can send a Circuit Query Message (CQM) on a CIC or a group of CICs. The CIC status will update accordingly if there has been any change. See the Circuit Group pane.
The options for the Discard Privacy Info field in the ISUP Group and ISDN Group panes have been changed. The option selected is removed from the outgoing message.
Off (default)
Display Only
Generic Number Only
Display and Generic Number
Calling Party Only
Display and Calling Number
Calling, Display and Generic
See Discard Privacy Info above.
IP Traffic Management, also called Call Admission Control, gives you the ability to limit the number of calls going to or coming from a particular gateway.
See the IP Traffic Management pane.
This feature enables the IMG to play a treatment to an originating number before outbound routing takes place, based on destination number or time of day. An example use would be to inform someone making a long distance call from a hotel room of the service provider. This feature uses the Service Route table, in addition to standard routing tables.
After the pre-call announcement, the call proceeds as normal to the outbound side. If this feature is used, translation table re-run is not performed.
This feature allows the configuration of the Input and Output Gain on a per Channel Group basis for TDM and RTP channels. Transformations are allowed from -21 dB to +18 dB in 3 dB increments. When 0 dB is selected the transformation option is disabled
Clipping - In the case of TDM to TDM calls, the combined Receive and Transmit Gain will be clipped at +18 dB. For example, if channel group A had the Receive gain set to +12 dB and channel group B had its Transmit gain set to +10 dB, and the call was flowing from A to B, one would expect +22 dB of gain. However, the IMG will implement clipping, so the gain on this call would be +18 dB. It will work the same in the reverse direction as well.
Gain Control is not supported for pre-call announcements, treatments, or ringback.
See the Channel Group pane reference.
The Dialogic VSAs now use standard text descriptors and have unique VSA numbers so that they can be easily parsed using software. See Cantata RADIUS VSAs.
The following VSAs have been added:
trans-cause-code (VSA # 53) - Translated Cause Code when translate cause table is used.
Call-ID (VSA #141) - Value of the Call-ID header.
prev-hop-via (VSA # 144) - “Sent-by” portion of topmost via when the request arrived at the proxy.
prev-hop-ip (VSA # 145) - Previous hop IP address, as seen by the proxy. What would normally be placed in the “received” parameter when the proxy detected that the sender does not agree with the top-most via
incoming-req-uri (VSA #146) - For inbound Radius mess. both Start & Stop. Access to the value after the RFS on the inbound side)
outgoing-req-uri (VSA # 147) - For outbound Radius mess.Both Start & Stop Access to the value after outseize of the Invite.
next-hop-ip (VSA #: 148) - Next-hop IP address where the request is forwarded.
next-hop-dn (VSA # 149) - The Domain Name (DN) or Fully Qualified Domain Name (FQDN) where the request is forwarded.
sip-resp-code (VSA #150) - Sip Cause Code before translation to the Q931 value
sip-attempt-info (VSA # 151) - In case IMG tries the contacts returned with 3xx, IMG will log to the CDR each attempt.
See Cantata RADIUS VSAs.
The IMG provides automatic alarming notification to IMG users when a Radius Server has changed states and can no longer be accessed. The alarm will include the RADIUS Server Type (Access, Accounting), the Server ID, the mode of the Radius Server (normal, debug), the state of the Radius Server and the IP address.
You can configure your RADIUS Client in Debug Mode so that calls will be completed whether the RADIUS server is active or not. The IMG will not require authentication for the RADIUS server to complete a call and no billing information will be logged if the RADIUS server goes down.
You enable RADIUS Debug Mode using the RADIUS Client screen.
The Fax Fallback feature is a backup mechanism to transmit a fax using Fax Bypass mode when T.38 cannot be negotiated successfully. This feature allows you to configure T.38 Fax Relay as the preferred type, and also allow Bypass Fax when T.38 is not supported by the remote end. The added negotiation will therefore reduce the call setup failure rate by increasing the content of the media offer.
In the event where the fallback scenario fails, the IMG is to allow the voice call to proceed, as if no negotiation had happened.
See IP Bearer Profile.
The following features have been added to the baseline Controlled Introduction release with Engineering Release 1.
This feature was modified in ER2. See above for current implementation.
The following features have been added to the baseline Controlled Introduction release with Engineering Release 2.
The G.729E/G codec is a low-bit rate codec that can support greater voice quality than standard G.729, using improved compression algorithms.
G.729E/G is available in VoIP Resource Profiles 6 and 7. See Vocoder Information for details.
You assign vocoders in the Vocoder Entry pane
This feature allows you to define the base RTP port value on a per module basis. The port for both VoIP modules can be set to any value in the range 8000-62462 in multiples of 2.
To modify the RTP port range in an existing configuration file, you must delete the VoIP module object under the Facility object and then re-create the object and change the port number.
This feature makes it easier for users with fire walls to insert the IMG into your network, because the RTP port ranges can be configured to fit your guidelines as to what port ranges are left open and what are closed.
You configure the RTP Port Number in the VoIP Module pane.
As of 10.3.2 ER2, the word Cantata appears at the beginning of all Cantata VSA names. See Cantata RADIUS VSAs.
The IMG now accepts and acts upon data received in RADIUS Authentication Response messages that the Radius Server may send pertaining to prepaid application. This will allow the IMG1010 to be used in a prepaid application environment.
You enable this feature in the RADIUS Client pane.
Note: Radius Prepaid Support Mode will be disabled if Radius Debug Mode is enabled. The two modes cannot be enabled at the same time.
The IMG sends the following VSAs to the RADIUS Server:
Cantata-call-type =
Cantata-voip-dst-sig-ip-in =
Cantata-trunk-grp-in =
and receives the following attributes in return:
Number of seconds for which the call is authorized.
Call Tracing: Will log the termination [Normal Call Clearing (16)] as a result of the max duration of the call being exceeded.
VSA: h323-credit-time (VSA # 102)
Phone number to which the call is redirected; for example, to a toll-free number or a customer service.
Call Tracing: Will log the use of the new Dialed Number, which overrides the Dialed number received in the incoming call.
VSA: h323-redirect-number (VSA # 106)
This feature allows the IMG to route ported numbers for SIP and SS7.
See Local Number Portability (LNP) for details.
You enable or disable LNP Routing in the ISUP Group pane.
This feature allows you to route based on the originating IMG as well as the Dialed Number.
You can route a call from the same dialed number to different channel groups, depending on the IMG it comes in on.
You enable this feature by selecting an IMG in the Match IMG as Well field in the Route Entry pane.
This feature allows you to distribute SIP traffic between IMGs configured as “SIP Servers” using virtual IP Addresses and a SIP load balancer.
See the following topics for more information:
Configuring SIP Based Load Balancing
Network Interface
The Reason Header field for the Session Initiation Protocol (SIP) is included in BYE, CANCEL, 4XXs, 5XXs, and 6XXs messages to indicate why a SIP request or response was issued. Clients and servers are free to ignore this header field as it has no impact on protocol processing.
This feature is useful for debugging purpose, particularly if there is a call failure in SIP to SS7 traffic.
See SIP Reason Header.
In the SIP protocol a “+” sign is used to indicate an international number. This feature allows you to append or strip digits based upon the presence or absence of the “+”, as well as how the Nature of Address is set.
Note: A “+” sign can only be the first digit in a number string.
See Translation Entry pane.
This feature allows you control the sending of UCIC. By default, UCIC is sent for National calls, and is suppressed for International calls, based on the Network Indicator setting of the SS7 Stack. You can change these setting if required.
See the Suppress UCIC field in the SS7 Stack pane.
The media attribute "Annexb=no" can be sent by the IMG in the SIP SDP when enforcing the use of the G.729a payload type.
The annexb setting is available for G.729 and G.729E payloads.
Note that the media attribute "Annexb=yes" is not sent by the IMG in a SIP SDP, as this value is implied when unspecified in the SDP.
This feature is configured using the Vocoder Entry pane.
This feature allows you to set the local time zone on a per IMG basis. All IMG functions that use time will use the local time.
The local time is also used in the Radius attributes that use time:
setup time
connect time
disconnect time
See Setting Local Time for more information.
Topic Location: Product Description > Summary of Previous Releases
The following SIP features were added to IMG release 10.3.2:
A SIP Profile allows you to easily assign unique features sets to a Physical IMG, or a common set of features to multiple IMGs. You create a SIP Profile and then assign profiles to a gateway in the External Gateway pane. You can also assign a SIP Profile to a SIP Signaling object, which will indicate to another IMG should treat a call going to or coming from the IMG.
See SIP Profiles for more information.
This feature allows the IMG to respond to the 3XX class of SIP messages returned from a redirect server.
See SIP Redirect Server Support.
The IMG supports the INVITE Diversion Header (Diversion and CC-Diversion) to support PSTN Redirecting Services (also known as Call Forwarding). The INVITE Diversion header carries information about the redirection. The Diversion header prevents this pertinent SS7 redirection information from being lost in the SS7 to SIP conversion. When SS7 redirection information is received on the incoming side, it is relayed in the Diversion header on the outgoing SIP side
You enable this feature in the SIP Profile.
See SIP Diversion Header.
The feature allows you to re-originate a call on another gateway to limit the amount of unnecessary bandwidth utilization on your network. By default, if the IMG does not receive a 100 Trying response to an INVITE, it will re-send the INVITE up to 5 times.
By using less re-origination attempts, less SIP messages go out to the network, which in effect reduces the bandwidth used.
Another benefit is the savings in time that the physical resources are allocated for a call that will never complete. By reducing the re-origination attempts, the call attempt will be torn-down sooner and the physical resources associated with the call will be released sooner.
See SIP Re-origination.
This feature allows the IMG to interact with SIP Proxy Servers and Session Border Controllers as intermediate routes between domains. The IMG can route SIP traffic to these SIP entities (SIP proxies) and with the knowledge of their final destination (remote SIP UA).
See SIP Proxy Handling.
Use these features if you have a Centralized Routing Model and do not require the IMG to perform routing decisions. These features are enabled or disabled in the SIP Profile, which can be assigned on a SIP Gateway or SIP Signaling basis.
This feature allows the use of the INFO method to send a DTMF digit to another gateway.
This feature allows you to select multiple non-standard tags to include in the From header. You configure this feature in the SIP Profile pane.