docHere - Dialogic
download 
Report Transcription
Here - Dialogic
IMG 1010 - Integrated Media Gateway Release 10.3.3 ER 2 Printer-Friendly Documentation This version of the IMG 1010 documentation is formatted specifically for printing. Cantata’s primary format for documentation is web-based help and is available from the Cantata support site: www.cantata.com Important Notice Disclaimer The contents of this document are subject to change without notice; therefore, the information presented herein shall not be construed as a commitment or warranty. Cantata Technology shall not be liable for any technical or editorial errors or omissions contained herein or for incidental or consequential damages resulting from the performance, furnishing, reliance on, or use of this material. Patents Certain equipment and software described in this document is protected by issued and pending U.S. and foreign patents. All products and services are trademarks or registered trademarks of their respective manufacturer. Copyright This document contains confidential and proprietary information protected by copyright. All rights reserved. Copying or other reproduction of all or parts of this document is prohibited without the permission of Cantata. Copyright 2007 by Cantata Technology Table Of Contents An Overview of New Features in 10.3.3...............................................................1 An Overview of New Features in 10.3.3 ER 1 ..................................................... 14 An Overview of New Features in 10.3.3 ER 2 ..................................................... 15 Introduction .................................................................................................. 18 Cantata Technology Product Warranty .............................................................. 18 About Cantata ............................................................................................... 21 Introduction to the IMG................................................................................... 23 Example IMG Network .................................................................................... 25 IMG Specifications.......................................................................................... 26 An Overview of New Features in 10.3.3............................................................. 28 Upgrading to IMG System Software 10.3.3 ........................................................ 41 Product Description ........................................................................................ 47 An Overview of Features in Previous Releases.................................................... 47 An Overview of Features in 10.1 (Initial Release) ............................................... 48 An Overview of Features in 10.3 ...................................................................... 51 An Overview of Features in 10.3.1.................................................................... 54 An Overview of Features in 10.3.2.................................................................... 58 An Overview of New SIP Features in 10.3.2 CI ................................................... 67 An Overview of VoIP on the IMG ...................................................................... 69 VoIP Features ................................................................................................ 71 Supported Codecs .......................................................................................... 73 Vocoder Information ....................................................................................... 77 Symmetric NAT Traversal ................................................................................ 79 Transcoding................................................................................................... 81 An Overview of H.323 on the IMG .................................................................... 83 Supported H.323 Messages ............................................................................. 85 Codec Negotiation .......................................................................................... 87 H.323 Fax/Modem .......................................................................................... 89 H.245 Tunneling ............................................................................................ 90 H.323 Keep Alive Timer .................................................................................. 92 H.323 Fast Start ............................................................................................ 93 An Overview of SIP......................................................................................... 95 SIP Features.................................................................................................. 96 SIP Profiles.................................................................................................... 99 iii IMG WebHelp Authentication and Outbound Registration....................................................... 101 Inbound SIP Codec Selection ......................................................................... 102 Supported 3xx Redirect Responses ................................................................. 103 SIP INVITE .................................................................................................. 104 UPDATE Method ........................................................................................... 106 INFO Method ............................................................................................... 109 SUBSCRIBE/NOTIFY Methods......................................................................... 110 SIP PRACK .................................................................................................. 112 SIP PRACK Call Flows.................................................................................... 114 SIP Diversion Header .................................................................................... 118 SIP Reason Header....................................................................................... 120 SIP Privacy .................................................................................................. 125 SIP Redirect Server Support .......................................................................... 127 Example Call Flow: SIP Redirect ..................................................................... 129 SIP Proxy Handling....................................................................................... 130 EXAMPLE SIP Call: Using an Outbound Proxy ................................................... 131 SIP Fax/Modem Support ............................................................................... 132 SIP CODEC Negotiation Priority Selection ........................................................ 133 Early Media ................................................................................................. 134 SIP ENUM.................................................................................................... 135 SIP-Based Load Balancing/Virtual IP Address ................................................... 137 SIP Trunk Group Selection............................................................................. 139 SIP 3PCC (Third Party Call Control) ................................................................ 140 SIP 3PCC Call Flows...................................................................................... 142 SIP Call Hold ............................................................................................... 147 SIP Busy Out ............................................................................................... 151 SIP Session Timer ........................................................................................ 153 SIP Session Timer Call Flows ......................................................................... 155 Pass through ‘+’ sign in the user part of URI.................................................... 159 Fully Qualified Domain Name Support ............................................................. 160 Multiple SIP 183 prior to 200 OK .................................................................... 166 SIP INFO Method for DTMF ............................................................................ 169 SIP SUBSCRIBE/NOTIFY Method for DTMF ....................................................... 173 SS7 Features ............................................................................................... 180 Pre/Post 95 Support for GRS/GRA .................................................................. 182 An Overview of ISDN on the IMG ................................................................... 183 iv Table Of Contents ISDN Features ............................................................................................. 184 Basic CAS Call Flows..................................................................................... 186 E1 CAS Timers ............................................................................................. 188 T1 CAS Filters and Timers ............................................................................. 191 An Overview of Routing on the IMG ................................................................ 199 Routing Components .................................................................................... 201 Incoming Translation Process......................................................................... 203 Digit matching ............................................................................................. 204 Digit Translation........................................................................................... 206 Digit Translation Examples ............................................................................ 208 ClientView Panes used for Service Routing ...................................................... 210 Services Routing: Pre-Call Announcements...................................................... 211 An Overview of Error Handling ....................................................................... 214 Local Number Portability (LNP) ...................................................................... 215 An Overview of RADIUS on the IMG................................................................ 217 RADIUS Scenarios ........................................................................................ 220 Generic RADIUS Attributes ............................................................................ 221 Cantata VSAs............................................................................................... 228 RADIUS Call Flow: SS7 to SIP........................................................................ 235 RADIUS Call Flow: SS7 to H.323 - Release from SS7 ........................................ 236 RADIUS Call Flow: SS7 to H.323 - Release from SS7 ........................................ 237 RADIUS CDR Example: SS7 to H.323.............................................................. 238 RADIUS CDR Example: SIP-to-ISDN ............................................................... 242 RADIUS CDR Example: SIP to SS7 ................................................................. 246 RADIUS CDR Example - SIP to SIP with Proxy and DNS .................................... 250 RADIUS CDR Example: CAS to SS7 ................................................................ 255 RADIUS CDR Example: SS7 to CAS ................................................................ 258 RADIUS for Pre-Paid Applications ................................................................... 261 RADIUS Call Trace Example: Pre-Paid Support ................................................. 263 RADIUS Call Trace Example: Routing with Pre-paid Application .......................... 269 Incomplete Call Behavior .............................................................................. 270 An Overview of SNMP on the IMG................................................................... 271 Supported MIBs ........................................................................................... 273 Supported SNMP Traps ................................................................................. 276 SNMP Basics ................................................................................................ 277 Basic SNMP Implementation .......................................................................... 279 v IMG WebHelp What are MIBs ? .......................................................................................... 281 An Overview of Interworking ......................................................................... 282 Interworking Features................................................................................... 283 SS7 ISUP to ISDN Interworking ..................................................................... 284 Call Flows: SS7 ISUP to ISDN ........................................................................ 285 SIP to SS7 ISUP Interworking: Calling Party Category ...................................... 287 Support for SPIROU/ITX in SIP INFO .............................................................. 290 ANSI ISUP Originating Line Info Support ......................................................... 292 SIP Carrier Identification Code (CIC) .............................................................. 295 SIP-T .......................................................................................................... 299 Default SIP-to-SS7 ISUP Cause Codes ............................................................ 300 Customizing SIP-to-SS7 ISUP Cause Codes ..................................................... 304 H.225 Release Reason to Q.931 Cause Code Mapping ....................................... 305 Quick Start Guide......................................................................................... 307 IMG Quick Start Guide Overview .................................................................... 307 Connecting Ethernet and TDM Cables.............................................................. 308 Connecting Power to the IMG......................................................................... 310 Installation and Setup Guide.......................................................................... 312 An Overview of Installation and Setup ............................................................ 312 Items Required for Installation....................................................................... 313 Sample Network Scenario ............................................................................. 315 Licensing..................................................................................................... 316 IMG Hardware Installation Task Summary ....................................................... 319 Site Preparation ........................................................................................... 320 Unpacking the IMG ....................................................................................... 323 Rack Mounting the IMG ................................................................................. 324 Surface Mounting the IMG ............................................................................. 327 Connecting AC Power.................................................................................... 328 Connecting DC Power to Ground .................................................................... 330 Connecting DC Power ................................................................................... 331 Connecting to a Single Power Source .............................................................. 332 The DC power module plugs are polarity sensitive. The unit will not operate if the plugs are not wired correctly. See wiring diagram below. ............................. 332 Connecting to Redundant Power Sources......................................................... 334 Connecting Ethernet and TDM Cables.............................................................. 336 Timing ........................................................................................................ 338 vi Table Of Contents Cabling for Redundancy ................................................................................ 339 Redundant Control ....................................................................................... 340 Redundant Data ........................................................................................... 341 Redundant Signaling..................................................................................... 342 Redundant SS7 Signaling .............................................................................. 343 Software Installation Overview ...................................................................... 344 Summary of Software Installation and Setup Tasks .......................................... 346 Installing Linux on the GateControl EMS Server ............................................... 347 Recommended Linux Configuration and OS Settings ......................................... 350 Selecting/De-selecting Linux Services ............................................................. 353 Configuring the Linux User ............................................................................ 354 Configuring the Linux User - Detailed Procedure............................................... 355 Installing Cantata GateControl EMS Software................................................... 357 Folders and Files Created During Installation ................................................... 359 GCEMS Installation Script.............................................................................. 362 Installing ClientView for Windows ................................................................... 365 GateControl EMS Redundancy ........................................................................ 366 Overview..................................................................................................... 368 Setting up GateControl EMS .......................................................................... 369 Downloading IMG System Software ................................................................ 374 Starting GateControl EMS.............................................................................. 376 Assigning ClientView Users ............................................................................ 378 Starting ClientView....................................................................................... 380 Configuring Remote Desktop (Strongly Recommended) .................................... 382 Changing or Deleting Cantata GateControl EMS and User Interface..................... 384 Sample dhcpd.conf File ................................................................................. 385 Setting Host Flags ........................................................................................ 387 Downloading IMG System Software Using Boot File on an SD Card ..................... 389 Downloading IMG System Software From an SD Card ....................................... 391 Distributing IMG System Software Using an SD Card ........................................ 392 Default bootup.cfg Configuration File .............................................................. 393 Setting Up Servers in Linux ........................................................................... 395 Setting Up an SNTP Server ............................................................................ 395 Sample ntp.conf File ..................................................................................... 398 Configuration............................................................................................... 401 Starting ClientView....................................................................................... 401 vii IMG WebHelp An Overview of ClientView............................................................................. 403 Using ClientView .......................................................................................... 406 The ClientView Main Window ......................................................................... 409 ClientView Menus ......................................................................................... 410 ClientView Menu buttons ............................................................................... 413 ClientView Indicators .................................................................................... 414 Configuring ClientView Properties ................................................................... 418 ClientView Search Capabilities ....................................................................... 419 Assigning ClientView Users ............................................................................ 421 Changing the Order of Objects in ClientView Tree............................................. 423 Upgrading ClientView.................................................................................... 424 Configuration Summary ................................................................................ 427 Validating Your Configuration......................................................................... 428 ClientView Objects Tree (with maximums)....................................................... 430 Sample Validation Report .............................................................................. 431 An Overview of Basic Configuration ................................................................ 433 Auto-create ClientView Configuration Tree....................................................... 434 Creating a Logical IMG .................................................................................. 435 Adding a Physical IMG .................................................................................. 436 Configuring a Synchronization Priority List....................................................... 437 About Synchronization Priority Lists ................................................................ 438 Setting Local Time........................................................................................ 439 Configuring Media ........................................................................................ 440 Importing Data ............................................................................................ 443 Configuring Network Interfaces ...................................................................... 445 Network Interface Scenarios .......................................................................... 447 Scenario 1 - One Subnet ............................................................................... 448 Scenario 2 - Two Subnets: Control/Signaling and Data ..................................... 451 Scenario 3 - Two Subnets B: Data/Signaling and Control .................................. 454 Scenario 4 - Three Subnets ........................................................................... 457 Configuring IP Interface Mode........................................................................ 460 Creating a Facility Object .............................................................................. 461 Using the Facility Wizard ............................................................................... 462 Facility Wizard ............................................................................................. 463 Configuring a T1 or E1 Bearer Span ................................................................ 464 Configuring a Range of TDM Bearer Spans....................................................... 465 viii Table Of Contents Configuring a Signaling Span ......................................................................... 466 Configuring a Range of Signaling Spans .......................................................... 467 DS3 Overview.............................................................................................. 468 Configuring a DS3 ........................................................................................ 469 Configuring a Range of DS3s ......................................................................... 470 DS3 Diagnostics........................................................................................... 471 An Overview of IP Configuration..................................................................... 473 ClientView Panes used for VoIP Configuration .................................................. 474 Configuring VoIP .......................................................................................... 475 Configuring a Second VoIP Module ................................................................. 477 Configuring IP Bearer Profiles ........................................................................ 479 Changing the Order of Codecs in an IP Bearer Profile ........................................ 481 Configuring External Network Elements........................................................... 482 Adding an External H.323 Gatekeeper............................................................. 483 Adding an External Gateway .......................................................................... 485 Configuring an NFS Server ............................................................................ 486 Configuring Signaling.................................................................................... 487 An Overview of SIP Configuration................................................................... 488 Configuring SIP Signaling .............................................................................. 490 Configuring SIP-Based Load Balancing ............................................................ 492 Configuring SIP-T ......................................................................................... 494 Configuring SIP Privacy................................................................................. 496 An Overview of H.323 Configuration ............................................................... 498 Configuring H.323 Signaling .......................................................................... 499 An Overview of SS7 Configuration .................................................................. 501 Configuring SS7 Signaling ............................................................................. 503 Configuring SS7 Signaling Routes................................................................... 506 Configuring SS7 Redundancy ......................................................................... 508 Configuring SS7 Redundancy with Remote Control of CICs ................................ 510 Configuring Multiple IMGs for SS7 .................................................................. 513 Configuring Control of Remote CICs................................................................ 515 Provisioning SS7 CICs................................................................................... 517 Configuring Custom SS7 Variants ................................................................... 518 An Overview of ISDN Configuration ................................................................ 520 Configuring ISDN Signaling ........................................................................... 522 CAS Quick Configuration Guide ...................................................................... 524 ix IMG WebHelp Configuring CAS........................................................................................... 525 Importing a CAS Variant ............................................................................... 527 Deleting a CAS Variant.................................................................................. 528 CAS E1 R2 DN-ANI-CAT ................................................................................ 530 E1 R2 DN-ANI-CAT Overlap ........................................................................... 534 T1 FGD ....................................................................................................... 536 T1 FGB ....................................................................................................... 538 An Overview of Routing Configuration............................................................. 541 Configuring Routing...................................................................................... 542 ClientView Panes Used for Routing ................................................................. 544 ClientView Panes used to Configure Routing Tables and Route Lists .................... 545 Creating a Channel Group ............................................................................. 546 Overlap Signaling ......................................................................................... 547 Configuring Routing Table ............................................................................. 549 Configuring Route Lists ................................................................................. 553 Configuring Time of Day Routing .................................................................... 555 Importing Route Table Entries ....................................................................... 557 Route String Wildcards.................................................................................. 564 ClientView Panes Used for Translation............................................................. 565 Configuring Digit Matching and Translation ...................................................... 566 Advanced Translation Features ...................................................................... 569 Translation Configuration Example ................................................................. 571 Configuring Advanced Number Matching Parameters for Incoming Calls .............. 573 Digit Translation Wildcards ............................................................................ 575 Translation Errors......................................................................................... 577 ClientView Panes for Configuring Error Handling............................................... 578 Configuring Error Handling ............................................................................ 579 Configuring a Channel Group to Play a Treatment ............................................ 581 Configuring a Channel to Release With Cause .................................................. 583 Adding Custom Announcements ..................................................................... 585 Adding Custom Treatments ........................................................................... 587 Configuring Pre-call Announcements............................................................... 590 Customizing SIP-to-SS7 ISUP Cause Codes ..................................................... 591 Default Cause Code Values ............................................................................ 592 Default Treatment Table ............................................................................... 596 Configuring SIP Routing ................................................................................ 597 x Table Of Contents Configuring an External SIP Gateway.............................................................. 599 SIP Call Flows .............................................................................................. 600 Configuring H.323 Routing ............................................................................ 604 Configuring an External H.323 Gateway .......................................................... 605 Adding an External H.323 Gatekeeper............................................................. 606 Configuring SS7 CICs ................................................................................... 608 Configuring ISDN Routing ............................................................................. 612 NFAS Examples............................................................................................ 614 ISDN Call Flows ........................................................................................... 616 Configuring RADIUS ..................................................................................... 618 Configuring Free RADIUS using GCEMS as a RADIUS Server .............................. 622 Configuring SNMP ........................................................................................ 625 Provisioning the IMG..................................................................................... 627 An Overview of Provisioning the IMG .............................................................. 627 Bringing Spans into (or out of) Service ........................................................... 630 Clearing the Configuration ............................................................................. 631 Monitoring the IMG....................................................................................... 632 Monitoring the IMG....................................................................................... 632 An Overview of MRTG ................................................................................... 634 Installing MRTG ........................................................................................... 637 Setting Up an MRTG Web Host ....................................................................... 640 Sample MRTG Main Page............................................................................... 643 Monitoring the IMG Using ClientView .............................................................. 645 Viewing IMG Status and Information............................................................... 648 Viewing Channel Group Call Statistics ............................................................. 649 Viewing Licensing Information ....................................................................... 650 An Overview of EventView............................................................................. 651 Filtering Alarm Views .................................................................................... 654 Exporting Alarms to a Text File ...................................................................... 656 Forcing a Log File to Roll-over........................................................................ 657 Restarting a Socket Connection...................................................................... 658 Troubleshooting ........................................................................................... 672 An Overview of Troubleshooting ..................................................................... 672 Recommendations for Supportability............................................................... 674 Log Files ..................................................................................................... 676 Call Statistics............................................................................................... 678 xi IMG WebHelp Troubleshooting: SS7 Signaling Links ............................................................. 680 An Overview of Call Tracing ........................................................................... 682 Setting Up Call Tracing ................................................................................. 684 Starting a Call Trace ..................................................................................... 686 Call Trace Example: Successful Call ................................................................ 687 Call Trace Example: No Match found in the translation table .............................. 691 Call Trace Example: No Match Found in Route Table ......................................... 692 Payload Types in Call Trace ........................................................................... 694 Sample Call Trace - Fax Fallback .................................................................... 696 Sample Call Trace - Codecs ........................................................................... 700 Call Trace Example - SIP to SS7..................................................................... 705 Administration ............................................................................................. 714 Downloading a License.................................................................................. 714 Downloading a Raw File to the IMG ................................................................ 715 Resetting an IMG ......................................................................................... 717 An Overview of AdminView ............................................................................ 718 Administering User Privileges......................................................................... 721 Admin Commands ........................................................................................ 724 Assigning ClientView Users ............................................................................ 726 Viewing User Information .............................................................................. 728 Starting AdminManager on an Alternate RMI port ............................................. 731 Software Reference ...................................................................................... 732 Hardware Maintenance.................................................................................. 733 Installing a VoIP or Media Module................................................................... 733 Replacing a Motherboard Tray........................................................................ 736 Replacing a Fuse .......................................................................................... 738 Troubleshooting Hardware............................................................................. 739 Hardware Reference ..................................................................................... 742 Hardware Reference Overview ....................................................................... 742 Physical Description...................................................................................... 743 Hardware Specifications ................................................................................ 744 I/O Cable Specifications ................................................................................ 746 RJ-48 Connector Pinouts ............................................................................... 748 Hardware Alarm Module ................................................................................ 750 Rear Panel Description .................................................................................. 752 Determining VoIP Module Type ...................................................................... 755 xii Table Of Contents Dell Server Configuration Details.................................................................... 756 Front Panel Overview.................................................................................... 758 Front Panel LEDs .......................................................................................... 759 LCD Display................................................................................................. 762 LCD Menus .................................................................................................. 764 System Info Menu ........................................................................................ 765 Physical Span Info Menu ............................................................................... 767 Timing Info Menu ......................................................................................... 769 IP Info Menu................................................................................................ 770 Hardware Info Menu ..................................................................................... 772 AC Power Specifications ................................................................................ 774 DC Power Information................................................................................... 775 Power and Fan Control .................................................................................. 776 Compliance Overview ................................................................................... 777 FCC Regulatory Compliance Notices................................................................ 778 EMI Statement............................................................................................. 781 ClientView Pane Reference ............................................................................ 782 Advanced Billing Number Translation .............................................................. 782 Advanced Carrier Number Translation ............................................................. 784 Advanced Dialed Number Parameters ............................................................. 785 Advanced Originating Number Parameters....................................................... 787 Alternate Gatekeepers .................................................................................. 790 BCI Override................................................................................................ 791 Bearer Capabilities Override .......................................................................... 794 BERT .......................................................................................................... 796 Call Tracing ................................................................................................. 799 Cantata IMG EMS ......................................................................................... 801 CAS Circuits ................................................................................................ 803 Cause Code Tables ....................................................................................... 806 Channel Associated Signaling......................................................................... 807 Channel Group............................................................................................. 808 Channel Group (Route List Entry) ................................................................... 814 Channel Groups ........................................................................................... 815 Circuit Group ............................................................................................... 816 Configuration............................................................................................... 820 Digit Mapping .............................................................................................. 821 xiii IMG WebHelp DNS Client .................................................................................................. 825 DNS Server ................................................................................................. 827 DNS Servers................................................................................................ 828 DS3 Physical Span........................................................................................ 829 E1 Physical Span .......................................................................................... 831 ENUM Server ............................................................................................... 836 ENUM Server Set ......................................................................................... 837 External Gatekeeper ..................................................................................... 839 External Gatekeepers ................................................................................... 841 External Gateway ......................................................................................... 842 External Gateways ....................................................................................... 846 External Network Elements............................................................................ 847 Facility........................................................................................................ 848 Facility Wizard ............................................................................................. 849 FCI Override ................................................................................................ 851 Filter/Timer Configure................................................................................... 854 H323 Signaling Pane..................................................................................... 857 H323 Timers Pane ........................................................................................ 861 Incoming Translation Tables Pane .................................................................. 863 Inpulsing Parameters.................................................................................... 864 Inseize Instruction ....................................................................................... 868 IP Bearer Profile Pane ................................................................................... 871 IP Bearer Traffic Profiles Pane ........................................................................ 877 IP Network Element Pane .............................................................................. 878 IP Traffic Management Entry.......................................................................... 879 ISDN Circuits Pane ....................................................................................... 881 ISDN D Channel Pane ................................................................................... 883 ISDN Group Pane ......................................................................................... 887 ISDN Signaling Pane..................................................................................... 889 ISDN Timers ................................................................................................ 890 ISUP Group ................................................................................................. 891 License Information ...................................................................................... 903 Location Override ......................................................................................... 905 Logical IMG ................................................................................................. 907 Media ......................................................................................................... 909 Media DSP................................................................................................... 911 xiv Table Of Contents Media Module .............................................................................................. 914 Network Interface ........................................................................................ 915 Network Interfaces ....................................................................................... 918 NFS Server.................................................................................................. 919 NFS Servers ................................................................................................ 921 SIP Options KeepAlive .................................................................................. 922 Outgoing Translation Tables .......................................................................... 924 Outseize Instruction ..................................................................................... 925 Physical IMG................................................................................................ 928 Physical Port Configuration ............................................................................ 931 Radius Client ............................................................................................... 932 Radius Server .............................................................................................. 935 Radius Servers............................................................................................. 938 Raw API Command....................................................................................... 939 Raw API Commands ..................................................................................... 940 Route List.................................................................................................... 941 Route Lists .................................................................................................. 943 Route Table ................................................................................................. 944 Routing Configuration ................................................................................... 946 Routing Tables ............................................................................................. 947 Signaling..................................................................................................... 948 Signaling Variants ........................................................................................ 949 Signaling Variant.......................................................................................... 950 SIP DTMF Support ........................................................................................ 954 SIP From Header Tags .................................................................................. 956 SIP Headers ................................................................................................ 958 SIP Network Element .................................................................................... 960 SIP Options KeepAlive .................................................................................. 962 SIP Profile ................................................................................................... 964 SIP Profile Timers......................................................................................... 970 SIP Proxy .................................................................................................... 971 SIP Session Timer ........................................................................................ 973 SIP Signaling ............................................................................................... 975 SIP T Entity ................................................................................................. 978 SIP Timers .................................................................................................. 979 SIP Virtual Address....................................................................................... 981 xv IMG WebHelp SNMP Agent ................................................................................................ 983 SNMP Manager............................................................................................. 985 SNMP Managers ........................................................................................... 989 SS7 Signaling .............................................................................................. 990 SS7 Link ..................................................................................................... 992 SS7 Link Set................................................................................................ 995 SS7 Parameter Filter .................................................................................... 997 SS7 Route ................................................................................................... 999 SS7 Stack ................................................................................................. 1001 T1 Physical Span ........................................................................................ 1006 TDM DS1................................................................................................... 1009 TDM DS3................................................................................................... 1010 Telnet Client .............................................................................................. 1012 Time of Day Entry ...................................................................................... 1013 Time of Day Table ...................................................................................... 1015 Time of Day Tables..................................................................................... 1017 Time Zone Setting...................................................................................... 1018 Timing Synchronization Priority List .............................................................. 1019 TMR-USI Override ...................................................................................... 1020 TOS Configuration ...................................................................................... 1022 Translation Entry........................................................................................ 1024 Translation Table........................................................................................ 1034 Treatment Entry......................................................................................... 1036 Treatment Phrase....................................................................................... 1037 Treatment Table ........................................................................................ 1039 Treatment Tables ....................................................................................... 1040 Variant Entry ............................................................................................. 1041 Vocabulary Index Entry............................................................................... 1044 Vocabulary Index File ................................................................................. 1046 Vocabulary Index Files ................................................................................ 1047 Vocoder Entry ............................................................................................ 1048 VoIP Module .............................................................................................. 1051 xvi An Overview of New Features in 10.3.3 Topic Location: Product Description > Summary of Previous Releases Channel Associated Signaling (CAS) SIP Interworking H.323 SS7 VoIP Routing SNMP RADIUS General Channel Associated Signaling (CAS) Channel Associated Signaling (CAS) is in-band signaling usually implemented as robbed-bit signaling. CAS is supported for both T1 and E1 (including DS3) on the IMG. Related Topics CAS Quick Configuration Guide Interworking ITU Q.699 Brief Description The IMG supports interworking between ISDN and SS7. For Interworking between ITU ISUP and ISDN IMG follows Q.699 recommendation. For Interworking between ANSI ISUP and ISDN IMG follows T1.609 recommendation Benefits Provides cost effective TDM to SS7 ISUP switch. Limitations Fallback procedures are not supported in IMG, hence any interworking related to that is also not supported. 1 IMG WebHelp Supplementary services are not supported in the IMG Related Topics Interworking Call Flows - ISDN to SS7 ISUP. SS7 ITU to SIP Interworking: Calling Party Category (CPC) (10.3.3 ER1) The CPC is a parameter that characterizes the station used to originate a call and carries other important state that can describe the originating party. This feature allows for the sending of the SS7 ITU Calling Party Category (CPC) in the From Header of SIP messages. Only SS7 to SIP is supported. There are two options to place the CPC parameter in the From header field user part parameter of the From URI Configuration SIP From Header Tags Related Topics SS7 ITU to SIP Interworking: Calling Party Category SIP SIP UPDATE Overview The UPDATE method allows a UAC to update parameters of a session, such as the SDP and session timers. The UPDATE method allows a greater control over a SIP session including, but not limited to, the following parameters: SDP (for example, to set the media on hold during early media) Session timers (for example, to adjust call duration in a prepaid application) RFC 3311 SIP UPDATE Method Benefits Allows you to update parameters during a session when conditions change. Configuration The SIP UPDATE method is to be accepted by the IMG without user intervention, and therefore cannot be disabled. There is no configuration involved. 2 An Overview of New Features in 10.3.3 Related Topics SIP UPDATE SIP Session Timer RFC RFC 4028 Session Timers in the Session Initiation Protocol Benefits Provides a "keep alive" method for SIP Calls which allows you to better manage your resources in an abnormal situation such as network outage. The RFC 3261 does not define a keep alive mechanism for the sessions it establishes. The result is that an UA will not always be able to determine whether a session is still active. For instance, when a remote party fails to send a BYE message at the end of a session, or when the BYE message gets lost due to network problems, the UA will not know that session has ended, thus will not release resource allocated for the session. To resolve this problem, the IMG supports the keep alive mechanism for SIP sessions defined in RFC 4028 Session Timers in the Session Initiation Protocol (SIP). Configuration SIP Session Timer You configure the Session Timer in the SIP Session Timer pane. SIP Session Timer is enabled by default. More Information SIP Session Timer SIP Busy Out Brief Description Set timers to determine if gateway is responsive or unresponsive. RFC RFC 3261 SIP: Session Initiation Protocol, Section 11. Overview The IMG can monitor the status of external SIP gateways by sending periodic SIP OPTIONS messages. If the gateway does not respond in a configured amount of time the IMG will mark the gateway as down and attempt to re-route the call to a different gateway. Benefit Allows you to monitor the status of external SIP gateways. 3 IMG WebHelp Configuration SIP Profile External Gateway Related Topic SIP Busy Out SIP SUBSCRIBE/NOTIFY Brief Description The IMG accepts user agent subscription requests (SIP SUBSCRIBE method) and the ability to respond to those user agents with the appropriate DTMF digit events via the SIP NOTIFY method. Only DTMF-events are currently supported. RFC 3265 Session Initiation Protocol (SIP)-Specific Event Notification Benefits Detect DTMF tones (##) in the middle of a call. You can develop user-specific applications that reside on your network entity and have the ability to subscribe for event services supported by the IMG. If the network entity wants the ability to detect an entered DTMF digit from the TDM-side of a call to the IP side of a call, the entity can subscribe to the IMG for these events and receive SIP NOTIFY events containing the digit event. Configuration SIP DTMF Support Related Topic SIP SUBSCRIBE/NOTIFY Method for DTMF SIP PRACK Brief Description Improves network reliability and supports additional call flows. RFCs 3262 - Reliability of Provisional Responses in the Session Initiation Protocol (SIP) Overview There are two types of responses defined by SIP that are provisional and final. Final responses convey the result of the request processing and are sent reliably. There are certain scenarios in which the provisional SIP responses must be delivered reliably. For example, in a SIP/PSTN inter-working scenario, a loss of 180 or 183 4 An Overview of New Features in 10.3.3 messages cannot be afforded. To solve this problem, the SIP PRACK method guarantees reliable and ordered delivery of provisional responses in SIP. In addition, SIP PRACK provides further opportunities for SDP offer/answer exchange mode because of its 3-way handshake design. Configuration SIP Profile SIP Carrier Identification Code Brief Description Send Carrier Id Code (CIC) between SIP and SS7. Benefits Gives you the ability to send mixed traffic over a trunk group and improve call routing. Overview This feature enables the IMG to receive and transmit the Carrier Identification Code (CIC) parameter between the SIP network and SS7. The CIC parameter is a three- or four- digit code used in routing tables to identify the network that serves the remote user when a call is routed over many different networks. The CIC parameter is carried in SIP INVITE requests and maps to the SS7 Request. Related Topic SIP Carrier Identification Code ISUP-OLI (ANSI Only) The ISUP OLI (also know as II digits) parameter includes information that is used for carriers to determine the origin of a call. This information gets lost over SIP networks if not inter-worked properly. This feature allows carrying ANSI ISUP OLI Parameter from traditional TDM network into SIP and vice versa. This information is passed in the From: header of the INVITE message. Related Topic SIP ISUP OLI ENUM RFC RFC 3764 enumservice registration for Session Initiation Protocol (SIP) Addresses-ofRecord Brief Description Translates phone numbers to SIP addresses. 5 IMG WebHelp Benefits Bypass PSTN for lower phone charges and faster connections. Overview The IMG supports ENUM E2U+sip to resolve an ENUM telephone number into a SIP URI. ENUM facilitates the interconnection of systems that rely on telephone numbers with those that use URIs to route transactions. E.164 is the ITU-T standard international numbering plan, under which all globally-reachable telephone numbers are organized. Configuration ENUM Servers ENUM Server Related Topic SIP ENUM SIP-Based Load Balancing Brief Description This feature allows you to distribute SIP traffic between IMGs configured as “SIP Servers” using virtual IP Addresses and a SIP load balancer. Benefits Improved scalability and fault tolerance. Related Topics SIP-Based Load Balancing SIP CODEC Negotiation Priority This feature allows you to configure whether the IMG or the remote gateway takes priority when selecting a codec. Benefits The feature gives you the flexibility to choose CODEC priority on either IMG or the far end gateway. Configuration SIP Profile You configure CODEC Negotiation Priority to either Local or Remote in the SIP Profile pane. 6 An Overview of New Features in 10.3.3 SIP REGISTER “Expires” Timer Control This feature gives you the ability to control the expiration of a registration request sent from the IMG to a Remote SIP User Agent. The default is 3600 sec. RFC RFC 3261 SIP: Session Initiation Protocol Configuration External Gateway You can change the default to a value between 10 and 7200 sec using the Registration Expiration Interval field in the External Gateway pane. SIP 305 Redirect Response Brief Description The IMG now supports the 305 Use Proxy message. Benefits Enables re-direct to Proxy Server. Related Topics SIP 3XX Redirect Responses SIP Call Hold Brief Description This feature allows the IMG to process a re-INVITE from a SIP endpoint that places a call on hold or releases a hold. This addition complements the current support for SIP Hold (via 0.0.0.0 ip address) by supporting RFC 3398 section 9, allowing for the proper Interworking of hold information between SIP and SS7. RFC RFC 3398 Integrated Services Digital Network (ISDN) User Part (ISUP) to Session Initiation Protocol (SIP) Mapping (section 9) Related Topic SIP Call Hold SS7 ITU to SIP Interworking: Calling Party Category (CPC) (10.3.3 ER1) ITX Message (SPIROU) Support 7 IMG WebHelp H.323 Keep Alive Timer Brief Description Set Time to Live parameter in Registration Request (RRQ) Benefits Greater user control when using H.323 gatekeepers Overview This feature gives you the ability to control the Time to Live value in the RRQ from the IMG when registering with a gatekeeper. This is an optional parameter in the RRQ. If no Time to Live is present in the RRQ, the gatekeeper returns a value in the RCF which the IMG has no control over. By inserting the Time to Live value in the RRQ, the user has control over it as the gatekeeper normally returns the value requested by the endpoint in the RRQ. If the gatekeeper returns a different value, that will be the value used by the IMG in subsequent lightweight RRQs to maintain registration. Configuration External Gatekeeper SS7 Pre/Post 95 Support for GRS/GRA Description This feature provides the capability to support both pre and post 1995 GRS (Group Reset)/GRA (Group Reset ACK) messages on a per CIC group basis (ANSI Only). Benefits Enables different CIC groups in an SS7 stack to connect to different types of DPCs. Configuration ISUP Group Related Topic Pre/Post 95 Support for GRS/GRA. JT-ISUP The IMG supports JT-ISUP, the SS7 standard for Japan (JT-Q.763). See JT-ISUP for more information. SS7 ITU to SIP Interworking: Calling Party Category (CPC) (10.3.3 ER1) 8 An Overview of New Features in 10.3.3 VoIP G.729 E/G Description 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. Benefit Better voice quality than G.729A. Configuration Vocoder Entry Related Topic Vocoder Information G.723 Maximum Packet Size Description The maximum packet size for the G.723 codec has been increased to 90. Benefits Handle larger payloads for reduced bandwidth markets. Related Topic Vocoder Information Modifiable RTP Base Port Number Overview 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. Benefits 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. 9 IMG WebHelp Configuration VoIP Module G.729 AnnexB Selection Overview 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. Configuration Vocoder Entry Routing Modify Cause Code for Re-Routing Purposes Description The IMG will automatically attempt to re-route calls in response to the following cause codes: 42,41,34. Use this field to select up to 4 additional Cause Codes for which the IMG will re-attempt a new call, per trunk group. Benefits This feature gives you more flexibility as to how to use the IMG 1010 under particular network conditions and configurations. Configuration Channel Group Use the Re-attempt Cause Code field to select up to 4 cause code values. Call Tracing New call tracing will be added to indicate that a re-attempt has occurred for the selected Cause Codes. Local Number Portability (LNP) Description Allows the IMG to route ported numbers for SIP and SS7. Benefit Properly handle ported numbers. 10 An Overview of New Features in 10.3.3 Configuration ISUP Group Related Topic Local Number Portability (LNP) Routing on Originating IMG Description This feature allows you to route based on the originating IMG as well as the Dialed Number. Benefits You can route a call from the same dialed number to different channel groups, depending on the IMG it comes in on. Configuration You enable this feature by selecting an IMG in the Match IMG as Well field in the Route Entry pane. Importing Route Tables using NFS Benefits More efficient method for loading large route tables. SNMP Support for the following MIBs has been added to the IMG SNMP offering. DSO MIB This feature will introduce support for the DS0-MIB as described in RFC 2494 ALARM-MIB RFC 3877 Support for the alarm MIB offers three major benefits: 1. The ability to inspect the alarm tables and find out what is currently wrong with the system. 2. The ability to model alarms in a generic way. 3. The ability to send out generic traps when alarms are raised. Traps 11 IMG WebHelp alarmActiveState - This trap is sent out when an alarm is raised. It contains the model number of the alarm as well as a resource ID which identifies specifically what the alarm refers to (for instance for a link down alarm you would indicate which link it is). alarmClearState - This gets sent out when an alarm is cleared. It contains the same information as the other trap. IF_MIB IMG now supports the new Interfaces MIB specified in RFC 2863 Support for this MIB provides several benefits: A view of control, signalling, and data ports Measurements of the flow of traffic including number of packets in and out Descriptive information about these ports Recording of errors such as numbers of packets dropped. Managers used to query the switch should update their list of compiled MIBs to include RFC 2863. Limitations The IMG does not allow an NMS to write to the IMG and will not support parts of the RFC which call for writes. RADIUS RADIUS VSA Names The word Cantata now appears at the beginning of all Cantata VSA names. See Cantata RADIUS VSAs. Example: Cantata-trunk-grp-out RADIUS for Pre-Paid Applications 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. Routing with RADIUS Pre-paid The IMG now accepts the Cantata-trunk-grp-out VSA in General 12 An Overview of New Features in 10.3.3 GCEMS There is no longer a Development Mode for the GCEMS. When you start GCEMS it is automatically started in Production Mode. Related Topic Starting GateControl EMS Setting Local Time 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 disconnect time connect time See Setting Local Time for more information. ClientView WebHelp Updates You can retrieve WebHelp updates from the Cantata Support site that will replace the WebHelp version launched from ClientView. Cantata Technology - IMG 1010 Printable WebHelp 13 An Overview of New Features in 10.3.3 ER 1 Topic Location: Product Description > Summary of Previous Releases SS7 to SIP Interworking: Calling Party Category (CPC) This feature allows for the sending of the SS7 Calling Party Category (CPC) in the From Header of SIP messages. Only SS7 to SIP is supported. The CPC is a parameter that characterizes the station used to originate a call and carries other important state that can describe the originating party. Configuration SIP From Header Tags pane NOTE: SIP OLI is also configured in the SIP From Header Tags pane (was previously configured in the SIP Profile pane). See SS7 ITU to SIP Interworking: Calling Party Category. SIP 3PCC (Third Party Call Control) The IMG supports the establishment of a session by a third party "controller" such as an application server or a Session Border Controller (SBC), allowing the IMG to integrate with services like auto attendant, conferencing, and unified messaging. See SIP 3PCC (Third Party Call Control). INFO for SPIROU/ITX The IMG supports the sending of the SS7 ITX message based on a SIP INFO message received from a SIP Application. This allows a SIP application to interwork with the SPIROU standard (Signalisation Pour l'Interconnexion des Réseaux Ouverts/Signaling for the Interconnection of Open Networks). This SS7 message is used for audio services that are paid by either a flat rate calculation or a time-based calculation. The calls are routed to the operator, and the operator reports the payment amount with the ITX message. See INFO for Spirou/ITX. RADIUS - Routing Using Pre-paid Application The IMG supports the routing of calls to a channel group indicated by a RADIUS server. If Pre-paid Support is enabled and the IMG receives VSA 45: Cantata-trunkgrp-out from the RADIUS server, the IMG will skip the mid-stream routing process and route the call to the channel group indicated by the RADIUS server. See Routing Using Pre-paid Application. Cantata Technology - IMG 1010 Printable WebHelp 14 An Overview of New Features in 10.3.3 ER 2 Fully Qualified Domain Name Support Benefit This feature allows you to manage IMG IP addresses via DNS for greater flexibility and security than hard-coded alternatives in SDP and SIP. Configuration You enter Fully Qualified Domain Names in the Fully Qualified Domain Name field of the SIP Signaling, SIP Virtual Address, and VoIP Module panes. You configure outgoing FQDN options in the Outgoing Fully Qualified Domain Name field of the SIP Profile. RADIUS The radius dictionary file has been updated to support this feature. Customers using RADIUS should update the dictionary.cantata file they are using with the latest one located in the GCEMS install under ‘/opt/cantata/common/radius‘ On a freeRADIUS server this file should be copied into ‘/usr/share/freeradius’ directory. The latest version of dictionary.cantata is v1.3: # dictionary.Cantata # # IMG release 10.3.3 ER2+ # Version. $id: dictionary.cantata,v1.3 2007/06/29 $ Related Topic Fully Qualified Domain Names Support Support for multiple SIP 183 prior to 200 OK The IMG supports receiving multiple SIP 183s prior to 200 OK for SIP hop forks where an INVITE request and SIP responses can potentially be received from multiple remote user agents. A proxy or an Application server that receives an INVITE from the IMG can then fork the request to multiple destinations. Benefits Multiple 183 responses are used in Follow-me services, and request forking scenarios. Applications that can benefit from the IMG handling multiple 18x responses are: Application Servers Proxy Servers See Multiple SIP 183s prior to 200 OK. 15 IMG WebHelp Translation of Null String This features allows you to translate a Null originating number only. This allows you, for example, to append a prefix to the originating number if the originating number is empty. Configuration Translation Entry ISDN Ability to assign Net5 Q.931 variant on T1 ISDN D-channels This feature allows you to configure Net5 Q.931 variant on a T1 ISDN DChannel. This is required, for example, when connecting to carriers in South America where a far end using E1 is terminated in the US on T1s. Enhanced variant support. See the Supported Variants in the ISDN Features topic for a complete list of supported variants. Configuration ISDN D Channel pane: Base Variant field Support for 3 SNMP Managers The IMG now supports up to 3 SNMP Managers. Configuration SNMP Manager Re-INVITE if switching into Modem Bypass Mode With this feature the IMG will indicate to the far-end using a re-INVITE when the IMG detects modem traffic and switches the RTP into Modem Bypass mode over G.711. The IMG will use the bypass codec type specified in the associated bearer profile (ulaw or a-law). Incoming Re-INVITEs during modem calls are accepted automatically. Configuration This feature is disabled by default. You enable it with the Outbound Modem Triggers Re-INVITE field in the SIP Profile. SIP INFO DTMF Digit Relay With this feature the IMG supports out-of-band tone passage of a single DTMF digit (0- 9, *, #, a, b, c, d) using the SIP INFO method. 16 An Overview of New Features in 10.3.3 ER 2 Configuring the Feature You enable this feature by selecting INFO DTMF digit relay in the Method field of the SIP DTMF Support pane. See INFO DTMF Digit Relay for more information. Cantata Technology - IMG 1010 Printable WebHelp 17 Introduction Cantata Technology Product Warranty Topic Location: Introduction Unless otherwise stated in an applicable product purchase agreement between the Customer and Cantata Technology, Inc. (“Cantata”), Cantata warrants that during the Warranty Period, products will operate in substantial conformance with Cantata’s standard published documentation accompanying the product. If a product does not operate in accordance therewith during the Warranty Period, the Customer must promptly notify Cantata. Cantata, at its option, will either repair or replace the product without charge. The Customer has the right, as their exclusive remedy, to return the product for a refund of purchase price or license fee if Cantata is unable to repair or replace it. Warranty Period: The period for which the warranty shall apply (the “Warranty Period”) with respect to Cantata’s products or software shall be: 12 months for new hardware purchases 90 days for hardware repairs for products for which the original Warranty Period has expired; and 90 days for software defects 30 day “out-of-box” failure expedited replacement for inoperative new hardware The Warranty Period begins on the date of shipment of any products or software by Cantata. The Warranty Period for repaired, replaced or corrected products and software shall be coterminous to the Warranty Provided for the original products or software purchased. To report warranty claims, Customer may contact Cantata via email at [email protected] or call (781) 433-6900. Warranty Provisions: A. During the Warranty Period, Cantata warrants to Customer only that (i) Products manufactured by Cantata (including those manufactured for Cantata by an original equipment manufacturer) will be free from defects in material and workmanship and will substantially conform to specifications for such products; (ii) software developed by Cantata will be free from defects which materially affect performance in accordance with the specifications for such software. With respect to products or software or partial assembly of products furnished by Cantata but not manufactured by Cantata, Cantata hereby assigns to Customer, to the extent permitted, the warranties given to Cantata by its vendors of such items. B. If, under normal and proper use, a defect or non conformity appears in warranted products or software during the applicable Warranty Period and Customer promptly notifies Cantata in writing during the applicable warranty period of such defect or non conformance, and follows Cantata’s instructions regarding return of such defective or non conforming Product or Software, then Cantata will, at no charge to Customer, either (i) repair, replace or correct the same at its manufacturing or repair 18 Introduction facility or (ii) if Cantata determines that it is unable or impractical to repair, replace or correct the product or software, provide a refund or credit not to exceed the original purchase price or license fee. C. No product or software will be accepted for repair or replacement without the written authorization of and in accordance with instructions from Cantata. Removal and reinstallation expenses as well as transportation expenses associated with returning such product or software to Cantata shall be borne by Customer. Cantata shall pay the costs of transportation of the repaired or replaced product or software to the destination designated in the original Order. If Cantata determines that any returned product or software is not defective, Customer shall pay Cantata's costs of handling, inspecting, testing and transportation. In repairing or replacing any product, part of product, or software medium under this warranty, Cantata may use new, remanufactured, reconditioned, refurbished or functionally equivalent products, parts or software media. Replaced products or parts shall become Cantata's property. D. Cantata makes no warranty with respect to defective conditions or non conformities resulting from any of the following: Customer's modifications, misuse, neglect, accident or abuse; improper wiring, repairing, splicing, alteration, installation, storage or maintenance performed in a manner not in accordance with Cantata's or its vendor's specifications, or operating instructions; failure of Customer to apply Cantata’s previously applicable modifications or corrections; or items not manufactured by Cantata or purchased by Cantata pursuant to its procurement specifications. Cantata makes no warranty with respect to products which have had their serial numbers removed or altered; with respect to expendable items, including, without limitation, fuses, light bulbs, motor brushes and the like; or with respect to defects related to Customer's data base errors. Improper packaging of product for repair will not be covered under this warranty agreement. No warranty is made that software will run uninterrupted or error free. E. Warranty does not include: a) Cantata’s assistance in diagnostic efforts; b) access to Cantata’s Technical Support web sites, databases or tools; c) product integration testing; d) on-site assistance; or e) product documentation updates. These services are available either during or after warranty at Cantata’s published prices. F. THE FOREGOING WARRANTIES ARE EXCLUSIVE & ARE GRANTED IN LIEU OF ALL OTHER EXPRESS & IMPLIED WARRANTIES (WHETHER WRITTEN, ORAL, STATUTORY OR OTHERWISE), INCLUDING BUT NOT LIMITED TO ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT. CUSTOMER’S SOLE AND EXCLUSIVE REMEDY AND CANTATA SWITCHING’S SOLE OBLIGATION HEREUNDER, SHALL BE TO REPAIR, REPLACE, CREDIT OR REFUND AS SET FORTH ABOVE. G. IN NO EVENT SHALL CANTATA, ITS DIRECTORS, OFFICERS, EMPLOYEES, AGENTS OR AFFILIATES, BE LIABLE FOR ANY COSTS OR DAMAGES ARISING DIRECTLY OR INDIRECTLY FROM YOUR USE OF ANY PRODUCT INCLUDING ANY INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, MULTIPLE, PUNITIVE OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, WHETHER BASED ON CONTRACT, TORT (INCLUDING NEGLEGENCE), STRICT LIABILITY OR OTHER LEGAL THEORY, EVEN IF CANTATA, OR ANY OF ITS DIRECTORS, OFFICERS, EMPLOYEES, AGENTS OR AFFILIATES HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN ANY EVENT, CANTATA’S CUMULATIVE LIABILITY TO YOU FOR ANY AND ALL CLAIMS RELATING TO THE USE OF ANY PRODUCT SHALL NOT EXCEED THE TOTAL AMOUNT 19 IMG WebHelp OF THE PURCHASE PRICE OR LICENSE FEES PAID TO CANTATA FOR SUCH PRODUCT. H. CUSTOMER AND CANTATA HEREBY WAIVE THEIR RIGHT TO TRIAL BY JURY TO THE FULLEST EXTENT PERMITTED BY LAW IN CONNECTION WITH ALL CLAIMS ARISING OUT OF OR RELATED TO THIS WARRANTY, THE PRODUCTS COVERED HEREBY OR THE PERFORMANCE OF ANY PARTY HEREUNDER. I. THIS WARRANTY SHALL BE CONSTRUED UNDER AND GOVERNED BY THE LAWS OF THE COMMONWEALTH OF MASSACHUSETTS WITHOUT GIVING EFFECT TO ANY CHOICE OR CONFLICT OF LAW PROVISION OR RULE (WHETHER OF THE COMMONWEALTH OF MASSACHUSETTS OR ANY OTHER JURISDICTION) THAT WOULD CAUSE THE APPLICATION OF THE LAWS OF ANY JURISDICTION OTHER THAN THE COMMONWEALTH OF MASSACHUSETTS. CUSTOMER SPECIFICALLY AND IRREVOCABLY CONSENTS TO THE PERSONAL AND SUBJECT MATTER JURISDICTION AND VENUE OF THE FEDERAL AND STATE COURTS OF THE COMMONWEALTH OF MASSACHUSETTS AND SUCH COURTS SHALL HAVE EXCLUSIVE JURISDICTION WITH RESPECT TO ALL MATTERS CONCERNING THIS WARRANTY OR THE ENFORCEMENT OF ANY OF THE FOREGOING. J. THIS WARRANTY GIVES YOU SPECIFIC LEGAL RIGHTS. YOU MAY ALSO HAVE OTHER RIGHTS WHICH VARY FROM JURISDICTION TO JURISDICTION. Cantata Technology - IMG 1010 Printable WebHelp 20 Introduction About Cantata Topic Location: Introduction Cantata Technology, established in 2006 through the combination of Brooktrout Technology and Excel Switching Corporation, provides enabling communications hardware and software that empowers the creation and delivery of anytime, anywhere IP-based communications applications. Leveraging more than 20 years of experience, Cantata offers the broadest range of products, along with a worldwide network of partners that allows service provider and enterprise customers to develop new products, introduce new services and cost-effectively transition networks to IP. Headquartered in Needham, Mass., Cantata maintains multiple locations worldwide in North America, Asia and Europe. Locations Cantata Technology provides sales and support to its customers and partners around the world through several locations, including: Corporate Headquarters: 15 Crawford Street Needham, Mass. 02494 Domestic Offices: Massachusetts, New Hampshire, California, Georgia, Illinois, and North Carolina International Offices: Belgium, The Netherlands, Canada, and Japan Products Cantata’s proven, open standards-based technology has given rise to one of the largest, broadest, and deepest enabling technology product lines in the communications industry. Used extensively by enterprises and service providers alike, Cantata’s technology enables innovative services and solutions with applications ranging from voice and video, messaging, IP call centers, fax document management and compliance, prepaid, and speech-enabled services. IMG 1010: intelligent, integrated media and signaling gateway Excel CSP 2090: Carrier-grade enhanced services multi-function platform for IP/TDM Excel MSP 1010: Cost-effective, multi-functional IP/TDM platform for voice, signaling SnowShore IP Media Server: IMS media processing software resource Brooktrout TR1034, SR140 and TruFax: intelligent fax platforms supported by 40+ fax applications Brooktrout TR1000: resource for voice and speech recognition Customers 21 IMG WebHelp Cantata has products deployed at 90% of the Fortune 500 and in more than 80 countries around the world including companies such as AT&T, MCI/Verizon, Comcast, Bank of America, Deutsche Telecom, and Alcoa. Partners Cantata has developed a global ‘ecosystem’ of partners whose knowledge and experience is unrivalled. Working as one, we’re able to help accelerate your speedto-market, reduce your risks, and ensure that you deploy your solutions with the utmost confidence. We partner with many leading service provider and enterprise application vendors including, Captaris, LogicaGMC, Openwave, Sylantro and Volt Delta, system integrators like Belnet and TekVizion, and leading speech software vendors, including Microsoft, Intervoice, Nuance Communications, Inc., and VoiceGenie. Cantata Technology has strategic partnerships with leading technology companies to ensure interoperability and performance at the system level as well. We work with leading platform vendors such as IBM, Microsoft, Sun, Red Hat, and Intel to ensure that we support the operating systems and form factors that meet the needs of our customers. Standards Cantata takes active role in industry standards not only to follow the development of new standards, but also to influence them in ways that will help our partners deliver innovative products and services. Cantata’s employees have contributed to more than 25 IETF RFCs and internet drafts, as well as 13 other standards in the ITU, W3C, IPCC and Packetcable groups. Cantata actively participates in standards organizations such as the SIP Forum, IMS Forum, SALT Forum, TIA, TMIA, VoiceXML Forum, W3C, and ECTA. Distribution Cantata markets its products through a global network of distributors, value added resellers (VARs), independent software vendors (ISVs), systems integrators (SIs), original equipment manufacturers (OEMs) and PC server manufacturers. Cantata Technology - IMG 1010 Printable WebHelp 22 Introduction Introduction to the IMG Topic Location: Introduction The IMG 1010 is a unique carrier-grade VoIP gateway solution that offers customer’s significant capital and operational savings while simultaneously speeding time to market. The IMG is unique in its ability to serve as an SS7 signaling server and media gateway with media processing capability all in one. With up to 768 channels in a 1U footprint that can be racked and stacked plus software licensing for costeffective in-service growth, the IMG 1010 is the solution for a wide variety service providers’ media gateway needs. Service providers can use the IMG 1010 to quickly and cost-effectively add new VoIP capacity while enabling long term migration to an all-VoIP environment. Service providers can rapidly provision and maintain a network of IMG 1010s using the GateControl EMS, a centralized management application with a user-friendly GUI for provisioning, monitoring and maintenance. Routing and translations on the IMG 1010 are significantly more robust than what many Service providers are used to finding in a VoIP gateway. The IMG 1010 comes with Cantata's patented Programmable Protocol Language for rapidly developing PSTN and IP network signaling variants. This unique capability allows IMG 1010 customers to implement advanced and proprietary SIP interoperability features on their own. Where Flexibility Meets Performance Cantata’s Integrated Media Gateway (IMG) 1010 is a powerful, efficient, carriergrade VoIP media gateway that performs two-way protocol conversion between circuit-switched networks like the Public Switched Telephone Network (PSTN) and packet-switched networks like the Internet. This VoIP media gateway provides service providers and enterprises with unparalleled price performance, reliability, and flexibility. The Integrated Media Gateway reduces the cost and complexity of implementing new services by combining PSTN and packet signaling, SS7 continuity tests, and media (tones and announcements) in a cost-effective, easy-to-manage, compact (1u) shelf. Flexibility and Interoperability You can use the Integrated Media Gateway as a VoIP Gateway, VoIP Transcoder, or back-to-back SIP User Agent. The IMG 1010 ensures interoperability with a wide range of VoIP networks by simultaneously supporting Primary Rate Interface (PRI) and SS7, plus the packet network protocols SIP and H.323. You can implement protocol changes yourself quickly and efficiently, using Cantata's patented Programmable Protocol Language (PPL). The Integrated Media Gateway supports advanced media capabilities without impacting VoIP channel processing. The IMG has undergone successful inter-operability testing with a wide spectrum of both VoIP and PSTN gateways. Reduced Capital Expenses, Faster Time to Market This VoIP media gateway lowers initial cost because it supports full interoperability between ISDN, SS7, SIP, and H.323 across multiple gateways. So you can roll out 23 IMG WebHelp new enhanced telecommunication offerings without buying, integrating, or managing third party softswitches, signaling gateways, application servers, FAX servers, media servers, proxy servers, or registration servers. While the Integrated Media Gateway can be configured for cost-effective entry-level requirements, it also allows you to seamlessly scale and gracefully upgrade your networks. And by using a single platform to provide rich application services across multiple networks, you significantly reduce the time, effort, and expense required to develop and deploy new services. Reduced Operational Expenses The Integrated Media Gateway 1010 also directly lowers your ongoing expenses. With signaling and media supported in a single platform, the cost and complexity of implementing new services is reduced, as are training, sparing, OAM&P, environmental, service agreement, and other costs that increase each time a new platform is deployed. And because the Integrated Media Gateway 1010 supports up to 672 channels in a 1U footprint, it can reduce rack space costs by up to 50%. Carrier-Grade Reliability "Carrier-grade" means more than having a hot-swappable fan tray. It means having 1+1 hot standby support for all active components. It means the ability to upgrade systems while they are in service. It means separating transport, signaling, and OAM&P to reduce susceptibility to intruders and to ensure better system performance. Improved Network Performance By integrating multiple network functions into the gateway, the Integrated Media Gateway 1010 improves network performance. It eliminates call hand-offs and redirection from box to box, improving call setup time and accelerating cost-effective integration of enhanced services. Investment Protection Cantata has a long history of ensuring compatibility between existing systems and new offerings, without “forklift” upgrades. Whether service providers are concerned with new network protocols, new service offerings, or powerful new chip technologies, they can be sure that the Cantata equipment they invest in today will be economically viable for many years to come. With the IMGs compact package, integrated SS7, and rich media processing capabilities, you can improve call quality while reducing your costs. New services, improved flexibility, investment protection, and higher quality, all at a lower cost and greater efficiency. Cantata's Integrated Media Gateway 1010 is the gateway platform of choice for service providers and enterprises worldwide. Cantata Technology - IMG 1010 Printable WebHelp 24 Introduction Example IMG Network Topic Location: Introduction In the example shown below, a wholesale carrier has POPs (Points of Presence) in Los Angeles, New York, and Miami. New York is the Main POP, which houses the NOC (Network Operations Center) and IMG server. The network has two separate SS7 connections, an F-link in Los Angeles to the ILEC and an A-link to Illuminet in New York, which allows them to connect to carriers out of New York and Miami with one point code. The role of the IMG Gateway Controller is to manage all of these connections and allow SS7 calls that come into Miami to be serviced over the New York signaling links. The IMG Gateway Controller will have routing information stored in all of the nodes that will allow calls to be routed between cities seamlessly. Cantata Technology - IMG 1010 Printable WebHelp 25 IMG WebHelp IMG Specifications Topic Location: Introduction The IMG supports the following: Telephony Interfaces Voice or Signaling 24 E1/32 T1 I/O DS3 + 4 T1 I/O Signaling/Timing - 4 E1/T1 ISDN PRI - NI2, Euro ISDN, 5ESS, DMS SS7 ISUP - worldwide variants CAS IP Interfaces 2 Fast Ethernet for Application Control (Gate Control EMS) 2 GIG-E for IP Bearer Traffic 2 Fast Ethernet for Network Signaling VoIP IP Signaling H.323 SIP TDM Signaling SS7 ISUP ISDN Routing Basic Routing on ANI, DNIS, Nature of Address, Channel Group, or Time of Day Pre and post routing digit translation Media Processing 26 On-board DSP resources for announcement and tones across IP and TDM Introduction Play messages to users of a particular network indicating call progress. These are currently statically mapped in the release cause code table and can not be configured Interworking The IMG supports interworking between SIP/H.323/SS7/ISDN. See An Overview of Interworking for more details on Interworking support and features. Customizable Variants Cantata can rapidly customize IP and TDM variants for you using our patented Programmable Protocol Language tool. OAM&P Centralized Element Management System. See Introduction to the Element Management System. Monitoring and provisioning up to 32 IMGs SNMP MRTG ClientView User Management You can administer user passwords and privileges with the AdminView utility. RADIUS The IMG uses Remote Authentication Dial In User Service (RADIUS) protocol for streaming the Call Detail Records (CDR). The implementation is compliant with RFC 2865 and RFC 2866. The RADIUS messages are sent to external RADIUS servers. Redundancy The IMG supports redundancy for the following: Network Management (Control) SS7 Signaling Data Cantata Technology - IMG 1010 Printable WebHelp 27 IMG WebHelp An Overview of New Features in 10.3.3 Topic Location: Product Description > Summary of Previous Releases Channel Associated Signaling (CAS) SIP Interworking H.323 SS7 VoIP Routing SNMP RADIUS General Channel Associated Signaling (CAS) Channel Associated Signaling (CAS) is in-band signaling usually implemented as robbed-bit signaling. CAS is supported for both T1 and E1 (including DS3) on the IMG. Related Topics CAS Quick Configuration Guide Interworking ITU Q.699 Brief Description The IMG supports interworking between ISDN and SS7. For Interworking between ITU ISUP and ISDN IMG follows Q.699 recommendation. For Interworking between ANSI ISUP and ISDN IMG follows T1.609 recommendation Benefits Provides cost effective TDM to SS7 ISUP switch. Limitations 28 Introduction Fallback procedures are not supported in IMG, hence any interworking related to that is also not supported. Supplementary services are not supported in the IMG Related Topics Interworking Call Flows - ISDN to SS7 ISUP. SS7 ITU to SIP Interworking: Calling Party Category (CPC) (10.3.3 ER1) The CPC is a parameter that characterizes the station used to originate a call and carries other important state that can describe the originating party. This feature allows for the sending of the SS7 ITU Calling Party Category (CPC) in the From Header of SIP messages. Only SS7 to SIP is supported. There are two options to place the CPC parameter in the From header field user part parameter of the From URI Configuration SIP From Header Tags Related Topics SS7 ITU to SIP Interworking: Calling Party Category SIP SIP UPDATE Overview The UPDATE method allows a UAC to update parameters of a session, such as the SDP and session timers. The UPDATE method allows a greater control over a SIP session including, but not limited to, the following parameters: SDP (for example, to set the media on hold during early media) Session timers (for example, to adjust call duration in a prepaid application) RFC 3311 SIP UPDATE Method Benefits Allows you to update parameters during a session when conditions change. Configuration 29 IMG WebHelp The SIP UPDATE method is to be accepted by the IMG without user intervention, and therefore cannot be disabled. There is no configuration involved. Related Topics SIP UPDATE SIP Session Timer RFC RFC 4028 Session Timers in the Session Initiation Protocol Benefits Provides a "keep alive" method for SIP Calls which allows you to better manage your resources in an abnormal situation such as network outage. The RFC 3261 does not define a keep alive mechanism for the sessions it establishes. The result is that an UA will not always be able to determine whether a session is still active. For instance, when a remote party fails to send a BYE message at the end of a session, or when the BYE message gets lost due to network problems, the UA will not know that session has ended, thus will not release resource allocated for the session. To resolve this problem, the IMG supports the keep alive mechanism for SIP sessions defined in RFC 4028 Session Timers in the Session Initiation Protocol (SIP). Configuration SIP Session Timer You configure the Session Timer in the SIP Session Timer pane. SIP Session Timer is enabled by default. More Information SIP Session Timer SIP Busy Out Brief Description Set timers to determine if gateway is responsive or unresponsive. RFC RFC 3261 SIP: Session Initiation Protocol, Section 11. Overview The IMG can monitor the status of external SIP gateways by sending periodic SIP OPTIONS messages. If the gateway does not respond in a configured amount of time the IMG will mark the gateway as down and attempt to re-route the call to a different gateway. 30 Introduction Benefit Allows you to monitor the status of external SIP gateways. Configuration SIP Profile External Gateway Related Topic SIP Busy Out SIP SUBSCRIBE/NOTIFY Brief Description The IMG accepts user agent subscription requests (SIP SUBSCRIBE method) and the ability to respond to those user agents with the appropriate DTMF digit events via the SIP NOTIFY method. Only DTMF-events are currently supported. RFC 3265 Session Initiation Protocol (SIP)-Specific Event Notification Benefits Detect DTMF tones (##) in the middle of a call. You can develop user-specific applications that reside on your network entity and have the ability to subscribe for event services supported by the IMG. If the network entity wants the ability to detect an entered DTMF digit from the TDM-side of a call to the IP side of a call, the entity can subscribe to the IMG for these events and receive SIP NOTIFY events containing the digit event. Configuration SIP DTMF Support Related Topic SIP SUBSCRIBE/NOTIFY Method for DTMF SIP PRACK Brief Description Improves network reliability and supports additional call flows. RFCs 3262 - Reliability of Provisional Responses in the Session Initiation Protocol (SIP) Overview There are two types of responses defined by SIP that are provisional and final. Final responses convey the result of the request processing and are sent reliably. 31 IMG WebHelp There are certain scenarios in which the provisional SIP responses must be delivered reliably. For example, in a SIP/PSTN inter-working scenario, a loss of 180 or 183 messages cannot be afforded. To solve this problem, the SIP PRACK method guarantees reliable and ordered delivery of provisional responses in SIP. In addition, SIP PRACK provides further opportunities for SDP offer/answer exchange mode because of its 3-way handshake design. Configuration SIP Profile SIP Carrier Identification Code Brief Description Send Carrier Id Code (CIC) between SIP and SS7. Benefits Gives you the ability to send mixed traffic over a trunk group and improve call routing. Overview This feature enables the IMG to receive and transmit the Carrier Identification Code (CIC) parameter between the SIP network and SS7. The CIC parameter is a three- or four- digit code used in routing tables to identify the network that serves the remote user when a call is routed over many different networks. The CIC parameter is carried in SIP INVITE requests and maps to the SS7 Request. Related Topic SIP Carrier Identification Code ISUP-OLI (ANSI Only) The ISUP OLI (also know as II digits) parameter includes information that is used for carriers to determine the origin of a call. This information gets lost over SIP networks if not inter-worked properly. This feature allows carrying ANSI ISUP OLI Parameter from traditional TDM network into SIP and vice versa. This information is passed in the From: header of the INVITE message. Related Topic SIP ISUP OLI ENUM RFC RFC 3764 enumservice registration for Session Initiation Protocol (SIP) Addresses-ofRecord 32 Introduction Brief Description Translates phone numbers to SIP addresses. Benefits Bypass PSTN for lower phone charges and faster connections. Overview The IMG supports ENUM E2U+sip to resolve an ENUM telephone number into a SIP URI. ENUM facilitates the interconnection of systems that rely on telephone numbers with those that use URIs to route transactions. E.164 is the ITU-T standard international numbering plan, under which all globally-reachable telephone numbers are organized. Configuration ENUM Servers ENUM Server Related Topic SIP ENUM SIP-Based Load Balancing Brief Description This feature allows you to distribute SIP traffic between IMGs configured as “SIP Servers” using virtual IP Addresses and a SIP load balancer. Benefits Improved scalability and fault tolerance. Related Topics SIP-Based Load Balancing SIP CODEC Negotiation Priority This feature allows you to configure whether the IMG or the remote gateway takes priority when selecting a codec. Benefits The feature gives you the flexibility to choose CODEC priority on either IMG or the far end gateway. Configuration SIP Profile 33 IMG WebHelp You configure CODEC Negotiation Priority to either Local or Remote in the SIP Profile pane. SIP REGISTER “Expires” Timer Control This feature gives you the ability to control the expiration of a registration request sent from the IMG to a Remote SIP User Agent. The default is 3600 sec. RFC RFC 3261 SIP: Session Initiation Protocol Configuration External Gateway You can change the default to a value between 10 and 7200 sec using the Registration Expiration Interval field in the External Gateway pane. SIP 305 Redirect Response Brief Description The IMG now supports the 305 Use Proxy message. Benefits Enables re-direct to Proxy Server. Related Topics SIP 3XX Redirect Responses SIP Call Hold Brief Description This feature allows the IMG to process a re-INVITE from a SIP endpoint that places a call on hold or releases a hold. This addition complements the current support for SIP Hold (via 0.0.0.0 ip address) by supporting RFC 3398 section 9, allowing for the proper Interworking of hold information between SIP and SS7. RFC RFC 3398 Integrated Services Digital Network (ISDN) User Part (ISUP) to Session Initiation Protocol (SIP) Mapping (section 9) Related Topic SIP Call Hold SS7 ITU to SIP Interworking: Calling Party Category (CPC) (10.3.3 ER1) 34 Introduction ITX Message (SPIROU) Support H.323 Keep Alive Timer Brief Description Set Time to Live parameter in Registration Request (RRQ) Benefits Greater user control when using H.323 gatekeepers Overview This feature gives you the ability to control the Time to Live value in the RRQ from the IMG when registering with a gatekeeper. This is an optional parameter in the RRQ. If no Time to Live is present in the RRQ, the gatekeeper returns a value in the RCF which the IMG has no control over. By inserting the Time to Live value in the RRQ, the user has control over it as the gatekeeper normally returns the value requested by the endpoint in the RRQ. If the gatekeeper returns a different value, that will be the value used by the IMG in subsequent lightweight RRQs to maintain registration. Configuration External Gatekeeper SS7 Pre/Post 95 Support for GRS/GRA Description This feature provides the capability to support both pre and post 1995 GRS (Group Reset)/GRA (Group Reset ACK) messages on a per CIC group basis (ANSI Only). Benefits Enables different CIC groups in an SS7 stack to connect to different types of DPCs. Configuration ISUP Group Related Topic Pre/Post 95 Support for GRS/GRA. JT-ISUP The IMG supports JT-ISUP, the SS7 standard for Japan (JT-Q.763). 35 IMG WebHelp See JT-ISUP for more information. SS7 ITU to SIP Interworking: Calling Party Category (CPC) (10.3.3 ER1) VoIP G.729 E/G Description 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. Benefit Better voice quality than G.729A. Configuration Vocoder Entry Related Topic Vocoder Information G.723 Maximum Packet Size Description The maximum packet size for the G.723 codec has been increased to 90. Benefits Handle larger payloads for reduced bandwidth markets. Related Topic Vocoder Information Modifiable RTP Base Port Number Overview 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. Benefits 36 Introduction 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. Configuration VoIP Module G.729 AnnexB Selection Overview 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. Configuration Vocoder Entry Routing Modify Cause Code for Re-Routing Purposes Description The IMG will automatically attempt to re-route calls in response to the following cause codes: 42,41,34. Use this field to select up to 4 additional Cause Codes for which the IMG will re-attempt a new call, per trunk group. Benefits This feature gives you more flexibility as to how to use the IMG 1010 under particular network conditions and configurations. Configuration Channel Group Use the Re-attempt Cause Code field to select up to 4 cause code values. Call Tracing New call tracing will be added to indicate that a re-attempt has occurred for the selected Cause Codes. Local Number Portability (LNP) Description 37 IMG WebHelp Allows the IMG to route ported numbers for SIP and SS7. Benefit Properly handle ported numbers. Configuration ISUP Group Related Topic Local Number Portability (LNP) Routing on Originating IMG Description This feature allows you to route based on the originating IMG as well as the Dialed Number. Benefits You can route a call from the same dialed number to different channel groups, depending on the IMG it comes in on. Configuration You enable this feature by selecting an IMG in the Match IMG as Well field in the Route Entry pane. Importing Route Tables using NFS Benefits More efficient method for loading large route tables. SNMP Support for the following MIBs has been added to the IMG SNMP offering. DSO MIB This feature will introduce support for the DS0-MIB as described in RFC 2494 ALARM-MIB RFC 3877 Support for the alarm MIB offers three major benefits: 1. The ability to inspect the alarm tables and find out what is currently wrong with the system. 38 Introduction 2. The ability to model alarms in a generic way. 3. The ability to send out generic traps when alarms are raised. Traps alarmActiveState - This trap is sent out when an alarm is raised. It contains the model number of the alarm as well as a resource ID which identifies specifically what the alarm refers to (for instance for a link down alarm you would indicate which link it is). alarmClearState - This gets sent out when an alarm is cleared. It contains the same information as the other trap. IF_MIB IMG now supports the new Interfaces MIB specified in RFC 2863 Support for this MIB provides several benefits: A view of control, signalling, and data ports Measurements of the flow of traffic including number of packets in and out Descriptive information about these ports Recording of errors such as numbers of packets dropped. Managers used to query the switch should update their list of compiled MIBs to include RFC 2863. Limitations The IMG does not allow an NMS to write to the IMG and will not support parts of the RFC which call for writes. RADIUS RADIUS VSA Names The word Cantata now appears at the beginning of all Cantata VSA names. See Cantata RADIUS VSAs. Example: Cantata-trunk-grp-out RADIUS for Pre-Paid Applications 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. 39 IMG WebHelp Routing with RADIUS Pre-paid The IMG now accepts the Cantata-trunk-grp-out VSA in General GCEMS There is no longer a Development Mode for the GCEMS. When you start GCEMS it is automatically started in Production Mode. Related Topic Starting GateControl EMS Setting Local Time 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 disconnect time connect time See Setting Local Time for more information. ClientView WebHelp Updates You can retrieve WebHelp updates from the Cantata Support site that will replace the WebHelp version launched from ClientView. Cantata Technology - IMG 1010 Printable WebHelp 40 Introduction Upgrading to IMG System Software 10.3.3 Topic Location: Introduction Overview This topic provides steps for performing the following tasks: Upgrade GCEMS Software from 10.3.2:x to 10.3.3:x Upgrade IMG1010 switch software from 10.3.2.x to 10.3.3.x Estimated total time required to execute this upgrade procedure: approximately 1 hour Estimated call processing downtime: approximately 10 minutes Pre-Installation It is recommended that you perform the following steps prior to upgrading the IMG software. 1. Note status of entities listed below: a. SPANS and Channels that are not currently in service c. SS7 Links b. d. ISDN D-Channels Network Interfaces e. ClientView users that are logged in. Notify them of the pending upgrade and have them log off if necessary. NOTE: Entities that not in service before the upgrade should not be expected to be in service after the upgrade. 2. Obtain the latest software from the Cantata BBS at http://excelbbs.cantata.com. If you do not have access to the BBS, are not sure how to obtain it, or do not know what the latest version is, e-mail Cantata technical Support at mailto:[email protected] or call +1-781-433-9600. 3. Rename the present configuration file, which will result in the new file name (*.csa). a. In ClientView Select Configuration at the top of right pane. b. Double-click in the text box marked User-Specified in the Filename field. c. When the text box becomes white you can edit it to the new name. 41 IMG WebHelp d. Commit and save the new file by selecting File > Save from the Main Menu. 4. Backup Files a. Backup all configuration files that are stored in the /opt/cantata/common/config directory. b. See Post Installation for more information about the directory structure. 5. Transfer new GCEMS and User Interface install files via FTP or SSH Important Note: You must transfer software files in binary mode, as indicated in step 1 of the Installation procedure, or the files will not work properly. a. Transfer IMG_10.3.3.xx.bin to the host running GCEMS /home/excelsw/ftpBuilds b. Transfer IMGUserInterface_10.3.3.xx.bin to the host running ClientView & EventView /home/excelsw/ftpBuilds 6. Transfer the new IMG1010 binary file to the Host running dhcp Transfer img1010_ver1033xxx.bin to the /home/excelsw/ftpBuilds directory or the location indicated in the dhcpd.conf file. Note: The dhcpd.conf file is located in the /etc directory. If you list this file you will see a line which states the filename ftpBuilds/IMG1010_id0101.bin This is the directory path to the IMG software. If you are using an SD Card to load system software, appropriate files must be transferred to the card using an SD card reader. See Using an SD Card in the IMG WebHelp for information. 7. Transfer new license files, if any, to the GCEMS server. If there are any license changes required for the upgrade, login as user excelsw and transfer the license file (<chassis serial number>-<date>.cfg) to the following folder on the GCEMS server: /opt/cantata/common/license When upgrading from 10.3.2 to 10.3.3, the license does not need to be changed unless you are increasing capacity or adding licensed functionality. 8. When running ClientView and GCEMS on different machines the configuration *.csv files containing route entries must reside on the host running GCEMS. All configuration *.csv files containing route entries must be moved into directory /opt/cantata/common/import_export on the host running GCEMS since the 42 Introduction import and export of route tables is now handled by Data Manager. NOTE: IP Port 2623 cannot be blocked since it is now used for file transfer, FTP, between Data Manager and ClientView. Installation of New Software This section covers installation of the Host Software and does not contain serviceaffecting steps. 1. Shutdown Current GC EMS Applications a. Close the EventView GUI b. Close the AdminView Application Terminal c. Run ‘StopGCEMS’ to shutdown all GC EMS processes (click on the StopGCEMS icon) 2. Become a root/superuser by entering the command “su” and password=excel2 3. Once files are transferred to GC EMS server you must change the ownership and mode of the file being installed. This is accomplished by executing the commands chown root:root IMG_10.3.3.bin chmod +x IMG_10.3.3.bin chown root:root IMGUserInterface_10.3.3.xx.bin chmod +x IMGUserInterface_10.3.3.xx.bin 4. Install the 10.3.3 version of GCEMS with the following command: ./IMG_10.3.3.xx.bin (xx=build number) 10.3.3 GCEMS will be installed in the directory /opt/cantata/installs/IMG_10.3.3.x (3 NFS mounts are setup by default) 4. Install the 10.3.3 version of IMG User Interface with the following command: ./IMGUserInterface_10.3.3.xx.bin (xx=build number) 10.3.2 IMG User Interface will be installed in the directory /opt/cantata/installs/IMGUserInterface_10.3.3.x 5. Install IMG Software From the GCEMS Server 43 IMG WebHelp Update the link to img1010_id0101.bin Link the file img1010_id0101.bin to the latest build manually or using the lnimg script. If you do not have the lnimg script on your server (home/excelsw/ftpBuilds) you can obtain it from the IMG Software CD or the Cantata Support website. If not using the lnimg script, type the following where the link and software are located: ln –sf “img1010_ver1033xxx.bin” img1010_id0101.bin (where xxx represents the version you are installing) From SD Card If you are installing the IMG software from an SD card, insert the card into the SD slot on the IMG. See Using an SD Card in the IMG WebHelp for information. 6. Restart the NFS Service by typing: > service nfs restart 7. Logout root 8. Login as excelsw (the new profile is now in effect). 9. If you are using RADIUS, replace the existing dictionary and dictionary.cantata files in /usr/share/freeradius with the updated files located in /opt/cantata/common/radius and restart the RADIUS server. 10. Restart ClientView. Upgrade Execution This section covers installation of the IMG1010 Switch Software and execution includes service-affecting steps. 1. Divert live traffic away from the IMG’s being upgraded and then Reset each IMG a. Telnet into each of the physical nodes. b. Shift Q to the Shell prompt; reset 9. 2. Verify each IMG is online a. Telnet into each of the physical nodes. b. Login and press ‘b’ to verify the 10.3.3 build has been loaded. Product: 44 IMG 1010 Introduction 3. S/W Version: 10.3.3:141, Apr 05 2007 01:19:19 ROM Version: 2.0.5:000, Apr 03 2006 11:51:39 File Loaded: ftpBuilds/img1010_id0101.bin File Svr IP: 10.129.47.20 Start the GCEMS a. Open the AdminView if needed. b. Start the GC EMS in Development Mode StartGCEMS c. Open the ClientView GUI. d. In ClientView click the button ‘Help’ and then ‘About ClientView’. In the pop up window select ‘Product/Company Info’ and verify the installation path and Version. 4. Reconfigure a. Open & Commit the current .csa file b. View the Configuration File Conversion Report to see any differences found between the configuration file and the new version of ClientView. See Upgrading ClientView. c. Choose Configure and save with changes or Save with changes but do not configure. 5. Verify Status a. Verify that all nodes return to online state. b. Verify all spans that were in service prior to upgrade return to in-service state. Post Installation This section covers changing between versions of the IMG1010 GCEMS Software and cleanup of old versions. 1. Changing GCEMS Version (Optional) To change to another installed version of GCEMS run the ChangeGCEMSVersion script located in the following directory: /opt/cantata/installs This will also update the links in StartGCEMS and StopGCEMS utilities to the new version. 2. Deleting Old Software Versions (Optional) 45 IMG WebHelp To remove unwanted versions of older software run the DeleteGCEMSVersion script located in the following directory: /opt/cantata/installs 3. Verify Upgrade To verify that the new software load has been installed in the Client View GUI go to the Physical IMG pane: Software Version field. Restoring Previous Version This section covers restoring to a previous 10.3.2 release after updating to 10.3.3. 1. Change the startup links using script tool ChangeGCEMSVersion located in: /opt/cantata/installs 2. Restore the 10.3.2 *.csa configuration file. It is very important to note that 10.3.3 treats configuration files differently than previous versions. For example, additional routing information is created and stored in new folders in: /opt/cantata/common/config A 10.3.3 *.csa configuration file cannot be used with previous versions. 3. Restore any RADIUS changes that may have been done. 4. Change the system software link using script lnimg. 5. Power cycle each IMG. 6. Stop GCEMS and restart. 7. Restart ClientView. Cantata Technology - IMG 1010 Printable WebHelp 46 Product Description Summary of Previous Releases An Overview of Features in Previous Releases Topic Location: Product Description > Summary of Previous Releases The following topics provide overviews of new features in each release of the IMG 1010. An Overview of Features in 10.1 An Overview of New Features in 10.3 An Overview of New Features in 10.3.1 An Overview of New Features in 10.3.2 An Overview of New Features in 10.3.3 Cantata Technology - IMG 1010 Printable WebHelp 47 IMG WebHelp An Overview of Features in 10.1 (Initial Release) Topic Location: Product Description > Summary of Previous Releases The following features were included in the initial release of the IMG 1010 (Release 10.1): Telephony Interfaces 28 T1 21 E1 120 Ohm IP Interfaces 2 Fast Ethernet for Gate Control EMS 2 GIG-E for IP Bearer Traffic 2 Fast Ethernet for VoIP Signaling VoIP The IMG supports two VoIP modules, each supporting the following features: 384 VoIP resources G3 Fax Relay that is compliant with the T.38 ASN.1 standard. Codecs: G.711, G.723.1, G.729 Voice/Fax/Data: Automatic Switching Fax Support: Group 3 2.4 – 14.4 kbps, T.38 compliant fax relay or automatic switch to PCM Modem Support: Up to V.92 rates, automatic switch to PCM Echo Cancellation: G.168-2000 Compliant; Maximum tail length of 64 milliseconds. Ping and Trace Route Capabilities If the IMG has two VoIP modules in it, the software will automatically spread all the licenses evenly across the two modules. This process is done in groups of 32 channels, so if there is an odd number of blocks, module 0 will have the extra channels. IP Signaling H.323 H.323v2 compliance 1 Active Gatekeeper and 8 standby 48 Simultaneous Gateway and Gatekeeper routed call models Product Description T.38 Fax, Modem Bypass Digital transmission via RFC 2833 Codecs: Uncompressed G.711/Compressed G.726, G.723.1, G.729 Codec negotiation on both incoming and outgoing calls including the ability to limit the codecs that are allowed Cause code mapping to SS7 ISUP via H.246 T.38 Fax, Fax Bypass Modem Bypass Out of band DTMF signaling for H.245 H.245 tunneling - H.245 data is sent with the H.225 message FastStart Cisco Interoperability TDM Signaling SS7 ISUP SS7 - H.323 Interworking Variants Control CICs on up to 32 IMGs (8 IMGs in this release.) Gateway Control Layer Basic Routing on ANI, DNIS, Nature of Address, or Channel Group Pre and post routing digit translation Media Processing On-board DSP resources for announcement and tones across IP and TDM Play messages to users of a particular network indicating call progress. These are currently statically mapped in the release cause code table and can not be configured. Customizable Variants Excel can rapidly customize IP and TDM variants for you using our patented Programmable Protocol Language tool. OAM&P Centralized Element Management System Monitoring and provisioning up to 8 IMGs. 49 IMG WebHelp Gate Control EMS Operating System Linux Enterprise Cantata Technology - IMG 1010 Printable WebHelp 50 Product Description An Overview of Features in 10.3 Topic Location: Product Description > Summary of Previous Releases The following features were added to IMG 10.3 CI release. SIP The IMG 10.3 supports SIP as a User Agent. The IMG will be able to register with a proxy, but will disallow incoming registration requests. The IMG supports the following SIP functionality: SIP to H.323 Interworking SIP to SS7 Interworking SIP to ISDN Interworking SIP-T DNS Lookups UDP or TCP (single or multi-socket) See Introduction to SIP ISDN The following are supported for ISDN: NFAS for 28 spans Interworking with SIP and H.323 Secondary D-channel Maximum support of 32 D-channels See Introduction to ISDN DS3 A DS3 has a bandwidth of 44.736 Mbps, which is the capacity of 28 T1 spans. Every 85th bit in a DS3 bit sequence is used for overhead functions such as frame alignment, error detection, and terminal-to-terminal data communication. All other bits are payload bits. The DS3 uses the M-Frame format and supports the following framing modes: M13 C-bit (default) The DS3 signal format typically transports 672 channels at 64 Kbps per channel. The DS3 signaling interface is bipolar with Bit 3 Zero Substitution (B3ZS). 51 IMG WebHelp Routing Enhancements Time of Day Routing See Configuring Time of Day Routing 1000 Route tables per GateControl EMS Each IMG supports 4 route tables unique to the system, allowing the GateControl EMS to control, monitor, and maintain 250 discrete gateways. Route tables can be specific to a particular gateway, or they can be global. Route verification See Validating Your Configuration Import either an Excel spreadsheet or CSV for routing and translation tables Route from one route table to another with the ability to prevent looping. Configure the IMG to accept calls from multiple gateways with one External Gateway Entry (Gateway Mask field). Excel RADIUS Format The IMG uses Remote Authentication Dial In User Service (RADIUS) protocol for streaming the Call Detail Records (CDR). The implementation is compliant with RFC 2865 and RFC 2866. The RADIUS messages are sent to external RADIUS servers. The IMG now supports an Excel RADIUS format, which includes some attributes defined by RFC 2865 and RFC 2865, as well as Excel Vendor Specific Attributes (VSA). See An Overview of RADIUS. ClientView GUI Enhancements Configuration Validation Report Use the Validation Report utility to confirm that your configuration does not contain any errors that may prohibit proper operation. Analyze the report for possible errors found and modify your configuration accordingly. See Validating Your Configuration External Gateway pane/Gateway Mask Added a Gateway Mask field to the External Gateway pane to allow you to configure the IMG to accept calls from multiple gateways. Licensing TDM spans now include signaling spans: 24 E1/32 T1 in 96 port increments SIP is licensed in 32 span increments. If there are 2 modules configured, the license is shared between them. 52 ISDN B Channels are licensed in 24 or 32 span groups Product Description Downloading Raw API file to IMG You can now download a raw API file to the IMG and have it become part of the config file. See Downloading a Raw File. Physical Port Configuration The IMG defaults to 10.100 with Auto-negotiation. For each port, you can change the setting to Full Duplex, in which case it will be negotiated to half-duplex. See Configuring Physical Port Interface Mode Cantata Technology - IMG 1010 Printable WebHelp 53 IMG WebHelp An Overview of Features in 10.3.1 Topic Location: Product Description > Summary of Previous Releases The following features were added to the IMG 10.3.1 release:. Engineering Release 4 The following features were added to the 10.3.1 ER 4: Multi Router Traffic Grapher (MRTG) Tool The Multi Router Traffic Grapher (MRTG) Tool is used to monitor various areas on network links. MRTG generates HTML pages containing PNG images which provide a live visual representation of this traffic. See Using the Multi Router Traffic Grapher (MRTG) Tool. Comedia for H.323 The IMG now supports Comedia for H.323. H323 uses the Comedia information internally; no Comedia information is shared with other gateways or endpoints. See Comedia. Controlled Introduction Release The following features were in the base 10.3.1 CI Release: Folder changes for Cantata Re-branding Some file and folder names have changed due to the change from Excel Switching Corp. to Cantata Technologies, as follows: Various files such as licences, routing, and logs are now installed in the following folder: opt/cantata/common Existing 10.3.0 configuration files will remain backed up in the following folder: opt/Excel Switching Corp/backup Currently used configuration files are stored in opt/cantata/IMG/config Backup 10.3.1 configuration files are stored in the following folder: opt/cantata/IMG/backup ClientView Enhancements 54 Hosts and Usernames Retained in Login Pane History See ClientView Properties. ClientView Upgrades When you upgrade to a newer version of ClientView, there may be some changes to panes or fields that affect your existing configuration. When you Product Description open an existing configuration file with a new version of ClientView, a log is generated that indicates any changes that would be required to the file. You are given the option to accept the changes or to not use the file. See Upgrading ClientView. Gateway Enhancements Gateway Mask Added a Gateway Mask field to the External Gateway pane to allow you to configure the IMG to accept calls from multiple gateways with one entry. Added CLIP/CLIR for IDs VoIP New Mindspeed module enables support for new codecs and IP-IP transcoding density improvements (up to 1024 VoIP channels) Wireless Codecs for SIP The following wireless codecs are now supported for SIP: AMR (license required) EVRC (license required) Adaptive Multi-Rate (AMR) is a variable bit rate (VBR) codec - used in wireless GSM networks. Enhanced Variable Rate CODEC - used in wireless CDMA networks. iLBC iLBC (internet Low Bitrate Codec) is a free speech codec suitable for robust voice communication over IP for such applications as SIP Endpoints (soft phones) and Packet Cable. The codec is designed for narrow band speech and results in a payload bit rate of 13.33 kbit/s with an encoding frame length of 30 ms and 15.20 kbps with an encoding length of 20 ms. Typically used Related Topics VoIP Overview Supported Codecs pane Vocoder Entry pane SIP G.168 Echo Cancel with 128 sec tail DNS Address Support for SIP 55 IMG WebHelp The IMG can route SIP traffic to a remote entity based on the IP Address or the Host Name. The IMG supports having multiple DNS servers for redundancy and reliability purposes. Related Topics Configuring DNS for SIP DNS Servers pane DNS Server pane DNS Client pane SIP Privacy The IMG supports RFC 3325, which establishes a standard way to transport Calling Party identification information (CLI) between trusted networks, enabling a network of trusted SIP servers to assert the identity of end users and servers. External SIP gateways can be configured as either being Trusted or Untrusted for issues of privacy. 2 new headers are supported: P-Asserted-Identity (Privacy ID) Remote-Party-ID (Privacy Tag, Screen Tag) Related Topics Configuring SIP Signaling SIP Signaling pane External Gateway pane ISUP Group pane ISDN Group pane SIP-to-SS7 ISUP Cause Code Mapping You can modify the default mapping between SS7 ANSI and SIP cause codes, which is defined by RFC3398. Related Topics Customizing SIP-to-SS7 ISUP Cause Codes Route Table pane Route Entry pane Channel Group pane 56 SIP Comedia (Symmetric RTP) This feature allows the passage of VoIP packets between endpoints when one (but not both) of the endpoints resides on a private network behind a NAT (Network Address Translation) device. The Connection-Oriented Media (Comedia) Enhancements for SIP allows the IMG to check the media source of Product Description incoming Realtime Transport Protocol (RTP) packets, and allows the endpoint to advertise its presence inside or outside of Network Address Translation (NAT). Using this enables symmetric NAT traversal by supporting the capability to modify and update an existing RTP session remote address and port. Related Topics SIP Comedia IP Bearer Profile pane (Comedia Mode field) ISDN Added support for NI2 and JATE User Side. See ISDN D Channel. Added support for ISDN Bearer Capabilities Override configuration. See Bearer Capabilities Override. Routing Translation Enhancements Appending Info Digits ANI and DNIS Translation Translation based on Channel Group Related Topics Translation Features Translation Entry DS3/DS1 Diagnostics DS3 BERT and Loopback T1/E1 Loopback Related Topics DS3 Diagnostics TDM DS3 pane BERT pane Management Improved Call Tracing. See Call Tracing. Call Statistics. See An Overview of Troubleshooting. Cantata Technology - IMG 1010 Printable WebHelp 57 IMG WebHelp An Overview of Features in 10.3.2 Topic Location: Product Description > Summary of Previous Releases The following features were added to IMG release 10.3.2: Controlled Introduction The following features are in the baseline Controlled Introduction release. Installation Changes File Names 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) Start/Stop GCEMS Scripts The scripts to start and stop the GCEMS have been renamed as follows: StartIMG now named StartGCEMS StopIMG now named StopGCEMS ClientView Enhancements Search Capabilities 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. Importing Data Enhancements 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. 58 Product Description Monitoring SNMP 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. See An Overview of SNMP MRTG 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. H.323 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. See Symmetric NAT Traversal. SIP See New SIP Features in 10.3.2 CI. SS7 Forward call Indicators (FCI) Override 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. COT Test Circuit Query Message You can send a Continuity Check request on a CIC or a group of CICs. See the Circuit Group pane. 59 IMG WebHelp 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. Discard Privacy Info 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) Generic Number Only Display Only Display and Generic Number Calling Party Only Display and Calling Number Calling, Display and Generic ISDN See Discard Privacy Info above. Routing IP Traffic Management 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. Pre-Call Announcements (Branding) 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. See Pre-call Announcements. Gain Control 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. 60 Product Description 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. RADIUS VSA Name/Numbering New VSAs The Cantata 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: call-id (VSA # 141) Value of the Call-ID header. incoming-req-uri (VSA # 146) next-hop-dn (VSA # 149) next-hop-ip (VSA #: 148) outgoing-req-uri (VSA # 147) prev-hop-ip (VSA # 145) prev-hop-via (VSA # 144) sip-attempt-info (VSA # 151) sip-resp-code (VSA #150) trans-cause-code (VSA # 53) For inbound Radius mess. both Start & Stop. Access to the value after the RFS on the inbound side The Domain Name (DN) or Fully Qualified Domain Name (FQDN) where the request is forwarded. Next-hop IP address where the request is forwarded. For outbound Radius mess.Both Start & Stop Access to the value after outseize of the Invite 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 “Sent-by” portion of topmost via when the request arrived at the proxy. In case IMG tries the contacts returned with 3xx, IMG will log to the CDR each attempt. Sip Cause Code before translation to the Q931 value Translated Cause Code when translate cause table is used. 61 IMG WebHelp See Cantata RADIUS VSAs. RADIUS Server Failure Alarm RADIUS Debug Mode 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. FAX Fallback to Fax Bypass for both H.323 and SIP 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. Engineering Release 1 The following features have been added to the baseline Controlled Introduction release with Engineering Release 1. RADIUS for Pre-Paid Applications This feature was modified in ER2. See above for current implementation. Engineering Release 2 The following features have been added to the baseline Controlled Introduction release with Engineering Release 2. G.729 E/G 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. 62 Product Description You assign vocoders in the Vocoder Entry pane Modifiable RTP Base Port Number 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. Benefits 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. RADIUS VSA Names As of 10.3.2 ER2, the word Cantata appears at the beginning of all Cantata VSA names. See Cantata RADIUS VSAs. RADIUS for Pre-Paid Applications 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: Call Duration 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) 63 IMG WebHelp New Dialed Number 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) Engineering Release 4 Local Number Portability (LNP) This feature allows the IMG to route ported numbers for SIP and SS7. See Local Number Portability (LNP) for details. Configuration You enable or disable LNP Routing in the ISUP Group pane. Routing on Originating IMG This feature allows you to route based on the originating IMG as well as the Dialed Number. Benefits You can route a call from the same dialed number to different channel groups, depending on the IMG it comes in on. Configuration You enable this feature by selecting an IMG in the Match IMG as Well field in the Route Entry pane. SIP Based Load Balancing 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: SIP Features Configuring SIP Based Load Balancing SIP Virtual Address Network Interface Engineering Release 5 SIP Reason Header RFC: 3326 64 Product Description Description 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. Benefits This feature is useful for debugging purpose, particularly if there is a call failure in SIP to SS7 traffic. See SIP Reason Header. Add "+" in Translation Table 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. SS7 - Suppress UCIC 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. Engineering Release 6 G.729 AnnexB Selection 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. Setting Local Time 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 disconnect time connect time 65 IMG WebHelp See Setting Local Time for more information. Cantata Technology - IMG 1010 Printable WebHelp 66 Product Description An Overview of New SIP Features in 10.3.2 CI Topic Location: Product Description > Summary of Previous Releases The following SIP features were added to IMG release 10.3.2: SIP Profiles 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. SIP Redirect Server Support This feature allows the IMG to respond to the 3XX class of SIP messages returned from a redirect server. See SIP Redirect Server Support. SIP Diversion Header 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. SIP Re-origination Attempts 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. 67 IMG WebHelp SIP Proxy Handling 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. SIP Trunk Group Selection 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. See SIP Trunk Group Selection for more information. SIP Info Method for DTMF This feature allows the use of the INFO method to send a DTMF digit to another gateway. See SIP INFO Method for DTMF. Non-Standard Tags in From Header 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. Cantata Technology - IMG 1010 Printable WebHelp 68 Product Description VoIP An Overview of VoIP on the IMG Topic Location: Product Description > VoIP The IMG performs two-way conversion between circuit-switched data and packetswitched data. This conversion is required by packetized voice applications, such as the Voice over Internet Protocol (VoIP). The IMG also integrates media resources over IP technology. Circuit-switched voice is converted to IP packets, using compression algorithms that can increase capacity toward the IP network side. You can have parameters modified for an individual call, often while the call is active, changing the quality of service, as needed. Integrated Media Resources Integrating media resources using IP technology provides many advantages. Typically, media resources are connected by T1, E1, or J1 interfaces that consume one 64 Kbps port per call, limiting the capacity of the system. The IMG integrates media resources over IP using the standards-based Real-Time Protocol (RTP). Integrating media resources using standards-based technology also allows media resources to be shared between the IMG and other network infrastructure. Packet switching to media resources allows the application to benefit from voice compression, increasing capacity on the application. This flexibility allows the IMG and the applications to scale independently and incrementally, as needed, eliminating excess hardware. Summary of VoIP Features SIP RFC 3261 Up to 512 VoIP resources depending on configuration H.323 V2 IP Bearer Profiles Integrated media resources Codecs: G.711, G.723.1, G.729/A/B, G.729E/G (10.3.2 ER 2 and above), iLBC, AMR, EVRC Fax Support: G3 Fax Relay that is compliant with the T.38 ASN.1 standard Group 3 2.4 – 14.4 kbps, T.38 compliant fax relay or switch to PCM (synchronized with SIP or H.323) Modem Support: Up to V.92 rates, automatic switch to PCM Echo Cancellation: G.168-2000 Compliant; Maximum tail: Switching between Voice/Fax/Data is synchronized with SIP or H.323 VoIP Module SLM-IPM-1001 - 128 milliseconds 69 IMG WebHelp VoIP Module SLM-IPM-0001 - 64 milliseconds. Ping Capabilities Symmetric NAT Traversal Jitter Buffer: Transcoding Cantata Technology - IMG 1010 Printable WebHelp 70 Product Description VoIP Features Topic Location: Product Description > VoIP These features are configured in the IP Bearer Profile pane. Silence Suppression During a normal voice conversation, much of the time is wasted on silence from one or both ends. Ethernet bandwidth can be conserved if, during these periods of silence, RTP packets are sent with silence-encoded, compressed payloads. The IMG Silence Suppression feature supports the concepts of Voice Activity Detection (VAD) and Comfort Noise Generation (CNG). When enabled, Silence suppression will not send RTP traffic during periods of silence, saving bandwidth usage. Also, at the beginning of a silence period, a single packet will be sent to the distant end to inform it that a period of silence is being entered, and that the distant end should begin to regenerate comfort noise to its TDM stream. You can enable or disable Silence Suppression on an established connection. NOTE: This does not apply to EVRC or GSM-AMR as they have their own internal Silence Suppression scheme. NOTE: For SIP calls, silence suppression is assumed to be enabled, therefore the attribute is not sent unless it is set to off, or in the case of Fax reinvites. If set to off, the following is included in the SDP: a=silenceSupp:off - - - - Echo Cancellation In compliance with ITU G.168-2000, this feature eliminates echo introduced by impedance mismatched hybrids on TDM channels. The maximum tail length is 128 milliseconds for VoIP Module SLM-IPM-0001 and 64 milliseconds for the VoIP Module SLM-IPM-0001. You may want to implement Echo Cancellation for tandem calls on trunks with echo or to clean an incoming signal before connecting to a media resource, such as a Voice Response Unit or Answering Machine Detection. See the Echo Cancellation field in the IP Bearer Profile pane. RTP Redundancy This feature provides RTP packet redundancy to guard against network packet loss. Refer to RFC 2198. This applies to RTP traffic in voice or fax/modem bypass calls. Note that Open Phone does not support RTP Redundancy. NOTE: This does not apply to EVRC, GSM-AMR or iLBC. See the RTP Redundancy and RTP Payload Type for Redundancy fields in the IP Bearer Profile pane. Digit Relay 71 IMG WebHelp You can propagate DTMF digits utilizing a separate RTP payload type and you can define the packet type used for digit relay. See the Digit Relay and Digit Relay Packet Type fields in the IP Bearer Profile pane. Fax Fallback to Fax Bypass 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 the Fax Mode and Fax Bypass Codec fields in the IP Bearer Profile pane. Fax Packet Redundancy This feature provides Fax packet redundancy to guard against network packet loss. Up to 3 levels are supported. Redundancy is applied to data and control T.38 packets. This is only applicable to Relay Fax Mode. This feature does not apply for the AMR or EVRC codecs. See the Fax Mode and Fax Packet Redundancy fields in the IP Bearer Profile pane. Modem Bypass If this feature is enabled the IMG switches to another codec when you are in a modem call. The codec that you switch to is specified in the Fax Bypass Codec field. For example, if you are using a low bit rate codec, such as G.729, a modem or fax call will probably not be successful. So in this case the IMG changes the codec to what is configured in the Fax Bypass Codec field. This functionality is not supported for the AMR and EVRC codecs. See the Modem Behaviour field in the IP Bearer Profile pane. Cantata Technology - IMG 1010 Printable WebHelp 72 Product Description Supported Codecs Topic Location: Product Description > VoIP You can define new vocoders and select the payload type and payload size (preferred, minimum, and maximum). The supported vocoders then are part of the IP bearer profile. When you have multiple vocoders, you create a priority order that is used in the H.245 Terminal Capability Exchange for the IP Bearer Profile (parent) object for codec negotiation with other network elements. The IMG supports the following codecs: SIP G.711 G.729 H.323 G.723 G.729E/G (10.3.2 ER 2 and above) T.38 iLBC AMR EVRC G.711 G.729 G.723 T.38 Codec Descriptions G.711 International standard for encoding telephone audio on an 64 kbps channel. Two different variants: A-law and mu-law. A-law is the standard for international circuits. It is a pulse code modulation (PCM) scheme Always used for Fax or Modem Bypass modes (A-law or u-law allowed) G.723 73 IMG WebHelp G.729 Designed for video conferencing / telephony over standard phone lines, and is optimized for realtime encode and decode. Part of the H.323 standards for video conferencing. 8 Kbps encoded bit stream rate G.729A and G.729A/B supported. Discontinuous transmission support (DTX) using Voice Activity Detection (VAD) and Comfort Noise Generation (CNG) G.729 AnnexB Selection 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 in the GUI Bearer Profile configuration for G.729 and G.729E payloads. The default selection yes, or Not Used, ensures that the existing IMG behavior is maintained for backwards compatibility. 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. G.729 E/G (10.3.2 ER 2 and above) SIP Only Provides increased voice quality 74 Codec defined by the ITU RFCs 3551 & 3555 Uses dynamic payload types (96-127 range), which must be agreed on by both endpoints of a call (using SIP/SDP). G.729E is a higher rate version of G.729 designed to provide higher quality for background noise conditions, music, and tandems. This mode is better for music, and it has greater complexity than the original G.729 coders Mandating a codec in this range provides high quality, low-bandwidth performance for on-net calls and ensures the highest possible performance for applications such as IVR systems. In addition, it provides superior background noise handling, as well as medium quality music carriage. Available in 10, 20 or 30 ms payload sizes Supports all attributes that G.729 supports (silence suppression, RTP redundancy, etc.) Annex G defines the silence suppression characteristics (VAD/CNG) for G.729E. G.729E and G.729E/G are essentially the same. According to RFC 3555 (defines MIME support for codecs), the “annexB” parameter can be used to enable/disable silence suppression in IP signaling negotiation. Product Description An example of the media representation in SDP for describing G.729E/G might be: m=audio 5104 RTP/AVP 96 a=rtpmap:96 G729E/8000 a=fmtp:96 annexb=no a=ptime:30 a=maxptime:60 iLBC (internet Low Bitrate Codec) SIP Only Available in 13.3 kbps (30 ms encoding frame length) or 15.2 kbps (20 ms encoding frame length) versions Defined by RFC 3591 and RFC 3592 Uses dynamic payload types (96-127 range), which must be agreed on by both endpoints of a call. Designed for narrow band speech (64kbps). Decoding algorithm does not depend on previous packets, therefore it is excellent at handling packet loss. Mandatory codec required for the released CableLabs PacketCableTM 1.1 audio/video codec specification for multimedia terminal adapters (MTAs) and media gateways. EVRC (Enhanced Variable Rate Codec) SIP Only Defined by RFC 3558. Requires Cantata license. A CDMA codec defined by 3GPP2. Used in millions of CDMA handsets. Sent in 20 ms output frames of 3 different sizes: Rate 1, Rate ½ or Rate 1/8. Output frame rate is chosen based on analysis of input frames (dynamically). Two payload modes: header-free and interleaved (only header-free in current release). Silence suppression supported internally (not configurable). Uses dynamic payload types (96-127 range) GSM-AMR (Global System for Mobile - Adaptive Multi-Rate) Requires Cantata licensing. AMR codecs (narrow and wide band) originally defined by ETSI for GSM. 75 IMG WebHelp Only AMR-NB supported in current IMG release. Uses dynamic payload types (96-127 range) Mandatory codec for 3G cellular systems. Supports eight narrow-band speech encoding modes with bit rates between 4.75 and 12.2 kbps. These rates can be adjusted dynamically during a session. Speech encoding performed in 20 ms frames. Multiple 20 ms frames can be encapsulated into a packet (maxptime in SDP defines max frames per packet). Reception of multiple frames in a packet allowed, but only one frame per packet will be transmitted. 12.2 kbps version of AMR-NB is defined by the GSM-EFR standard. 7.4 kbps version of AMR-NB is defined by the IS-641 codec in TDMA. 6.7 kbps version of AMR-NB is defined by the PDC-EFR standard. Silence suppression supported internally (not configurable). Host Flags You must set your desired codec configuration in the BOOTP Flags. See Setting Host Flags. Once you load the profile to the IMG, all codecs defined for that profile are available to use for as many calls as are defined by the channel density for that profile. Cantata Technology - IMG 1010 Printable WebHelp 76 Product Description Vocoder Information Topic Location: Product Description > VoIP VoIP Resource Profiles Profile Number Profile Name 5 LBR (Low Bit Rate) (default) CODECs Supported G.711 u-law G.711 a-law Resources Channels per DSP Channels per Module 512 128 512 (100 for T.38) (400 for T.38) 336 84 336 336 84 336 if using: G.723 G.729 6 iLBC and G.729EG Profile 5 + G.729E/G (SIP Only) (10.3.2 ER 2 and above) iLBC 7 Wireless Profile 6 + GSM-AMR EVRC G.711 G.729 G.723 T.38 iLBC AMR EVRC Codec Payload Size The following table includes the payload sizes of the codecs supported by the IMG. Codec Payload Sizes (ms) Base Rate (ms) G.711 u-Law 10,20,30,40,50,60 5 G.711 A-law 10,20,30,40,50,60 5 G.723 30,60, 90 30 G.729 A/B 10,20,30,40,50,60 10 77 IMG WebHelp ILBC-13k 30 30 ILBC-15k 20 20 GSM-AMR 20 20 EVRC 20 20 Vocoder Host Flag You must set the host flag bits 3 and 4 in the DHCP.conf file depending on the Profile ID you require, as shown below. See Editing the DHCP Conf File. Profile ID Profile Name Host Flag Bit 4 Host Flag Bit 3 Host Flag Hex Value Host Flag Decimal Value 5* LBR 0 0 0x00 0 6 LBR, iLBC 1 0 0x10 16 7 LBR, iLBC, AMR, EVRC 1 1 0x18 24 * default Cantata Technology - IMG 1010 Printable WebHelp 78 Product Description Symmetric NAT Traversal Topic Location: Product Description > VoIP This feature allows the passage of VoIP packets between endpoints when one (but not both) of the endpoints resides on a private network behind a NAT (Network Address Translation) device. This allows the IMG to check the media source of incoming Realtime Transport Protocol (RTP) packets, and allows the endpoint to advertise its presence inside or outside of Network Address Translation (NAT). Using this enables symmetric NAT traversal by supporting the capability to modify and update an existing RTP session remote address and port. When Symmetric NAT Traversal is enabled, the IMG will look for incoming packets from the distant end and use the source address information in those packets to define the IP address and UDP port information that must be sent back out via RTP to the distant end. The Comedia feature is based on the Comedia IETF draft version 04 (draft-ietfmmusic-sdp-comedia). SIP Symmetric NAT Traversal for SIP signaling provides the following: Ability to specify the connection role of the IMG when acting as a UAC or UAS. Enable interoperability in networks where NAT devices are unaware of SIP or SDP signaling. SIP endpoints may both be outside NAT or one inside and the other outside. H.323 H323 uses the Symmetric NAT Traversal information internally; no Symmetric NAT Traversal information is shared with other gateways or endpoints. Symmetric NAT Traversal Mode When you enable Symmetric NAT Traversal (in the IP Bearer Profile pane) you specify the setup role for the IMG. Passive Used when the IMG is on a public network and you want the IMG to allow calls to a distant endpoint that is behind a NAT. The IMG uses the Source IP and Ports of the incoming RTP, RTCP, and T38 packets as the Destination IP and Port of the outgoing RTP, RTCP, and T38 packets. 79 IMG WebHelp Active This applies to SIP only. It used when the IMG is behind a NAT and you want the IMG to send or accept SIP INVITEs. The IMG will convey that it is behind a NAT to the distant endpoint in the SDP. The IMG advertises to other gateways to change their RTP port and IP address to map with the NAT by sending the direction attribute a=direction<active> in the SIP SDP. Troubleshooting Notes If both the IMG and the remote GW is set to passive you will have no voice path. If neither side is set to passive and you are connecting through a NAT you may not have voice path. Cantata Technology - IMG 1010 Printable WebHelp 80 Product Description Transcoding Topic Location: Product Description > VoIP Overview Service providers have traditionally relied on TDM interconnections to move voice traffic on and off their networks, in part because of the high quality and reliable interconnections inherent in the technology. Recent advances in VoIP-based technology present a new lower-cost alternative that offers a quality and reliability that rivals TDM networks. VoIP networks have the added benefit of supporting advanced capabilities such as point to multi-point interconnection not available in TDM offerings. This combination of the increased quality/reliability, advanced features, proliferation of VoIP-based networks, and the lower cost of VoIP is encouraging service providers to use VoIP peering solutions for network interconnection. with this transition to allVoIP networks a new host of challenges arise. The use of the Public Internet brings up questions of security, quality, media interworking, and trust. Session border controllers and media gateways are the edge devices ideally suited to address these new challenges. Session border controllers provide the security for VoIP network interconnection through topology hiding and user authentication. Session border controllers can also address the concerns of trust and signaling interworking. The last challenge on the edge of VoIP networks is Media Interworking. H.323 to SIP signaling interworking can be handled by the media gateway or by the session border controller. RTP layer transcoding is best handled by a hardware DSPbase media gateway. IMG Solution The rapid proliferation and growth of VoIP networks introduce new challenges for service providers. The replacement of TDM interconnection with VoIP peering introduces the requirement for Session Border Controllers for session management and Media Gateways for transcoding. The IMG solves current and future problems in next generation networks with its integrated transcoding. With its high density wireless and wireline codec support in a 1U form factor, the IMG 1010 is an excellent solution for the next generation service provider. The IMG supports SIP, H.323, SS7, and ISDN giving true any-to-any voice network connectivity as well as simultaneous TDM and IP hairpins. The ability to support IP hairpins enables not only IP signaling translation, but media translation as well. As VoIP networks evolve and move away from the PSTN, wide-band codecs will gain popularity. The IMG, coupled with a Session Border Controller, is the ideal solution to bridge islands of VoIP traffic. 81 IMG WebHelp Codecs/Maximum Session Supported Codecs Maximum Sessions G.711 a-law 512 G.711 u-law 512 G.723.1 5.3kbps 512 G.723.1 6.3kbps 512 G.729 a/b/e 512 iLBC 336 GSM-AMR 336 EVRC 336 Cantata Technology - IMG 1010 Printable WebHelp 82 Product Description H.323 An Overview of H.323 on the IMG Topic Location: Product Description > H.323 The IMG 1010 supports Version 2 of ITU H.323, including: Basic Support H.225 Call Signaling Protocol (Q.931 embedded) Registration, Admission, and Status (RAS) Media H.245 Control Protocol Keep Alive Timer Real-time Transport Protocol/Real-time Transport Control Protocol (RTP/RTCP) Out-of-band DTMF signaling via H.245 and RFC2833 Cisco Interoperability FastStart IP Bearer Profiles Codecs: G.711 (Uncompressed), G.723.1 (Compressed), G.729 (Compressed) T.38 Fax, Fax Bypass, Modem Bypass DTMF transmission supported via DTMF tones using G.711, or out via RFC 2833 or H.245 UII signals. Codec negotiation on both incoming and outgoing calls including the ability to limit the codecs that are allowed Interworking Cause code mapping to SS7 ISUP H.245 tunneling - H.245 data is sent with the H.225 message Cause code mapping of H.225 release reasons to Q.931 cause codes using H.246 interworking specification Routing Simultaneous gateway and gatekeeper routed calls Symmetric NAT Traversal Gatekeeper Support: 1 active gatekeeper and six alternate, auto-discovery, aliases for E.164, URL, and email. 83 IMG WebHelp Cantata Technology - IMG 1010 Printable WebHelp 84 Product Description Supported H.323 Messages Topic Location: Product Description > H.323 The H.323 offering in the IMG supports the following H.323 messages. ACF - Admission Confirm ARJ - Admission Request ARQ - Admission Request DCF- Disengage Confirm DRJ - Disengage Reject DRQ - Disengage Request GRQ - Gatekeeper Request GCF- Gatekeeper Confirm GRJ - Gatekeeper Reject IACK - Info Request Acknowledge INAK - Info Request Neg Acknowledge IRQ - Information Request IRR -Information Request Response RRQ - Registration Request RCF - Registration Confirm RRJ - Registration Reject UCF - Unregistration Confirm URJ - Unregistration Reject URQ- Unregistration Request Unsupported Messages BRQ - Bandwidth Request BCF - Bandwidth Confirm BRJ - Bandwidth Reject LRQ - Location Request LCF - Location Confirm LRJ - Location Reject RIP - Request in Progress RAI - Resource Availability Indicator RAC - Resource Availability Confirm 85 IMG WebHelp Cantata Technology - IMG 1010 Printable WebHelp 86 Product Description Codec Negotiation Topic Location: Product Description > H.323 Fast Start Call Model Codec negotiation is slightly different in a Fast Start call model than in a Terminal Capabilities (non-Fast Start) call model. However, in both call models the basic principle of codec negotiation is the same but they may be encapsulated in different H.225 / H.245 messages. The supported codecs are advertised to the remote endpoint in a list sorted by preference with the top of the list containing the most preferred codec. This list represents all the media characteristics of the channel that the IMG is attempting to open. Included in this are the payload size and the forwardChannelParamters / reverseChannelParameters. These parameters represent each direction of the channel. Important: The IMG only supports symmetrical channels, which means that the codec / payload size must be the same in the forward and reverse directions. The IMG can not be transmitting G.729 and receiving G.711 on the same media channel. In the Fast Start call model the negotiation of codec is present in the OpenLogicalChannel component of the H.225 messages: Setup Progress Call Proceeding Alerting Connect In this call model, a media channel tries to open as soon as possible so the parameters advertised for each codec are the ones that the IMG attempts to use. For instance, the payload size specified for each codec is the preferred size that we want to use, not the maximum that the IMG supports. If there are no codecs that both endpoints support, the IMG falls out of the Fast Start model and use H.245 for codec negotiation using the TerminalCapabilitiesSet message. In the TerminalCapabilitiesSet message the codecs are listed in order of preference just as in Fast Start, but the payload size for each codec is the maximum supported, not the preferred size as in the case of Fast Start. In both call models, H.245 must be started and completed before the IMG can learn all the media characteristics of the remote endpoint. This process is necessary because the IMG might not know all the characteristics of the channel until it receives the TerminalCapabilitySet message, which contains more information than just the codecs to use. This message contains the elements such as the T.38 fax information and if RFC2833 is going to be used for digit transmission. G.723r63/53 Negotiation 87 IMG WebHelp When negotiating G.723.1 codecs with the remote endpoint, we do not differentiate between G.723r53 and G.723r63. We simply advertise that we are capable of or prefer to use G.723.1. It is up to each endpoint to determine whether they want to transmit G.723r53 or G.723r63, which is acceptable because the G.723.1 specification states that the coder must support both rates. In order for the G.723.1 codec to be accepted, both the payload size must be in our range and the silence suppression must match. For more information, refer to the G.723.1 specification. Cantata Technology - IMG 1010 Printable WebHelp 88 Product Description H.323 Fax/Modem Topic Location: Product Description > H.323 The IMG supports the following fax/modem functionality for H.323: T.38 Fax The IMG negotiates T.38 support at call establishment time. The IMG supplies a T.38 port in the Fast Start component of the Setup, Call Proceeding, Alerting, or Connect message. Once a fax data mode has been detected at the IP bearer level, H.245 will send a RequestMode message to the distant end. If the distant end had not supplied a T.38 port in the Fast Start component of the Setup, Call Proceeding, Alerting, or Connect message at call establishment time, this information must be supplied in the openLogicalChannelAck. Fax Bypass T.38 or fax bypass modes are supported (except for the AMR and EVRC codecs). Fax bypass codes are not negotiated by H.323 so they must be configured to match properly at each gateway. The IMG allows G.711 A-Law or G.711 u-Law only for fax/modem bypass codecs. Once a fax data mode has been detected at the IP bearer level, H.245 will send a RequestMode message to the distant end requesting to change the codec to the fax bypass codec. Fallback to Fax Bypass 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 neither a T.38 fax nor a Bypass fax can be established in a fax fallback scenario, the IMG allows the voice call to proceed as if no negotiation had happened. Redundancy RTP redundancy levels will apply to fax bypass packets (RTP G.711 packets), but not to T.38 packets. Fax Redundancy level setting applies only to T.38 fax relay packets (not to RTP voice or fax bypass packets). Port Number For the VoIP Module SLM-IPM-0001, the IMG always assigns the T.38 port to be "RTP port + 2". RTCP port is always assigned as "RTP Port + 1". For the VoIP Module SLM-IPM-1001 , the T.38 port and the RTP port are the same. Cantata Technology - IMG 1010 Printable WebHelp 89 IMG WebHelp H.245 Tunneling Topic Location: Product Description > H.323 Overview The H.245 protocol is a media control protocol, that is a part of H.323 protocol suite. The H.245 protocol is used primarily to negotiate master-slave relationship between communicating endpoints, to exchange terminal capabilities of to be communicating endpoints, and finally logical channel manipulations (open, close, modify). The H.245 messages can be encapsulated and carried between H.225 controlled endpoints within H.225 messages. This way of "piggy-backing" an H.245 message to H.225 message is referred to as H245 Tunneling. The H.245 Tunneling method is optional and negotiable between communicating H.323 endpoints. If both endpoints support this option, usually the H.245 Media Controlled messages are exchanged via the Tunneling method. Enabling You enable inbound tunneling when you configure H.323 Signaling with the H.323 Signaling pane. If inbound tunneling is enabled, you can enable outbound tunneling in the IP Bearer Traffic Profile used for outbound calls. Functionality The tunneling feature relies on H.225 endpoint-to-endpoint connectivity (via TCP) to pass H.245 messages. The Tunneling feature uses the H.225 communication channel without creating a separate TCP socket connection (per the H.323 call) for media control. This approach allows the following faster call setup because there is no need to establish a new socket via a three way handshake preservation of TCP socket resources within the operating system While using the H.245 tunneling feature, a single TCP socket is created and used per H.323 call. An H.323 call setup that does not use tunneling uses two sockets. The H.245 messages are encapsulated into H.225 messages within a special header called H245Control as described by ASN.1. The H245Control header can be added to any message except initial Setup message. However, if there are no other messages to be shipped out from an endpoint, a designated Facility message is used. (H.323 V2 accepts and defines Empty Facility message) as transport vehicle to carry on H.245 contents. Related Topics H323 Overview Configuring H.323 Signaling 90 Product Description Cantata Technology - IMG 1010 Printable WebHelp 91 IMG WebHelp H.323 Keep Alive Timer Topic Location: Product Description > H.323 Brief Description Set Time to Live parameter in Registration Request (RRQ) Benefits Greater user control when using H.323 gatekeepers Overview This feature gives you the ability to control the value of the Time to Live parameter (optional) in the RRQ from the IMG when registering with a gatekeeper. If no Time to Live is present in the RRQ, the gatekeeper returns a value in the RCF which the IMG has no control over. By inserting the Time to Live value in the RRQ, the user has control over it as the gatekeeper normally returns the value requested by the endpoint in the RRQ. If the gatekeeper returns a different value, that will be the value used by the IMG in subsequent lightweight RRQs to maintain registration. Configuration External Gatekeeper Cantata Technology - IMG 1010 Printable WebHelp 92 Product Description H.323 Fast Start Topic Location: Product Description > H.323 Fast Start, also known as Fast Connect, bypasses some call setup steps in order to make it faster and allows the media channels to be operational before the CONNECT message is sent, which is a requirement for certain billing procedures. The Fast Start procedure is optional in the network, but the IMG will always attempt it. If Fast Start fails due to unmatched preferred capabilities or because the remote end does not support Fast Start, then the IMG will fall back to TermCaps procedure. For more information regarding the Fast Start procedure, refer to Version 2 of the ITU H.323 Specification. Cantata Technology - IMG 1010 Printable WebHelp 93 IMG WebHelp SIP 94 Product Description Overview An Overview of SIP Topic Location: Product Description > SIP > Overview SIP on the IMG The following diagram shows an example of the IMG in a SIP network. Cantata Technology - IMG 1010 Printable WebHelp 95 IMG WebHelp SIP Features You are here: Product Description > SIP > Overview Basic Support Supported Methods SIP Extensions Routing/Call Handling Media Interworking Basic Support SIP (Session Initiation Protocol), based on RFC 3261 SDP (Session Description Protocol) based on RFC 2327 and RFC 3551 Backward compatible with entities running RFC 2543 Interworking with H.323, ISDN, and SS7 Authentication and Outbound Registration (IMG can register with other entities). The IMG does not support inbound registration, since it is not applicable for Media Gateways. The IMG acts as a User Agent (UA) and can interoperate with SIP proxies. The IMG can act as a UAC (User Agent Client) or a UAS (User Agent Server). 3xx Redirection (e.g. 302 Moved Temporarily). Also see Supported 3xx Redirect Responses. Transcoding via SIP Transmission Control Protocol (TCP) Transport layer (single or multi-socket) Call Hold Session Timer Early Media (supporting 180/183 Session Progress) Reliable User Datagram Protocol (UDP) transport, with retransmissions Supported Response Messages 1xx, 2xx, 3xx, 4xx, 5xx, 6xx SIP Profiles A SIP Profile allows you to easily assign a number of SIP features to a Physical IMG. You create a SIP Profile and then assign profiles to a gateway in the External Gateway pane. Supported Methods 96 Product Description INVITE SUBSCRIBE/NOTIFY INFO UPDATE OPTIONS REGISTER (Outbound) CANCEL BYE PRACK reliable provisional responses SIP Extensions SIP Diversion Header Network asserted identity and privacy SIP Reason Header Session Timer SIP 3rd Party Call Control (3PCC) Non-Standard Tags in From/To Header Non-Standard Tags in R-URI Routing/Call Handling ENUM SIP Trunk Group Selection SIP-Based Load Balancing/Virtual IP Address SIP Proxy Handling SIP Redirect Server Support and 3xx responses This feature allows the IMG to respond to the 3XX class of SIP messages returned from a redirect server. DNS (Domain Name Server) Lookup The IMG can route SIP traffic to a remote entity based on the IP Address or the Host Name. The IMG supports having multiple DNS servers for redundancy and reliability purposes. See DNS Server and DNS Client panes. Re-origination This feature allows you to limit the number of INVITE re-transmission attempts (1-5 attempts). The number configured supersedes the standard # of retransmissions specified in RFC3261 (which is based on timers T1 and T2. The default is Re-transmit All. You enable this feature in the SIP Profile. SIP 3rd Party Call Control (3PCC) 97 IMG WebHelp SIP Gateway Busy Out The IMG can monitor the status of external SIP gateways by sending periodic SIP OPTIONS messages. If the gateway does not respond in a configured amount of time the IMG will mark the gateway as down and attempt to reroute the call to a different gateway. See SIP Busy Out. Remote party ID DTMF out-of-band transfer using INFO and SUBSCRIBE/NOTIFY Representing trunk groups in SIP Uniform Resource Identifiers (URIs) Media Symmetric NAT Traversal SIP Codec Negotiation Priority Selection Relay for Dual Tone Multi Frequency (DTMF) digits, including payload type negotiation (RFC 2833) T.38 Real Time Fax using SIP Note: If the remote side includes the fax maximum rate parameter in the SDP body of the INVITE message, the gateway returns the same rate in the response SDP. Modem Support Gain Control on SIP Channel Groups Call Hold G.729 AnnexB Selection Interworking Interworking with H.323, ISDN, and SS7 ITX (SPIROU) Support SS7 to SIP Calling Party Category (CPC) ANSI ISUP Originating Line Info Support SIP Carrier Identification Code SIP-T Network asserted identity and privacy Customizable SIP-to-SS7 ISUP Cause Codes Support of RFC 3666 Call Flows - SIP to PSTN Dialing Cantata Technology - IMG 1010 Printable WebHelp 98 Product Description Basic Support SIP Profiles Topic Location: Product Description > SIP > Basic Support A SIP Profile allows you to easily assign a number of SIP features to a Physical IMG. You create a SIP Profile and then assign profiles to a gateway in the External Gateway pane. The following features are configured/enabled using the SIP Profile pane. PRACK Support R-URI Header Tags Codec Priority 3xxx Redirect Support Loop Detection Re-Origination Attempts SIP Trunk Group Selection Append/Remove + for Headers INFO for SPIROU/ITX After you create a SIP Profile you can create the following objects to configure more SIP features that apply to the profile: SIP DTMF Support Use this pane to enable and configure SIP DTMF support to send a DTMF digit to another gateway. SIP From Header Tags Use this pane to configure how the IMG handles certain tags in the SIP From header. SIP Headers Use this pane to enable support for the following: Diversion Header Support Time Stamp Support P Charge Info P Asserted Info Remote Party ID SIP OPTIONS KeepAlive Use this pane to configure parameters for the SIP Busy Out feature. SIP Profile Timers Use this pane to configure SIP timers that apply to a specific SIP Profile. 99 IMG WebHelp SIP Proxy Use this pane to configure various settings for connection to a SIP Proxy. SIP Session Timer Use this pane to configure SIP Session Timer values. Cantata Technology - IMG 1010 Printable WebHelp 100 Product Description Authentication and Outbound Registration Topic Location: Product Description > SIP > Basic Support Cantata has implemented SIP Authentication which includes protective measures to prevent an active attacker from modifying and replaying SIP requests and responses. SIP authentication enables the Cantata platform to provide its own credentials (login/password based scheme) to other gateways. It ensures that only valid users can make calls through the Cantata platform. The cryptographic measures are used to ensure the authenticity of the SIP message and authenticate the originator of the message as being the IMG. SIP extends the HTTP WWW Authenticate and Authorization header field and their Proxycounterparts to include cryptographically strong signatures. Cantata Technology - IMG 1010 Printable WebHelp 101 IMG WebHelp Inbound SIP Codec Selection Topic Location: Product Description > SIP > Basic Support The IMG selects a vocoder from the offered media list by finding a match between the offered list and the IP Bearer Profile in use for the corresponding channel group. When an overlap condition exists between the list of vocoders in the IP Bearer Profile and the offered media list, preference is given to the vocoder order defined the incoming IP Bearer Profile. For example, consider the following media list offering G.711 ulaw, G.711 alaw, and iLBC: m=audio 5108 RTP/AVP 0 8 97 If the IMG IP Bearer Profile has the following vocoder priority configured: 1. G.729 2. G.723 3. iLBC 4. G.711 alaw Then the overlap of vocoders includes G.711 alaw and iLBC. G.711 alaw is the highest priority vocoder offered, but the highest priority vocoder in the IMG list is iLBC. As such, the IMG will give preference to its ordered list of vocoders and will respond offering only iLBC. It is important to note the IMG gives priority to the list of codecs defined in the IP Bearer Profile and does not respond with all vocoders in the overlap group, just the single vocoder that is the highest priority match for the IMG. Cantata Technology - IMG 1010 Printable WebHelp 102 Product Description Supported 3xx Redirect Responses Topic Location: Product Description > SIP > Basic Support 3xx responses give information about the user's new location, or about alternative services that might be able to satisfy the call. 300 Multiple Choices The address in the request resolved to several choices, each with its own specific location, and the user (or UA) can select a preferred communication end point and redirect its request to that location. 301 Moved Permanently The user can no longer be found at the address in the Request-URI, and the requesting client SHOULD retry at the new address given by the Contact header field (Section 20.10). The requester SHOULD update any local directories, address books, and user location caches with this new value and redirect future requests to the address(es) listed. 302 Moved Temporarily The requesting client SHOULD retry the request at the new address(es), given by the Contact header field (Section 20.10. The Request-URI of the new request uses the value of the Contact header field in the response. 305 Use Proxy 305 provides information for next hop to reach proxy server. The requested resource MUST be accessed through the proxy given by the Contact field. The Contact field gives the URI of the proxy. The recipient is expected to repeat this single request via the proxy. 305 (Use Proxy) responses MUST only be generated by UASs. 3xx is enable by default on the IMG and is configurable with the SIP SGP on a per gateway basis. Cantata Technology - IMG 1010 Printable WebHelp 103 IMG WebHelp Supported Standard Methods SIP INVITE Topic Location: Product Description > SIP > Supported Standard Methods The INVITE is a SIP method that specifies the action that the requestor (Calling Party) wants the server (Called Party) to take. The INVITE request contains a number of header fields. Header fields are named attributes that provide additional information about a message. The ones present in an INVITE include a unique identifier for the call, the destination address, Calling Party Address address, and information about the type of session that the requestor wishes to establish with the server. Example INVITE sip:[email protected] SIP/2.0 Via: SIP/2.0/UDP pc33.atlanta.com;branch=z9hG4bK776asdhds Max-Forwards: 70 To: Bob <sip:[email protected]> From: Alice <sip:[email protected]>;tag=1928301774 Call-ID: [email protected] CSeq: 314159 INVITE Contact: <sip:[email protected]> Content-Type: application/sdp Content-Length: 142 The first line of the text-encoded message contains the method name (INVITE). The lines that follow are a list of header fields. This example contains a minimum required set. The header fields are briefly described below: Via - contains the address (pc33.atlanta.com) at which Alice is expecting to receive responses to this request. It also contains a branch parameter that identifies this transaction. To - contains a display name (Bob) and a SIP or SIPS URI (sip:[email protected]) towards which the request was originally directed. From - also contains a display name (Alice) and a SIP or SIPS URI (sip:[email protected]) that indicate the originator of the request. This header field also has a tag parameter containing a random string (1928301774) that was added to the URI by the softphone. It is used for identification purposes. Call-ID - contains a globally unique identifier for this call, generated by the combination of a random string and the softphone's host name or IP address. The combination of the To tag, From tag, and Call-ID completely defines a peer-to-peer SIP relationship between Alice and Bob and is referred to as a dialog. CSeq - or Command Sequence, contains an integer and a method name. The CSeq number is incremented for each new request within a dialog and is a traditional sequence number. Contact - contains a SIP or SIPS URI that represents a direct route to contact Alice, usually composed of a username at a fully qualified domain name (FQDN). While an 104 Product Description FQDN is preferred, many end systems do not have registered domain names, so IP addresses are permitted. While the Via header field tells other elements where to send the response, the Contact header field tells other elements where to send future requests. Max-Forwards - serves to limit the number of hops a request can make on the way to its destination. It consists of an integer that is decremented by one at each hop. Content-Type - contains a description of the message body (not shown). Content-Length - contains an octet (byte) count of the message body. Copyright (C) The Internet Society (2004). All Rights Reserved Re-INVITE The INVITE method is used to establish media sessions between User Agents. The RE-INVITE message permits the IMG to change parameters of an existing or pending call. The IMG supports the following: RE-INVITE messages that change the port to which media should be sent. Media stream on hold (connection address is zero). RE-INVITE messages that change the connection address or media type. Initial INVITE messages on hold. RE-INVITE messages for FAX (T.38 and Bypass). Cantata Technology - IMG 1010 Printable WebHelp 105 IMG WebHelp UPDATE Method Topic Location: Product Description > SIP > Supported Standard Methods Overview The UPDATE method allows a UAC to update parameters of a session, such as the SDP and session timers. The UPDATE has no impact on the state of a dialog. In that sense, it is like a re-INVITE, except that it can be sent before the initial INVITE has been completed. This makes it very useful for updating session parameters within early dialogs. The UPDATE method allows a greater control over a SIP session including, but not limited to, the following parameters: SDP (for example, to set the media on hold during early media) Session timers (for example, to adjust call duration in a prepaid application) IMG Support The IMG supports the following for SIP UPDATE: an UPDATE request that is received before or after the initial INVITE transaction is completed and when a dialog exists (early or confirmed), in accordance with RFC 3261. the validation of an SDP contained in an UPDATE follows the existing restrictions of the offer/answer model (RFC 3264). The IMG will reject an UPDATE request that is meant as a FAX re-INVITE. Although it is possible, the RFC does not recommend the use of the UPDATE method in this fashion. RFC 3311 The Session Initiation Protocol (SIP) UPDATE Method Configuration The SIP UPDATE method is accepted without user intervention and cannot be configured or disabled. Call Flows The following calls flows are a few possible transactions. For more call flows refer to RFC 3311 and RFC 3261. IMG handles a UAS UPDATE transaction while in a UAS INVITE transaction 106 Product Description IMG initiates a UAC UPDATE transaction while in a UAS INVITE transaction IMG handles a UAS UPDATE transaction while in a UAC INVITE transaction IMG initiates a UAC UPDATE transaction while in a UAC INVITE transaction 107 IMG WebHelp IMG handles a UAS UPDATE transaction while in answered state IMG initiates a UAC UPDATE transaction while in answered state Cantata Technology - IMG 1010 Printable WebHelp 108 Product Description INFO Method Topic Location: Product Description > SIP > Supported Standard Methods The purpose of the INFO message is to carry application level information along the SIP signaling path. The INFO method is not used to change the state of SIP calls, or the parameters of the sessions SIP initiates. It merely sends optional application layer information, generally related to the session. It is necessary that the mid-session signaling information traverse the post session setup SIP signaling path. This is the path taken by SIP re-INVITEs, BYEs and other SIP requests that are tied to an individual session. This allows SIP proxy servers to receive, and potentially act on, the mid-session signaling information. Example Uses The following are a few of the potential uses of the INFO message: - Carrying mid-call PSTN signaling messages between PSTN gateways. - Carrying DTMF digits generated during a SIP session. - Carrying wireless signal strength information in support of wireless mobility applications. - Carrying account balance information. - Carrying images or other non streaming information between the participants of a session. Copyright (C) The Internet Society (2004). All Rights Reserved For more information see RFC 2976 - The SIP INFO Method. Related Topics INFO Method for DTMF Pass through ‘+’ sign in the user part of URI Cantata Technology - IMG 1010 Printable WebHelp 109 IMG WebHelp SUBSCRIBE/NOTIFY Methods Topic Location: Product Description > SIP > Supported Standard Methods Overview The ability to request asynchronous notification of events proves useful in many types of SIP services for which cooperation between end-nodes is required. Examples of such services include automatic callback services (based on terminal state events), buddy lists (based on user presence events), message waiting indications (based on mailbox state change events), and PSTN and Internet Internetworking (PINT) [2] status (based on call state events). The general concept is that entities in the network can subscribe to resource or call state for various resources or calls in the network, and those entities (or entities acting on their behalf) can send notifications when those states change. Copyright (C) The Internet Society (2004). All Rights Reserved SUBSCRIBE The SUBSCRIBE method is used to request current state and state updates from a remote node. SUBSCRIBE requests SHOULD contain an "Expires" header. This expires value indicates the duration of the subscription. In order to keep subscriptions effective beyond the duration communicated in the "Expires" header, subscribers need to refresh subscriptions on a periodic basis using a new SUBSCRIBE message on the same dialog. If no "Expires" header is present in a SUBSCRIBE request, the implied default is defined by the event package being used. NOTIFY Copyright (C) The Internet Society (2004). All Rights Reserved NOTIFY messages are sent to inform subscribers of changes in state to which the subscriber has a subscription. Subscriptions are typically put in place using the SUBSCRIBE method; however, it is possible that other means have been used. Copyright (C) The Internet Society (2004). All Rights Reserved Call Flow A typical flow of messages would be: Subscriber Notifier |-----SUBSCRIBE---->| |<-------200--------| |<------NOTIFY----- | Request state subscription Acknowledge subscription Return current state information |--------200------->| |<------NOTIFY----- | Return current state information |--------200------->| Subscriptions are expired and must be refreshed by subsequent SUBSCRIBE messages. Copyright (C) The Internet Society (2004). All Rights Reserved 110 Product Description For more information see 3265 - Session Initiation Protocol (SIP)-Specific Event Notification. Related Topics SIP SUBSCRIBE/NOTIFY Method for DTMF Cantata Technology - IMG 1010 Printable WebHelp 111 IMG WebHelp SIP PRACK Topic Location: Product Description > SIP > Supported Standard Methods Brief Description Improves network reliability and supports additional call flows. RFC 3262 - Reliability of Provisional Responses in the Session Initiation Protocol (SIP) Overview There are two types of responses defined by SIP that are provisional and final. Final responses convey the result of the request processing and are sent reliably. There are certain scenarios in which the provisional SIP responses must be delivered reliably. For example, in a SIP/PSTN inter-working scenario, a loss of 180 or 183 messages cannot be afforded. To solve this problem, the SIP PRACK method guarantees reliable and ordered delivery of provisional responses in SIP. Configuration SIP Profile IP Network Element Diagram - SIP PRACK Handshake UAC - UAS Behaviour The following table shows the overall behavior of UAS and UAC with various SGP configuration combinations. UAC UAS SGP: PRACK Disabled SGP: PRACK Disabled Normal Call SGP: PRACK Disabled SGP: PRACK Supported Normal Call SGP: PRACK Disabled SGP: PRACK Require Call Rejected SGP: PRACK SGP: PRACK Disabled Normal Call 112 Call Processing Product Description Supported SGP: PRACK Supported SGP: PRACK Supported PRACK Call SGP: PRACK Supported SGP: PRACK Require PRACK Call SGP: PRACK Require SGP: PRACK Disabled Call Rejected SGP: PRACK Require SGP: PRACK Supported PRACK Call SGP: PRACK Require SGP: PRACK Require PRACK Call Call Tracing Success 16:32:35.762 CALL(SIP) (00:0004:00) SENT 183 Session Progress Reliable (100rel) to 10.129.45.102:8000 UDP 16:32:35.782 CALL(SIP) (00:0004:00) RCVD PRACK from 10.129.45.102:8000 Cseq:2 with Via sent-by: 10.129.45.102 UDP 16:32:35.782 CALL(SIP) (00:0004:00) SENT 200 OK PRACK to 10.129.45.102:8000 UDP Failure 21:16:47.845 CALL(SIP) (01:00004:00) SENT 421 Extension Required [PRACK support is required] to 10.129.45.104:5060 Cseq:1 21:18:09.286 CALL(SIP) (01:00005:00) SENT 420 Bad Extension [Unsupported SIP request arrived at L3UA-TUC] to 10.129.45.104:5060 Cseq:1 Troubleshooting If you are experiencing problems with this feature, check the following: Make sure PRACK is enabled in the SIP SGP The External Gateway must support PRACK. Make sure the correct SIP SGP is assigned to the External Gateway Cantata Technology - IMG 1010 Printable WebHelp 113 IMG WebHelp SIP PRACK Call Flows Topic Location: Product Description > SIP > Supported Standard Methods Changes to Basic Call Flow with PRACK enabled The call flow on the left highlights the changes when PRACK is enabled, as compared to the call flow on the right without PRACK enabled. UAS Honors UAC’s Preference This call flow shows the call flow when UAS and UAC are set to PRACK Supported option. UAS Agrees to UAC’s Enforcement This call flow shows when UAS and UAC are set to PRACK Require option. 114 Product Description UAS Ignores UAC’s Preference This call flow shows the call flow when UAS is PRACK Supported and UAC is PRACK Disable. UAS Rejects UAC’s Enforcement This call flow shows the call flow when UAS is PRACK Require and UAC is PRACK Disable. UAS Insists UAC MUST Support 100rel This call flow shows the call flow when UAS is PRACK Disable and UAC is PRACK Require. 115 IMG WebHelp UAC Insists on Reliable Delivery of Provisional Responses This call flow shows when UAS is configured with PRACK Require option. IMG Acts as UAC and UAS 116 Product Description Cantata Technology - IMG 1010 Printable WebHelp 117 IMG WebHelp SIP Extensions SIP Diversion Header Topic Location: Product Description > SIP > SIP Extensions 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. Scenarios SIP Call Forwarding Scenario SIP-SS7 Call Forwarding Scenario IP> 14:30:24.912 SIP (W) ---> [89.254.79.195, 41057] INVITE sip:[email protected]:-1 SIP/2.0 Session-Expires: 1800 CSeq: 1 INVITE Call-ID: [email protected] Supported: path, timer Diversion: <sip:[email protected]:5060>;reason=userbusy;privacy="off" Via: SIP/2.0/UDP 89.254.79.195:5060;wlsscid=310b48bd18;branch=z9hG4bK452276d682cebe5 fc121895fb70a25d2 From: <sip:[email protected]>;tag=c21207c1 Content-Type: application/sdp Allow: INVITE, BYE, REGISTER, ACK, OPTIONS, CANCEL, SUBSCRIBE, NOTIFY, INFO, UPDATE To: sip:[email protected]:5060 Contact: <sip:89.254.79.195:5060;transport=udp;wlsscid=310b48bd18;appsession id=app-p3d0hkwjl3j2> Content-Length: 309 User-Agent: Cantata-SIP/10.3.3.171 VPABX-IMG2 1 Expires: 300 Max-Forwards: 70 118 Product Description v=0 o=Cantata_SDP 0 0 IN IP4 89.254.79.209 s=Cantata-SIP c=IN IP4 89.254.79.210 t=0 0 m=audio 8188 RTP/AVP 0 8 4 18 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729/8000 a=rtpmap:4 G723/8000 a=bitrate:6.3 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=silenceSupp:off - - - ISDN-SIP Call Forwarding Scenario SIP-ISDN Call Forwarding Scenario Cantata Technology - IMG 1010 Printable WebHelp 119 IMG WebHelp SIP Reason Header Topic Location: Product Description > SIP > SIP Extensions 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. Call Tracing The Reason Header text is to be printed out in a Call Trace for the following incoming SIP messages: BYE 4XX, 5XX, and 6XX CANCEL NOTE: In case of multiple Reason Headers presented in the incoming SIP message, only the first Reason Header is decoded. Benefits This feature is useful for debugging purpose, particularly if there is a call failure in SIP to SS7 traffic. Implementation Cause Number 1 (404 message) When a call is generated from SIP side and SS7 receives an IAM and releases the call with cause number 1, the IMG then would send a 404 message with cause indicating Unallocated (unassigned) number. Call Flow Call Trace <--- [10.129.39.123, 5060 <- 10.129.39.59, 5060] SIP/2.0 404 Not Found Call processing released Via: SIP/2.0/UDP 10.129.39.123:5060;branch=z9hG4bK-d87543672bb759901c9e2a-1--d87543-;rport;received=10.129.39.1 Contact: <sip:10.129.39.59:5060> 23 Call-ID: 2b61265d2e589e06ZjIzZDY3ZjU4ODA3NmRhODdmNGI4Y2M0NGRmNTYyMTY. From: "Boston"<sip:[email protected]>;tag=f818c458 120 Product Description To: "508"<sip:[email protected]>;tag=a94c095b773be1dd6e8d668a785a9c8449dc CSeq: 1 INVITE Server: Cantata-SIP/10.3.2.22 Boston 0 Reason: Q.850 ;cause=1 ;text="Unallocated (unassigned) number" Content-Length: 0 Cause Number 17 (486 message) The 486 message with cause 17 that indicates User Busy is sent out by IMG to SIP when SS7 side releases the call with cause 17. Call Flow Call Trace <--- [10.129.39.123, 5060 <- 10.129.39.59, 5060] SIP/2.0 486 Busy Here Call processing released Via: SIP/2.0/UDP 10.129.39.123:5060;branch=z9hG4bK-d87543af44ae69a320e04a-1--d87543-;rport;received=10.129.39.1 Contact: <sip:10.129.39.59:5060> 23 Call-ID: 1c214262d2299f3cZjIzZDY3ZjU4ODA3NmRhODdmNGI4Y2M0NGRmNTYyMTY. From: "Boston"<sip:[email protected]>;tag=244d4425 To: "508"<sip:[email protected]>;tag=a94c095b773be1dd6e8d 668a785a9c84c527 CSeq: 1 INVITE Server: Cantata-SIP/10.3.2.22 Boston 0 Reason: Q.850 ;cause=17 ;text="User busy" Content-Length: 0 Cause Number 16 (BYE message) Cause number 16 is normal call clearing. Call Flow Call Trace <--- [10.129.39.123, 5060 <- 10.129.39.59, 5060] BYE sip:[email protected]:5060 SIP/2.0 121 IMG WebHelp Via: SIP/2.0/UDP 10.129.39.59:5060;rport;branch=z9hG4bK-3a95-46623-19995361 Call-ID: [email protected] CSeq: 2 BYE Max-Forwards: 70 To: <sip:[email protected]:5060>;tag=8262313b From: <sip:[email protected]>;tag=95ffcd055e0f78f7d5d397020e89288d2b07 User-Agent: Cantata-SIP/10.3.2.22 Boston 0 Reason: Q.850 ;cause=16 ;text="Normal call clearing" Content-Length: 0 Cause Number 3 (404 message) If the user dials an incorrect number that is not in the route table the IMG will reject the call and send a 404 Not Found to the SIP side. Call Flow Call Trace <--- [10.129.39.123, 5060 <- 10.129.39.59, 5060] SIP/2.0 404 Not Found Call processing released Via: SIP/2.0/UDP 10.129.39.123:5060;branch=z9hG4bK-d8754347486a49a1277175-1--d87543-;rport;received=10.129.39.1 23 Contact: <sip:10.129.39.59:5060> Call-ID: 3355d752f5739754ZjIzZDY3ZjU4ODA3NmRhODdmNGI4Y2M0NGRmNTYyMTY. From: "Boston"<sip:[email protected]>;tag=2816b75a To: "999"<sip:[email protected]>;tag=a94c095b773be1dd6e8d668a785a9c84de15 CSeq: 1 INVITE Server: Cantata-SIP/10.3.2.37 Boston 0 Reason: Q.850 ;cause=3 ;text="No route to destination" Content-Length: 0 Cause Number 1 (404 message) 122 Product Description In case the user dials correct number but incoming translation table has wrong number, then IMG would reject the call and send a 404 Not Found to the SIP side. Call Flow Call Trace <--- [10.129.39.123, 5060 <- 10.129.39.59, 5060] SIP/2.0 404 Not Found Call processing released Via: SIP/2.0/UDP 10.129.39.123:5060;branch=z9hG4bK-d8754347486a49a1277175-1--d87543-;rport;received=10.129.39.1 23 Contact: <sip:10.129.39.59:5060> Call-ID: 3355d752f5739754ZjIzZDY3ZjU4ODA3NmRhODdmNGI4Y2M0NGRmNTYyMTY. From: "Boston"<sip:[email protected]>;tag=2816b75a To: "999"<sip:[email protected]>;tag=a94c095b773be1dd6e8d668a785a9c84de15 CSeq: 1 INVITE Server: Cantata-SIP/10.3.2.37 Boston 0 Reason: Q.850 ;cause=1 ;text="Unallocated (unassigned) number" Content-Length: 0 SIP to SIP In the case of SIP to SIP traffic, the Reason header field is usually not needed in responses because the status code and the reason phrase already provide sufficient information, according to RFC 3326. However, the Reason Header is included for BYE, 4XXs, 5XXs, and 6XXs. Please note that CANCEL message in the SIP to SIP traffic does not include the Reason header field. Call Flow Call Trace <--- [10.129.39.123, 5060 <- 10.129.39.59, 5060] BYE sip:[email protected]:5060 SIP/2.0 Via: SIP/2.0/UDP 10.129.39.59:5060;rport;branch=z9hG4bK-2701-1786-19997-394 Call-ID: [email protected] CSeq: 2 BYE Max-Forwards: 70 123 IMG WebHelp To: <sip:[email protected]:5060>;tag=d47d7510 From: <sip:[email protected]>;tag=95ffcd055e0f78f7d5d397020e89288d708e User-Agent: Cantata-SIP/10.3.2.37 Boston 0 Reason: SIP ;cause=16 ;text="Normal call clearing" Content-Length: 0 487 Message In the case below, where SIP sends an INVITE message and then sends CANCEL, the IMG sends a 487 Request Terminated in response to the CANCEL message. Call Flow Call Trace <--- [10.129.39.123, 5070 <- 10.129.39.59, 5060] SIP/2.0 487 Request Terminated Via: SIP/2.0/UDP 10.129.39.123:5070;branch=z9hG4bK-675e-1160585843-1998810-129-39-123;received=10.129.39.123 Contact: <sip:10.129.39.59:5060> Call-ID: [email protected] From: sipp <sip:[email protected]:5070>;tag=1 To: sut <sip:[email protected]:5060>;tag=a94c095b773be1dd6e8d668a785a9c84e50d CSeq: 1 INVITE Server: Cantata-SIP/10.3.2.37 Boston 0 Reason: SIP ;cause=487 ;text="Request Terminated" Content-Length: 0 Cantata Technology - IMG 1010 Printable WebHelp 124 Product Description SIP Privacy Topic Location: Product Description > SIP > SIP Extensions With this feature the IMG supports SIP Privacy (RFC 3325), which is a way for trusted network elements operated by the service providers (for example SIP proxy servers) to communicate the identity of the subscribers to such a service, yet also need to withhold this information from entities that are not trusted when necessary. Such networks typically assume some level of transitive trust amongst providers and the devices they operate. Copyright (C) The Internet Society (2002). All Rights Reserved. RFC RFC 3325 Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks. Headers P-Asserted-Identity The P-Asserted-Identity header field is used among trusted SIP entities (typically intermediaries) to carry the identity of the user sending a SIP message as it was verified by authentication. A proxy server which handles a message can, after authenticating the originating user in some way (for example: Digest authentication), insert such a P-Asserted-Identity header field into the message and forward it to other trusted proxies. A proxy that is about to forward a message to a proxy server or UA that it does not trust MUST remove all the P-Asserted-Identity header field values if the user requested that this information be kept private. Copyright (C) The Internet Society (2002). All Rights Reserved. For more information on the handling of the P-Asserted-Identity header by proxies (section 5) and User Agents (section 8) see the RFC 3325. P-Preferred-Identity Header The P-Preferred-Identity header field is used from a user agent to a trusted proxy to carry the identity the user sending the SIP message wishes to be used for the P-AssertedHeader field value that the trusted element will insert. Copyright (C) The Internet Society (2002). All Rights Reserved. Remote Party ID The SIP Remote-Party-ID header identifies the calling party and includes user, party, screen and privacy headers that specify how a call is presented and screened. The new header contains a URL and an optional display name that identifies a user. A 125 IMG WebHelp valid Remote-Party-ID header may be either a SIP URL or a TEL URL. See the sections Remote-Party-ID Syntax and Screening and Presentation Information for more information on the syntax of the new header. The following example shows representative Remote-Party-ID headers, including user, party, screen, and privacy. Call Flows Cantata Technology - IMG 1010 Printable WebHelp 126 Product Description Called Party Resolution SIP Redirect Server Support Topic Location: Product Description > SIP > Called Party Resolution This feature allows the IMG to respond to the 3XX class of SIP messages returned from a redirect server. 3xx responses provide information about a user's new location, or alternative services that may be able to satisfy the call. This feature is based on RFC 3261 section 8.1.3.4 and RFC 2543. In a SIP network it is very common to have a re-direct server which determines where to route the call. The redirect server may reply to the IMG with a 300 response with a list of contacts to try. The IMG will try each one of those contacts one at a time, until the call is completed, to a maximum of 10 attempts. The IMG will only accept redirects to another endpoint in the SIP network. The endpoint does not have to be one of the configured SIP external gateways. This feature is enabled by default in the SIP Profile. Notes The maximum number of redirects is 10. Once a contact has responded with a 180 Ringing or 183, the IMG will not make any more redirect attempts The same IP Profile is used for all attempts. Not Supported Simultaneous redirects 3xx Responses for Registration Requests Redirection to another Channel Group 380 Responses (they will be mapped to 410 Gone error code and released) 305 Response (they will be mapped to 410 Gone error code and released) Location changes are not saved internally The IMG cannot be redirected back to the PSTN 3XX Response Mapping If this feature is not enabled, the IMG will map the 3xx responses to 4xx responses, as shown below: Redirection (3xx) Response Maps to 4xx (client error) response 300 Multiple choices 410 Gone 301 Moved Permanently 410 Gone 127 IMG WebHelp 302 Moved Temporarily 480 Temporarily Unavailable 305 Use Proxy 410 Gone 380 Alternative Service 410 Gone any other 3xx response 410 Gone Cantata Technology - IMG 1010 Printable WebHelp 128 Product Description Example Call Flow: SIP Redirect Topic Location: Product Description > SIP > Called Party Resolution Cantata Technology - IMG 1010 Printable WebHelp 129 IMG WebHelp SIP Proxy Handling Topic Location: Product Description > SIP > Called Party Resolution 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). A SIP Proxy receives SIP requests from a client, even though it may not be the server resolved by the Request-URI. Typically, a UA is manually configured with an outbound proxy, or can learn about one through auto-configuration protocols. You can configure one SIP Outbound Proxy Server for each external SIP gateway using the SIP Proxy pane under a SIP Profile and then assign that profile to the External Gateway. References RFC 3261 Session Initiation Protocol RFC 2543 Session Initiation Protocol UA Supported Outbound proxy handling (non-redundant) Re-invite and 3xx Redirect to outbound proxy Outbound registration to outbound proxy Cantata Technology - IMG 1010 Printable WebHelp 130 Product Description EXAMPLE SIP Call: Using an Outbound Proxy Topic Location: Product Description > SIP > Called Party Resolution Example of Eyebeam UAC sending an SIP Request to an outbound proxy Outbound proxy: 10.129.39.37:5060 [IMG has no equivalent config param] Domain: 10.129.39.38:5060 [IMG equivalent is remote gateway] Dialed number: [email protected] [IMG equivalent is remote gateway] Client IP address: 10.129.39.115:5062 [IMG equivalent is SIP stack IP:port] SENDING TO: 10.129.39.37:5060 INVITE sip:[email protected];transport=udp SIP/2.0 To: <sip:[email protected]> From: 33871<sip:[email protected]>;tag=7224787d Via: SIP/2.0/UDP 10.129.39.115:5062;branch=z9hG4bK-d87543-426271217-1-d87543-;rport Call-ID: b93d6c09661e5564 CSeq: 1 INVITE Contact: <sip:[email protected]:5062;transport=udp> Max-Forwards: 70 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO Content-Type: application/sdp User-Agent: eyeBeam release 3004w stamp 16863 Content-Length: 182 v=0 o=- 5790011 5790033 IN IP4 10.129.39.115 s=eyeBeam c=IN IP4 10.129.39.115 t=0 0 m=audio 7244 RTP/AVP 18 101 a=fmtp:101 0-15 a=rtpmap:101 telephone-event/8000 a=sendrecv Cantata Technology - IMG 1010 Printable WebHelp 131 IMG WebHelp Media SIP Fax/Modem Support Topic Location: Product Description > SIP > Media Initially, the IMG establishes a normal voice call using an audio codec. The IMG negotiates T.38 support once the voice path is established. Case where the IMG is terminating a fax call: Once a fax data mode has been detected at the IP bearer level, SIP will send a REINVITE message to the distant end. The IMG supplies a T.38 port and parameters in a SIP RE-INVITE SDP and waits for the remote SIP gateway to accept with an OK including a corresponding SDP. Case where the IMG is originating a fax call: Once a fax data mode has been detected at the IP bearer level, SIP will accept a REINVITE message from the distant end. The IMG will reply with a Fax port in a SIP 200 OK SDP and will wait for the remote SIP gateway to accept with an ACK. T.38 or fax bypass modes are supported. The IMG allows G.711 A-Law or G.711 u-Law only for fax/modem bypass codecs. RTP redundancy levels will apply to fax bypass packets (RTP G.711 packets), but not to T.38 packets. Fax Redundancy level setting applies only to T.38 fax relay packets (not to RTP voice or fax bypass packets). Fallback to Fax Bypass 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 neither a T.38 fax nor a Bypass fax can be established in a fax fallback scenario, the IMG allows the voice call to proceed as if no negotiation had happened. Cantata Technology - IMG 1010 Printable WebHelp 132 Product Description SIP CODEC Negotiation Priority Selection Topic Location: Product Description > SIP > Media This feature allows you to configure whether the IMG or the remote gateway takes priority when selecting a codec. Example: If the IMG has a CODEC list of: g711u g711a g729 and a remote gateway offers: g729 g711u If the Codec Negotiation Priority is set to Local, the IMG will answer with g711u. If the Codec Negotiation Priority is set to Remote, the IMG will answer with g729. Benefits The feature gives you the flexibility to choose CODEC priority on either IMG or the far end gateway. Configuration You configure CODEC Negotiation Priority to either Local or Remote in the SIP Profile pane. Cantata Technology - IMG 1010 Printable WebHelp 133 IMG WebHelp Early Media Topic Location: Product Description > SIP > Media Early media is the ability of two SIP User Agents to communicate before a SIP call is actually established. Typically, this scenario occurs when the called party is a PSTN gateway. Before the call is set up, the gateway might provide in-band tones or announcements that inform the caller of the call progress. Early media can involve the transfer of media from caller to callee. Within the PSTN, forward channels can be established to convey DTMF signaling to select a final destination to call. This feature can be used to access Interactive Voice Response (IVR) systems “behind” 800 numbers. Implementation connects the media path prior to the 200 OK message. converts the SS7 Call Progress (CPG) message to a 183 response message with SDP. supports pre-answer DTMF and announcements. When the called party wishes to send early media to the caller, the called party sends a 183 response to the caller. That response contains the SDP. When the caller receives the 183 response, it suppresses any local alerting of the user (for example, audible ring tones or pop-up window) and plays out media that it receives. If the call is ultimately rejected, that called party generates a non-2xx final response. When the caller receives this response, the caller stops playing out or sending media. If the call is accepted, the called party generates a 2xx response and sends that to the caller. Media transmission continue as before. Cantata Technology - IMG 1010 Printable WebHelp 134 Product Description Routing/Call Handling SIP ENUM Topic Location: Product Description > SIP > Routing/Call Handling The IMG supports ENUM E2U+sip to resolve an ENUM telephone number into a SIP URI. With ENUM native SIP users, even at different VoIP service providers, can call each other directly without ever touching a PSTN service which can result in faster connection times and lower phone charges. ENUM facilitates the interconnection of systems that rely on telephone numbers with those that use URIs to route transactions. E.164 is the ITU-T standard international numbering plan, under which all globally-reachable telephone numbers are organized. RFC RFC 3764 enumservice registration for Session Initiation Protocol (SIP) Addresses-ofRecord Benefits This feature is required when: a user is calling from the PSTN through a PSTN-SIP gateway and the gateway is expected to map routing information from the PSTN directly on to SIP signaling. a native SIP user intentionally initiates a call addressed to an E.164 number. Although this task is also accomplished by SIP Proxy Servers, there is value in adding the ENUM behavior in the IMG gateway as a way to minimize the proxy’s activities and centralize the number translation functions in the UA. Application servers may initiate SIP calls destined to end users and transiting through the IMG. Configuration 1. Configure ENUM servers with the ENUM Server pane. 2. Configure a SIP Channel Group. 135 IMG WebHelp 3. Configure a IP Network Element 4. Configure a Route Table. 5. Add a Route Entry with the Outgoing Channel Group pointing to the ENUM Channel Group. Call Tracing Indication of Feature function: CLI will display a query being sent to the ENUM Server as well as the response from the ENUM Server. Indication of Feature rejection: CLI will display an error that the ENUM Query has failed to the following: a) Entry does not exist. b) Query timed out Cantata Technology - IMG 1010 Printable WebHelp 136 Product Description SIP-Based Load Balancing/Virtual IP Address Topic Location: Product Description > SIP > Routing/Call Handling This feature allows you to distribute SIP traffic between IMGs configured as “SIP Servers” using Virtual IP Addresses and a SIP load balancer. The IMG allows you to configure a Virtual IP addresses (VIP) in addition to the existing Real IP address. The IP address set allows SIP calls to be terminated concurrently on any of the IP addresses, real or virtual. The deployment of multiple IMG products sharing Virtual IP addresses creates in effect a set of redundant SIP signaling paths. Accounting for capacity and the balancing algorithm are configured on the Load Balancer, not the IMG. Diagram - SIP-Based Load Balancing Load balancers can create pools of IMG gateways, all sharing the same Virtual IP addresses. The diagram below shows the relationship between these network endpoints. Load Balancers Load balancers automatically detect when a server is unavailable using “heartbeats”, either through ICMP Ping or SIP OPTIONS. Load balancing takes place between the set of IMGs reachable through such heartbeats. This provides increased VoIP network availability by routing traffic through “healthy” signaling paths. It also reduces the number of re-transmitted SIP INVITEs and consequently increases the overall call completion rate. This activity is commonly described using one of the following terms: Server Load Balancing (SLB) Direct Server Response (DSR) Describe Switchback Routing (DSR) The use of Virtual IP addresses on the IMG enables seamless integration of load balancers in a Cantata solution. 137 IMG WebHelp Load balancers are not SIP-specific, however they are SIP-aware in order to route subsequent transactions for an existing call to the correct gateway/IMG. Load balancers have redundant features and can be geographically distributed. NOTE: A SIP proxy could also be used to load balance SIP traffic, however it would use the actual IMG IP address and not the MAC address; therefore, the Virtual IP Address could not be used. Related Topics Configuring SIP-Based Load Balancing SIP Virtual Address Network Interface Cantata Technology - IMG 1010 Printable WebHelp 138 Product Description SIP Trunk Group Selection Topic Location: Product Description > SIP > Routing/Call 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. Incoming Originating Trunk Group (OTG) Selection When the OTG field is included in the “From” header the IMG will use this trunk group as the incoming trunk group to determine which route table to use. The OTG will also be able to be added to the “From” header in an outbound SIP INVITE (the OTG will have the A side trunk group name). The IMG extracts the OTG from the SIP "From" header and passes it in the initial Setup. If an OTG is found, the IMG will use that channel group instead of the one that came from the lookup table in the SIP process. Incoming Destination Trunk Group (DTG) Selection When the DTG is received in the request-URI the IMG will skip the mid-call router and use the DTG that was received as the outbound channel group. When the IMG is about to perform routing for the outbound side, it will look for the DTG from the same location as the Calling Party Number. If the DTG is valid, the call will then use the channel group that corresponds to that DTG instead of performing a routing lookup Outgoing Destination Trunk Group (DTG) Selection On an outgoing invite, the OTG that was received from the incoming call will take precedence over the internal IMG incoming channel group name if it was a SIP call (for any other inbound protocol, the OTG would be the incoming Trunk Group Name). This OTG is then appended in the “From” header of the outbound invite. Cantata Technology - IMG 1010 Printable WebHelp 139 IMG WebHelp SIP 3PCC (Third Party Call Control) Topic Location: Product Description > SIP > Routing/Call Handling The IMG supports the establishment of a session by a third party "controller" such as an application server or a Session Border Controller (SBC), allowing the IMG to integrate with services like auto attendant, conferencing, and unified messaging. Delayed Media The Cantata platform supports delayed media to allow interworking with third party call control applications (3PCC) in accordance with RFC 3725. Delayed media is implemented for inbound calls. The IMG accepts INVITE and RE-INVITE messages with or without SDP or with a held SDP. The IMG accepts SDP in the SIP ACK message. RFC RFC 3725 - Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP) Benefits Seamless IMG integration with SIP application servers, enabling the IMG to be part of a larger service set. More robust interoperability with other application-specific SIP devices such as for operator interaction, fax servers, media servers. Avoid use of a front-end SIP device to delay media prior to SIP signaling reaching the IMG. Diagram 140 Product Description Related Topics SIP 3PCC Call Flows Cantata Technology - IMG 1010 Printable WebHelp 141 IMG WebHelp SIP 3PCC Call Flows Topic Location: Product Description > SIP > Routing/Call Handling The IMG supports the following call flows for SIP 3PCC. NOTE: A and B are assumed to be IMG gateways. RFC Recommendations Call Flow 1 represents the simplest and the most efficient flow. This flow SHOULD be used by a controller if it knows with certainty that user B is actually an automata that will answer the call immediately. This is the case for devices such as media servers, conferencing servers, and messaging servers, for example. Since we expect a great deal of third party call control to be to automata, special casing in this scenario is reasonable. For calls to unknown entities, or to entities known to represent people, it is RECOMMENDED that Call Flow 4 be used for third party call control. Call Flow 3 MAY be used instead, but it provides no additional benefits over Call Flow 4. However, Call Flow 2 SHOULD NOT be used, because of the potential for infinite ping-ponging of re-INVITEs. Several of these flows use a "black hole" connection address of 0.0.0.0. This is an IPv4 address with the property that packets sent to it will never leave the host which sent them; they are just discarded. Those flows are therefore specific to IPv4. For other network or address types, an address with an equivalent property SHOULD be used. In most cases, including the recommended flows, user A will hear silence while the call to B completes. This may not always be ideal. It can be remedied by connecting the caller to a music-on-hold source while the call to B occurs. Copyright (C) The Internet Society (2004). All Rights Reserved Call Flow 1: Call setup with Delayed Media via Third-Party Call Controller This flow is simple, requires no manipulation of the SDP by the controller, and works for any media types supported by both endpoints. However, it has a serious timeout problem. User B may not answer the call immediately. The result is that the controller cannot send the ACK to A right away. This causes A to retransmit the 200 OK response periodically. As specified in RFC 3261 Section 13.3.1.4, the 200 OK will be retransmitted for 64*T1 seconds. If an ACK does not arrive by then, the call is considered to have failed. This limits the applicability of this flow to scenarios where the controller knows that B will answer the INVITE immediately. Copyright (C) The Internet Society (2004). All Rights Reserved For more details on this call flow see RFC 3725. 142 Product Description Call Flow 2: Call Setup with Hold An alternative flow, Flow II, is shown <below>. The controller first sends an INVITE to user A (1). This is a standard INVITE, containing an offer (sdp1) with a single audio media line, one codec, a random port number (but not zero), and a connection address of 0.0.0.0. This creates an initial media stream that is "black holed", since no media (or RTCP packets [8]) will flow from A. The INVITE causes A's phone to ring. Copyright (C) The Internet Society (2004). All Rights Reserved For more details on this call flow see RFC 3725. 143 IMG WebHelp Call Flow 3: Call Setup and Subsequent Hold with Delayed Media This flow has many benefits. First, it will usually operate without any spurious retransmissions or timeouts (although this may still happen if a re-INVITE is not responded to quickly). Secondly, it does not require the controller to guess the media that will be used by the participants. There are some drawbacks. The controller does need to perform SDP manipulations. Specifically, it must take some SDP, and generate another SDP which has the same media composition, but has connection addresses equal to 0.0.0.0. This is needed for message 3. Secondly, it may need to reorder and trim SDP X, so that its media lines match up with those in some other SDP, Y. Thirdly, the offer from B (offer2) may have no codecs or media streams in common with the offer from A (offer 1). The controller will need to detect this condition, and terminate the call. Finally, the flow is far more complicated than the simple and elegant Call Flow 1. Copyright (C) The Internet Society (2004). All Rights Reserved For more details on this call flow see RFC 3725. 144 Product Description Call Flow 4: Call Setup with SDP but no media line Call Flow 4 shows a variation on Flow III that reduces its complexity. The actual message flow is identical, but the SDP placement and construction differs. The initial INVITE (1) contains SDP with no media at all, meaning that there are no m lines. This is valid, and implies that the media makeup of the session will be established later through a reINVITE [4]. Once the INVITE is received, user A is alerted. When they answer the call, the 200 OK (2) has an answer with no media either. This is acknowledged by the controller (3). The flow from this point onwards is identical to Call Flow 3. However, the manipulations required to convert offer2 to offer2', and answer2' to answer2, are much simpler. Indeed, no media manipulations are needed at all. The only change that is needed is to modify the origin lines, so that the origin line in offer2' is valid based on the value in offer1 (validity requires that the version increments by one, and that the other parameters remain unchanged). There are some limitations associated with this flow. First, user A will be alerted without any media having been established yet. This means that user A will not be able to reject or accept the call based on its media composition. Secondly, both A and B will end up answering the call (i.e., generating a 200 OK) before it is known whether there is compatible media. If there is no media in common, the call can be terminated later with a BYE. However, the users will have already been alerted, resulting in user annoyance and possibly resulting in billing events. Copyright (C) The Internet Society (2004). All Rights Reserved 145 IMG WebHelp For more details on this call flow see RFC 3725. Cantata Technology - IMG 1010 Printable WebHelp 146 Product Description SIP Call Hold Topic Location: Product Description > SIP > Routing/Call Handling This feature allows the IMG to process a re-INVITE from a SIP endpoint that places a call on hold or releases a hold. This addition complements the support for SIP Hold ( via 0.0.0.0 ip address) by supporting RFC 3398 section 9, allowing for the proper Interworking of hold information between SIP and SS7. RFC RFC 3398 Integrated Services Digital Network (ISDN) User Part (ISUP) to Session Initiation Protocol (SIP) Mapping: section 9 Call Flows Suspend then Resume from SS7 side Upon receiving a SUS message from the remote SS7 side, the IMG sends a re-Invite to the remote SIP side with the Connection IP address set to 0.0.0.0 in order to request that gateway to place the call on hold. 147 IMG WebHelp Suspend then Resume from SIP side Upon receiving a re-Invite with the connection address equal to a valid IP address for a call that has been placed on hold, the IMG sends a CPG message with the notification indicator set to ‘remote hold released’ to the remote SS7 ANSI side. 148 Product Description Suspend then Resume from SS7 side when SIP-T is enabled When SIP-T is enabled, the IMG will encapsulate the RES message received into an Info message instead of sending a Re-invite to the SIP side. 149 IMG WebHelp Cantata Technology - IMG 1010 Printable WebHelp 150 Product Description SIP Busy Out Topic Location: Product Description > SIP > Routing/Call Handling The IMG can monitor the status of external SIP gateways by sending periodic SIP OPTIONS messages. If the gateway does not respond in a configured amount of time the IMG will mark the gateway as down and attempt to re-route the call to a different gateway. RFC RFC 3261 SIP: Session Initiation Protocol, Section 11. Configuration SIP Profile External Gateway Configuration You enable the SIP Busy Out feature on a specific gateway in the External Gateway pane (OPTIONSKeepalive field). You configure the Busy Out parameters in the SIP Options KeepAlive pane. The parameters to be configured are: Timer to define the interval between OPTIONS when the gateway is responsive. Timer to define the interval between OPTIONS when the gateway is non responsive. Number of responses received before marking the gateway as reachable. EventView Alarm A SIP gateway Alarm in EventView indicates the status of a particular SIP Gateway. This alarm will contain the status (either “unreachable” or “reachable”) and the ip address of this particular Gateway. Call Tracing Call Tracing will capture the sending/reception of the OPTIONS method and indicate that re-routing has taken place because the gateway is down. Example Call Trace 21:24:03.305 SIP (W) <--- [10.129.43.154, 5060 <- 10.129.43.23, 5060] OPTIONS sip:10.129.43.154:5060;ttl=0 SIP/2.0 Via: SIP/2.0/UDP 10.129.43.23:5060;rport;branch=z9hG4bK151 IMG WebHelp 6df4-1156281802-19999-423 Call-ID: [email protected] CSeq: 1 OPTIONS Max-Forwards: 70 To: <sip:10.129.43.154;ttl=0> From: <sip:10.129.43.23>;tag=95ffcd055e0f78f7d5d397020e8 9288db5f2 User-Agent: Cantata-SIP/10.3.2.57 chiloe 0 Contact: <sip:10.129.43.23:5060> Accept: application/sdp Content-Length: 0 Implementation Details When sending a 200 OK to an OPTIONS request the IMG will not include SDP information. If an OPTIONS message is not answered the correspondent gateway will be marked as “down or unreachable”. When a call is attempted to an “unreachable” gateway, the IMG will automatically trigger the re-attempt logic. A gateway will only be marked as “reachable” when the number of sequential responses meet a configurable value. The IMG will keep sending OPTIONS request at a configurable rate. Cantata Technology - IMG 1010 Printable WebHelp 152 Product Description SIP Session Timer Topic Location: Product Description > SIP > Routing/Call Handling Description The IMG supports SIP Session Timers, an extension of SIP RFC 2543 which allows a periodic refreshing of SIP sessions using the RE-INVITE message. The refreshing allows both user agents and proxies to determine if the SIP session is still active. a keep alive mechanism for SIP sessions that allows User Agents (UA) or proxies to determine the status of a session and to release it if it is not active, even if a BYE has not been received. Reference RFC 4028 Session Timers in the Session Initiation Protocol (SIP) Configuration You configure the Session Timer in the SIP Session Timer pane. SIP Session Timer is enabled by default. Overview When a UAC sends an INVITE, it includes a Supported header field with the option tag 'timer', indicating support for this extension. This request passes through proxies, any one of which may have an interest in establishing a session timer. Each proxy can insert a Session-Expires header field and a Min-SE header field into the request (if none is already there) or alter the value of existing Session-Expires and Min-SE header fields. If the Session-Expires interval is too low for a proxy (lower than the value of Min-SE that the proxy would wish to assert), the proxy rejects the request with a 422 response. That response contains a Min-SE header field identifying the minimum session interval it is willing to support. The UAC will try again, this time including the Min-SE header field in the request. The header field contains the largest Min-SE header field it observed in all 422 responses previously received. This way, the minimum timer meets the constraints of all proxies along the path. After several INVITE/422 iterations, the request eventually arrives at the UAS. The UAS can adjust the value of the session interval as if it were a proxy; when done, it places the final session interval into the Session-Expires header field in a 2xx response. The Session-Expires header field also contains a 'refresher' parameter, which indicates who is doing the refreshing -- the UA that is currently the UAC, or the UA that is currently the UAS. As the 2xx response travels back through the proxy chain, each proxy can observe the final session interval but can't change it. From the Session-Expires header field in the response, both UAs know that a session timer is active, when it will expire, and who is refreshing. At some point before the expiration, the currently active refresher generates a session refresh request, which is a re-INVITE or UPDATE request. If the refresher never gets a response to that session refresh request, it sends a BYE to terminate the session. Similarly, if the 153 IMG WebHelp other side never gets the session refresh request before the session expires, it sends a BYE. The refresh requests sent once the session is established are processed identically to the initial requests, as described above. This means that a successful session refresh request will extend the session, as desired. Implementation Details If support of session timer is disabled, the Supported header in an outgoing request will not contain the tag ‘timer’. If the incoming request has Require header that contains tag ‘timer’, the request will be rejected with 420 response code. If support of session timer is enabled, the IMG will always request a session timer, and depending on the configuration the IMG may enforce the session timer even if the remote gateway does not support it. Session refresh timer will be one half of the session interval. Session end timer will be the two thirds of the session interval, or the session interval minus 32 seconds, whichever is larger. The IMG can choose to use re-INVITE or UPDATE to do the refresh. If it is configured to use UPDATE, but the remote gateway does not support UPDATE, the IMG will use re-INVITE instead. If re-INVITE is used, there will be an SDP on it. If UPDATE is used, there will be NO SDP on it. A re-INVITE or UPDATE request sent within a dialog for purpose other than session refreshes will also have the effect of refreshing the session, and its processing will follow the procedures described below. Call Flows See SIP Session Timer Call Flows. Cantata Technology - IMG 1010 Printable WebHelp 154 Product Description SIP Session Timer Call Flows Topic Location: Product Description > SIP > Routing/Call Handling IMG is UAC and does the refresh IMG requests session timer by including Session-Expires header on the INVITE. IMG receives 422 Session Interval Too Small response with Min-SE header. IMG sends out new INVITE with Min-SE and updated Session-Expires value. IMG receives 200 OK that set session timer to 1800 seconds and IMG as the refresher. IMG starts 900 seconds session refresh timer. After refresh timer expires, IMG sends out refresh request with Session-Expires value set to current value 1800 seconds and refresher to UAC. IMG receives 200 OK and resets the timer. Once again IMG sends out refresh request after session refresh timer expires, but now the remote gateway crashed so that IMG receives 408 Request Timeout. IMG sends out BYE and the call is terminated. IMG is UAC and remote gateway does the refresh IMG sends INVITE that has Supported header with option tag ‘timer’ and SessionExpires to request session timer. The remote gateway accepts it. The session interval is set to 1800 seconds and refresher is the remote gateway. IMG starts 1768 seconds session end timer. IMG receives session refresh request before the session end timer expires. IMG sends 200 OK back and set refresher to UAC so that the role of refresher doesn’t change. IMG restarts 1768 seconds session end timer. Now the remote gateway crashes and no refresh request sent. 1768 seconds later the session end timer expires, IMG sends out BYE and terminates the call. 155 IMG WebHelp IMG is UAS and remote gateway does the refresh IMG receives INVITE that has Supported header with option tag ‘timer’. IMG sends 200 OK and requests session timer by including Require header with tag ‘timer’ and Session-Expires header. The session interval is set to 1800 seconds and refresher is the remote gateway. IMG starts 1768 seconds session end timer. IMG receives session refresh request before the session end timer expires. IMG sends 200 OK back and set refresher to UAC so that the role of refresher doesn’t change. IMG restarts 1768 seconds session end timer. Now the remote gateway crashes and no refresh request sent. 1768 seconds later the session end timer expires, IMG sends out BYE and terminates the call. IMG is UAS and does the refresh IMG receives INVITE that has Supported header with option tag ‘timer’ and SessionExpires header with 90 seconds value. Since IMG’s minimum session timer is configured to 1800 seconds, IMG sends back 422 response with Min-SE header set to 1800. Then the remote gateway sends new INVITE with updated session timer and IMG accepts it. The session interval is set to 1800 seconds and refresher is IMG. IMG 156 Product Description starts 900 seconds session refresh timer. After refresh timer expires, IMG sends out refresh request with Session-Expires value set to current value 1800 seconds, refresher is set to UAC so that ensure IMG will always perform refresh. IMG receives 200 OK and resets the timer. Once again IMG sends out refresh request after session refresh timer expires, but now the remote gateway crashed so that IMG receives 408 Request Timeout. IMG sends out BYE and the call is terminated. IMG is UAC and Requests Session Timer IMG requests session timer by including Session-Expires header on the INVITE. IMG receives 200 OK without Session-Expires header that indicates the remote gateway does no support session timer. Since IMG is configured to enforce session timer, IMG sets session interval to 1800 seconds and refresher to ‘UAC’. IMG starts 900 seconds session refresh timer. After refresh timer expires, IMG sends out refresh request with Session-Expires value set to current value 1800 seconds and refresher to UAC. IMG receives 200 OK and resets the timer. Once again IMG sends out refresh request after session refresh timer expires, but now the remote gateway crashed so that IMG receives 408 Request Timeout. IMG sends out BYE and the call is terminated. 157 IMG WebHelp IMG is UAS and configured to enforce session timer on INVITE IMG receives INVITE that the Supported header does not contain tag ‘timer’. IMG sends back 200 OK. Since IMG is configured to enforce session timer, IMG sets session interval to 1800 seconds and refresher is ‘UAS’ IMG starts 900 seconds session refresh timer. After refresh timer expires, IMG sends out refresh request with Session-Expires value set to current value 1800 seconds, refresher is set to UAC so that ensure IMG will always perform refresh. IMG receives 200 OK and resets the timer. Once again IMG sends out refresh request after session refresh timer expires, but now the remote gateway crashed so that IMG receives 408 Request Timeout. IMG sends out BYE and the call is terminated. Cantata Technology - IMG 1010 Printable WebHelp 158 Product Description Pass through ‘+’ sign in the user part of URI Topic Location: Product Description > SIP > Routing/Call Handling The IMG supports the passing of the ‘+’ sign from the incoming SIP side to the outgoing SIP side, or the removal of the "+" if you do not want to pass it through. This process is only applied to INVITE. Configuration You enable this feature in the SIP Profile with the Append (+) for Headers and Remove (+) for Headers fields. You can apply this feature to the following headers in the INVITE: R_URI TO FROM P_ASSERTED P_PREFERRED REMOTE_PARTY_ID NOTE: The Contact header is not put into the bit mask, but ‘+’ is supported in the Contact header if it is included in the incoming Contact. NOTE: The ‘+’ is not supported for routing or translation; only a simple pass through. Cantata Technology - IMG 1010 Printable WebHelp 159 IMG WebHelp Fully Qualified Domain Name Support Topic Location: Product Description > SIP > Routing/Call Handling Overview This feature allows the IMG to support SDP connection (c=) lines with a Fully Qualified Domain Name (FQDN). If outgoing FQDN is enabled, the IMG SIP Signaling and VoIP module IP addresses will not be shown in the outgoing request and response SIP messages. Benefit This feature allows you to manage IMG IP addresses via DNS for greater flexibility and security than hard-coded alternatives in SDP and SIP. Configuration Incoming support is enabled by default and is not configurable. If the IMG receives an SDP c= line with FQDN, the IMG will always try an DNS query. If DNS is not configured or not configured properly, the call will fail. You enter Fully Qualified Domain Names in the Fully Qualified Domain Name fields of the SIP Signaling, SIP Virtual Address, and VoIP Module panes. You configure outgoing FQDN options in the SIP Profile. RADIUS VSAs The following Cantata VSAs support the Fully Qualified Domain Name feature. Cantata-voip-src-sig-fqdn Cantata-voip-dst-rtp-fqdn Cantata-voip-src-rtp-fqdn See Cantata RADIUS VSAs for more information. Dictionary File The radius dictionary file has been updated to support this feature. Customers using RADIUS should update the dictionary.cantata file they are using with the latest one located in the GCEMS install under ‘/opt/cantata/common/radius‘ On a freeRADIUS server this file should be copied into ‘/usr/share/freeradius’ directory. 160 Product Description Call Flows Outgoing with FQDN Enabled The following call flow shows an SS7 to SIP call flow where FQDNs is enabled. Incoming FQDN DNS Query The following call flow shows the case where an incoming INVITE includes an SDP c line w/ FQDN to perform a DNS query before the call is established. 161 IMG WebHelp Example INVITE Messages Outgoing FQDN option = Signaling ONLY When the Outgoing FQDN option is set to Signaling Only, the FQDN of the local IMG signaling IP address only is inserted in the outgoing SIP messages. Relevant lines are in bold. <--- [10.129.39.123, 5060 <- 10.129.39.59, 5060] INVITE sip:[email protected]:5060 SIP/2.0 Via: SIP/2.0/UDP img1-dtran.Cantata.com:5060;rport;branc h=z9hG4bK-53d0-1180551394-19996-487 Call-ID: [email protected] CSeq: 1 INVITE Max-Forwards: 70 To: <sip:[email protected]:5060> From: unavailable<sip:[email protected] >;tag=95ffcd055e0f78f7d5d397020e89288d3de1 User-Agent: Cantata-SIP/10.3.3.68 Quincy 0 Contact: <sip:[email protected]:5060> Allow: INVITE, BYE, REGISTER, ACK, OPTIONS, CANCEL, SUBSCRIBE, NOTIFY, INFO, UPDATE Supported: path, timer 162 Product Description Session-Expires: 1800 Expires: 300 Organization: Cantata Technology Inc Content-Type: application/sdp Content-Length: 187 v=0 o=Cantata_SDP 0 0 IN IP4 img1-dtran.Cantata.com s=Cantata-SIP c=IN IP4 10.129.39.32 t=0 0 m=audio 8000 RTP/AVP 0 a=rtpmap:0 PCMU/8000 a=silenceSupp:off - - - Outgoing FQDN option = SDP c equal line ONLY When the Outgoing FQDN option is set to SDP c=line ONLY, the FQDN of the local IMG VoIP IP address only is inserted in the outgoing SIP messages. Relevant lines are in bold. <--- [10.129.39.123, 5060 <- 10.129.39.59, 5060] INVITE sip:[email protected]:5060 SIP/2.0 Via: SIP/2.0/UDP 10.129.39.59:5060;rport;branc h=z9hG4bK-53d0-1180551394-19996-487 Call-ID: [email protected] CSeq: 1 INVITE Max-Forwards: 70 To: <sip:[email protected]:5060> From: unavailable<sip:[email protected] >;tag=95ffcd055e0f78f7d5d397020e89288d3de1 User-Agent: Cantata-SIP/10.3.3.68 Quincy 0 Contact: <sip:[email protected]:5060> Allow: INVITE, BYE, REGISTER, ACK, OPTIONS, CANCEL, SUBSCRIBE, NOTIFY, INFO, UPDATE Supported: path, timer Session-Expires: 1800 Expires: 300 Organization: Cantata Technology Inc 163 IMG WebHelp Content-Type: application/sdp Content-Length: 187 v=0 o=Cantata_SDP 0 0 IN IP4 10.129.39.59 s=Cantata-SIP c=IN [email protected] t=0 0 m=audio 8000 RTP/AVP 0 a=rtpmap:0 PCMU/8000 a=silenceSupp:off - - - Outgoing FQDN option =Both The following shows a SIP INVITE message when the Outgoing FQDN option is set to Both. <--- [10.129.39.123, 5060 <- 10.129.39.59, 5060] INVITE sip:[email protected]:5060 SIP/2.0 Via: SIP/2.0/UDP img1-dtran.Cantata.com:5060;rport;branc h=z9hG4bK-53d0-1180551394-19996-487 Call-ID: [email protected] CSeq: 1 INVITE Max-Forwards: 70 To: <sip:[email protected]:5060> From: unavailable<sip:[email protected] >;tag=95ffcd055e0f78f7d5d397020e89288d3de1 User-Agent: Cantata-SIP/10.3.3.68 Quincy 0 Contact: <sip:[email protected]:5060> Allow: INVITE, BYE, REGISTER, ACK, OPTIONS, CANCEL, SUBSCRIBE, NOTIFY, INFO, UPDATE Supported: path, timer Session-Expires: 1800 Expires: 300 Organization: Cantata Technology Inc Content-Type: application/sdp Content-Length: 187 164 Product Description v=0 o=Cantata_SDP 0 0 IN IP4 img1-dtran.Cantata.com s=Cantata-SIP c=IN IP4 [email protected] t=0 0 m=audio 8000 RTP/AVP 0 a=rtpmap:0 PCMU/8000 a=silenceSupp:off - - - - FQDN enabled But No FQDN Configured If Outgoing FQDN options is enabled but NO FQDN hostname entered from ClientView, then we will send out a WARNING and process the call normally with IPs. For example: 1. Signaling ONLY option is enabled but NO IMG Signaling FQDN Local IMG Signaling IP of the IMG will be shown 2. SDP C Equal Line ONLY option is enabled but NO VoIP module FQDN Local VoIP module IP of the IMG will be shown 3. Both option is enabled but NO IMG Signaling FQDN Local Signaling IP of the IMG will be shown FQDN of VoIP module (NOT IP) will be shown at SDP C equal line 4. Both option is enabled but NO VoIP module FQDN FQDN of the local IMG Signaling will be shown Local VoIP module IP of the IMG will be shown Cantata Technology - IMG 1010 Printable WebHelp 165 IMG WebHelp Multiple SIP 183 prior to 200 OK Topic Location: Product Description > SIP > Routing/Call Handling Overview The IMG supports receiving multiple SIP 183s prior to 200 OK for SIP hop forks where an INVITE request and SIP responses can potentially be received from multiple remote user agents. A proxy or an Application server that receives an INVITE from the IMG can then fork the request to multiple destinations. The IMG will handle multiple inbound 183 if and only if the To header tags are different in each response. Multiple 18x responses are to be processed during the initial INVITE transaction only. A maximum number of five 18x responses will be accepted per call, with different To header tags. Benefits Multiple 183 responses are used in Follow-me services, and request forking scenarios. Applications that can benefit from the IMG handling multiple 18x responses are: Application Servers Proxy Servers Configuration This feature is implemented by default and no configuration is required. Feature Interaction: Comedia Mode When the Comedia Mode is set to Passive, the outbound RTP packets are to be sent to the second RTP destination, even if the first destination continued to send RTP packets. If Comedia Mode is set to active, the IMG behavior is to be the same as if it were disabled. See Symmetric NAT Traversal for more information on Comedia Mode. Call Tracing Call tracing will reflect SDP decoding and the overlap logic for multiple 18x responses. Call Flows Standard Behavior The typical signaling call flow is shown in the diagram below. The initiating gateway can receive multiple 18x responses, each containing an SDP answer. This SIP behavior is defined in RFC 3261. 166 Product Description SIP 183 with SDP response followed by another 183 with SDP In the case of a SIP 183 with SDP response followed by another 183 with SDP, the IMG sends RTP packets to the SDP connection last received. 183 Followed by 180 If a SIP 183 with SDP (or a SIP 180 with SDP) is followed by a 180 (no SDP), the IMG will ignore the 180 and Local ring back will not be played. 167 IMG WebHelp Failure Scenario If one of the subsequent 18x responses is syntactically incorrect or the SDP offer/answer overlap fails, the IMG will ignore the 18x response and will not send a SIP CANCEL request to the external gateway. Cantata Technology - IMG 1010 Printable WebHelp 168 Product Description SIP INFO Method for DTMF Topic Location: Product Description > SIP > Routing/Call Handling This feature allows the use of the SIP INFO method to send a DTMF digit to another gateway. The voice stream is established after a successful SIP 200 OK-ACK message sequence. NOTE: A more robust method to use for sending DTMF digits in SIP is SIP SUBSCRIBE/NOTIFY Method for DTMF. You enable this feature using the SIP DTMF Support pane. There are two ways of using the INFO Method for DTMF: INFO Using Pattern INFO DTMF Digit Relay INFO Using Pattern After a match of the configured number of ‘#’ characters in the voice stream, the IMG will send a # character in the SIP INFO to the same endpoint to which the 200 OK ACK was sent. The voice stream is established after a successful SIP 200 OK-ACK message sequence. The SIP INFO will contain a SIP header of Signal (showing the # character) and the duration header (showing the length in milliseconds of the duration to play the # signal). Configuration You enable this feature using the SIP DTMF Support pane by selecting INFO with Pattern in the Method field. The only implementation currently supported is the sending of the pound (#) character in response to the configured number of pound (#) characters received (14). SIP INFO Header The existing header of the SIP INFO method will be modified to carry the digit. Signal parameter - used to carry the ‘#’ character in the SDP. Content-Type header - will be changed to dtmf-relay when this feature is invoked. Duration parameter - used in the SDP to store the length of time in milliseconds to play the digit. The following shows a SIP INFO header with the changes: INFO sip:[email protected]:5060 SIP/2.0 Via: SIP/2.0/UDP 150.129.38.217:5060;rport;branch=z9hG4bK-11701145483948-19998-190 Call-ID: [email protected] 169 IMG WebHelp CSeq: 2 INFO Max-Forwards: 70 To: <sip:[email protected]>;tag=75001a07 From: <sip:[email protected]>;tag=95ffcd055e0f78f7d5d397020e89288de8b1 User-Agent: Excel-Open-SIP/10.3.1.56 MFG_5 0 Timestamp: 04192006215908 Accept: application/sdp Content-Length: 26 Content-Type: application/dtmf-relay Signal= # Duration= 120 Call Flow: # Character in SIP INFO INFO DTMF Digit Relay With this feature the IMG supports out-of-band tone passage of a single DTMF digit (0- 9, *, #, a, b, c, d) using the SIP INFO method. 170 Product Description Configuring the Feature You enable this feature by selecting INFO DTMF digit relay in the Method field of the SIP DTMF Support pane. Digits Received from TDM Side The IMG will send out a single DTMF digit in the INFO if it receives a digit from a TDM Channel (no pattern match required) Example INFO Message: TDM-to-SIP INFO sip:10.129.39.95:5060 SIP/2.0 Via: SIP/2.0/UDP 10.129.39.49:5060;rport;branch=z9hG4bK16cf-1182872402-19997-319 Call-ID: [email protected] CSeq: 2 INFO Max-Forwards: 70 To: <sip:[email protected]:5060>;tag=1 From: <sip:[email protected]>;tag=95ffcd055e0f78f7d5d3970 20e89288dc959 User-Agent: Cantata-SIP/10.3.3.172 YUE_NODE 0 Accept: application/sdp Content-Type: application/dtmf-relay Content-Length: 26 Signal= 6 Duration= 100 171 IMG WebHelp Digits Received from IP Side The IMG will send out a single DTMF digit in the INFO if it receives a SIP INFO request that has the Content-Type set to “application\dtmf-relay”. When the Content-Type header of incoming INFO request has value “application/dtmf-relay”, the IMG will look for a DTMF digit in the “Signal=” line and the digit interval in the “Duration=” line. If there is more than one digit in the “Signal=” line from incoming INFO, the IMG will only accept first digit. If the Duration= line is not present, the interval will be set to 100. Error Conditions The IMG will return a 488 if an INFO message with the Content-Type set to application/dtmf-relay is received and: the IMG configuration is not set to INFO DTMF relay. the IMG configuration is set to INFO DTMF relay, but the Signal= line contains un-recognizable character. Cantata Technology - IMG 1010 Printable WebHelp 172 Product Description SIP SUBSCRIBE/NOTIFY Method for DTMF Topic Location: Product Description > SIP > Routing/Call Handling Overview The IMG accepts user agent subscription requests (SIP SUBSCRIBE method) and the ability to respond to those user agents with the appropriate DTMF digit events via the SIP NOTIFY method. Only telephone event of “###” are currently supported. RFC: 3265 Session Initiation Protocol (SIP)-Specific Event Notification Benefits You can develop user-specific applications that reside on your network entity and have the ability to subscribe for event services supported by the IMG. If the network entity wants the ability to detect an entered DTMF digit (only telephone event of “###” are currently supported) from the TDM-side of a call to the IP side of a call, the entity can subscribe to the IMG for these events and receive SIP NOTIFY events containing the digit event. Limitations Only patterns of 1-4 pound ("#") characters are supported The IMG cannot send a SIP SUBSCRIBE The ‘Pending’ state is not supported Configuration You enable and configure this feature with the SIP DTMF Support pane. In the Method field select Subscribe and then configure other fields as required. Call Flows 173 IMG WebHelp 174 Product Description 175 IMG WebHelp Call Tracing Each SIP request received or transmitted for the SIP SUBSCRIBE and NOTIFY methods will be displayed in the normal call tracing. For the NOTIFY method, the trace will also display the NOTIFY method’s payload. In the case of detected DTMF digits, the ‘###’ will be displayed in the call tracing. Example Trace The following is an example call trace showing SIP Subscribe Notify for DTMF. Related lines are in bold. ---> [10.129.55.74, 5060] SUBSCRIBE sip:[email protected]:5060 SIP/2.0 Via: SIP/2.0/UDP 10.129.55.74:5060 176 Product Description From: 7340 <sip:[email protected]:5060>;tag=1 To: 8519 <sip:[email protected]:5060>;tag=a94c095b773be1 dd6e8d668a785a9c84113d Call-id: [email protected] Cseq: 1 SUBSCRIBE Contact: <sip:[email protected]:5060;transport=UDP> Event: telephone-event;duration=300 Expires: 600 Content-Length: 0 18:17:08.733 SIP (W) <--- [10.129.55.74, 5060 <- 10.129.55.80, 5060] SIP/2.0 200 OK Via: SIP/2.0/UDP 10.129.55.74:5060;received=10.129.55.74 Call-ID: [email protected] From: 7340 <sip:[email protected]:5060>;tag=1 To: 8519 <sip:[email protected]:5060>;tag=a94c095b773be1 dd6e8d668a785a9c84113d CSeq: 1 SUBSCRIBE Server: Cantata-SIP/10.3.3.129 SIP-Gateway1 0 Expires: 600 Content-Length: 0 <--- [10.129.55.74, 5060 <- 10.129.55.80, 5060] NOTIFY sip:[email protected]:5060 SIP/2.0 Via: SIP/2.0/UDP 10.129.55.80:5060;rport;branch=z9hG4bK- 5c5e1163009828-19999-33 Call-ID: [email protected] CSeq: 1 NOTIFY Max-Forwards: 70 To: <sip:[email protected]>;tag=1 From: <sip:[email protected]>;tag=a94c095b773be1dd6e8d668a785a9c84113d User-Agent: Cantata-SIP/10.3.3.129 SIP-Gateway1 0 Event: telephone-event;duration=300 Subscription-State: Active;expires=600 Content-Length: 0 177 IMG WebHelp 18:17:08.753 SIP (W) ---> [10.129.55.74, 5060] SIP/2.0 200 OK Via: SIP/2.0/UDP 10.129.55.80:5060;rport;branch=z9hG4bK- 5c5e1163009828-19999-33 From: <sip:[email protected]>;tag=a94c095b773be1dd6e8d668a785a9c84113d To: <sip:[email protected]>;tag=1;tag=1 Call-ID: [email protected] CSeq: 1 NOTIFY Contact: <sip:10.129.55.74:5060;transport=UDP> Content-Length: 0 NOTIFY sip:[email protected]:5060 SIP/2.0 Via: SIP/2.0/UDP 10.129.55.80:5060;rport;branch=z9hG4bK-d371163009863-19998-33 Call-ID: [email protected] CSeq: 2 NOTIFY Max-Forwards: 70 To: <sip:[email protected]>;tag=1 From: <sip:[email protected]>;tag=a94c095b773be1dd6e8d668a785a9c84113d User-Agent: Cantata-SIP/10.3.3.129 SIP-Gateway1 0 Event: telephone-event;duration=300 Subscription-State: Active;expires=125 Content-Type: application/dtmf-relay Content-Length: 26 Signal= # Duration= 160 18:17:43.893 SIP (W) ---> [10.129.55.74, 5060] SIP/2.0 200 OK Via: SIP/2.0/UDP 10.129.55.80:5060;rport;branch=z9hG4bK-d371163009863-19998-33 From: <sip:[email protected]>;tag=a94c095b773be1dd6e8d668a785a9c84113d To: <sip:[email protected]>;tag=1;tag=1 178 Product Description Call-ID: [email protected] CSeq: 2 NOTIFY Contact: <sip:10.129.55.74:5060;transport=UDP> Content-Length: 0 Troubleshooting If you are experiencing problems with this feature, ensure the following: Subscribe is enabled in the SIP SGP The correct SIP SGP is assigned to the External Remote Gateway Cantata Technology - IMG 1010 Printable WebHelp 179 IMG WebHelp SS7 SS7 Features Topic Location: Product Description > SS7 ISUP Variants You select your ISUP variant in the SS7 Stack pane. ANSI 97 ANSI 92 Misc 180 ANSI 95 ITU 97 ITU 93 CCITT 88 ETSI V1 ETSI V2 ETSI V3 China JT-ISUP Custom Variants Forward Call Indicators (FCI) Override 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. Backward Call Indicators (BCI) Override Location Override Circuit Query Message You can send a Circuit Query Message (CQM) on a CIC or a group of CICs using the Circuit Group pane. The CIC status will update accordingly if there has been any change. COT Test Pre/Post 95 Support for GRS/GRA Suppress UCICs 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 the SS7 Stack pane. Product Description Control CICs on up to 32 IMGs Gain Control on SS7 Channel Groups Interworking ISDN to SIP, SS7 ISUP, and H.323 Call Flows: SS7 ISUP to ISDN ANSI ISUP Originating Line Info Support SIP Carrier Identification Code (CIC) SIP to SS7 ISUP Interworking: Calling Party Category SS7 ISUP to ISDN Interworking Support for SPIROU/ITX in SIP INFO SIP Privacy Cantata Technology - IMG 1010 Printable WebHelp 181 IMG WebHelp Pre/Post 95 Support for GRS/GRA Topic Location: Product Description > SS7 Description This feature provides the capability to support both pre and post 1995 GRS/GRA message on a per CIC group basis (ANSI Only). This enables different CIC groups in an SS7 stack to connect to different types of DPCs. Configuration ISUP Group pane. Implementation Sending GRS/GRA The post 1995 GRA message, which would be sent in response to an incoming post 1995 GRS, will have the optional circuit assignment map parameter included if it was included in the incoming GRS. The pre 1995 GRA message, which would be sent in response to an incoming pre 1995 GRS, will not have a pointer to optional circuit assignment map parameter. Receiving GRS/GRA The received GRS/GRA messages are validated against the pre 1995 or post 1995 format depending upon the configuration for the base CIC. A confusion (CFN) message will be sent if the incoming message does not have the expected format. Troubleshooting If CICs do not come in service verify that the IMG configuration matches the distant end. Cantata Technology - IMG 1010 Printable WebHelp 182 Product Description ISDN An Overview of ISDN on the IMG Topic Location: Product Description > ISDN The IMG supports Integrated Services Digital Network (ISDN) for multiple communications tasking (voice, data, compressed), 128 Kbps high-speed and highbandwidth service. ISDN, non-compressed (512 KBps compressed) also provides ondemand service, connects up to eight devices simultaneously, and can be callmanaged. The basic configuration is 23+D (Primary Rate Interface) and 30B+D outside of North America. The IMG interfaces to various equipment types supporting the ISDN PRI protocol, including tandem (Class 4) switches and end office (Class 5) switches. The IMG ISDN PRI implementation is based on ITU-T Q.921 and Q.931 specifications. Each implemented variant references the appropriate interface document supplied by the equipment manufacturer. The interface document is usually a variant of the ITU-T recommendations. The IMG supports up to 32 D channels. Each D channel provides the High Data Link Control (HDLC) communications over T1, E1, or DS3 on one timeslot on the span. Each D channel can control up to 19 other spans in addition to the span on which it is located. National ISDN PRI NI 2 The IMG supports National ISDN PRI NI 2. National ISDN PRI supports Non-Facility Associated Signaling (NFAS), allowing up to 30 DS1 interfaces and the D channel backup procedure, as well as B channel availability and provisioning. Connection endpoint variants are defined for National ISDN User side and Network side. Depending upon your provisioning requirements, you can have one D channel per span [Facility Associated Signaling (FAS)], or one D channel managing up to 20 spans [Non-Facility Associated Signaling (NFAS)]. You can control a total of 32 spans using all FAS D channels, or up to 20 spans per NFAS D channel (to a maximum of 64 spans per system). You can intermix both FAS and NFAS D channels with each supporting a different variant. Cantata Technology - IMG 1010 Printable WebHelp 183 IMG WebHelp ISDN Features Topic Location: Product Description > SS7 Basic Support Gain Control on ISDN Channel Groups 24 D Channels over or E1 (21 bearer + 3 signaling spans) 32 D channels per-IMG over T1/DS3 ITU-T Q.921, Q.931-based Incoming B channel Negotiation ISDN Bearer Capabilities Override Supported Variants T1 Network Side Variants National-ISDN 2 ATT5ESS Q.931 PRI (Custom) ATT 4ESS Q.931 PRI Northern Telecom DMS-100 Q.931 PRI (Custom) Northern Telecom DMS-250 Q.931 PRI JATE Net5 Q.931 (10.3.3 ER2) T1 User Side Variants ATT 4ESS Q.931 PRI User Side Northern Telecom DMS-100 Q.931 PRI (Custom) User Side ATT 5ESS Q.931 PRI (Custom) User Side Northern Telecom DMS-250 Q.931 PRI National-ISDN 2 JATE Net5 Q.931 (10.3.3 ER2) E1 Network Side Variants Euro-ISDN E1 User Side Variants 184 Euro-ISDN Product Description D channel backup The IMG supports the D channel backup procedure as defined by Lucent TR 41459. This procedure provides a standby D channel when using NFAS. When an active D channel fails, or if there is a span alarm, the IMG converts to the standby D channel and maintains active calls. This is a provisioned option and is applicable only when using NFAS. D channel backup is supported on the T1 only. NFAS NFAS is supported over T1 with the NI-2, 4ESS/5ESS, and DMS 100/250 variants. It is not supported over E1 with the Euro ISDN variant, or over T1 with the JATE variant. Interworking ISDN to SS7 ISUP, SIP, and H.323 Cantata Technology - IMG 1010 Printable WebHelp 185 IMG WebHelp CAS Basic CAS Call Flows Topic Location: Product Description > CAS SIP to CAS CAS to H.323 186 Product Description CAS to SS7 CAS to ISDN Cantata Technology - IMG 1010 Printable WebHelp 187 IMG WebHelp E1 CAS Timers Topic Location: Product Description > CAS Timer ID Description: (State Used); Timer Description Default Value 1 (S19) Incoming Layer 4 busy out Acknowledge wait 4000 2 (S2) Incoming Stage 1 FWD digit receive wait 20000 3 (S3) Incoming Stage 2 FWD digit receive wait 20000 4 (S4) Incoming Stage 3 FWD digit receive wait 20000 5 (S5) Incoming Stage 4 FWD digit receive wait 20000 6 (S13) Layer 4 Connect wait 24,0000 7 (S14) Layer 4 wait 4000 8 (S21) Clear Forward (idle line signaling) wait 15000 9 (S3) Incoming Stage 2 Initial FWD digit receive wait 20000 10 (S2) Incoming Stage 1 Initial FWD digit receive wait 20000 11 (S5) Incoming Stage 4 Initial FWD digit receive wait 20000 12 (S4) Incoming Stage 3 Initial FWD digit receive wait 2000 20000 13 (S15) Layer 3 Circuit Release wait 100 14 (S18) Layer 3 Circuit Release wait 100 15 (S6) Host Control Wait 60000 16 (S13) Layer 3 Connect wait 240000 17 (S29) Seize Acknowledge wait 4000 18 (S31) Time to wait before transmitting idle signal after detecting glare 100 19 (S32) Time to wait before looking for idle signal after transmitting idle signal after detecting glare 100 188 Product Description 20 (S39) Outgoing Stage 1 BWD R2 signal wait 15000 21 (S39) Outgoing Stage 1 Initial BWD R2 signal wait 15000 22 (S41) Outgoing Stage 2 BWD R2 signal wait 15000 23 (S41) Outgoing Stage 2 Initial BWD R2 signal wait 15000 24 (S43) Outgoing Stage 3 BWD R2 signal wait 15000 25 (S43) Outgoing Stage 3 Initial BWD R2 signal wait 15000 26 (S45) Outgoing Stage 4 BWD R2 signal wait 15000 27 (S45) Outgoing Stage 4 Initial BWD R2 signal wait 15000 28 (S46) Outgoing wait for answer 24000 29 (S48) Outgoing Layer 4 Clear wait 4000 30 (S49) Outgoing idle line signal wait 120000 31 (S50) Outgoing idle line signal wait after glare detected 120000 32 (S24) Host Control wait 240000 33 (S33) Time to wait for Clear Forward after glare detected 10000 34 Receive line signaling filter 40 36 (S6, S24) Incoming BWD R2 Cycle Complete Event wait 4000 38 (S10) Time to wait for idle line signaling after invalid line signal detected while receiving FWD R2 digits 20000 39 (S22) Layer 3 Clear Forward wait 3000 40 (S39) Outgoing Stage 1 BWD A signal wait after sending all of Stage 1 FWD digits 20000 41 (S2, S3, S4, S5) FWD R2 digits receive wait when String Collection Data field in Inpulsing Parameters Configure is set to 0xFF 200 43 R2 Cycle Complete Event wait 2000 45 (S43) Time to wait for next BWD R2 signal when stage 3 digits have been outpulsed 20000 189 IMG WebHelp Cantata Technology - IMG 1010 Printable WebHelp 190 Product Description T1 CAS Filters and Timers Topic Location: Product Description > CAS Signal Scanning Filters Signal Scanning Filters define the duration that an expected signaling condition is expected to be valid before it is declared to have occurred Filter values are entered in the Filter/Timer Configure pane in millisecond decimal units, however they are sent to the IMG in 10 millisecond units and so therefore must be in 10 ms increments. If there is no value in a field, the timer does not apply. Timer No. Signal Scanning Filter E&M FXS-LS 0x01 Preseize 100 0x02 Inseize 150 0x03 Modified Incoming Release 700 700 0x04 Modified Outgoing Release 700 700 0x05 Normal Incoming Release 700 700 0x06 Normal Incoming Release w/Flash 1020 1020 0x07 Normal Outgoing Release 700 0x08 Normal Outgoing Release w/Flash 1020 0x09 Post Inseize Acknowledgment 0x0A Outseize Acknowledgment 0x0B Outseize Answer 0x0C Outseize Dial Signal End 0x0D First Release 0x0E ANI Req Offhook 100 200 700 1020 180 350 40 700 200 700 200 Signal Scanning Timers Signal Scanning Timers (table below) define the minimum and maximum acceptable durations for signaling condition to exist from the point they are declared valid. Timer No. Signal Scanning Timer E&M FXOLS FXS-LS FXOGS FXS-GS 191 IMG WebHelp 0x15 Inseize Complete 0x16 Post Inseize Complete 0x17 Start Normal Outgoing Release 0 0x18 Start Normal Incoming Release 0 0x19 Outseizure Acknowledgment 0x1A Outseizure Answer 0x1B Guard Time-out 0x1C Release 0x1D Glare Detection 100 300 0x1E Minimum Flash 300 300 300 300 300 0x1F Maximum Flash 1000 1000 1000 1000 1000 0x20 Start Dial (Wink 1) Minimum Wink 100 0x21 Start Dial (Wink 2) Maximum Wink 350 0x22 Minimum Delay Dial Signal 140 0x23 Maximum Delay Dial Signal 4000 0x24 Post Start Dial Signal Outpulse Delay 80 0x25 Wink 2 Minimum Receive Duration 100 0x26 Wink 2 Maximum Receive Duration 500 0x27 Wink 2 Minimum Post Outpulse 100 192 6040 220 5000 5000 100,000 700 6000 640,000 850 320,000 850 320,000 320,000 320,000 100 Product Description Delay 0x28 Wink 2 Maximum Post Outpulse Delay 3500 0x29 Wink 2 Maximum Receive Detection 0x2A Wink 3 Minimum Receive Duration 100 0x2B Wink 3 Maximum Receive Duration 600 0x2C Wink 3 Minimum Post Outpulse Delay 100 0x2D Wink 3 Maximum Post Outpulse Delay 3500 0x2E Wink 3 Maximum Receive Detection 4,000 0x2F Wink 4 Minimum Receive Duration 100 0x30 Wink 4 Maximum Receive Duration 350 0x31 Wink 4 Minimum Post Outpulse Delay 100 0x32 Wink 4 Maximum Post Outpulse Delay 3,500 0x33 Wink 4 Maximum Receive Detection 4,000 0x34 Wink 5 Minimum Receive Duration 100 0x35 Wink 5 Maximum 350 11,500 193 IMG WebHelp Receive Duration 0x36 Wink 5 Minimum Post Outpulse Delay 0x37 Wink 5 Maximum Post Outpulse Delay 3,500 0x38 Wink 5 Maximum Receive Detection 4,000 0x39 Wink 6 Minimum Receive Duration 100 0x3A Wink 6 Maximum Receive Duration 350 0x3B Wink 6 Minimum Post Outpulse Delay 100 0x3C Wink 6 Maximum Post Outpulse Delay 3,500 0x3D Wink 6 Maximum Receive Detection 4,000 0x3E Wink 7 Minimum Receive Duration 100 0x3F Wink 7 Maximum Receive Duration 350 0x40 Wink 7 Minimum Post Outpulse Delay 100 0x41 Wink 7 Maximum Post Outpulse Delay 3,500 0x42 Wink 7 Maximum Receive Detection 4,000 194 100 Product Description 0x43 Wink 8 Minimum Receive Duration 100 0x44 Wink 8 Maximum Receive Duration 350 0x45 Wink 8 Minimum Post Outpulse Delay 100 0x46 Wink 8 Maximum Post Outpulse Delay 3,500 0x47 Wink 8 Maximum Receive Detection 4,000 0x48 Post ANI Offhook Outpulse Detection 1,000 0x49 Maximum Receive ANI Offhook Request 16,000 0x4A Maximum Receive Dialtone Detection 8,000 8,000 8,000 8,000 8,000 0x4B MFR1 Minimum Receive KP Duration 50 50 50 50 50 0x4C MFR1 Minimum Receive Digit Duration 30 30 30 30 30 0x4D MFR1 Maximum Receive KP Duration 10,000 10,000 10,000 10,000 10,000 0x4E MFR1 Minimum Receive Interdigit Duration 30 30 30 30 30 0x4F MFR1 Maximum Receive Interdigit Duration 10,000 10,000 10,000 10,000 195 IMG WebHelp 0x50 DTMF Maximum Receive 1st Digit Detection 20,000 20,000 20,000 20,000 20,000 0x51 DTMF Minimum Receive Digit Duration 40 40 40 40 40 0x52 DTMF Minimum Receive Interdigit Duration 40 40 40 40 40 0x53 DTMF Maximum Receive Interdigit Duration 20,000 20,000 20,000 20,000 20,000 Transmit Signaling Timers Timer No. Timer E&M FXO LS FXS LS 0x5B Wink (1 or KP) Duration 20 0x5C Flash Duration 600 600 0x5D Primary Outseize Signaling 0x5E Outseize Signaling Complete 300 300 0x5F Delay Dial Signal Start 70 0x60 Fixed Pause 70 0x61 Timed Answer 0x62 Ringing On Duration 2000 0x63 Ringing Off Duration 4000 0x64 Wink 1 Minimum Transmit Delay 80 0x65 Wink 2 Minimum Transmit Delay 800 196 600 FXO GS FXS GS 600 600 70 70 70 500 500 Product Description 0x66 Wink 2 Maximum Transmit Delay 11,500 0x67 Wink 2 Transmit Duration 200 0x68 Wink 3 Minimum Transmit Delay 100 0x69 Wink 3 Maximum Transmit Delay 400 0x6A Wink 3 Transmit Duration 200 0x6B Wink 4 Minimum Transmit Delay 0x6C Wink 4 Maximum Transmit Delay 400 0x6D Wink 4 Transmit Duration 200 0x6E Wink 5 Minimum Transmit Delay 80 0x6F Wink 5 Maximum Transmit Delay 400 0x70 Wink 5 Transmit Duration 200 0x71 Wink 6 Minimum Transmit Delay 80 0x72 Wink 6 Maximum Transmit Delay 400 0x73 Wink 6 Transmit Duration 200 0x74 Wink 7 Minimum Transmit Delay 80 0x75 Wink 7 Maximum Transmit Delay 400 0x76 Wink 7 Transmit Duration 200 80 197 IMG WebHelp 0x77 Wink 8 Minimum Transmit Delay 80 0x78 Wink 8 Maximum Transmit Delay 400 0x79 Wink 8 Transmit Duration 200 0x7A MFR1 Transmit KP Duration 100 0x7B MFR1 Transmit Digit Duration 60 0x7C MFR1 Transmit Interdigit Duration 60 0x7D DTMF Transmit Digit Duration 60 0x7E DTMF Transmit Interdigit Duration 60 Cantata Technology - IMG 1010 Printable WebHelp 198 Product Description Routing An Overview of Routing on the IMG Topic Location: Product Description > Routing The IMG router is a robust routing engine that selects an outgoing channel for an incoming call based on a set of user-defined routing criteria. It can perform pre and post routing translation and handle various call processing functions such as rerouting an incoming call to a different channel group or overriding cause code treatments. You can route on the following criteria: ANI (Calling Party) Incoming Channel Group DNIS (Called Party) Q.931 Nature of Address (NOA) Time of Day Routing Features 1000 Route tables per GateControl EMS Route tables can be specific to a particular gateway, or they can be global. Each IMG supports 4 route tables unique to the system, allowing the GateControl EMS to control, monitor, and maintain 250 discrete gateways. Route verification See Validating Your Configuration Import either an Excel spreadsheet or CSV for routing and translation tables. Route from one route table to another with the ability to prevent looping. Configure the IMG to accept calls from multiple gateways with one External Gateway Entry (Gateway Mask field). Translation Appending Info Digits ANI and DNIS Translation Translation based on Channel Group Routing Process The following diagram shows the process the IMG goes through to route a call, and the ClientView GUI panes you use to configure various routing elements. Grey boxes represent ClientView configuration panes. 199 IMG WebHelp Cantata Technology - IMG 1010 Printable WebHelp 200 Product Description Routing Components Topic Location: Product Description > Routing Channel Group A Channel Group is an aggregation of channels that have the same routing requirements. These groups enable you to assign a set of routing properties to all of the channels in a channel group and to assign channel groups to route lists for outgoing channel selection. Translation Tables Translation Tables specify the rules for digit matching, translation, and error detection that the IMG uses to process incoming and outgoing digit strings. See Overview of Translation. Route Tables Route tables specify the way in which the IMG routes or processes a call based on one or more sets of routing criteria. You can create multiple route tables, each of which can contain multiple routing criteria. When the router routes a call, it searches each criteria type until it finds one that matches the call. The sequence in which the routing criteria are listed helps to ensure that the router uses the correct criteria type. You can combine multiple criteria from one or more route tables and instruct the router to use these combined criteria to determine the appropriate terminating channel for a call. You can also use route tables to override cause code treatments. Route Lists Route lists are sets of channel groups from which the router can select an outgoing channel for a call. The goal of the route lists is to route calls in the most efficient and cost-effective manner possible. The channel groups that you assign to a route list provide alternate routes to a call destination. If the channels in one channel group are unavailable due to one of the Cause Codes listed below, the router attempts to select a channel from the remaining channel groups within the route list. The router searches the channel groups based on the hunting option that you specify for the route list. It selects an individual channel based on the hunting option that you specify within a channel group definition. Re-routing Cause Codes: NO CIRCUIT AVAILABLE - Cause Code 34 TEMPORARY FAILURE - Cause Code 41 EXCHANGE CONGESTION - Cause Code 42 201 IMG WebHelp Within each route list, you can define multiple channel group entries to specify alternate channels that the router can use to route a call. If all of the channels in one channel group are seized, the IMG searches each channel group in succession until it either finds a free channel or it runs out of channel groups to check. If the router cannot find a free channel, the call fails. Treatment Tables/Cause Code Mapping Tables In the event that a call can not be routed, the IMG can play a tone or an announcement and/or return a Cause Code to the network. Treatment tables specify the announcements or tones that the IMG plays when it detects an interruption in the call flow. You cannot modify the default Treatment Table. Cause code mapping tables map a cause code to an alternate cause code, enabling you to override the default treatment behavior. See An Overview of Error Handling IP Bearer Profile IP Bearer profiles allow the group to negotiate the terminal capabilities used in H.323 call setup. See IP Bearer Profiles. Cantata Technology - IMG 1010 Printable WebHelp 202 Product Description Incoming Translation Process Topic Location: Product Description > Routing The following diagram illustrates the process that occurs when you implement digit translation on an incoming call. Cantata Technology - IMG 1010 Printable WebHelp 203 IMG WebHelp Digit matching Topic Location: Product Description > Routing The IMG uses digit matching for number selection and validation. The IMG matches on a specific digit string such as dialed number or originating number. Digit Matching is available for all types of Translation Tables. When you create a Translation Table that includes more than one entry, the IMG selects the most specific digit string match. When the IMG receives a call, it searches the entries in the specified Translation Table until it finds a match for the digit string and all applicable call parameters (based on the values in the String to Match and String fields). When it finds a match, the IMG performs the associated translation or error detection. NOTE: To prevent unmatched calls from failing, define a match string for each Translation Table that will match all numbers. For example: &. Sort Order in Translation Tables and Routing Tables Dialed number strings in Translation Tables and Route Tables are sorted according to the following rules: from highest number to lowest (from 9 to 0) from shortest to longest on identical matches (for example, 99 comes before 999) from most specific to least specific (for example, 9 comes before 9&) Example Route Table Entries The following example shows actual entries in a route table as they would be sorted. Entry 2 - Dialed Number,8888 Entry 18 - Dialed Number,8331 Entry 19 - Dialed Number,5828 Entry 8 - Dialed Number,55555 Entry 11 - Dialed Number,5551 Entry 1 - Dialed Number,5348 Entry 14 - Dialed Number,5347 Entry 5 - Dialed Number,5088623000 Entry 4 - Dialed Number,5& Entry 9 - Dialed Number,3778 Entry 13 - Dialed Number,3777 Entry 0 - Dialed Number,3& Digit Matching Examples 204 Product Description The table below shows several matching examples. The first column of the table displays the match strings in a Translation Table. The second column shows the incoming numbers, the third column shows the match string from the Translation Table that the IMG uses to match the number, and the fourth column explains why the number matches. Translation Table Match Strings Number to be Matched Matching String Explanation 5088623200 5088623200 5088623200 exact match 5088623000 5087783000 508XXX3000 No exact match, but the first three digits are 508, the next three can be any value and the last three digits are 3000 508862& 5088622400 508862& No exact or more specific match, but the first six digits are 508862 and the remaining digits can be any value 508XXX3000 5083859999 508& No exact or more specific match, but the first three digits are 508 and the remaining digits can be any value 508& 5088623000 5988623000 exact match Cantata Technology - IMG 1010 Printable WebHelp 205 IMG WebHelp Digit Translation Topic Location: Product Description > Routing Digit translation enables you to modify an incoming or outgoing number or parameter value for purposes such as the following: Adding or removing national or international indicators or carrier codes Handling non-standard parameter values from a service provider Normalizing calls to the same dialing plan Changing a parameter value based on the value in another parameter Rearranging the sequence of digits in a number When the Type of Operation field in the Incoming or Outgoing Translation Table Entry is set to Translation, the IMG will translate the matched number to a different number. The IMG can also translate a parameter value to a different value. You can translate the following numbers and parameters: Dialed Number The dialed number is usually the Called Party Number. Originating Number The originating number is usually the Calling Party Number. When the IMG translates digit strings, it uses a translation mask that you define for the dialed number or originating number. It can also use digits from a secondary digit string to provide a portion of the translated string. For example, if you configure the IMG to translate the dialed number, you can specify that a segment of the translated dialed number is to come from the originating number. Translation Tables Translation Tables define the mechanism that the IMG uses for matching and translating digits in an incoming and/or outgoing digit string. You configure translation using the Incoming Translation Entry or Outgoing Translation Entry panes. You can assign an incoming and/or outgoing translation table to each channel group to specify the type of matching and manipulation the IMG performs for numbers associated with a call that is being routed through a channel in the channel group. You can create up to 20 translation tables which you can assign to one or more channel groups. Each translation table can include one or more entries that define the operations and matching criteria that are required to meet your digit processing needs. Translation Table Types 206 Incoming Translation Table Product Description Provides digit matching and translation for digit strings on an incoming span or channel. Outgoing Translation Table Provides digit matching and translation for digit strings on an outgoing span or channel. ClientView Panes used to Configure Translation Translation Table Table Entry Advanced Dialed Number Parameters Advanced Originating Number Parameters See Using ClientView to Configure Translation Translation Process The digit translation process consists of the following: 1. When the IMG identifies the channel group that is associated with an incoming or outgoing call, it determines whether a translation table is assigned to the channel group. 2. When the IMG determines that a call is associated with a translation table, it passes the call to the IMG 3. Within the translation table, the IMG identifies the entry that contains match criteria that match the call number and applicable call parameters. 4. The IMG then processes the digits and passes the call to the router. If the IMG does not find a match, the call fails. Cantata Technology - IMG 1010 Printable WebHelp 207 IMG WebHelp Digit Translation Examples Topic Location: Product Description > Routing The following table shows various examples of digit translation that will help you to understand how the IMG uses the following translation components to translate a digit string: Digit string to be translated Translation string Match string Digit String to be translated Match string Translation string Description Result 6032253066 6032253066 1& Insert 1 before the number 16032253066 6032253066 603& 011603& Replace the digits to the left of the & (603) with 011603 0116032253066 6032253066 603& & Remove the digits to the left of the & 2253066 6032253066 603& 508& Replace the digits to the left of the & (603) with 508 5082253066 92253066 9& 603& Replace the digit to the left of the & (9) with 603 6032253066 6032253066 6032253066 6035551212 Replace the digits in the match string with the digits in the translation string 6035551212 6032253066 603& &11 Remove the digits to the left of the & 225306611 208 Product Description (603) and append 11 to the end of the number 8005551212 800555& & Remove all digits to the left of the & (800555) 1212 8002221212 800XX& & Remove all digits to the left of the & (80022) 21212 5085551212 508XXX& &603XXX Remove all digits to the left of the & (508555) and then append 603 and the original digits represented by XXX (555) to the end of the number X555YYYY YYYY555X Move the first digit (1) to the end of the number and move the last four digits (3030) to the beginning of the number 30305551 XYYYZZZ& XZZZYYY& Transpose the digits represented by YYY (508) and those represented by ZZZ (862) 18625083000 & Remove the terminating character 6169991 15553030 15088623000 6169991# &# 1212603555 Cantata Technology - IMG 1010 Printable WebHelp 209 IMG WebHelp ClientView Panes used for Service Routing Topic Location: Product Description > Routing The following graphic shows the ClientView panes used in configuring Routing Services and their relationship to one another. Cantata Technology - IMG 1010 Printable WebHelp 210 Product Description Services Routing: Pre-Call Announcements Topic Location: Product Description > Routing Description 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. Implementation This feature uses the Service Route table, in addition to standard routing tables. The flow of a call accessing the various tables is shown below: Based on Destination Number Based on Time of Day 211 IMG WebHelp Functionality SS7 COT If SS7 continuity testing is required on the inbound call leg, the continuity procedure should be completed before the announcement will be played, even if the outbound leg is using the SS7 protocol as well. If an incoming SS7 IAM requests continuity test, indicated in nature of connection indicator parameter the behavior is as follows. If the Continuity Check Indicator is not 0, IMG waits for 10 seconds for the continuity test success event. Once COT with test success is received within this time, treatment will be played. Call Tracing The following information will be present in the call tracing: DPE output: Invoke Service [Branding Service] Router table used to get treatment information Apply treatment: table ID and treatment ID Treatment completed Errors In the event that an internal error occurs during Service Route processing, the call will be allowed to complete without interruption. An Internal error may be: Router response time out Router response NACK No treatment information found on service route table Any NACK from L4 SS7 continuity test time out. Before playing the treatment, internally the channel will be parked which will result in “ACM” (for SS7) or “Alerting” ( for H323 and ISDN) or “183 Call Progress” (for SIP) message being sent to inbound side. Rerun option in a translation entry will not work if service table is selected in that entry. If “bearer capability” information is present in the incoming signaling setup message, the announcement is made only if the value of “Information Transfer capability is one of the following: Speech (0x0) Audio(0x10) Unrestricted digital information(0x8) Unrestricted Digital Information w/Tone&Announcement (0x11) 212 Product Description Cantata Technology - IMG 1010 Printable WebHelp 213 IMG WebHelp An Overview of Error Handling Topic Location: Product Description > Routing The IMG supports the playing of announcements or tones to the Public Switched Telephone Network (PSTN) based on cause codes when a call fails due to an internal or network error. You can specify whether the IMG plays a treatment or releases a call on a per channel group basis. Entities Error handling consists of the following entities: Cause Codes Treatments Cause Codes Cause Code mapping enables you to map the cause code that the IMG receives from the terminating side of a call to a different cause code that the IMG will send to the originating side of the call. You can assign a cause code mapping table to any incoming channel group that requires special cause code handling. See Configuring Error Handling Treatments In response to a Cause Code, the IMG can be configured to release the call and send the Cause Code to the network, or it can play a Treatment: an announcement or a tone. You can map the Treatment that is played in response to a particular Cause Code override, at the channel group level, the treatment that the IMG normally associates with a cause code. When you override the treatment assigned to a cause code, your custom treatment takes precedence over any treatment that either a service or the default cause code handling returns. See Configuring a Channel to Play Treatment Cantata Technology - IMG 1010 Printable WebHelp 214 Product Description Local Number Portability (LNP) Topic Location: Product Description > Routing Overview This feature allows the IMG to route ported numbers for SIP and SS7. Compliance The IMG complies with the following: RFC3398 Section 7.2.1.1 (INVITE to IAM procedures) for SIP to SS7 call scenarios. RFC3398 Section 8.2.1.1 (IAM to INVITE procedures) for SS7 to SIP call scenarios Example A basic LNP scenario is shown below. In this example: Subscriber A=508-4445555 is calling Subscriber B=508-8623606 Subscriber B has been ported and the LEC servicing B is LEC2 and its LRN=3332233445 NOTE: The IMG does not perform the LNP. Tags This feature will add the support of 2 new tags in the R-URI: rn This tag is used to convey the location routing number. npdi 215 IMG WebHelp This is used to indicate whether an LNP query has been performed. Examples INVITE sip:[email protected]:5060;rn=2233445566;npdi=yes SIP/2.0 INVITE sip:[email protected]:5060;rn=2233445566;npdi SIP/2.0 INVITE sip:[email protected]:5060;npdi=yes SIP/2.0 INVITE sip:[email protected]:5060;npdi SIP/2.0 SIP-SS7 Interworking This feature will interwork between the SS7 LNP information and SIP. SS7 to SIP Call Flow SIP to SS7 Call Flow Configuration You enable or disable LNP Routing in the ISUP Group pane. Cantata Technology - IMG 1010 Printable WebHelp 216 Product Description RADIUS An Overview of RADIUS on the IMG Topic Location: Product Description > RADIUS The IMG uses Remote Authentication Dial In User Service (RADIUS) protocol for streaming the Call Detail Records (CDR). The implementation is compliant with RFC 2865 and RFC 2866. The RADIUS messages are sent to external RADIUS servers. The IMG RADIUS interface generates an ACCESS, a START & a STOP Request for the inbound leg and a START & STOP Request for the outbound leg of the call, as well as data associated with the INVITE, the 200 OK, the BYE and the CANCEL methods for those legs utilizing a SIP protocol. Specifications The IMG implementation of RADIUS is based on the following RADIUS RFCs: RFC 2865 - Remote Authentication Dial-In User Service (RADIUS) RFC 2866 - RADIUS Accounting Formats The IMG 1010 supports the Cantata RADIUS formats, which Includes some attributes defined by RFC 2865 and RFC 2866, as well as Cantata Vendor Specific Attributes (VSA). Scenarios The IMG 1010 supports RADIUS Authentication and Accounting. IMG 1010 customer has the option of using one of the following scenarios: Authentication and Accounting In this case an Authentication Server and an Accounting Server are both assigned to the RADIUS client on the IMG. Accounting only In this case only an Accounting Server is assigned to the RADIUS client on the IMG. Authentication only In this case only an Authentication Server is assigned to the RADIUS client on the IMG 1010. See RADIUS Scenarios for more details. As per RFC 2865 and RFC 2866, the IMG 1010 uses port 1812 for Authentication and port 1813 for Accounting by default. But these ports are also configurable. The Authentication and Accounting servers could be the same entity, in which case both servers will have the same IP address. Or they could be different entities with different IP addresses. 217 IMG WebHelp The RADIUS attributes and VSA’s included in the messages will vary based on the protocol for used for a specific side of the call, depending on whether it is a TDM protocol (SS7 or ISDN) or IP protocol (SIP or H.323). The User name and Password values configured for the Authentication Server used will be included in the user name and password attributes in the Access Request message sent from the IMG. RADIUS Server Redundancy The IMG 1010 supports an Active Standby redundancy scheme. Redundancy logic is independent for Authentication and Accounting Servers. When configuring RADIUS servers you may create them with an initial priority preference. The IMG will begin using the preferred Server(s) and switchover to an alternate server after detecting a communication failure to the currently active server. Once the switchover occurs all future Radius messages will flow to the newly active server until a failure occurs on this server. If an error is detected in trying to send a Radius message to this newly active server, the IMG will attempt to switch again back to the previously active server. This behaviour is repeated, until a working server is detected. If the IMG fails to connect to a RADIUS Server an alarm will be sent. You can monitor alarms using EventView. Typically when a RADIUS message needs to be sent to a server, it is assembled and passed to the OS for transport to the currently active server. These servers are configured to send the message, wait 2 seconds and then retry sending the message an additional 3 times. Therefor a RADIUS message will be sent a total of 4 times, with 2 second intervals, before attempting a switchover to the next server, if one is configured. The switchover behaviour is coupled to the message type. Therefore an Accounting Server switchover is independent of an Authentication Server switchover. Under typical call load it will take a while for the switchover to complete since the IMG may have many RADIUS messages queued up to the failed server. Each of these messages must fail and be retried on the newly active server following notification of the send failure. NOTE: A negative response does not constitute a server failure. Supported Packet Types Access-Request Access-Accept Sent to a RADIUS server - conveys information used to determine whether a user is allowed access to a specific NAS, and any special services requested for that user. 218 Sent by the RADIUS server - provides specific configuration information necessary to begin delivery of service to the user. Access-Reject Sent by the RADIUS Server if any value of the received Attributes is not acceptable Product Description Accounting-start Accounting-stop RADIUS Server Debug Mode 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. You enable RADIUS Debug Mode using the RADIUS Client screen. RADIUS Server Failure Alarm The IMG provides automatic alarming notification to IMG users when a Radius Server has changed states and can no longer be accessed. The alarm, reported in EventView, 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. Related Topics Basic RADIUS Call Flow Generic RADIUS Attributes Cantata RADIUS VSAs RADIUS Call Flow: SS7 to H.323 RADIUS CDR Example: SIP-to-ISDN Configuring Billing and Authentication Cantata Technology - IMG 1010 Printable WebHelp 219 IMG WebHelp RADIUS Scenarios Topic Location: Product Description > RADIUS The IMG 1010 supports RADIUS Authentication and Accounting. IMG 1010 customer has the option of using one of the following scenarios: Authentication and Accounting In this case an Authentication Server and an Accounting Server are both assigned to the RADIUS client on the IMG. Accounting only In this case only an Accounting Server is assigned to the RADIUS client on the IMG. Authentication only In this case only an Authentication Server is assigned to the RADIUS client on the IMG 1010. Cantata Technology - IMG 1010 Printable WebHelp 220 Product Description Generic RADIUS Attributes Topic Location: Product Description > RADIUS RADIUS Attributes carry the specific authentication, authorization, information and configuration details for the request and reply. Some Attributes may be included more than once. IETF Attribute # Attribute Name Description Values Example 1 User-Name Account number or calling party number String 50886230002 2 UserPassword 16 octets user password String cantata 4 NAS-IPAddress IP Address of the requesting IMG Numeric (4 octets) 192.168.0.100 5 NAS-Port The Physical Port Number of the NAS (Network Access Server) that is authenticating the user. Numeric (4 octets) 1812 6 ServiceType The Type of Service the user has requested, or the type of service to be provided Numeric Login-User 14 Login-IPHost This Attribute indicates the system with which to connect the user, when the LoginService Attribute is Numeric (4 octets) 192.168.0.100 Values Values 221 IMG WebHelp included. It MAY be used in AccessAccept packets. It MAY be used in an AccessRequest packet as a hint to the server that the NAS would prefer to use that host, but the server is not required to honor the hint. 29 TerminationAction 30 CalledStation-Id RADIUS-Request String 50886230002 1 RADIUSRequest This Attribute allows the NAS to send in the AccessRequest packet the phone number that the user called, using Dialed Number Identification (DNIS) or similar technology. Note that this may be different from the phone number the call comes in on. It is only used in AccessRequest packets. 222 0 Default The String field is one or more octets, containing the phone number that the user's call came in on. Product Description 31 CallingStation-Id This Attribute allows the NAS to send in the AccessRequest packet the phone number that the call came from, using Automatic Number Identification (ANI) or similar technology. It is only used in AccessRequest packets. String 32 NASIdentifier This Attribute contains a string identifying the NAS originating the AccessRequest. It is only used in AccessRequest packets. String 40 Acct-StatusType Indicates whether this AccountingRequest marks the beginning of the user Numeric (4 octets) The String field is one or more octets, containing the phone number that the user placed the call from. 50886230002 The String field is one or more octets, and should be unique to the NAS within the scope of the RADIUS server. For example, a fully qualified domain name would be suitable as a NASIdentifier. Start Values 223 IMG WebHelp service (Start) or the end (Stop). 41 Acct-DelayTime This attribute indicates how many seconds the client has been trying to send this record for, and can be subtracted from the time of arrival on the server to find the approximate time of the event generating this AccountingRequest. (Network transit time is ignored.) Numeric (4 octets) 0 42 Acct-InputOctets Indicates how many octets have been received from the port over the course of this service being provided, and can only be present in AccountingRequest records where the AcctStatus-Type is set to Stop. Numeric (4 octets) 1 43 AcctOutputOctets indicates how many octets have been sent to the port in the course of delivering this service, and Numeric (4 octets) 1 224 Product Description can only be present in AccountingRequest records where the AcctStatus-Type is set to Stop. 44 AcctSession-ID This attribute is a unique Accounting ID to make it easy to match start and stop records in a log file. String 00201c0405b90090003500001000129e48b 46 AcctSessionTime This attribute indicates how many seconds the user has received service for, and can only be present in AccountingRequest records where the AcctStatus-Type is set to Stop. Numeric (4 octets) 10 47 Acct-InputPackets This attribute indicates how many packets have been received from the port over the course of this service being provided to a Framed User, and can only be present in AccountingRequest records where the AcctStatus-Type is set to Stop. Numeric (4 octets) 1 The String field SHOULD be a string of UTF-8 encoded 10646 [7] characters. 225 IMG WebHelp 48 AcctOutputPackets This attribute indicates how many packets have been sent to the port in the course of delivering this service to a Framed User, and can only be present in AccountingRequest records where the AcctStatus-Type is set to Stop. 49 AcctTerminateCause This attribute indicates how the session was terminated, and can only be present in AccountingRequest records where the AcctStatus-Type is set to Stop. 60 ChapChallenge This Attribute contains the CHAP Challenge sent by the NAS to a PPP ChallengeHandshake Authentication Protocol (CHAP) user. It is only used in AccessRequest packets. 61 NAS-PortType This Attribute indicates the type of the 226 Numeric (4 octets) Values 0 NAS-Request String The String field contains the CHAP Challenge. Values Ethernet Product Description physical port of the NAS which is authenticating the user. Cantata Technology - IMG 1010 Printable WebHelp 227 IMG WebHelp Cantata VSAs Topic Location: Product Description > RADIUS Cantata RADIUS Vendor Code: 2754 IETF Attribute # for all VSAs: 26 NOTE: As of 10.3.2 ER2, the word Cantata appears at the beginning of all Cantata VSA names. Attribute Name VSA # Description Cantataani-posttranslate 42 Calling number to be sent out of the IMG. String 5088623000 Cantataani-pretranslate 40 Incoming Automatic Number Identification String 5088623000 Cantatacalldirection 43 The direction of the call. String Calling Party Cantatacall-id 141 Value of the Call-ID header. String [email protected] Gateway's behavior in relation to the connection that is active for this leg. answer = Legs 1 and 3 originate Protocol type or family used on this leg of the call. Telephony Connect time in Network Time Protocol hh:mm:ss:mmm ZON DDD MMM ## YYYY CantataCall-Origin CantataCall-Type 26 27 For example, answer on a leg 1; originate on a leg 2; callback on leg 1. Cantataconnect- 228 28 Value Format Syntax is as per RFC 3261 "SIP:Session Initiation protocol" originate = Legs 2 and 4 Example Called Party callback = Legs 1 and 3 VOIP h323 Call Type = SS7 VOFR 12:30:00.094 EST Fri Mar 24 2006 Product Description time Cantatacredit-time (NTP) format: hour, minutes, seconds, microseconds, time_zone, day, month, day_of_month, and year. 102 Number of seconds for which the call is authorized Integer in decimal notation 3200 Valid Range:1-7200 sec. 0 = unlimited seconds Cantatadisconnecttime 29 Disconnect time in NTP format: hour, minutes, seconds, microseconds, time_zone, day, month, day_of_month, year. hh:mm:ss:mmm ZON DDD MMM ## YYYY 12:30:00.094 EST Fri Mar 24 2006 Cantatadnis-posttranslate 41 Called number to be sent out of the IMG. String 5088623000 Cantatadnis-pretranslate 39 Incoming Dialed Number Identification Service String 5088623000 Cantatah323-confid 24 Unique call identifier generated by the gateway. Used to identify the separate billable events (calls) within a single calling session 16-byte number in hexadecimal notation with one space between each 4-byte integer 75834551 A69E11D6 808D87CA 50D5A43C Cantatah323-gwid 33 Domain name server (DNS) name or local name of the voice gateway that is sending the VSA Character string boston.cantata.com 229 IMG WebHelp Cantatah323incomingconf-id 35 Unique number for identifying a calling session on a gateway, where a session is closed when the calling party hangs up 16-byte number in hexadecimal notation with one space between each 4-byte integer 75834551 A69E11D6 808D87CA 50D5A43C Cantataincomingreq-uri 146 For inbound Radius mess. both Start & Stop. Access to the value after the RFS on the inbound side string. Syntax is as per RFC 3261"SIP:Session Initiation protocol" sip:5551212 @10.129.39.142user=phone Cantatalostpackets 47 Number of lost voice packets during the call. Unsigned integer 0 Cantatamedia-dstrtp-ip 37 Remote media gateway IP address. Numerals in dotted decimal notation: nnn.nnn.nnn.nnn 192.168.0.100 Cantatanext-hopdn 149 The Domain Name (DN) or Fully Qualified Domain Name (FQDN) where the request is forwarded. string next-hop-dn=company.com Cantatanext-hopip 148 Next-hop IP address where the request is forwarded. Numerals in dotted decimal notation: nnn.nnn.nnn.nnn 192.168.0.10 Cantataoutgoingreq-uri 147 For outbound Radius mess.Both Start & Stop Access to the value after outseize of the Invite string. Syntax is asper RFC 3261"SIP:SessionInitiation protocol" outgoing-req-uri = "OUTGOING SIP URI(in) = sip:5551212 @10.129.39.142" Cantataprev-hopip 145 Previous hop IP address, as seen by the string of the form 10.129.39.142:5061/UDP 230 FQDN[:port][/protocol] Where FQDN is a host, domain name or dotted IP address. ip- Product Description 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 address[:port][/protocol] 144 Sent-by portion of topmost via when the request arrived at the proxy. String 10.129.39.142:5060 30 Q.931 disconnect cause code retrieved from CCAPI. The source of the code is the disconnect location such as a PSTN, terminating gateway, or SIP. 2-character, ASCIIencoded hexadecimal number representing a Q.931 code. Range: 01 to A0 (which is 1 to 160 decimal) 3 Cantata redirectnumber 106 Phone number to which the call is redirected; for example, to a toll-free number or a customer service E.164 format (decimal digits with no spacing characters) 14088531111 Cantatareleasesource 38 If a call was released by the calling Values 1 Cantataprev-hopvia CantataQ931disconnectcause Where "port" is an optional parameter giving the transport layer port number and the default is5060. Where "protocol" is an optional parameter giving the transport layer protocol and the default is UDP. Valid values are TCP and UDP, but since the proxy does not support TCP, this parameter Is never included Syntax is as per RFC 3262 "SIP:Session Initiation protocol" Max # of digits is 24 231 IMG WebHelp party, called party, or an internal or external source. CantataSetupTime 25 Setup time in NTP format: hour, minutes, seconds, microseconds, time_zone, day, month, day_of_month, year. hh:mm:ss.mmm ZON DDD MMM ## YYYY 12:30:00.094 EST Fri Mar 24 2006 Cantatasipattemptinfo 151 In case IMG tries the contacts returned with 3xx, IMG will log to the CDR each attempt. Character String sip-attempt-info ="ATTEMPT 1 : [email protected]:5060 status 302" Cantatasip-respcode 150 Sip Cause Code before translation to the Q931 value Character String sip-resp-code = "486 Busy Here" Cantatatimestamp 105 Time of day at the dialed number or at the remote gateway hour, minutes, seconds. Decimal number 8:00:30 Cantatatranscause-code 53 Translated Cause Code when translate cause table is used. Character String trans-cause-code = "16" Cantatatrunk-grpin 44 The trunk group name from where the incoming call has come. Character string SS7_IMG Cantatatrunk-grpout 45 The trunk group name to which the outgoing call is routed. Character string SS7_IMG 232 hh:mm:ss Product Description Cantatavoip-dstrtp-fqdn * 56 Remote RTP FQDN String "module2.cantata.com" Cantatavoip-dstrtp-ip-in 36 Inbound Remote VoIP gateway IP address Numerals in dotted decimal notation: nnn.nnn.nnn.nnn 192.168.0.100 Cantatavoip-dstrtp-ip-out 50 Outbound Remote VoIP gateway IP address. Numerals in dotted decimal notation: nnn.nnn.nnn.nnn 192.168.0.100 Cantatavoip-dstsig-ip-in 23 Inbound IP address of the remote gateway Numerals in dotted decimal notation: nnn.nnn.nnn.nnn 192.168.0.100 Cantatavoip-dstsig-ip-out 49 Outbound IP address of the remote gateway Numerals in dotted decimal notation: nnn.nnn.nnn.nnn 192.168.0.100 Voip Module FQDN. String "module2.cantata.com" Cantatavoip-srcrtp-fqdn * 54 Cantatavoip-srcrtp-ip-in 46 Inbound Source VoIP RTP IP Address Numerals in dotted decimal notation: nnn.nnn.nnn.nnn 192.168.0.100 Cantatavoip-srcrtp-ip-out 51 Outbound Source VoIP RTP IP Address Numerals in dotted decimal notation: nnn.nnn.nnn.nnn 192.168.0.100 Cantatavoip-srcsig-fqdn * 55 SIP Signaling FQDN String "module2.cantata.com" Cantatavoip-srcsig-ip-in 48 Outbound IP address of the source gateway Numerals in dotted decimal notation: nnn.nnn.nnn.nnn 192.168.0.100 Cantatavoip-srcsig-ip-out 52 Inbound IP address of the source gateway Numerals in dotted decimal notation: nnn.nnn.nnn.nnn 192.168.0.100 233 IMG WebHelp * 10.3.3 ER2 or later Cantata Technology - IMG 1010 Printable WebHelp 234 Product Description RADIUS Call Flow: SS7 to SIP Topic Location: Product Description > RADIUS Cantata Technology - IMG 1010 Printable WebHelp 235 IMG WebHelp RADIUS Call Flow: SS7 to H.323 - Release from SS7 Topic Location: Product Description > RADIUS The following call flow shows a call that is released by the calling party (SS7). Cantata Technology - IMG 1010 Printable WebHelp 236 Product Description RADIUS Call Flow: SS7 to H.323 - Release from SS7 Topic Location: Product Description > RADIUS Cantata Technology - IMG 1010 Printable WebHelp 237 IMG WebHelp RADIUS CDR Example: SS7 to H.323 Topic Location: Product Description > RADIUS Thu Apr 26 15:50:41 2007 NAS-IP-Address = 10.129.44.240 NAS-Port = 1812 Calling-Station-Id = "5003" Called-Station-Id = "7000" Acct-Session-Id = "00201c0403c1009400fe1001171135fe0006" Acct-Status-Type = Start NAS-Port-Type = Ethernet Service-Type = Login-User Cantata-h323-conf-id = "a998f20b 433c5a4c 9411f64a f3c12b95" Cantata-call-origin = "originate" Cantata-call-type = "H323" Acct-Delay-Time = 0 Login-IP-Host = 10.129.44.253 Tunnel-Client-Endpoint:0 = "10.129.44.240" Cantata-setup-time = "THU APR 26 19:50:41:337 2007" Cantata-voip-dst-sig-ip-in = "10.129.44.229" Cantata-voip-dst-rtp-ip-in = "10.129.44.229" Cantata-dnis-pre-translate = "7000" Cantata-ani-pre-translate = "6170095003" Cantata-call-direction = "INCOMING LEG" Cantata-trunk-grp-in = "5003_H323_MG02" Cantata-voip-src-rtp-ip-in = "10.129.44.241" Cantata-voip-src-sig-ip-in = "10.129.44.240" Client-IP-Address = 10.129.44.240 Acct-Unique-Session-Id = "e979bb7438eb1b0f" Timestamp = 1177617041 Thu Apr 26 15:50:42 2007 NAS-IP-Address = 10.129.44.240 NAS-Port = 1812 Calling-Station-Id = "6170095003" Called-Station-Id = "6170097000" 238 Product Description Acct-Session-Id = "00201c0403c1009400fe1001171135fe0006" Acct-Status-Type = Start NAS-Port-Type = Ethernet Service-Type = Login-User Cantata-call-origin = "answer" Cantata-call-type = "SS7" Acct-Delay-Time = 0 Login-IP-Host = 10.129.44.253 Tunnel-Client-Endpoint:0 = "10.129.44.240" Cantata-setup-time = "THU APR 26 19:50:41:397 2007" Cantata-connect-time = "THU APR 26 19:50:42:397 2007" Cantata-dnis-post-translate = "6170097000" Cantata-ani-post-translate = "6170095003" Cantata-call-direction = "OUTGOING LEG" Cantata-trunk-grp-out = "7000_INET_SS7_1" Client-IP-Address = 10.129.44.240 Acct-Unique-Session-Id = "e979bb7438eb1b0f" Timestamp = 1177617042 Thu Apr 26 15:51:10 2007 NAS-IP-Address = 10.129.44.240 NAS-Port = 1812 Calling-Station-Id = "5003" Called-Station-Id = "7000" Acct-Session-Id = "00201c0403c1009400fe1001171135fe0006" Acct-Session-Time = 28 Acct-Status-Type = Stop Acct-Terminate-Cause = NAS-Request NAS-Port-Type = Ethernet Service-Type = Login-User Cantata-h323-conf-id = "a998f20b 433c5a4c 9411f64a f3c12b95" Cantata-call-origin = "originate" Cantata-call-type = "H323" Cantata-Q931-disconnect-cause = "10" Acct-Delay-Time = 0 Login-IP-Host = 10.129.44.253 Tunnel-Client-Endpoint:0 = "10.129.44.240" 239 IMG WebHelp Cantata-setup-time = "THU APR 26 19:50:41:337 2007" Cantata-connect-time = "THU APR 26 19:50:42:397 2007" Cantata-disconnect-time = "THU APR 26 19:51:10:907 2007" Cantata-voip-dst-sig-ip-in = "10.129.44.229" Acct-Input-Octets = 216960 Acct-Output-Octets = 235840 Acct-Input-Packets = 1356 Acct-Output-Packets = 1474 Cantata-voip-dst-rtp-ip-in = "10.129.44.229" Cantata-release-source = "CALLING PARTY RELEASE" Cantata-dnis-pre-translate = "7000" Cantata-ani-pre-translate = "6170095003" Cantata-call-direction = "INCOMING LEG" Cantata-trunk-grp-in = "5003_H323_MG02" Cantata-voip-src-rtp-ip-in = "10.129.44.241" Cantata-lost-packets = "0" Cantata-voip-src-sig-ip-in = "10.129.44.240" Client-IP-Address = 10.129.44.240 Acct-Unique-Session-Id = "e979bb7438eb1b0f" Timestamp = 1177617070 Thu Apr 26 15:51:10 2007 NAS-IP-Address = 10.129.44.240 NAS-Port = 1812 Calling-Station-Id = "6170095003" Called-Station-Id = "6170097000" Acct-Session-Id = "00201c0403c1009400fe1001171135fe0006" Acct-Session-Time = 28 Acct-Status-Type = Stop Acct-Terminate-Cause = NAS-Request NAS-Port-Type = Ethernet Service-Type = Login-User Cantata-call-origin = "answer" Cantata-call-type = "SS7" Cantata-Q931-disconnect-cause = "10" Acct-Delay-Time = 0 Login-IP-Host = 10.129.44.253 240 Product Description Tunnel-Client-Endpoint:0 = "10.129.44.240" Cantata-setup-time = "THU APR 26 19:50:41:397 2007" Cantata-connect-time = "THU APR 26 19:50:42:397 2007" Cantata-disconnect-time = "THU APR 26 19:51:10:907 2007" Cantata-release-source = "CALLING PARTY RELEASE" Cantata-dnis-post-translate = "6170097000" Cantata-ani-post-translate = "6170095003" Cantata-call-direction = "OUTGOING LEG" Cantata-trunk-grp-out = "7000_INET_SS7_1" Client-IP-Address = 10.129.44.240 Acct-Unique-Session-Id = "e979bb7438eb1b0f" Timestamp = 1177617070 Cantata Technology - IMG 1010 Printable WebHelp 241 IMG WebHelp RADIUS CDR Example: SIP-to-ISDN Topic Location: Product Description > RADIUS Tue Mar 6 16:45:01 2007 NAS-IP-Address = 10.129.44.240 NAS-Port = 1812 Calling-Station-Id = "2125551212" Called-Station-Id = "5088623000" Acct-Session-Id = "00201c0403c100810089100131ddec1e0002" Acct-Status-Type = Start NAS-Port-Type = Ethernet Service-Type = Login-User Cantata-call-origin = "originate" Cantata-call-type = "SIP" Acct-Delay-Time = 0 Login-IP-Host = 10.129.44.253 Tunnel-Client-Endpoint:0 = "10.129.44.240" Cantata-setup-time = "TUE MAR 06 21:45:01:738 2007" Cantata-voip-dst-sig-ip-in = "10.129.44.254" Cantata-voip-dst-rtp-ip-in = "10.129.44.254" Cantata-dnis-pre-translate = "5088623000" Cantata-ani-pre-translate = "2125551212" Cantata-call-direction = "INCOMING LEG" Cantata-trunk-grp-in = "EB_SIP" Cantata-voip-src-rtp-ip-in = "10.129.44.251" Cantata-voip-src-sig-ip-in = "10.129.44.240" Cantata-call-id = "NDMzNGY0Yjc2Y2FhMDZmNzVlZTQ4ODJiZWZlNWRjNWM." Cantata-prev-hop-ip = "10.129.44.254:5061/UDP" Cantata-prev-hop-via = "sip:10.129.44.254:5061" Cantata-incoming-req-uri = "sip:[email protected]" Client-IP-Address = 10.129.44.240 Acct-Unique-Session-Id = "4366fe3b438fd016" Timestamp = 1173217501 Tue Mar 6 16:45:05 2007 NAS-IP-Address = 10.129.44.240 NAS-Port = 1812 242 Product Description Calling-Station-Id = "2125551212" Called-Station-Id = "5088623000" Acct-Session-Id = "00201c0403c100810089100131ddec1e0002" Acct-Status-Type = Start NAS-Port-Type = Ethernet Service-Type = Login-User Cantata-call-origin = "answer" Cantata-call-type = "ISDN" Acct-Delay-Time = 0 Login-IP-Host = 10.129.44.253 Tunnel-Client-Endpoint:0 = "10.129.44.240" Cantata-setup-time = "TUE MAR 06 21:45:02:408 2007" Cantata-connect-time = "TUE MAR 06 21:45:05:408 2007" Cantata-dnis-post-translate = "5088623000" Cantata-ani-post-translate = "2125551212" Cantata-call-direction = "OUTGOING LEG" Cantata-trunk-grp-out = "ISDN_1" Client-IP-Address = 10.129.44.240 Acct-Unique-Session-Id = "4366fe3b438fd016" Timestamp = 1173217505 Tue Mar 6 16:45:25 2007 NAS-IP-Address = 10.129.44.240 NAS-Port = 1812 Calling-Station-Id = "2125551212" Called-Station-Id = "5088623000" Acct-Session-Id = "00201c0403c100810089100131ddec1e0002" Acct-Session-Time = 20 Acct-Status-Type = Stop Acct-Terminate-Cause = NAS-Request NAS-Port-Type = Ethernet Service-Type = Login-User Cantata-call-origin = "answer" Cantata-call-type = "ISDN" Cantata-Q931-disconnect-cause = "10" Acct-Delay-Time = 0 Login-IP-Host = 10.129.44.253 Tunnel-Client-Endpoint:0 = "10.129.44.240" 243 IMG WebHelp Cantata-setup-time = "TUE MAR 06 21:45:02:408 2007" Cantata-connect-time = "TUE MAR 06 21:45:05:408 2007" Cantata-disconnect-time = "TUE MAR 06 21:45:25:448 2007" Cantata-release-source = "CALLED PARTY RELEASE" Cantata-dnis-post-translate = "5088623000" Cantata-ani-post-translate = "2125551212" Cantata-call-direction = "OUTGOING LEG" Cantata-trunk-grp-out = "ISDN_1" Client-IP-Address = 10.129.44.240 Acct-Unique-Session-Id = "4366fe3b438fd016" Timestamp = 1173217525 Tue Mar 6 16:45:25 2007 NAS-IP-Address = 10.129.44.240 NAS-Port = 1812 Calling-Station-Id = "2125551212" Called-Station-Id = "5088623000" Acct-Session-Id = "00201c0403c100810089100131ddec1e0002" Acct-Session-Time = 20 Acct-Status-Type = Stop Acct-Terminate-Cause = NAS-Request NAS-Port-Type = Ethernet Service-Type = Login-User Cantata-call-origin = "originate" Cantata-call-type = "SIP" Cantata-Q931-disconnect-cause = "10" Acct-Delay-Time = 0 Login-IP-Host = 10.129.44.253 Tunnel-Client-Endpoint:0 = "10.129.44.240" Cantata-setup-time = "TUE MAR 06 21:45:01:738 2007" Cantata-connect-time = "TUE MAR 06 21:45:05:408 2007" Cantata-disconnect-time = "TUE MAR 06 21:45:25:448 2007" Cantata-voip-dst-sig-ip-in = "10.129.44.254" Acct-Input-Octets = 183840 Acct-Output-Octets = 184960 Acct-Input-Packets = 1149 Acct-Output-Packets = 1156 Cantata-voip-dst-rtp-ip-in = "10.129.44.254" 244 Product Description Cantata-release-source = "CALLED PARTY RELEASE" Cantata-dnis-pre-translate = "5088623000" Cantata-ani-pre-translate = "2125551212" Cantata-call-direction = "INCOMING LEG" Cantata-trunk-grp-in = "EB_SIP" Cantata-voip-src-rtp-ip-in = "10.129.44.251" Cantata-lost-packets = "0" Cantata-voip-src-sig-ip-in = "10.129.44.240" Cantata-call-id = "NDMzNGY0Yjc2Y2FhMDZmNzVlZTQ4ODJiZWZlNWRjNWM." Cantata-prev-hop-ip = "10.129.44.254:5061/UDP" Cantata-prev-hop-via = "sip:10.129.44.254:5061" Cantata-incoming-req-uri = "sip:[email protected]" Client-IP-Address = 10.129.44.240 Acct-Unique-Session-Id = "4366fe3b438fd016" Timestamp = 1173217525 Cantata Technology - IMG 1010 Printable WebHelp 245 IMG WebHelp RADIUS CDR Example: SIP to SS7 Topic Location: Product Description > RADIUS Fri Oct 27 11:47:39 2006 NAS-IP-Address = 10.129.51.152 NAS-Port = 1812 Calling-Station-Id = "6175551212" Called-Station-Id = "5088625347" Acct-Session-Id = "00201c0403d9009e007300001000de1b459d4" Acct-Status-Type = Start NAS-Port-Type = Ethernet Service-Type = Login-User Cantata-Call-Origin = "originate" Cantata-Call-Type = "SIP" Acct-Delay-Time = 0 Login-IP-Host = 10.129.51.150 Tunnel-Client-Endpoint:0 = "10.129.51.152" Cantata-Setup-Time = "FRI OCT 27 15:47:39:959 2006" Cantata-voip-dst-sig-ip-in = "10.129.51.140" Cantata-voip-dst-rtp-ip-in = "10.129.51.144" Cantata-dnis-pre-translate = "5088625347" Cantata-ani-pre-translate = "6175551212" Cantata-call-direction = "INCOMING LEG" Cantata-trunk-grp-in = "SIP_CSP" Cantata-voip-src-rtp-ip-in = "10.129.51.134" Cantata-voip-src-sig-ip-in = "10.129.51.152" Cantata-call-id = "[email protected]" Cantata-prev-hop-ip = "10.129.51.140:1053/UDP" Cantata-prev-hop-via = "sip:10.129.51.140:5060" Cantata-incoming-req-uri = "sip:[email protected]" Client-IP-Address = 10.129.51.152 Acct-Unique-Session-Id = "d34eddf4b59683df" Timestamp = 1161964059 Fri Oct 27 11:47:43 2006 246 Product Description NAS-IP-Address = 10.129.51.152 NAS-Port = 1812 Calling-Station-Id = "6175551212" Called-Station-Id = "5088625347" Acct-Session-Id = "00201c0403d9009e007300001000de1b459d4" Acct-Status-Type = Start NAS-Port-Type = Ethernet Service-Type = Login-User Cantata-Call-Origin = "answer" Cantata-Call-Type = "SS7" Acct-Delay-Time = 0 Login-IP-Host = 10.129.51.150 Tunnel-Client-Endpoint:0 = "10.129.51.152" Cantata-Setup-Time = "FRI OCT 27 15:47:40:239 2006" Cantata-connect-time = "FRI OCT 27 15:47:43:869 2006" Cantata-dnis-post-translate = "5088625347" Cantata-ani-post-translate = "6175551212" Cantata-call-direction = "OUTGOING LEG" Cantata-trunk-grp-out = "SS7_E1_CSP" Client-IP-Address = 10.129.51.152 Acct-Unique-Session-Id = "d34eddf4b59683df" Timestamp = 1161964063 Fri Oct 27 11:48:05 2006 NAS-IP-Address = 10.129.51.152 NAS-Port = 1812 Calling-Station-Id = "6175551212" Called-Station-Id = "5088625347" Acct-Session-Id = "00201c0403d9009e007300001000de1b459d4" Acct-Session-Time = 22 Acct-Status-Type = Stop Acct-Terminate-Cause = NAS-Request NAS-Port-Type = Ethernet Service-Type = Login-User Cantata-Call-Origin = "originate" Cantata-Call-Type = "SIP" Cantata-Q931-disconnect-cause = "10" 247 IMG WebHelp Acct-Delay-Time = 222719 Login-IP-Host = 10.129.51.150 Tunnel-Client-Endpoint:0 = "10.129.51.152" Cantata-Setup-Time = "FRI OCT 27 15:47:39:959 2006" Cantata-connect-time = "FRI OCT 27 15:47:43:869 2006" Cantata-disconnect-time = "FRI OCT 27 15:48:05:019 2006" Cantata-voip-dst-sig-ip-in = "10.129.51.140" Acct-Input-Octets = 197760 Acct-Output-Octets = 197920 Acct-Input-Packets = 1236 Acct-Output-Packets = 1237 Cantata-voip-dst-rtp-ip-in = "10.129.51.144" Cantata-release-source = "CALLING PARTY RELEASE" Cantata-dnis-pre-translate = "5088625347" Cantata-ani-pre-translate = "6175551212" Cantata-call-direction = "INCOMING LEG" Cantata-trunk-grp-in = "SIP_CSP" Cantata-voip-src-rtp-ip-in = "10.129.51.134" Cantata-lost-packets = "0" Cantata-voip-src-sig-ip-in = "10.129.51.152" Cantata-call-id = "[email protected]" Cantata-prev-hop-ip = "10.129.51.140:1053/UDP" Cantata-prev-hop-via = "sip:10.129.51.140:5060" Cantata-incoming-req-uri = "sip:[email protected]" Client-IP-Address = 10.129.51.152 Acct-Unique-Session-Id = "d34eddf4b59683df" Timestamp = 1161964085 Fri Oct 27 11:48:05 2006 NAS-IP-Address = 10.129.51.152 NAS-Port = 1812 Calling-Station-Id = "6175551212" Called-Station-Id = "5088625347" Acct-Session-Id = "00201c0403d9009e007300001000de1b459d4" Acct-Session-Time = 22 Acct-Status-Type = Stop Acct-Terminate-Cause = NAS-Request 248 Product Description NAS-Port-Type = Ethernet Service-Type = Login-User Cantata-Call-Origin = "answer" Cantata-Call-Type = "SS7" Cantata-Q931-disconnect-cause = "10" Acct-Delay-Time = 0 Login-IP-Host = 10.129.51.150 Tunnel-Client-Endpoint:0 = "10.129.51.152" Cantata-Setup-Time = "FRI OCT 27 15:47:40:239 2006" Cantata-connect-time = "FRI OCT 27 15:47:43:869 2006" Cantata-disconnect-time = "FRI OCT 27 15:48:05:019 2006" Cantata-release-source = "CALLING PARTY RELEASE" Cantata-dnis-post-translate = "5088625347" Cantata-ani-post-translate = "6175551212" Cantata-call-direction = "OUTGOING LEG" Cantata-trunk-grp-out = "SS7_E1_CSP" Client-IP-Address = 10.129.51.152 Acct-Unique-Session-Id = "d34eddf4b59683df" Timestamp = 1161964085 Cantata Technology - IMG 1010 Printable WebHelp 249 IMG WebHelp RADIUS CDR Example - SIP to SIP with Proxy and DNS Topic Location: Product Description > RADIUS Thu Apr 26 15:33:38 2007 NAS-IP-Address = 10.129.44.240 NAS-Port = 1812 Calling-Station-Id = "4003" Called-Station-Id = "4004" Acct-Session-Id = "00201c0403c1008700ae100113129b080002" Acct-Status-Type = Start NAS-Port-Type = Ethernet Service-Type = Login-User Cantata-call-origin = "originate" Cantata-call-type = "SIP" Acct-Delay-Time = 0 Login-IP-Host = 10.129.44.253 Tunnel-Client-Endpoint:0 = "10.129.44.240" Cantata-setup-time = "THU APR 26 19:33:38:630 2007" Cantata-voip-dst-sig-ip-in = "10.129.44.229" Cantata-voip-dst-rtp-ip-in = "10.129.44.229" Cantata-dnis-pre-translate = "4004" Cantata-ani-pre-translate = "4003" Cantata-call-direction = "INCOMING LEG" Cantata-trunk-grp-in = "4003_SIP_MG02" Cantata-voip-src-rtp-ip-in = "10.129.44.241" Cantata-voip-src-sig-ip-in = "10.129.44.240" Cantata-call-id = "MGI0MjExMzllOGNkYTgwZWQxNGQ1YWExYThkN2VkMGI." Cantata-prev-hop-ip = "10.129.44.229:5060/UDP" Cantata-prev-hop-via = "sip:10.129.44.229:5060" Cantata-incoming-req-uri = "sip:[email protected]" Client-IP-Address = 10.129.44.240 Acct-Unique-Session-Id = "61f0602f64390c0f" Timestamp = 1177616018 Thu Apr 26 15:33:44 2007 NAS-IP-Address = 10.129.44.240 250 Product Description NAS-Port = 1812 Calling-Station-Id = "4003" Called-Station-Id = "4004" Acct-Session-Id = "00201c0403c1008700ae100113129b080002" Acct-Status-Type = Start NAS-Port-Type = Ethernet Service-Type = Login-User Cantata-call-origin = "answer" Cantata-call-type = "SIP" Acct-Delay-Time = 0 Login-IP-Host = 10.129.44.253 Tunnel-Client-Endpoint:0 = "10.129.44.240" Cantata-setup-time = "THU APR 26 19:33:39:110 2007" Cantata-connect-time = "THU APR 26 19:33:44:260 2007" Cantata-dnis-post-translate = "4004" Cantata-ani-post-translate = "4003" Cantata-call-direction = "OUTGOING LEG" Cantata-trunk-grp-out = "4004_SIP_IBM" Cantata-next-hop-ip = "10.129.55.38" Cantata-outgoing-req-uri = "sip:[email protected]" Cantata-next-hop-dn = "10.129.55.38" Cantata-call-id = "[email protected]" Cantata-voip-dst-sig-ip-out = "10.129.55.38" Cantata-voip-dst-rtp-ip-out = "10.129.44.254" Cantata-voip-src-rtp-ip-out = "10.129.44.241" Cantata-voip-src-sig-ip-out = "10.129.44.240" Client-IP-Address = 10.129.44.240 Acct-Unique-Session-Id = "61f0602f64390c0f" Timestamp = 1177616024 Thu Apr 26 15:33:50 2007 NAS-IP-Address = 10.129.44.240 NAS-Port = 1812 Calling-Station-Id = "4003" Called-Station-Id = "4004" Acct-Session-Id = "00201c0403c1008700ae100113129b080002" Acct-Session-Time = 6 251 IMG WebHelp Acct-Status-Type = Stop Acct-Terminate-Cause = NAS-Request NAS-Port-Type = Ethernet Service-Type = Login-User Cantata-call-origin = "answer" Cantata-call-type = "SIP" Cantata-Q931-disconnect-cause = "10" Acct-Delay-Time = 0 Login-IP-Host = 10.129.44.253 Tunnel-Client-Endpoint:0 = "10.129.44.240" Cantata-setup-time = "THU APR 26 19:33:39:110 2007" Cantata-connect-time = "THU APR 26 19:33:44:260 2007" Cantata-disconnect-time = "THU APR 26 19:33:50:090 2007" Acct-Input-Octets = 45920 Acct-Output-Octets = 46560 Acct-Input-Packets = 287 Acct-Output-Packets = 291 Cantata-release-source = "CALLED PARTY RELEASE" Cantata-dnis-post-translate = "4004" Cantata-ani-post-translate = "4003" Cantata-call-direction = "OUTGOING LEG" Cantata-trunk-grp-out = "4004_SIP_IBM" Cantata-lost-packets = "0" Cantata-next-hop-ip = "10.129.55.38" Cantata-outgoing-req-uri = "sip:[email protected]" Cantata-next-hop-dn = "10.129.55.38" Cantata-call-id = "[email protected]" Cantata-voip-dst-sig-ip-out = "10.129.55.38" Cantata-voip-dst-rtp-ip-out = "10.129.44.254" Cantata-voip-src-rtp-ip-out = "10.129.44.241" Cantata-voip-src-sig-ip-out = "10.129.44.240" Client-IP-Address = 10.129.44.240 Acct-Unique-Session-Id = "61f0602f64390c0f" Timestamp = 1177616030 Thu Apr 26 15:33:50 2007 NAS-IP-Address = 10.129.44.240 252 Product Description NAS-Port = 1812 Calling-Station-Id = "4003" Called-Station-Id = "4004" Acct-Session-Id = "00201c0403c1008700ae100113129b080002" Acct-Session-Time = 6 Acct-Status-Type = Stop Acct-Terminate-Cause = NAS-Request NAS-Port-Type = Ethernet Service-Type = Login-User Cantata-call-origin = "originate" Cantata-call-type = "SIP" Cantata-Q931-disconnect-cause = "10" Acct-Delay-Time = 0 Login-IP-Host = 10.129.44.253 Tunnel-Client-Endpoint:0 = "10.129.44.240" Cantata-setup-time = "THU APR 26 19:33:38:630 2007" Cantata-connect-time = "THU APR 26 19:33:44:260 2007" Cantata-disconnect-time = "THU APR 26 19:33:50:090 2007" Cantata-voip-dst-sig-ip-in = "10.129.44.229" Acct-Input-Octets = 86880 Acct-Output-Octets = 88640 Acct-Input-Packets = 543 Acct-Output-Packets = 554 Cantata-voip-dst-rtp-ip-in = "10.129.44.229" Cantata-release-source = "CALLED PARTY RELEASE" Cantata-dnis-pre-translate = "4004" Cantata-ani-pre-translate = "4003" Cantata-call-direction = "INCOMING LEG" Cantata-trunk-grp-in = "4003_SIP_MG02" Cantata-voip-src-rtp-ip-in = "10.129.44.241" Cantata-lost-packets = "0" Cantata-voip-src-sig-ip-in = "10.129.44.240" Cantata-call-id = "MGI0MjExMzllOGNkYTgwZWQxNGQ1YWExYThkN2VkMGI." Cantata-prev-hop-ip = "10.129.44.229:5060/UDP" Cantata-prev-hop-via = "sip:10.129.44.229:5060" Cantata-incoming-req-uri = "sip:[email protected]" 253 IMG WebHelp Client-IP-Address = 10.129.44.240 Acct-Unique-Session-Id = "61f0602f64390c0f" Timestamp = 1177616030 Cantata Technology - IMG 1010 Printable WebHelp 254 Product Description RADIUS CDR Example: CAS to SS7 Topic Location: Product Description > RADIUS Tue Oct 24 16:54:42 2006 NAS-IP-Address = 10.129.39.51 NAS-Port = 1812 Calling-Station-Id = "5088888888" Called-Station-Id = "1181234566" Acct-Session-Id = "00201c111973009e00f6000010012614a6b26" Acct-Status-Type = Start NAS-Port-Type = Ethernet Service-Type = Login-User Cantata-call-origin = "originate" Cantata-call-type = "CAS T1" Acct-Delay-Time = 0 Login-IP-Host = 10.129.45.71 Tunnel-Client-Endpoint:0 = "10.129.39.51" Cantata-setup-time = "TUE OCT 24 20:54:44:846 2006" Cantata-dnis-pre-translate = "1181234566" Cantata-ani-pre-translate = "5088888888" Cantata-call-direction = "INCOMING LEG" Cantata-trunk-grp-in = "IncomingCAS" Client-IP-Address = 10.129.39.51 Acct-Unique-Session-Id = "6331a70cd9eff252" Timestamp = 1161723282 Tue Oct 24 16:54:42 2006 NAS-IP-Address = 10.129.39.51 NAS-Port = 1812 Calling-Station-Id = "5088888888" Called-Station-Id = "1181234566" Acct-Session-Id = "00201c111973009e00f6000010012614a6b26" Acct-Status-Type = Start NAS-Port-Type = Ethernet Service-Type = Login-User Cantata-call-origin = "answer" Cantata-call-type = "SS7" Acct-Delay-Time = 0 255 IMG WebHelp Login-IP-Host = 10.129.45.71 Tunnel-Client-Endpoint:0 = "10.129.39.51" Cantata-setup-time = "TUE OCT 24 20:54:44:916 2006" Cantata-connect-time = "TUE OCT 24 20:54:44:916 2006" Cantata-dnis-post-translate = "1181234566" Cantata-ani-post-translate = "5088888888" Cantata-call-direction = "OUTGOING LEG" Cantata-trunk-grp-out = "ss7_out" Client-IP-Address = 10.129.39.51 Acct-Unique-Session-Id = "6331a70cd9eff252" Timestamp = 1161723282 Tue Oct 24 16:54:48 2006 NAS-IP-Address = 10.129.39.51 NAS-Port = 1812 Calling-Station-Id = "5088888888" Called-Station-Id = "1181234566" Acct-Session-Id = "00201c111973009e00f6000010012614a6b26" Acct-Session-Time = 7 Acct-Status-Type = Stop Acct-Terminate-Cause = NAS-Request NAS-Port-Type = Ethernet Service-Type = Login-User Cantata-call-origin = "answer" Cantata-call-type = "SS7" Cantata-Q931-disconnect-cause = "11" Acct-Delay-Time = 0 Login-IP-Host = 10.129.45.71 Tunnel-Client-Endpoint:0 = "10.129.39.51" Cantata-setup-time = "TUE OCT 24 20:54:44:916 2006" Cantata-connect-time = "TUE OCT 24 20:54:44:916 2006" Cantata-disconnect-time = "TUE OCT 24 20:54:51:486 2006" Cantata-release-source = "CALLED PARTY RELEASE" Cantata-dnis-post-translate = "1181234566" Cantata-ani-post-translate = "5088888888" Cantata-call-direction = "OUTGOING LEG" Cantata-trunk-grp-out = "ss7_out" Client-IP-Address = 10.129.39.51 256 Product Description Acct-Unique-Session-Id = "6331a70cd9eff252" Timestamp = 1161723288 Tue Oct 24 16:54:50 2006 NAS-IP-Address = 10.129.39.51 NAS-Port = 1812 Calling-Station-Id = "5088888888" Called-Station-Id = "1181234566" Acct-Session-Id = "00201c111973009e00f6000010012614a6b26" Acct-Session-Time = 9 Acct-Status-Type = Stop Acct-Terminate-Cause = NAS-Request NAS-Port-Type = Ethernet Service-Type = Login-User Cantata-call-origin = "originate" Cantata-call-type = "CAS T1" Cantata-Q931-disconnect-cause = "11" Acct-Delay-Time = 0 Login-IP-Host = 10.129.45.71 Tunnel-Client-Endpoint:0 = "10.129.39.51" Cantata-setup-time = "TUE OCT 24 20:54:44:846 2006" Cantata-connect-time = "TUE OCT 24 20:54:44:916 2006" Cantata-disconnect-time = "TUE OCT 24 20:54:51:486 2006" Cantata-release-source = "CALLED PARTY RELEASE" Cantata-dnis-pre-translate = "1181234566" Cantata-ani-pre-translate = "5088888888" Cantata-call-direction = "INCOMING LEG" Cantata-trunk-grp-in = "IncomingCAS" Client-IP-Address = 10.129.39.51 Acct-Unique-Session-Id = "6331a70cd9eff252" Timestamp = 1161723290 Cantata Technology - IMG 1010 Printable WebHelp 257 IMG WebHelp RADIUS CDR Example: SS7 to CAS Topic Location: Product Description > RADIUS Wed Oct 25 13:38:56 2006 NAS-IP-Address = 10.129.39.51 NAS-Port = 1812 Calling-Station-Id = "9082841234" Called-Station-Id = "5088621234" Acct-Session-Id = "00201c111973008f004d00001000f8305baaf4" Acct-Status-Type = Start NAS-Port-Type = Ethernet Service-Type = Login-User Cantata-call-origin = "originate" Cantata-call-type = "SS7" Acct-Delay-Time = 0 Login-IP-Host = 10.129.45.71 Tunnel-Client-Endpoint:0 = "10.129.39.51" Cantata-setup-time = "WED OCT 25 17:38:56:672 2006" Cantata-dnis-pre-translate = "5088621234" Cantata-ani-pre-translate = "9082841234" Cantata-call-direction = "INCOMING LEG" Cantata-trunk-grp-in = "ss7_in" Client-IP-Address = 10.129.39.51 Acct-Unique-Session-Id = "77debfa2fbe236b0" Timestamp = 1161797936 Wed Oct 25 13:39:06 2006 NAS-IP-Address = 10.129.39.51 NAS-Port = 1812 Calling-Station-Id = "9082841234" Called-Station-Id = "5088621234" Acct-Session-Id = "00201c111973008f004d00001000f8305baaf4" Acct-Status-Type = Start NAS-Port-Type = Ethernet Service-Type = Login-User Cantata-call-origin = "answer" Cantata-call-type = "CAS T1" Acct-Delay-Time = 0 258 Product Description Login-IP-Host = 10.129.45.71 Tunnel-Client-Endpoint:0 = "10.129.39.51" Cantata-setup-time = "WED OCT 25 17:39:00:234 2006" Cantata-connect-time = "WED OCT 25 17:39:07:164 2006" Cantata-dnis-post-translate = "5088621234" Cantata-ani-post-translate = "9082841234" Cantata-call-direction = "OUTGOING LEG" Cantata-trunk-grp-out = "IncomingCAS" Client-IP-Address = 10.129.39.51 Acct-Unique-Session-Id = "77debfa2fbe236b0" Timestamp = 1161797946 Wed Oct 25 13:39:16 2006 NAS-IP-Address = 10.129.39.51 NAS-Port = 1812 Calling-Station-Id = "9082841234" Called-Station-Id = "5088621234" Acct-Session-Id = "00201c111973008f004d00001000f8305baaf4" Acct-Session-Time = 10 Acct-Status-Type = Stop Acct-Terminate-Cause = NAS-Request NAS-Port-Type = Ethernet Service-Type = Login-User Cantata-call-origin = "originate" Cantata-call-type = "SS7" Cantata-Q931-disconnect-cause = "10" Acct-Delay-Time = 0 Login-IP-Host = 10.129.45.71 Tunnel-Client-Endpoint:0 = "10.129.39.51" Cantata-setup-time = "WED OCT 25 17:38:56:672 2006" Cantata-connect-time = "WED OCT 25 17:39:07:164 2006" Cantata-disconnect-time = "WED OCT 25 17:39:17:214 2006" Cantata-release-source = "CALLING PARTY RELEASE" Cantata-dnis-pre-translate = "5088621234" Cantata-ani-pre-translate = "9082841234" Cantata-call-direction = "INCOMING LEG" Cantata-trunk-grp-in = "ss7_in" Client-IP-Address = 10.129.39.51 259 IMG WebHelp Acct-Unique-Session-Id = "77debfa2fbe236b0" Timestamp = 1161797956 Wed Oct 25 13:39:18 2006 NAS-IP-Address = 10.129.39.51 NAS-Port = 1812 Calling-Station-Id = "9082841234" Called-Station-Id = "5088621234" Acct-Session-Id = "00201c111973008f004d00001000f8305baaf4" Acct-Session-Time = 10 Acct-Status-Type = Stop Acct-Terminate-Cause = NAS-Request NAS-Port-Type = Ethernet Service-Type = Login-User Cantata-call-origin = "answer" Cantata-call-type = "CAS T1" Cantata-Q931-disconnect-cause = "10" Acct-Delay-Time = 0 Login-IP-Host = 10.129.45.71 Tunnel-Client-Endpoint:0 = "10.129.39.51" Cantata-setup-time = "WED OCT 25 17:39:00:234 2006" Cantata-connect-time = "WED OCT 25 17:39:07:164 2006" Cantata-disconnect-time = "WED OCT 25 17:39:17:214 2006" Cantata-release-source = "CALLING PARTY RELEASE" Cantata-dnis-post-translate = "5088621234" Cantata-ani-post-translate = "9082841234" Cantata-call-direction = "OUTGOING LEG" Cantata-trunk-grp-out = "IncomingCAS" Client-IP-Address = 10.129.39.51 Acct-Unique-Session-Id = "77debfa2fbe236b0" Timestamp = 1161797958 Cantata Technology - IMG 1010 Printable WebHelp 260 Product Description RADIUS for Pre-Paid Applications Topic Location: Product Description > RADIUS The IMG sends and receives certain data pertaining to prepaid applications, allowing the IMG to be used in a prepaid application environment. Configuration 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. Sent VSAs The IMG sends the following VSAs and RADIUS attributes to the Authentication Server: Called-Station-Id Calling-Station-Id Cantata-call-type = Cantata-voip-dst-sig-ip-in = Cantata-trunk-grp-in = Received VSAs The IMG accepts and acts upon the following VSAs received in RADIUS Authentication Response messages: VSA 102: Cantata-credit-time (Call Duration) Number of seconds for which the call is authorized. Call Tracing: Will indicate Using Radius MaxDurCall=<n> seconds and Releasing Call,Radius MaxCallDuration=<n> secs elapsed. (VSA # 102) VSA 106: Cantata-redirect-number (New Dialed Number) Phone number to which the call is redirected; for example, to a toll-free number or a customer service. Call Tracing: Will indicate Using Radius DN=[<#>], which overrides the Dialed number received in the incoming call. VSA 45: Cantata-trunk-grp-out (Outgoing Trunk Group) (10.3.3 ER1 and above) 261 IMG WebHelp The trunk group name to which the outgoing call is routed. The IMG will skip the mid-stream routing process and route the call to the channel group indicated by the RADIUS server. Call Tracing: Will indicate Using Radius DTG=[<trunk grp>] Routing Using Pre-paid Application The IMG supports the routing of calls to a channel group indicated by a RADIUS server. If Pre-paid Support is enabled and the IMG receives VSA 45: Cantata-trunkgrp-out from the RADIUS server, the IMG will skip the mid-stream routing process and route the call to the channel group indicated by the RADIUS server. Also See RADIUS Call Trace: Pre-paid Support RADIUS Call Trace: Routing with Pre-paid Application Cantata RADIUS VSAs RADIUS Client pane Cantata Technology - IMG 1010 Printable WebHelp 262 Product Description RADIUS Call Trace Example: Pre-Paid Support Topic Location: Product Description > RADIUS The following call trace shows a SIP to SIP call with Pre-paid Support enabled. Important lines related to Pre-paid Support are in red. 18:07:02.077 CALL(SIP) (01:0001:00) RCVD INVITE from 10.129.44.226:5060 UDP 18:07:02.077 CALL(SIP) (01:0001:00) 10.129.44.226 with Via sent-by: 18:07:02.077 CALL(SIP) (01:0001:00) SENT 100 Trying [] to 10.129.44.226:5060 18:07:02.077 CALL(SIP) (01:0001:00) SENT Route Ctrl to L4 18:07:02.077 CALL(L4) (01:0001:00) RCVD Route Control from SIP 18:07:02.077 CALL(L4) (01:0001:00) Accessing Route Table 2 18:07:02.077 CALL(L4) (01:0001:00) Accessing Resource Table 1 18:07:02.077 CALL(L4) (01:0001:00) SENT Route Control Ack to SIP 18:07:02.077 CALL(SIP) (01:0001:00) RCVD Route Ctrl Ack from L4 18:07:02.077 CALL(SIP) (01:0001:00) Session Group Profile ID is 0 18:07:02.077 CALL(SIP) (01:0001:00) SENT Route Ctrl to L4 18:07:02.077 CALL(L4) (01:0001:00) RCVD Route Control from SIP 18:07:02.077 CALL(L4) (01:0001:00) Accessing IP Bearer Profiles 18:07:02.077 CALL(L4) (01:0001:00) Profile Id 1 (RG 769) 18:07:02.077 CALL(L4) (01:0001:00) SENT Route Control Ack to SIP 18:07:02.077 CALL(SIP) (01:0001:00) RCVD Route Ctrl Ack from L4 18:07:02.077 CALL(SIP) (01:0001:00) m line codec list: 0 101 18:07:02.077 CALL(SIP) (01:0001:00) RTP Type: 0, name: PCMU, clk: 8000 18:07:02.077 CALL(SIP) (01:0001:00) RTP Type: 101, name: telephoneevent, clk: 8000 18:07:02.077 CALL(SIP) (01:0001:00) Leg 0 associated with hndl(19999), LTS(1792) 18:07:02.077 CALL(SIP) (01:0001:00) SENT Setup to L4 18:07:02.077 CALL(L4) (01:0001:00) RCVD Setup Ind 18:07:02.077 CALL(L4) (01:0001:00) SENT RFS to GCL from SIP 18:07:02.077 CALL(GCL) (00:0000:00) SENT RADIUS AUTH REQUEST 18:07:02.077 CALL(GCL) (01:0001:00) RCVD RFS DN=[4004] ANI=[5084444444] from L4 18:07:02.077 CALL(GCL) (01:0001:00) ANI APRI=[0],SI=[0],Category=[10] 263 IMG WebHelp 18:07:02.077 CALL(GCL) (01:0001:00) Incoming Channel Group = 10 [4001_SIP_Snom200] 18:07:02.087 CALL(GCL) (01:0001:00) RCVD RADIUS AUTH ACCEPT ACK 18:07:02.087 CALL(GCL) (01:0001:00) Using Radius MaxDurCall=1 seconds 18:07:02.087 CALL(GCL) (01:0001:00) SENT RADIUS ACCT START 18:07:02.087 CALL(L4) (01:0001:00) RCVD RFS response from GCL 18:07:02.397 CALL(GCL) (01:0001:00) RCVD RADIUS ACCT START 18:07:02.397 CALL(GCL) (01:0001:01) SENT Route Control to L4 18:07:02.397 CALL(L4) (01:0001:00) RCVD Route Control from GCL 18:07:02.397 CALL(L4) (01:0001:00) Accessing Route Table 5 18:07:02.397 CALL(GCL) (01:0001:01) RCVD Mid Stream Router Response 18:07:02.397 CALL(GCL) (01:0001:01) Outgoing Channel Group = 13 [SIP_IBM_5060] 18:07:02.397 CALL(GCL) (01:0001:01) SENT Route Control to L4 18:07:02.397 CALL(L4) (01:0001:01) RCVD Route Control from GCL 18:07:02.397 CALL(L4) (01:0001:01) Accessing Resource Table 1 18:07:02.397 CALL(L4) (01:0001:01) Resource Group ID is 1 18:07:02.407 CALL(L4) (01:0001:01) SENT Outseize Ctrl to SIP 18:07:02.407 CALL(GCL) (01:0001:01) RCVD CPE of ADDRESS INFO from L4 18:07:02.407 CALL(GCL) (01:0001:01) Leg 1 associated with LTS(1024) 18:07:02.407 CALL(SIP) (01:0001:01) RCVD Outseize Ctrl from L4 18:07:02.407 CALL(SIP) (01:0001:01) SENT Route Ctrl to L4 18:07:02.407 CALL(L4) (01:0001:01) RCVD Route Control from SIP 18:07:02.407 CALL(L4) (01:0001:01) Accessing GatewayId to IP Tables 18:07:02.407 CALL(L4) (01:0001:01) Gateway ID is 1028 18:07:02.407 CALL(L4) (01:0001:01) SENT Route Control Ack to SIP 18:07:02.407 CALL(SIP) (01:0001:01) RCVD Route Ctrl Ack from L4 18:07:02.407 CALL(SIP) (01:0001:01) Session Group Profile ID is 0 18:07:02.407 CALL(SIP) (01:0001:01) SENT Route Ctrl to L4 18:07:02.407 CALL(L4) (01:0001:01) RCVD Route Control from SIP 18:07:02.407 CALL(L4) (01:0001:01) Accessing IP Bearer Profiles 18:07:02.407 CALL(L4) (01:0001:01) Profile Id 1 (RG 769) 18:07:02.407 CALL(L4) (01:0001:01) SENT Route Control Ack to SIP 18:07:02.407 CALL(SIP) (01:0001:01) RCVD Route Ctrl Ack from L4 18:07:02.407 CALL(SIP) (01:0001:01) SENT INVITE to 10.129.44.254:5060 UDP 18:07:02.407 CALL(SIP) (01:0001:01) UDP 264 with R-URI: 10.129.44.254:5060 Product Description 18:07:02.517 CALL(SIP) (01:0001:01) RCVD 180 Ringing from 10.129.44.254:5060 UDP 18:07:02.517 CALL(SIP) (01:0001:01) SENT Outseize Ack to L4 18:07:02.517 CALL(SIP) (01:0001:01) SENT Alerting to L4 18:07:02.517 CALL(L4) (01:0001:01) RCVD Outseize ACK 18:07:02.517 CALL(L4) (01:0001:01) RVCD Alerting from SIP from SIP 18:07:02.517 CALL(GCL) (01:0001:00) SENT Connect Tone to L4 18:07:02.517 CALL(L4) (01:0001:00) RCVD Connect Tone from GCL 18:07:02.517 CALL(L4) (01:0001:00) SENT Request DSP Service to SYSRM 18:07:02.517 CALL(MED) (01:0001:00) Transmitting tone 0x2 on (0x1,0x1,0x0) 18:07:02.517 CALL(MED) (01:0001:00) RCVD OUTPULSE CP 18:07:02.517 CALL(GCL) (01:0001:00) SENT Connect w/Pad Response to L4 18:07:02.517 CALL(L4) (01:0001:00) SENT Progress to SIP 18:07:02.517 CALL(SIP) (01:0001:01) RCVD Host Connect from L4 18:07:02.517 CALL(SIP) (01:0001:00) RCVD Progress from L4 18:07:02.517 CALL(SIP) (01:0001:00) Set Fax Type to Bypass 18:07:02.517 CALL(SIP) (01:0001:00) SENT L3-L3 Outseize Ctrl to VPPL 18:07:02.517 CALL(IP) [m1.0.1] (01:0001:00) RCVD Outseize from L3, [vts 768] 18:07:02.517 CALL(IP) (01:0001:00) RTP: (Src) 10.129.44.251:11072 18:07:02.517 CALL(IP) (01:0001:00) RTP: (Dst) 10.129.44.226:10002 18:07:02.527 CALL(IP) Size is 20ms (01:0001:00) VoIP Codec is G711Mulaw; Payload 18:07:02.527 CALL(IP) Payload Type is 101 (01:0001:00) RFC2833 DTMF Relay in use, Dynamic 18:07:02.547 CALL(IP) x66 (01:0001:00) SENT Outseize ACK to L3P, toPvid: 18:07:02.547 CALL(SIP) (01:0001:00) RCVD Outseize Ack from VPPL 18:07:02.547 CALL(SIP) (01:0001:00) SENT 183 Session Progress to 10.129.44.226:5060 UDP 18:07:02.547 CALL(SIP) (01:0001:00) RCVD Cut Thru from VPPL 18:07:02.547 CALL(SIP) (01:0001:00) RCVD Connect from VPPL 18:07:06.337 CALL(SIP) (01:0001:01) RCVD 200 OK from 10.129.44.254:5060 UDP 18:07:06.337 CALL(SIP) (01:0001:01) SENT ACK to 10.129.44.254:5060 UDP 18:07:06.337 CALL(SIP) (01:0001:01) UDP with R-URI: 10.129.44.254:5060 18:07:06.337 CALL(SIP) (01:0001:01) m line codec list: 0 18:07:06.337 CALL(SIP) (01:0001:01) RTP Type: 0, name: PCMU, clk: 8000 265 IMG WebHelp 18:07:06.337 CALL(SIP) (01:0001:01) Set Fax Type to Bypass 18:07:06.337 CALL(SIP) (01:0001:01) SENT L3-L3 Outseize Ctrl to VPPL 18:07:06.337 CALL(IP) [m0.0.1] (01:0001:01) RCVD Outseize from L3, [vts 0] 18:07:06.337 CALL(IP) (01:0001:01) RTP: (Src) 10.129.44.241:8000 18:07:06.337 CALL(IP) (01:0001:01) RTP: (Dst) 10.129.44.254:29574 18:07:06.347 CALL(IP) Size is 20ms (01:0001:01) VoIP Codec is G711Mulaw; Payload 18:07:06.347 CALL(IP) Payload Type is 120 (01:0001:01) RFC2833 DTMF Relay in use, Dynamic 18:07:06.367 CALL(IP) x66 (01:0001:01) SENT Outseize ACK to L3P, toPvid: 18:07:06.367 CALL(SIP) (01:0001:01) RCVD Outseize Ack from VPPL 18:07:06.367 CALL(SIP) (01:0001:01) SENT Connect to L4 18:07:06.367 CALL(SIP) (01:0001:01) RCVD Cut Thru from VPPL 18:07:06.367 CALL(SIP) (01:0001:01) RCVD Connect from VPPL 18:07:06.367 CALL(L4) (01:0001:01) RCVD Connect from SIP 18:07:06.367 CALL(L4) (01:0001:01) SENT CPE of ANSWER 18:07:06.367 CALL(GCL) (01:0001:01) RCVD CPE of ANSWER to GCL from L4 18:07:06.367 CALL(GCL) (01:0001:01) SENT RADIUS ACCT START 18:07:06.367 CALL(GCL) (01:0001:01) RCVD RADIUS ACCT START 18:07:06.367 CALL(GCL) (01:0001:00) SENT Disconnect Tone to L4 18:07:06.367 CALL(L4) (01:0001:00) RCVD Disconnect Tone from GCL 18:07:06.367 CALL(L4) (01:0001:00) SENT Cancel DSP Service to SYSRM 18:07:06.367 CALL(MED) (01:0001:00) RCVD CANCEL OUTPULSE CP 18:07:06.367 CALL(MED) (01:0001:00) RCVD CANCEL OUTPULSE DIGITS 18:07:06.367 CALL(GCL) (01:0001:00) SENT CPE of ANSWER to L4 18:07:06.367 CALL(L4) (01:0001:00) RCVD CPE of ANSWER from GCL 18:07:06.367 CALL(L4) (01:0001:00) SENT Connect to SIP 18:07:06.367 CALL(L4) (01:0001:01) SENT Connect to SIP 18:07:06.367 CALL(SIP) (01:0001:00) RCVD Connect from L4 18:07:06.367 CALL(SIP) (01:0001:00) SENT 200 OK to 10.129.44.226:5060 UDP 18:07:06.367 CALL(SIP) (01:0001:01) RCVD Connect from L4 18:07:06.437 CALL(SIP) (01:0001:00) RCVD ACK from 10.129.44.226 UDP 18:07:06.437 CALL(SIP) (01:0001:00) 10.129.44.226 with Via sent-by: 18:07:07.387 CALL(GCL) (01:0001:00) Releasing Call,Radius MaxCallDuration=1 secs elapsed 18:07:07.387 CALL(GCL) (01:0001:00) SENT Park Port to L4 266 Product Description 18:07:07.387 CALL(L4) (01:0001:00) RCVD Park from GCL 18:07:07.387 CALL(GCL) (01:0001:01) SENT Clear Response to L4 18:07:07.387 CALL(GCL) (01:0001:00) SENT Clear Response to L4 18:07:07.387 CALL(L4) (01:0001:01) RCVD Clear from GCL 18:07:07.387 CALL(L4) (01:0001:01) SENT Clear Request to SIP 18:07:07.387 CALL(L4) (01:0001:00) RCVD Clear 18:07:07.387 CALL(L4) (01:0001:00) SENT Clear Request to SIP from GCL 18:07:07.387 CALL(SIP) (01:0001:01) RCVD Clear Request from L4 18:07:07.387 CALL(SIP) (01:0001:01) SENT BYE to 10.129.44.254:5060 UDP 18:07:07.387 CALL(SIP) (01:0001:01) UDP with R-URI: 10.129.44.254:5060 18:07:07.387 CALL(SIP) (01:0001:00) RCVD Clear Request from L4 18:07:07.387 CALL(SIP) (01:0001:00) SENT BYE to 10.129.44.226:5060 UDP 18:07:07.387 CALL(SIP) (01:0001:00) UDP with R-URI: 10.129.44.226:5060 18:07:07.437 CALL(SIP) (01:0001:00) RCVD 200 OK from 10.129.44.226:5060 UDP 18:07:07.437 CALL(SIP) (01:0001:00) SENT L3-L3 Clear Req to VPPL 18:07:07.437 CALL(IP) (01:0001:00) RCVD Clear Request from L3 18:07:07.437 CALL(IP) (01:0001:00) RTCP STATS: TxPackets=244; RxPackets=241; lostPackets=0 18:07:07.437 CALL(IP) (01:0001:00) RTCP/T38 Packet STATS: TxPackets=244; RxPackets=241; lostPackets=0 18:07:07.437 CALL(SIP) (01:0001:00) RCVD Clear Req from VPPL 18:07:07.437 CALL(SIP) (01:0001:00) SENT Clear Request to L4 18:07:07.437 CALL(L4) (01:0001:00) RCVD Clear request from SIP 18:07:07.437 CALL(L4) (01:0001:00) SENT Channel Release w/data to GCL 18:07:07.437 CALL(GCL) (01:0001:00) RCVD Channel Released w/data from L4 18:07:07.437 CALL(GCL) (01:0001:00) Call Duration(sec): 1 18:07:07.437 CALL(GCL) (01:0001:00) Radius Call Duration(sec): 1 18:07:07.437 CALL(GCL) (01:0001:00) SENT RADIUS ACCT STOP 18:07:07.557 CALL(SIP) (01:0001:01) RCVD 200 OK from 10.129.44.254:5060 UDP 18:07:07.557 CALL(SIP) (01:0001:01) SENT L3-L3 Clear Req to VPPL 18:07:07.557 CALL(IP) (01:0001:01) RCVD Clear Request from L3 18:07:07.557 CALL(IP) (01:0001:01) RTCP STATS: TxPackets=59; RxPackets=49; lostPackets=0 18:07:07.557 CALL(IP) (01:0001:01) RTCP/T38 Packet STATS: TxPackets=59; RxPackets=49; lostPackets=0 267 IMG WebHelp 18:07:07.557 CALL(SIP) (01:0001:01) RCVD Clear Req from VPPL 18:07:07.557 CALL(SIP) (01:0001:01) SENT Clear Request to L4 18:07:07.557 CALL(L4) (01:0001:01) RCVD Clear request from SIP 18:07:07.557 CALL(L4) (01:0001:01) SENT Channel Release w/data to GCL 18:07:07.557 CALL(GCL) (01:0001:01) RCVD Channel Released w/data from L4 18:07:07.557 CALL(GCL) (01:0001:01) Call Duration(sec): 1 18:07:07.557 CALL(GCL) (01:0001:01) Radius Call Duration(sec): 1 18:07:07.557 CALL(GCL) (01:0001:01) SENT RADIUS ACCT STOP Cantata Technology - IMG 1010 Printable WebHelp 268 Product Description RADIUS Call Trace Example: Routing with Pre-paid Application Topic Location: Product Description > RADIUS The following call trace shows the IMG using the trunk group indicated by the RADIUS server in the Cantata-trunk-grp-out VSA. Related lines are in bold. 14:15:32.116 CALL(SS7) (00:00001:00) RCVD IAM from (0x2:0x1:0) 14:15:32.116 CALL(SS7) (00:00001:00) SENT Setup Ind w/info (0x2:0x1:0) to L4 14:15:32.116 CALL(L4) (00:00001:00) RCVD Setup Ind 14:15:32.116 CALL(L4) (00:00001:00) SENT RFS to GCL from SS7 14:15:32.116 CALL(GCL) (00:00001:00) RCVD RFS DN=[617456789012] ANI=[121423501110] from L4 14:15:32.116 CALL(GCL) (00:00001:00) ANI APRI=[0],SI=[1],Category=[11] 14:15:32.116 CALL(GCL) (00:00001:00) SENT RADIUS AUTH REQUEST to RADIUS 14:15:32.116 CALL(GCL) (00:00001:00) Incoming Channel Group = 0 [ss7chiloe] 14:15:32.116 CALL(GCL) (00:00001:00) RCVD AUTH ACCEPT ACK from RADIUS 14:15:32.116 CALL(GCL) (00:00001:00) Using Radius DTG=[uas_grp] 14:15:32.116 CALL(GCL) (00:00001:00) Using Radius DN=[6172597306] 14:15:32.116 CALL(GCL) (00:00001:00) DPE Input :DN=[6172597306] ANI=[121423501110] 14:15:32.116 CALL(GCL) (00:00001:00) DPE input plus(+) sign mask 0x00000000 14:15:32.116 CALL(GCL) (00:00001:00) Invoke Incoming DPE 1; Channel Group 0 14:15:32.116 CALL(GCL) (00:00001:00) DPE response: Proc Complete 14:15:32.116 CALL(GCL) (00:00001:00) DPE Output:DN=[7812597306] ANI=[121423501110] 14:15:32.116 CALL(GCL) (00:00001:00) DPE output plus(+) sign mask 0x00000000 14:15:32.116 CALL(GCL) (00:00001:00) SENT Make Call Request to GCL 14:15:32.116 CALL(GCL) (00:00001:00) Using DTG[uas_grp] as OutgoingChanGroup [4] 14:15:32.116 CALL(GCL) (00:00001:00) Skip mid-stream router 14:15:32.116 CALL(GCL) (00:00001:01) Outgoing Channel Group = 4 [uas_grp] Cantata Technology - IMG 1010 Printable WebHelp 269 IMG WebHelp Incomplete Call Behavior Topic Location: Product Description > RADIUS This section outlines the behavior of the IMG 1010 gateway in case of the most common incomplete calls. User Busy No Circuit/Channel Available No Answer from User Unallocated Number H.323 Release Reason H.323 non-Fast-Start Cantata Technology - IMG 1010 Printable WebHelp 270 Product Description SNMP An Overview of SNMP on the IMG Topic Location: Product Description > SNMP Description SNMP The SNMP provides a way to control and monitor a variety of equipment using one network management protocol. To do this, SNMP uses a number of common Management Information Bases (MIBs) and some company-specific MIBs to allow vendors to provide specific information about the equipment being managed. A MIB is a collection of objects that can be accessed via SNMP. For some basic information about SNMP, see the following topics: SNMP Basics What are MIBs ? Cantata Implementation The IMG supports the following for SNMP: Ability to monitor DS1, DS3, and Ethernet interfaces using industry standards MIBs Get and Trap commands. - query MIB-II statistics via SNMP "GET" messages - direct MIB-II traps to a manager. - set up the MIB-II variables (geographic location, etc.) See Supported MIBs and Supported Traps. NMS Management Tools Built-in support for industry standard MIBs among common Network Management tools. Manage network resources consumed by SNMP - limit number of packets by limiting traps Manage resources SNMP consumes on the IMG 2 SNMP Managers per GC EMS - memory usage Restrictions The IMG SNMP cannot act as a proxy. SETs are not be supported The IMG does not support provisioning with SNMP 271 IMG WebHelp Related Topics Supported MIBs Supported Traps 272 Cantata Technology - IMG 1010 Printable WebHelp Product Description Supported MIBs Topic Location: Product Description > SNMP The IMG SNMP solution supports the following standard MIBs. These MIB libraries should be included with your NMS, however, should you need to compile a standard MIB you can access them at the following web site: http://www.rfceditor.org/rfc.html There are currently no Cantata Enterprise MIBs for the IMG. RFC 1213 - Management Information Base for Network Management of TCP/IP-based internets:MIB-II A collection of managed objects used to define SNMP entities within the SNMP architecture. RFC 3895 - Definitions of Managed Objects for the DS1, E1, DS2, and E2 Interface Types Defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes objects used for managing DS1, E1, DS2 and E2 interfaces. RFC 3896 - Definitions of Managed Objects for the DS3/E3 Interface Type RFC 2571 - An Architecture for Describing SNMP Management Frameworks RFC 1907 - Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2) RFC 2494 - Definitions of Managed Objects for the DS0 and DS0 Bundle Interface Type. RFC 2863 - The Interfaces Group MIB Industry Standard MIB which enables monitoring of a DS3 trunk on the IMG. A collection of managed objects used to define SNMP entities. Support for this MIB provides several benefits: - A view of control, signalling, and data ports - Descriptive information about these ports - Measurements of the flow of traffic including number of packets in and out 273 IMG WebHelp - Recording of errors such as numbers of packets dropped. Managers used to query the switch should update their list of compiled MIBs to include RFC 2863. RFC 3877 - Alarm Management Information Base (MIB) Support for the alarm MIB offers these major benefits: The ability to inspect the alarm tables and find out what is currently wrong with the system. The ability to model alarms in a generic way. The ability to send out generic traps when alarms are raised. Supported SNMP Alarms 1. Ethernet Link Failure 2. System Busy Condition 3. System Busy Warning 4. System Memory Low 5. NFS Minor Traffic 6. NFS Major Traffic 7. SS7 Remote ISUP Unavailable 8. SS7 Signalling Stack Busy 9. SS7 Signalling Link Congestion 10. Radius Server No Access 11. Approaching Busy 12. Busy 13. Span Dead 14. VMOD OOS 15. VMOD Dead Alarm Traps Related Topics alarmActiveState - This trap is sent out when an alarm is raised. It contains the model number of the alarm as well as a resource ID which identifies specifically what the alarm refers to (for instance for a link down alarm you would indicate which link it is). alarmClearState - This gets sent out when an alarm is cleared. It contains the same information as the other trap. Supported Traps 274 Product Description Cantata Technology - IMG 1010 Printable WebHelp 275 IMG WebHelp Supported SNMP Traps Topic Location: Product Description > SNMP alarmActiveState This trap is sent out when an alarm is raised. It contains the model number of the alarm as well as a resource ID which identifies specifically what the alarm refers to (for instance for a link down alarm you would indicate which link it is) alarmClearState This gets sent out when an alarm is cleared. It contains the same information as the other trap. coldStart Indicates agent reinitializing. Configuration data may have been altered. dsx1LineStatusChange dsx1 LineStatus changed dsx3LineStatusChange dsx3 Line Status changed linkDown ifOperStatus (Link Status) changed from up to down. linkUp ifOperStatus (Link Status) changed from up to down. warmStart Indicates agent reinitializing. Configuration data was not altered. Cantata Technology - IMG 1010 Printable WebHelp 276 Product Description SNMP Basics Topic Location: Product Description > SNMP When computers began to get connected to form bigger and bigger networks, the people in charge of maintaining the networks ran into this kind of problem. They had to learn many languages to talk to the different computers. Even when they did, often they still couldn't get the answers to their questions. To solve this problem, SNMP was designed as the standard language to be used by all computers on the network. MIBs were designed as the standard questions each computer should be able to give an answer to. SNMP is a tool for improving network performance. Key Words enterprise MIB A proprietary MIB developed by a private company. Users of the MIB will have to design their managers around it. entity MIB Get NMS Notify A well-defined MIB laid out in RFCs. Users of this MIB will likely already have software in place to handle it. A type of SNMP message sent from a manager to an agent which requests to know the value of a particular variable on the agent. Network Management System. A collection of applications used to monitor and maintain a network. An SNMP manager would be one such application. A message sent from an SNMP agent (server) to the set of SNMP managers (clients) that have registered to receive it. The agent expects an acknowledgement from the manager. If it does not receive the acknowledgement within the specified interval, it will resend a number of times. SNMP Message Format Each SNMP message contains the following: Version Number One or more SNMP PDUs Community Name (password) 277 IMG WebHelp An SNMP PDU (other than traps) contains the following: request id error index error status list of OIDs and values A Trap contains the following: enterprise generic trap id 278 agent address specific trap id time stamp list of OIDs and values Cantata Technology - IMG 1010 Printable WebHelp Product Description Basic SNMP Implementation Topic Location: Product Description > SNMP The diagram below shows a basic SNMP Implementation, where you have a packetswitched network that is monitored and maintained by a network administrator. The portal into the network is through an NMS - network management station (or network management system). The NMS is a collection of applications which fall into the following broad categories: Configuration management Accounting Performance management Fault management Security NMS 279 IMG WebHelp Through a Graphical User Interface (GUI) or some other interface (such as a pager or CLI), the network administrator can: Use a GETs to find out the value of variables on a device (such as number of packets lost) Use a SETs to set the value of variables (such as tell a device that is flooding the network to shut down) Use TRAPs to be informed of some event (such as CPU utilization threshold reached). Set up applications to handle this information automatically. For instance, in the scenario where a device is flooding the network, an NMS application can be set up to cut that device off from the network and send a page to the network administrator who can debug the problem. SNMP Manager GET, SET, and TRAP messages come from an SNMP manager. The SNMP agent software must have three sets of hooks into the SNMP Manager: An API to be called by some other application on the box that will start up and initialize the SNMP agent. An API to be called by any application on the box that will tell the SNMP agent to generate and send out a TRAP. Stubs coming out from the agent for accessing the data. These stubs have to get plugged into higher-level applications that know where to get the data. MIBs All of the variables follow a hierarchical, tree structure, a database, called MIBs (Management Information Base). All the MIBs hook together to form one large MIB, with the Internet being the root. Cantata Technology - IMG 1010 Printable WebHelp 280 Product Description What are MIBs ? Topic Location: Product Description > SNMP You start at the top and add the name of each branch until you get to the variable you want to address. To address Cantata through SNMP the address is: iso.org.dod.internet.private.enterprises.cantata. You can append information to a node to extend the tree, as much as you need. The MIBs for a specific company's device are called an enterprise MIB. Standards have been made describing the format of common data. These are called standard MIBs. A special set of these MIBs are called MIB-II. These are MIBs for data you would expect every network device to have such as Ethernet, TCP, and UDP. Network Management Systems (NMS) are already set up for Standard MIBs, so if a new device supports standard MIBs you can just plug it into the network. All your existing high-level applications can work with the device. For an enterprise MIB you can query the data and look at it as numbers on a screen but your higher-level NMS apps won't have any idea what the data means until you write software that interprets the values. Cantata Technology - IMG 1010 Printable WebHelp 281 IMG WebHelp Interworking An Overview of Interworking Topic Location: Product Description > Interworking Cantata Technology - IMG 1010 Printable WebHelp 282 Product Description Interworking Features Topic Location: Product Description > Interworking The IMG supports interworking between SIP/H.323/SS7/ISDN, including the following support and features: Basic Support SIP-T Support of RFC 3666 Call Flows - SIP to PSTN Dialing SS7 ISUP - ISDN SS7 ISUP to ISDN Interworking Call Flows: SS7 ISUP to ISDN SIP - SS7 SIP to SS7 ISUP Interworking: Calling Party Category ANSI ISUP Originating Line Info Support Support for SPIROU/ITX in SIP INFO SS7 Carrier Identification Code in SIP INVITE Customizing SIP-to-SS7 ISUP Cause Codes H.323 - SS7 H.323 to SS7 Cause Code Mapping H.323 - ISDN CAS Digit Mapping Cantata Technology - IMG 1010 Printable WebHelp 283 IMG WebHelp SS7 ISUP to ISDN SS7 ISUP to ISDN Interworking Topic Location: Product Description > Interworking Brief Description The IMG supports interworking between ISDN and SS7. For Interworking between ITU ISUP and ISDN IMG follows Q.699 recommendation. For Interworking between ANSI ISUP and ISDN IMG follows T1.609 recommendation Benefits Provides cost effective TDM to SS7 ISUP switch. Limitations Fallback procedures are not supported in IMG, hence any interworking related to that is also not supported. Supplementary services are not supported in the IMG Related Topics Interworking Call Flows - ISDN to SS7 ISUP. Cantata Technology - IMG 1010 Printable WebHelp 284 Product Description Call Flows: SS7 ISUP to ISDN Topic Location: Product Description > Interworking Basic call control (en bloc operation) from ISDN to ISUP Basic call control (over operation) from ISDN to ISUP 285 IMG WebHelp Cantata Technology - IMG 1010 Printable WebHelp 286 Product Description SIP to SS7 SIP to SS7 ISUP Interworking: Calling Party Category Topic Location: Product Description > Interworking Overview This feature allows for the sending of the SS7 Calling Party Category (CPC) in the From Header of SIP messages. Only SS7 to SIP is supported. The CPC is a parameter that characterizes the station used to originate a call and carries other important state that can describe the originating party. The following diagram shows how the data flow from the SS7 ISUP side to the IP network SIP side. Configuration There are two options to place the CPC parameter in the From Header, configurable in the SIP From Header Tags pane. CPC Placed at User Part Support CPC Placed at URI Parameter Support If neither option is selected, the IMG sends out an INVITE message without any CPC parameter regardless of whether the IAM message is received with or without CPC parameter. You can also configure how the IMG responds when it receives unmapped CPC parameters of spare, unknown, or reserved. The options are: Ignore Send value Call Flow 287 IMG WebHelp CPC Mapping The following table shows the mapping of CPCs received from SS7 to CPC sent in SIP message from IMG. Received CPC CPC sent out in a SIP message Operator, language French operator Operator, language English operator Operator, language German operator Operator, language Russian operator Operator, language Spanish operator Ordinary calling subscriber ordinary 288 Product Description Calling subscriber with priority priority Data call (voice band data) datacall Test call test Payphone payphone Cantata Technology - IMG 1010 Printable WebHelp 289 IMG WebHelp Support for SPIROU/ITX in SIP INFO Topic Location: Product Description > Interworking The IMG supports the sending of the SS7 ITX message based on a SIP INFO message received from a SIP Application. This allows a SIP application to interwork with the SPIROU standard (Signalisation Pour l'Interconnexion des Réseaux Ouverts/Signaling for the Interconnection of Open Networks). This SS7 message is used for audio services that are paid by either a flat rate calculation or a time-based calculation. The calls are routed to the operator, and the operator reports the payment amount with the ITX message. Each ITX message indicates 1 charging unit which is the equivalent of 0.1 Euro. For example, if a caller dialed a service such as a weather forecast with a 1 Euro fee, then the network would send 10 ITX messages. RFC: 2976 - The SIP INFO Method Implementation The SIP application controls the sending of ITX messages by sending SIP INFO messages to the IMG. Call Flow Configuration SIP Profile 290 Product Description Cantata Technology - IMG 1010 Printable WebHelp 291 IMG WebHelp ANSI ISUP Originating Line Info Support Topic Location: Product Description > Interworking Overview The ISUP OLI (also know as II digits) parameter includes information that is used for carriers to determine the origin of a call. This information gets lost over SIP networks if not inter-worked properly. This feature allows carrying ANSI ISUP OLI Parameter from traditional TDM network into SIP and vice versa. This information is passed in the From: header of the INVITE message. Example From: “Anonymous”<sip:[email protected];isupoli=00>;tag=95ffcd055e0f78f7d5d397020e89288d63d4 Common ISUP-OLI codes 00 = Ordinary POTS call - not payphone 01 = Party line 02 = ANI Failure 27 = Payphone with network provided coin control 70 = Payphone without network provided coin control Configuration You enable this feature using the SIP From Header Tags pane. When this option is enabled, the IMG will include the INFO digits received in the Originating Line Info parameter (OLI) in the IAM message from the SS7 ANSI side into the ISUP_OLI tag in the From Header on the SIP side, and vice versa. Call Flows SS7 to SIP The following call flow shows where the IMG receives a call setup request from the PSTN/SS7 with the OLIP. With the ISUP-OLI feature this ISUP-OLI parameter will appear in the From header of the INVITE request 292 Product Description SIP to SS7 The following call flow shows where the IMG receives an INVITE with the From Header containing the ‘ISUP-OLI’ tag. With the ISUP-OLI feature, the IMG will send a call setup request to the PSTN/SS7 with the OLI parameter. 293 IMG WebHelp Cantata Technology - IMG 1010 Printable WebHelp 294 Product Description SIP Carrier Identification Code (CIC) Topic Location: Product Description > Interworking Overview This feature enables the IMG to receive and transmit the Carrier Identification Code (CIC) parameter between the SIP network and SS7. This preserves the remote user’s carrier identity over different networks and allows you the send mixed traffic over a trunk group. The CIC parameter is a three- or four- digit code used in routing tables to identify the network that serves the remote user when a call is routed over many different networks. The CIC parameter is carried in SIP INVITE requests and maps to the Carrier Identification Parameter (CIP) or the Transit Network Selection (TNS) parameter in ISUP. The ‘cic’ tag is included in the ‘sip’ R-URI. Example: INVITE sip:044;[email protected]:5060 SIP/2.0 Call Flows SS7 to SIP This call flow shows where the IMG receives a call setup request from the PSTN/SS7 with the carrier information code (cic). This cic parameter will appear in the SIP URI of the INVITE request. 295 IMG WebHelp SIP to SS7 ANSI This call flow shows where the IMG receives an INVITE with the SIP URI containing the ‘cic’ tag. The IMG will send a call setup request to the SS7 ANSI with the carrier information parameter. 296 Product Description SIP to SS7 ITU This call flow shows where the IMG receives an INVITE with the SIP URI containing the ‘cic’ tag. The IMG will send a call setup request to the SS7 ITU with the Transit Network Selection. 297 IMG WebHelp SIP to SIP Troubleshooting If you are experiencing problems with this feature, check the following: Make sure CIC is selected in the R-URI Header Tags field of the SIP SGP. The incoming IAM must contain a value in the CIP or TNS for IMG to pass this value in the SIP INVITE. Make sure the correct SGP is assigned to the External Gateway. The IMG forwards the cic parameter only if it appears in the format below: INVITE sip:044;[email protected]:5060 SIP/2.0 Cantata Technology - IMG 1010 Printable WebHelp 298 Product Description SIP-T Topic Location: Product Description > Interworking Overview The IMG supports SIP-T for interworking between SIP and SS7 ISUP for call setup, call tear down, and conversion of message formats for SIP Bridging, that is, a call that originates in the PSTN, goes into a SIP network, and terminates in the PSTN again. SIP-T provides ISUP transparency between the PSTN switches handling the call by encapsulating the incoming ISUP messages in the body of the SIP message. The ingress IMG places the incoming ISUP messages in the SIP body and the ISUP messages generated by the egress IMG are the ones present in the SIP body. For mid-call messaging, The INFO message is used to transport mid-call signaling messages that do not have a one-to-one mapping to SS7 ISUP messages like INR and INF. Why Enable SIP-T ? You should implement SIP-T (SIP for Telephones) when a call is passing from the PSTN, through a SIP network, and back to the PSTN, so that no SS7 information is lost. SIP Bridging Cantata Technology - IMG 1010 Printable WebHelp 299 IMG WebHelp Default SIP-to-SS7 ISUP Cause Codes Topic Location: Product Description > Interworking ISUP Cause Value SIP Response Normal event 1 – unallocated number 404 Not Found 2 – no route to network 404 Not Found 3 – no route to destination 404 Not Found 16 – normal call clearing --- (*) 17 – user busy 486 Busy here 18 – no user responding 408 Request Timeout 19 – no answer from the user 480 Temporarily unavailable 20 – subscriber absent 480 Temporarily unavailable 21 – call rejected 403 Forbidden (+) 22 – number changed (s/o diagnostic) 410 Gone 22 – number changed (w/ diagnostic) 301 Moved permanently 23 – redirection to new destination 410 Gone 26 – non-selected user clearing 404 Not Found (=) 27 – destination out of order 502 Bad Gateway 28 – address incomplete 484 Address incomplete 29 – facility rejected 510 Not implemented 31 – normal unspecified 480 Temporarily unavailable Resource unavailable 34 – no circuit available 503 Service unavailable 38 – network out of order 503 Service unavailable 41 – temporary failure 503 Service unavailable 42 – switching equipment congestion 503 Service unavailable 300 Product Description 47 – resource unavailable 503 Service unavailable Service or option not available 55 – incoming calls barred within CUG 403 Forbidden 57 – bearer capability not authorized 403 Forbidden 58 – bearer capability not presently 503 Service unavailable 65 – bearer capability not implemented 488 Not Acceptable here 70 – only restricted digital avail 488 Not Acceptable here 79 – service or option not implemented 501 Not implemented Invalid message 87 – user not member of CUG 403 Forbidden 88 – incompatible destination 503 Service unavailable Protocol error 102 – recovery of timer expiry 504 Gateway timeout 111 – protocol error 500 Server internal error Interworking 127 – interworking unspecified 500 Server internal error Others 500 – Server internal error (default) (*) ISDN Cause 16 will usually result in a BYE or CANCEL (+) If the cause location is ‘user’ than the 6xx code could be given rather than the 4xx code. the cause value received in the H.225.0 message is unknown in ISUP, the unspecified cause value of the class is sent. (=) ANSI procedure 301 IMG WebHelp SIP Status Code to ISDN Cause Code Mapping Response received Cause value in the REL 400 – Bad Request 41 – Temporary failure 401 – Unauthorized 21 – Call rejected (*) 402 – Payment required 21 – Call rejected 403 – Forbidden 21 – Call rejected 404 – Not Found 1 – Unallocated number 405 – Method not allowed 63 – Service or option unavailable 406 – Not acceptable 79 – Service/option not implemented (+) 407 – Proxy authentication required 21 – Call rejected (*) 408 – Request timeout 102 – Recovery on timer expiry 410 – Gone 22 – Number changed (w/o diagnostic) 413 – Request Entity too long 127 – Interworking (+) 414 – Request –URI too long 127 – Interworking (+) 415 – Unsupported media type 79 – Service/option not implemented (+) 416 – Unsupported URI Scheme 127 – Interworking (+) 402 – Bad extension 127 – Interworking (+) 421 – Extension Required 127 – Interworking (+) 423 – Interval Too Brief 127 – Interworking (+) 480 – Temporarily unavailable 18 – No user responding 481 – Call/Transaction Does not Exist 41 – Temporary Failure 482 – Loop Detected 25 – Exchange – routing error 483 – Too many hops 25 – Exchange – routing error 484 – Address incomplete 28 – Invalid Number Format (+) 485 – Ambiguous 1 – Unallocated number 486 – Busy here 17 – User Busy 487 – Request Terminated --- (no mapping) 488 – Not Acceptable here --- by warning header 500 – Server internal error 41 – Temporary Failure 501 – Not implemented 79 – Not implemented, unspecified 502 – Bad gateway 38 – Network out of order 503 – Service unavailable 41 – Temporary Failure 504 – Service time-out 102 – Recovery on timer expiry 505 – Version Not supported 127 – Interworking (+) 302 Product Description 513 – Message Too Large 127 – Interworking (+) 600 – Busy everywhere 17 – User busy 603 – Decline 21 – Call rejected 604 – Does not exist anywhere 1 – Unallocated number 606 – Not acceptable --- by warning header Cantata Technology - IMG 1010 Printable WebHelp 303 IMG WebHelp Customizing SIP-to-SS7 ISUP Cause Codes Topic Location: Configuration > Routing > Treatments To change Cause Code Mapping from the RFC 3398 default, 1. Create a Cause Code Table. 2. Add an entry to the Cause Code Table. a. In the Criteria Values field, select the original Cause Code for which you want to change the mapping. b. In the Outgoing Cause Code field, select the value to which you want the original value mapped. c. Add other entries to the Cause Code Table as desired. 3. Assign the Cause Code Table to a Channel Group. Cantata Technology - IMG 1010 Printable WebHelp 304 Product Description H.323 to SS7 H.225 Release Reason to Q.931 Cause Code Mapping Topic Location: Product Description > Interworking The following table shows the mapping of H.225 Release reason to Q.931 Cause Codes in the IMG. If the cause value received in the H.225.0 message is unknown in ISUP, the unspecified cause value of the class is sent. H.323 SS7 noBandwidth 34 – no circuit/channel available getekeeperResources 47 – Resource unavailable, unspecified unreachableDestination 3 – No route to destination destinationRejection 16 – Normal call clearing invalidRevision 88 – Incompatible destination noPermission 127 – Interworking, unspecified unreachableGatekeeper 38 – Network out of order gatewayResources 42 – Switching equipment congestion badFormatAddress 28 – Invalid number format adaptiveBusy 41 – Temporary failure inConf 17 – User busy undefinedReason 31 – Normal, unspecified facilityCallDelection 16 – Normal call clearing securityDenied 31 – Normal, unspecified calledPartyNotRegistered 20 – Subscriber absent callerNotRegistered 31 – Normal, unspecified newConnectionNeeded 47 – Resource unavailable, unspecified nonStandardReason 127 – Interworking, unspecified replaceWithConferenceInvite 31 – Normal, unspecified genericFaaReason 31 – Normal, unspecified neededFeatureNotSupported 31 – Normal, unspecified 305 IMG WebHelp tnnelledSignallingRejected 127 – Interworking, unspecified invalidCID 3 – No route to destination Cantata Technology - IMG 1010 Printable WebHelp 306 Quick Start Guide IMG Quick Start Guide Overview Topic Location: Quick Start Guide This IMG Quick Start Guide is intended to show you how to quickly connect power to your IMG and connect cables for Network Control and VoIP and SS7 bearer channels and signaling. See the IMG Installation and Setup Guide on the Technical Publications CD ROM or the Excel Support Web Site for more detailed information on installing and setting up the IMG and the GateControl EMS server. Shipping Information After opening your shipment, verify that you have received the following items: 1. IMG 1010 2. GateControl EMS Server 3. Software CD ROM 4. Technical Publications CD ROM 5. 2 DC Power Module Plugs, in plastic bag (DC Chassis only) 6. AC Power Cord, if ordered (AC Chassis only) If there are any discrepancies, contact your supplier. Topics Quick Start - Connecting Power Quick Start - Connecting Ethernet and TDM Cables Cantata Technology - IMG 1010 Printable WebHelp 307 IMG WebHelp Connecting Ethernet and TDM Cables Topic Location: Quick Start Guide CAUTION: Cantata recommends that you configure any routers or switches connected to the IMG for 100Mbit and Auto-negotiation. Disabling autonegotiation may result in packet loss. Also, broadcast propagation between ports must be enabled to allow BootP. The IMG supports a variety of scenarios for designing your IP network. In this example, you connect your Network Management to CTRL 0 and both your VoIP bearer channels and H.323/SIP Signaling to DATA 0. For information on all of the scenarios supported, see Network Interface Scenarios in the On-line Help. 1. Connect to Control port CTRL 0 is a Fast Ethernet port dedicated to network management that allows the GateControl EMS to access the Server. a. To assign an IP address to the IMG, locate the MAC address that is printed on a label on the underside of the IMG 1010. Enter the MAC address in the DHCP/BOOTP configuration. b. In the DHCP server, assign an IP address to the IMG that is on the same subnet as the GateControl EMS. Once this IP address is set, the GateControl EMS will be able to connect and provision the IMG 1010 Gateway 2. Connect to Data ports DATA 0 is a Gigabit-Ethernet port dedicated to VoIP Bearer Channels and VoIP Signaling. This port can be on the same IP network as the management network or on a separate network. You assign the IP addresses for these ports through the ClientView GUI. 3. Connect SS7 Signaling and Bearer channels. The bearer path, SS7 voice circuits, come in over the BEARER ports 0-27 ports, and can be configured as either T1 or E1. The SS7 Signaling links can either be brought into one of the SIGNALING/TIMING ports or one of the Bearer spans. 308 Quick Start Guide Cantata Technology - IMG 1010 Printable WebHelp 309 IMG WebHelp Connecting Power to the IMG Topic Location: Quick Start Guide Cautions Do not daisy-chain two or more IMG chassis. Direct wiring to the fused power source eliminates the coupling mechanism, which appears as impedance in the power distribution system. If impedance is not controlled, transient voltages will cause temporary or permanent malfunctions. Do not wire chassis directly to other equipment or to a common bus bar. Most feeders from the -48 V to frames are limited to about 20 A, whereas load distributions support several hundred amperes. Power Specifications The input power must conform to the following specifications. AC DC Power 120-240 V AC, 60-50 Hz, 3A-1.5A -48 V DC (nominal), 7A Range 90 to 240 V AC -40 to -60 V DC -48 V Wiring The DC power module must be wired directly to a –48 V fused power source. To connect a power source to the chassis, you need the following: 14 AWG machine tool wire (MTW) Blue for –48 V, White for –48 V Return DC power module plugs Cantata-supplied (in plastic bag) The DC power module plugs are polarity-sensitive. The unit will not operate if the plugs are not wired correctly, as shown below. 310 Quick Start Guide Cantata Technology - IMG 1010 Printable WebHelp 311 Installation and Setup Guide Introduction An Overview of Installation and Setup Topic Location: Installation and Setup Guide > Introduction This Installation and Setup Guide will walk you through the procedures to get your IMG 1010 and GateControl EMS Server from the box to the point where you can start the ClientView GUI and begin configuration. Once you launch ClientView, you will be able to access the On-line Help for documentation on configuring the IMG. Assumptions It is assumed that personnel performing these installation and setup procedures are familiar with telecommunications equipment and have a working knowledge of Linux. Task Summary 1. Install Hardware 2. Install Software (if required) 3. Setup the GateControl EMS server 4. Start ClientView You can then perform IMG configuration such as Routing and Signaling by referring to the Configuration section of the IMG 1010 On-line Help. Cantata Technology - IMG 1010 Printable WebHelp 312 Installation and Setup Guide Items Required for Installation Topic Location: Installation and Setup Guide > Introduction This topic describes the items required for the IMG and GateControl EMS Server installation. Certain models of the GateControl EMS Server purchased through your IMG supplier have software installed, as indicated below. Otherwise, you will need to obtain and install the software yourself. See Software Installation Overview. Server SLM-EMS1000 SLM-EMS1000R SLM-EMS1100 SLM-EMS1100R 3rd party servers must meet the following minimum requirements for a single IMG configuration: 800 MHz processor 512 MB RAM 20GB hard drive Item Hardware (Optional. Not Supplied by Cantata) (Optional. Not Supplied by Cantata) IMG System Software FactoryInstalled On software CD included with shipment. GateControl EMS Software FactoryInstalled unless ordered without. On software CD included with shipment. VNC Monitor Software FactoryInstalled Installed but not enabled. The following items are required unless you are connecting to the server remotely using VNC. Keyboard Monitor Mouse (img1010_ver1010xxx_id0101.bin) (IMG_<version>.bin, IMGUserInterface_<version>.bin) Obtain updates from RealVNC. 313 IMG WebHelp Install Scripts - xldhcp - lnimg FactoryInstalled Automatically installed into directory /opt/cantata/common/osconfig FactoryInstalled Obtain via RedHat web site. Sent separately by your supplier. Sent separately by your supplier. - xlntp RedHat Linux 3.0 ES, (Kernal 2.4) Obtain updates from RedHat. IMG License (<chassis serial number>-<sw version>.cfg) Cantata Technology - IMG 1010 Printable WebHelp 314 Installation and Setup Guide Sample Network Scenario Topic Location: Installation and Setup Guide > Introduction The following is an example of a basic network scenario that you can use to get started with your IMG. For other options, see Network Interface Scenarios in the Online Help. Cantata Technology - IMG 1010 Printable WebHelp 315 IMG WebHelp Licensing Topic Location: Installation and Setup Guide > Introduction The IMG and various components require a license to be operated or enabled. TDM spans, including signaling spans: 24 E1/32 T1 in 96 port increments SIP: 32 span increments. If there are 2 modules configured, the license is shared between them. ISDN B Channels: 24 or 32 span groups File Format The IMG license file name contains the unique serial number of the IMG. The format of the file includes the eight digit serial number followed by a timestamp: NNNNNNNN_YYYYMMDDHHSS.cfg If you rename or alter the license file in any way, it becomes unusable. Downloading a new License When you receive upgrades for your IMG (for example, additional SS7 link or VoIP ports) you must download the new license to the appropriate IMG. Steps 1. Ensure that the license file is in the correct folder on the server: /opt/cantata/common/license/ 2. Right-click the Physical IMG and select IMG Licensing Info. 3. Right-click IMG License Info and select Commit. 4. The License Info pane appears. Click the Download Node License button. The license is downloaded to the IMG based on the serial number of the IMG. IMPORTANT NOTE: If you rename or alter the license file in any way, it becomes unusable. Viewing License Info You can view the current license status on a Physical IMG using the License Info pane. Evaluation License Evaluation licenses expire after a specified number of days. If you are using an Evaluation License, the License Expiration Info field indicates the date/time that the license will expire, as shown below. If you are not using an Evaluation License, the field will say "Does not expire". 316 Installation and Setup Guide You will get an EventView alarm and a warning pop-up in ClientView when there is 72 hours remaining on the license and when it expires. License Validation Failure The icon shown below will appear in the ClientView tree if there is a problem with license validation. A license validation has failed. Make sure you have the required license and that it is configured on the IMG. See Downloading a New License and the License Info pane. Licensed Components The following IMG components require a license, as described below. System Software Includes 1,024 DSP Resources GCEMS GateControl EMS TDM Ports 24 E1/32 T1 in 96 port increments VoIP Ports 96 H.323/SIP sessions and 96 VoIP ports NOTE on VoIP Channel Distribution: If the IMG has two VoIP modules installed, channels are assigned to each module in groups of 32. For example if the IMG is licensed for 96 channels, 64 will be on the first module and 32 will be on the second module. SS7 SS7 Base ISUP CICs - 96 CIC increments SS7 Links - 2 link increments ISDN B channels 96 channel increments 317 IMG WebHelp Wireless Codecs 318 AMR - 48 channel increments EVRC - 48 channel increments Cantata Technology - IMG 1010 Printable WebHelp Installation and Setup Guide Hardware Installation IMG Hardware Installation Task Summary Topic Location: Installation and Setup Guide > Hardware Installation Perform the following steps to install the IMG. 1. Prepare Site 2. Unpack the IMG 3. Mount the IMG Rack Mounting the IMG Surface Mounting the IMG 4. Connect Power Connecting AC Power Connecting DC Power 5. Connect Ethernet and TDM Cables Related Topics Hardware Reference Overview (in the On-line Help) RJ 48 Connector Pinouts (in the On-line Help) First Task Unpacking the IMG Cantata Technology - IMG 1010 Printable WebHelp 319 IMG WebHelp Site Preparation Topic Location: Installation and Setup Guide > Hardware Installation Ensure that the following requirements are met before you begin installation. Important: Any variances from the mutually agreed upon site preparation details (such as DC power cabling, network cabling, equipment room readiness) may affect installation scheduling. Site Preparation Checklist Requirements Completed Location Spacing Mounting Power Electromagnetic Interference Channel Service Units Electrostatic Discharge Protection Location The -48 V DC unit must be located in a restricted area, such as a dedicated equipment room or limited access office. The 120/240 V AC unit does not have to be located in a restricted area. For example, it can be located in a clean and well ventilated office space. Spacing Allow approximately 76 cm (2.5 ft.) of space in front of the IMG, so that the tray can be removed and maneuvered with ease. Mounting The IMG can be mounted in a 19-inch rack. The mounting brackets can also be mounted at either the front or the middle of the chassis. 320 Installation and Setup Guide When mounting multiple IMGs in a rack, ensure that a hazardous condition does not exist due to uneven mechanical loading. Avoid putting the IMG inside a cabinet with closed doors unless you can provide sufficient ventilation inside the cabinet. Elevated operating ambient conditions may occur in an enclosed equipment rack. The operating ambient temperature may be greater than the room temperature. When installing the IMG do not block the four fans at the front of the chassis. This will cause the unit to overheat. Power See Connecting AC Power or Connecting DC Power. Electromagnetic Interference Electromagnetic Interference (EMI) is a type of radiation that can hinder your system. Keep the following in mind when selecting cables: Shielded cable prevents outside electrical interference and drains off any induced current. Twisted wire reduces induction, and thus interference, from one wire to the other. Varying the length of twists reduces the potential for signal interference between pairs. Twisted pair wiring is available in various thicknesses. Thicker cable covers longer distances and provides better sound quality but it is more expensive. Channel Service Units A Channel Service Unit (CSU) connects a digital phone line (T1, E1) from the phone company to a digital communications device. CSUs are required between all telecommunication ports and the network to provide necessary linking capabilities such as: Line conditioning for long haul transmissions Equalization Remote loopback Regeneration and monitoring of digital signals Digital circuit testing Protection from outside lines Electrostatic Discharge Protection 321 IMG WebHelp Electrostatic Discharge Protection (EDP) must always be used. Electrostatic Discharge (ESD) protective straps, shoes, or mats must be used when working with electronic components. Electrostatic discharge from your body can damage integrated circuits during installation. Cantata Technology - IMG 1010 Printable WebHelp 322 Installation and Setup Guide Unpacking the IMG Topic Location: Installation and Setup Guide > Hardware Installation Warnings/Cautions Use caution when moving and lifting the unit. The unit weighs 9 kg (20 lbs.). Retain all shipping materials in case you need to either relocate or re-ship the unit in the future. Use the packing materials to return the unit to the supplier, otherwise you may be charged for any damage that may occur during shipment. Procedure The IMG and supplied items are shipped in a single container. Carefully unpack the IMG as described below. 1. Open the container and remove the packing list. 2. Remove the protective cover and remove the IMG from the container. 3. Carefully remove the static protective bag from the IMG. 4. Carefully inspect the IMG. Should any discrepancies exist, contact your supplier representative immediately. Supplied items Review the packing list to ensure that the following items have been sent. Should any discrepancies exist, contact your supplier representative immediately. AC Power Chassis AC power cord (AC option) Software CD ROMs DC Power Chassis DC power module plugs (2) (DC option) Software CD ROMs DC grounding lug (factory-installed on back of unit) (DC option) Next Task Rack Mounting the IMG or Surface Mounting the IMG Cantata Technology - IMG 1010 Printable WebHelp 323 IMG WebHelp Rack Mounting the IMG Topic Location: Installation and Setup Guide > Hardware Installation Overview The IMG is shipped with the tray and docking station mated together for easy mounting. Factory Installed 19" Bracket Position The IMG ships with 19" inch brackets installed in the front mount position. Mounting Options The IMG has the following mounting options: 19" Brackets can be positioned and rotated to align ears as required. 23" Front Mount (factory default) Mid Mount There are two mid-mount options: ears forward, or ears backward. Front and Rear for added stability (must order kit) 23" inch brackets can be ordered for Enterprise racking. 324 Installation and Setup Guide Warnings/Cautions Use caution when moving and lifting the unit. The unit weighs 9 kg (20 lbs.). Always use two people to mount the unit. Mounting Guidelines When mounting the chassis, follow these guidelines: Use two people. Allow approximately 76 cm (2.5 ft.) to slide the field-replaceable tray out. Do not obstruct air flow to the front fans or the side vent holes towards the rear of the unit. 19" Rack Mounting Required Tools and Hardware The following customer-supplied tools and hardware are needed to mount the unit. Phillips head screwdriver Rack mounting hardware Procedure 1. Remove the brackets from the front mount position. 2. Position the mounting brackets to the desired position. 3. Align the holes on the mounting bracket ears to the mounting holes on the rack. 4. Secure with screws. At the rear of the unit on each side, a mounting hole with a captive nut is available for attaching additional mounting ears for extra support. Contact your Sales Representative to order additional brackets. Use 6/32 screws for this application. 23" Rack Mounting Bracket Positions 325 IMG WebHelp Required Tools and Hardware 23" Bracket Kit (order from Cantata) Includes 4 brackets and 2 screws Phillips head screwdriver Procedure 1. Remove existing 19" brackets from front mounting position. 2. Replace with 23" brackets, re-using existing screws. 3. Attach Rear Bracket Mounts to chassis as shown in figure. 4. Attach 23" brackets to the Bracket Mounts using screws provided. Next Task Connecting AC Power or Connecting DC Power Cantata Technology - IMG 1010 Printable WebHelp 326 Installation and Setup Guide Surface Mounting the IMG Topic Location: Installation and Setup Guide > Hardware Installation Overview The IMG is shipped with the tray and docking station mated together to provide ease in mounting. Caution Use caution when moving and lifting the unit. The unit weighs 9 kg (20 lbs.). Always use two people to mount the unit. Mounting Guidelines When mounting the chassis, follow these guidelines: Do not obstruct air flow to the front fans or the side vent holes towards the rear of the unit. Allow sufficient room, approximately 76 cm (2.5 ft.), to access the tray. Procedure 1. If desired, mount the self-adhesive feet to the bottom of the unit to protect the surface finish. 2. Set the unit on a clean, secure, and level surface. Next Task Connecting AC Power or Connecting DC Power Cantata Technology - IMG 1010 Printable WebHelp 327 IMG WebHelp Connecting AC Power Topic Location: Installation and Setup Guide > Hardware Installation Related Topic AC Power Information (in On-line Help) Overview The IMG supports an AC power option to support domestic and international customers. The AC power module is located at the rear of the docking station. Internally, the output of the AC power module connects to a panel-mounted connector via a cable assembly. This connector mates with an AC-to-DC 12 V DC power supply connector on the tray. Warnings/Cautions Ensure the AC power module switch is set to O (Off) prior to connecting the IMG to the AC power source. Do not ground the AC unit using the external grounding points located at the rear of the unit. These grounding points are for DC unit grounding only. The power up sequence will only start when the tray is fully seated into the docking station, to ensure that the main board does not power up until the system is properly seated. Procedure Complete the following steps to connect AC power to the chassis. 1. Plug the AC power cable into a grounded outlet. 1. Plug AC cable into the receptacle on the AC power module. 2. Insert other end into a grounded wall outlet, uninterruptible power supply (UPS), or surge protector. 3. Press switch on the AC power module to I (On). AC Power Module The AC power docking station provides an AC input power module with an integrated fuse, power switch, and standard three position female AC input connector. This connector allows the docking station to interface with all variations of AC outlets by simply using a standard power cable with a compatible outlet plug. The figure below shows the AC Power Module. 328 Installation and Setup Guide Other Considerations Uninterruptible Power Supply Option If your site has frequent power interruptions, consider using an Uninterruptible Power Supply (UPS) for your IMG 1010. You can prevent downtime by running your system that receives its AC power from batteries during a power failure. Surge Protection Cantata recommends installing a surge protector between your call processing system and the power outlet. If a high voltage surge occurs on the power line, this device protects your system by sending the overload to ground. Cantata Technology - IMG 1010 Printable WebHelp 329 IMG WebHelp Connecting DC Power to Ground Topic Location: Installation and Setup Guide > Hardware Installation Warning Always connect the DC unit to earth ground before connecting DC power to maintain signaling integrity and to prevent electrical shock. Do not connect ground to -48 V.. Earth Ground Wiring Specifications To connect a true earth ground to the chassis, you need the following: 14-16 AWG machine tool wire (MTW) (green/yellow) two-hole, # 10 solderless crimp, grounding lug (Cantata-supplied, attached to the grounding screws at the rear of the chassis) Procedure Complete the following steps to connect the IMG 1010 chassis to earth ground. 1. Remove the two-hole grounding lug at the rear of the IMG by removing the grounding screws. 2. Crimp the grounding wire to the lug. Re-attach the lug to the unit using the grounding screws. 3. Attach the other end of grounding wire to either a grounding point on the mounting rack or a building ground point. Diagram The figure below shows the DC 1010 earth ground connection. Cantata Technology - IMG 1010 Printable WebHelp 330 Installation and Setup Guide Connecting DC Power Topic Location: Installation and Setup Guide > Hardware Installation Related Topic DC Power Information (in On-line Help) The IMG supports a DC input power option to support both domestic and international customers. Docking Station The DC docking station provides a DC power module with two -48 V DC input power terminals and two ON/OFF circuit breakers. You can select either a single nonredundant power source or dual, redundant power sources. DC Power Module The DC power module, shown below, is located at the rear of the docking station. Internally, the output of the DC power module connects to a panel-mounted connector via a cable assembly. This connector mates with a DC-to-DC 12 V DC power supply connector on the tray. The DC docking station provides the following: Two -48 V DC power input terminals (PWR1/PWR2) Two ON/OFF circuit breakers (CB1/CB2). Related Topics Connecting DC Power to Ground Connecting to a Single Power Source Connecting to Redundant Power Sources Cantata Technology - IMG 1010 Printable WebHelp 331 IMG WebHelp Connecting to a Single Power Source Topic Location: Installation and Setup Guide > Hardware Installation Warnings/Cautions WARNING: Failure to turn power OFF at the power source may result in electrical shock. Ensure that the wires are pushed into the plug far enough, so that none of the copper is visible. The DC power module plugs are polarity sensitive. The unit will not operate if the plugs are not wired correctly. See wiring diagram below. Procedure Complete the following steps to connect a single power source to the DC power module. 1. Ensure both circuit breakers on the DC power module are set to OFF (O). 2. Turn power OFF at power source. 3. Route the RET and -48V wires from the external power source to the DC power module plug. Secure the wires to the plug with screws. NOTE: The power module plugs are in a small plastic bag included in your shipment. 4. Insert the plug into the DC power module and secure with screws. 5. Turn power ON at power source. 6. Press the required circuit breaker on DC power module to ON (I). Wiring Diagram The DC power wiring installation is shown below. 332 Installation and Setup Guide Cantata Technology - IMG 1010 Printable WebHelp 333 IMG WebHelp Connecting to Redundant Power Sources Topic Location: Installation and Setup Guide > Hardware Installation You can add a second power source to the chassis for redundancy in case the primary power source fails. The secondary source (battery) serves as backup to the primary source (power supply). Warnings/Cautions WARNING: Failure to turn power OFF at the redundant power source may result in electrical shock. Ensure that the wires are pushed into the plug far enough, so that none of the copper is visible. The DC power module plugs are polarity sensitive. The unit will not operate if the plugs are not wired correctly. See wiring diagram below. Procedure Complete the following steps to connect a redundant power source to the chassis 1. Ensure both circuit breakers on the DC power module are set to OFF (O). 2. Turn power OFF at redundant power source. 3. Route the RET and -48V wires from the redundant power source to the DC power module plug. Secure the wires to the plug with screws. NOTE: The power module plugs are in a small plastic bag included in your shipment. 4. Insert the plug into the DC power module and secure with screws. 5. Turn power ON at redundant power source. 6. Press the required circuit breaker on the DC power module to ON (I). Redundant DC Power Wiring Diagram The redundant DC power wiring installation is shown below. 334 Installation and Setup Guide Cantata Technology - IMG 1010 Printable WebHelp 335 IMG WebHelp Connecting Ethernet and TDM Cables Topic Location: Installation and Setup Guide > Hardware Installation CAUTION: Cantata recommends that you configure any routers or switches connected to the IMG for 100Mbit and Auto-negotiation. Disabling autonegotiation may result in packet loss. Also, broadcast propagation between ports must be enabled to allow BootP. Network Interface Ports There are three types of Network Interface ports on the IMG: Control (Network Management) Signaling (H.323) Data (RTP) The IMG supports a variety of scenarios for designing your IP network. In this example, the Network Management is connected to CTRL 0 and the VoIP interfaces to DATA 0. These can be on the same subnet, or different ones. For information on all of the scenarios supported, see Network Interface Scenarios in the On-line Help. TDM Bearer Channels and SS7 Signaling In this example scenario, the Bearer ports are used for both bearer and signaling. Your SS7 Signaling can also be brought into the SIGNAL/TIMING port. 336 Installation and Setup Guide Related Topic RJ 48 Connector Pinouts Cantata Technology - IMG 1010 Printable WebHelp 337 IMG WebHelp Timing Topic Location: Installation and Setup Guide > Hardware Installation Reference Timing Any 2 of the 4 SIGNAL/TIMING ports can be used for Reference Timing, as shown below. For reference timing pinouts see RJ 48 Connector Pinouts. Loop Timing Any of the SIGNAL/TIMING ports or Bearer ports can be used for Loop Timing, as shown below. IMG Back Panel Cantata Technology - IMG 1010 Printable WebHelp 338 Installation and Setup Guide Cabling for Redundancy Topic Location: Installation and Setup Guide > Hardware Installation The following topics show recommended cabling for various redundancy scenarios. Redundant Control Redundant Data Redundant Signaling Redundant SS7 Cantata Technology - IMG 1010 Printable WebHelp 339 IMG WebHelp Redundant Control Topic Location: Installation and Setup Guide > Hardware Installation The following illustration shows the recommended cabling for redundant control for Network Management. Cantata Technology - IMG 1010 Printable WebHelp 340 Installation and Setup Guide Redundant Data Topic Location: Installation and Setup Guide > Hardware Installation The following illustration shows the recommended cabling for redundant data. Cantata Technology - IMG 1010 Printable WebHelp 341 IMG WebHelp Redundant Signaling Topic Location: Installation and Setup Guide > Hardware Installation The following illustration shows the recommended cabling for redundant VoIP signaling. Cantata Technology - IMG 1010 Printable WebHelp 342 Installation and Setup Guide Redundant SS7 Signaling Topic Location: Installation and Setup Guide > Hardware Installation The following illustration shows the recommended cabling for redundant SS7 signaling. Cantata Technology - IMG 1010 Printable WebHelp 343 IMG WebHelp Software Installation (if required) Software Installation Overview Topic Location: Installation and Setup Guide > Software Installation This section documents the installation of software on your GateControl EMS server if it is not factory installed. If you purchased your server through Cantata or your IMG supplier the software is already installed unless you specifically ordered it without software. If software is installed proceed to Setting Up the GateControl EMS Server. If you purchased you server from Cantata without software installed, or purchased from a 3rd party, you must install software. Items Required for Installation See Items Required for Installation. Minimum Server Specifications If you purchase a server through a 3rd party, it must meet the following minimum requirements for a single IMG configuration: 800 MHz processor 512 MB RAM 20GB hard drive See Dell Server Configuration Details. Linux Services Needed All of the services can be on the same Linux Server or a different one. DHCP (Dynamic Host Configuration Protocol) FTP Server (Daemon) SNTP (Simple Network Time Protocol) Server NFS (Network File System) 344 Required to perform BootP function for the IMG 1010. The BootP server and the IMG(s) must be on the same subnet. This is installed with Linux. Required to download the system software to the IMG. This is installed with Linux. Required to synchronize the time on the IMG. Must co-locate with the FTP server. Used to download packaged treatments to the IMG. Installation and Setup Guide Next Topic Summary of Software Installation Tasks Cantata Technology - IMG 1010 Printable WebHelp 345 IMG WebHelp Summary of Software Installation and Setup Tasks Topic Location: Installation and Setup Guide > Software Installation 1. Install Linux on the GateControl EMS Server 2. Configure System Services 3. Install Linux Patches (if required) 4. Configure the Linux User 5. Install Cantata GateControl EMS Software (GCEMS, ClientView, EventView) 6. Install ClientView for Windows (Optional) 7. Start GateControl EMS 8. Start ClientView Related Topic Changing or Deleting Cantata GCEMS Cantata Technology - IMG 1010 Printable WebHelp 346 Installation and Setup Guide Installing Linux on the GateControl EMS Server Topic Location: Installation and Setup Guide > Software Installation Before You Begin Install Operating System Software per manufacturer's instructions. Notes IMPORTANT NOTE: The IMG only supports RedHat Linux 3.0 ES, Kernal 2.4. Do not install later versions. IMPORTANT NOTE: If you are installing Linux on a Dell server and your Linux installation files are on a CD-R, the Dell Server Assistant may not recognize the CD-R. If this occurs, you will need to install your Dell Server software manually (without using the Dell Server Assistant) and then install the Linux files. IMPORTANT NOTE: In order to customize partitioning as required to run the IMG EMS, you must use Dell Server Assistant Version 8.4 P/N: K7709 Rev. A00 or above. When installing the Linux Operating System on an SLM-EMS-1100 (Dell 1850 1U AC), the Dell Installation and Management Software must be used. Insert the Dell CD, wait for the Welcome screen, and answer questions when prompted. Instructions will be given to configure the hard disk drive RAID for mirroring along with the OS installation instruction using the Red Hat Linux Installation Wizard. Note on Re-installation If you are re-installing Linux, make sure that you close ClientView and stop any IMG or Linux processes that are running. Steps 1. Insert Linux Installation disks and follow instructions on screen. NOTE: If you installed the Dell server software using the Dell Server Assistant, insert the Linux disks when prompted. 2. Configure the hard drive. See Partitioning 3. Perform Network Adaptor Configuration. Enter your IP Address and Subnet Mask. 4. Perform RedHat Linux Configuration using the following values: 347 IMG WebHelp Unique Hostname Domain Name: localdomain Firewall: disabled Change Root Password: excel2 DNS Server: appropriate value Default Gateway: appropriate value 5. Follow instructions for remaining install and then reboot. 6. Login as user: root password: excel2 Do Not Install Server Administrator. 7. Continue with installation, following instructions. Enter Startx to start the Red Hat Graphical User Interface. If you would like the GUI to auto-start after a boot, you must edit the inittab file located in the \etc directory. Edit the file as follows: Original File: id:3:initdefault: Change to: id:5:initdefault: Reboot and the Red Hat Linux GUI will restart automatically. When the GUI is running, insert Red Hat disk 1 into the CD ROM drive and mount the CD. Click YES to the prompt: mnt/cdrom/autorun ? CD Click forward to Add or Remove packages. 8. Install or remove Linux packages. See Recommended_Linux_Packages. 9. When installation is complete, register for Red Hat updates. Click on the flashing red circle on the right side of the Linux taskbar and follow instructions. Related Topics Recommended Linux Configuration Next Task 348 Installation and Setup Guide Configuring the Linux User Cantata Technology - IMG 1010 Printable WebHelp 349 IMG WebHelp Recommended Linux Configuration and OS Settings Topic Location: Installation and Setup Guide > Software Installation Partitioning These partition sizes are recommended for your server if you have the following: SLM-EMS-1100 (Dell 1850 1U AC) If you are using a PC for a server, select Automatically Partition during install. Partition Recommended Size (MB) / (remaining balance) /boot 1024 swap 4096 /usr 10240 /home 12301 /opt 23234 *Required Partition (Locate large blocks of free drive space into this partition.) /var 10240 Settings Select default boot loader Disable Linux Firewall Enter Network Configuration Parameters Select your Additional Language Support Set the Time Zone selection Set System Root Password (Super User is root) Cantata Defaults are: user: root password: excel2 Linux Packages You must install the following packages. Other packages are not required and should not be enabled (if they are enabled by default, disable them). Desktops X WINDOWS SYSTEMS GNOME DESKTOP ENVIRONMENT KDE DESKTOP ENVIRONMENT Applications 350 EDITORS Installation and Setup Guide ENGINEERING AND SCIENTIFIC GRAPHICAL INTERNET Servers Server Configuration Tools Windows File Server FTP Server Network Servers (including freeradius) Legacy Network Server Development Development Tools System Administration Tools System Tools (including etherealgnome, and net-snmp-utils) Services Required The following Linux Services are required. Ensure that the corresponding boxes are checked for all run levels (3, 4, and 5). For help configuring services see Selecting/De-selecting Linux Services. arptables if auth (installed at factory but not selected) atd autofs crond dhcpd dkms autoinstaller gpm irqbalance keytable mdmonitor microcode-ctl netfs network nfs nfslock ntpd portmap random 351 IMG WebHelp rawdevices sgi-fam rhnsd sshd syslog vnc server (RealVNC installed at factory but not set to run) vsftpd xinietd Not Required The following Linux Services are not required. For maximum IMG performance, it is recommended that you do not run them. During Linux Configuration, uncheck the corresponding boxes if they are checked. Set for all run levels (3, 4, and 5) apmd cups audit hpoj iptables iptables6 irda isdn kudzu PCMCIA sendmail Cantata Technology - IMG 1010 Printable WebHelp 352 Installation and Setup Guide Selecting/De-selecting Linux Services Topic Location: Installation and Setup Guide > Software Installation 1. A service such as dhcpd can be started or stopped using the Service Configuration screen. To stop or start a service login as Super User. 2. Go to Main Menu >> Server Settings >> Services 3. Check or un-check the desired services for each run level (specify run levels 3, 4, and 5). 4. Start, stop, or re-start the desired services. 5. Store the settings by pressing the SAVE button. 6. Logout as Super User and Login as user excelsw. Cantata Technology - IMG 1010 Printable WebHelp 353 IMG WebHelp Configuring the Linux User Topic Location: Installation and Setup Guide > Software Installation 1. Create a new user called excelsw. The password must be excelsw to download IMG Software. 2. Assign user excelsw permissions to FTP and SSHD. 3. Start the VSFTP service (all run levels). 4. Add a folder named ftpBuilds to /home/excelsw/ with owner and group set to excelsw. 5. Verify that the user excelsw can use FTP (optional). If you need more help configuring the Linux User, see Configuring the Linux User Detailed Procedure. Next Task Installing GateControl EMS Cantata Technology - IMG 1010 Printable WebHelp 354 Installation and Setup Guide Configuring the Linux User - Detailed Procedure Topic Location: Installation and Setup Guide > Software Installation 1. Create a new user called excelsw. a. Go to Main Menu >> System Settings >> Users and Groups >> Add New User b. For User Name enter: excelsw c. For Password enter: excelsw (the password must be excelsw to download IMG Software). d. Click OK. 2. Assign user excelsw permissions to use FTP and SSHD. a. Select user excelsw 355 IMG WebHelp b. Select the ‘Properties’ button. c. Select the Group Users tab and check ftp and sshd. d. Click OK to exit to the desktop. e. Restart VSFTP service. a. Go to the Main Menu>>System Settings >>Server Settings >> Services. b. Scroll down to the process vsftpd and check the box. c. Right click and select ‘Restart’ to restart the service. d. Exit back to the desktop, saving changes. 4. Create the following folder with owner and group as excelsw: /home/excelsw/ftpBuilds a. Logout and login as user excelsw. b. Run a gnome terminal and create the directory ftpBuilds mkdir ftpBuilds Cantata Technology - IMG 1010 Printable WebHelp 356 Installation and Setup Guide Installing Cantata GateControl EMS Software Topic Location: Installation and Setup Guide > Software Installation Follow this procedure to install the IMG software on the GateControl EMS Server. You can install the IMG User Interfaces (ClientView and EventView) on the same machine as the GateControl EMS, another Linux machine, or a PC running Windows. This procedure includes steps for installing them on the same Linux machine as the GateControl EMS. To install the IMG User Interfaces on Windows, see Installing ClientView for Windows. Before you Begin Obtain the software builds from the IMG Software CD or get the latest version from the Customer Support BBS. Obtain the IMG license sent to you before the IMG was shipped. The license is also included on its own CD with your shipment. Steps 1. Transfer the following files to /home/excelsw/ftpBuilds on the GateControl EMS Server: IMG_10.x.x.xx.bin (IMG GCEMS) IMGUserInterface_10.x.x.xx.bin (ClientView, EventView) NOTE: If the files are transferred using FTP, you must change the mode of the .bin files to executable by performing a chmod +x to each .bin file 2. Transfer the IMG System Software binary file to the following folder on the GCEMS Server: /home/excelsw/ftpBuilds File Syntax: img1010_ver1010xxx_id0101.bin (where xxx = software build number) 3. As Super User, install IMG GCEMS software by running: ./IMG_10.x.x.xx.bin Follow the instructions as prompted. See GCEMS Installation Script. NOTE: If you are installing a Redundant GCEMS, make sure you indicate this when prompted. Icons for StartGCEMS and StopGCEMS are automatically created and placed on your desktop. Also see Folders and Files Created During Installation. 357 IMG WebHelp 4. As Super User, install IMG User Interface (ClientView) software by running: ./IMGUserInterface_10.x.x.xx.bin An icon for ClientView is automatically created and placed on your desktop. 5. Log out of the system as root and log back in as user excelsw. This creates an entry in the /etc/profile to set the SK_LIB_DIR directory. 6. To verify that the SK_LIB_DIR path is correct, type ‘set’ to show your environment variables or type echo $SK_LIB_DIR to see the current setting. 7. Use FTP to transfer your IMG license to the license folder. Login as user excelsw and put the file <chassis serial number>-<date>.cfg into the following directory: /opt/cantata/common/license. Next Task Setting Up the GateControl EMS Server Cantata Technology - IMG 1010 Printable WebHelp 358 Installation and Setup Guide Folders and Files Created During Installation Topic Location: Installation and Setup Guide > Software Installation Directory Structure The following folders and subfolders are created during installation. See below for information on important folders. Common Folder backup Stores backup log and configuration files calltracing 359 IMG WebHelp config Holds configuration files Imports (contains CAS Variants) Variant routing Variants working .csa NOTE: During the installation, if a system.cfg file already exists, it will be renamed system_<DATE_OF_INSTALL>.cfg. license Folder where the IMG looks for current licenses. log Stores current log files. See Log Files. reports Stores report output files. stats Stores the statistics files collected per object. treatment Contains vocabulary index files. cron IMG Folder GateControl EMS Contains the files for the currently running version of GCEMS. IMGUserInterface 360 Installation and Setup Guide Contains the files for the currently running version of the ClientView User Interface. Installs Folder This folder contains a subfolder for each version of GCEMS and ClientView software you have downloaded. It also contains the following utilities that allow you to change or delete the running version of GCEMS: changeGCEMSVersion - change to another installed version of GCEMS deleteGCEMSVersion - remove unwanted versions of older software Cantata Technology - IMG 1010 Printable WebHelp 361 IMG WebHelp GCEMS Installation Script Topic Location: Installation and Setup Guide > Software Installation This example shows what you will see when installing the GCEMS software. Note on Redundant GCEMS If you are installing a redundant GCEMS, make sure you select 2 (Yes) when you see the following prompt: Is this going to be a redundant system? and enter the IP Address for the Secondary Host when prompted. Script [root@img229 ftpBuilds]# ./IMG_10.3.2.88.bin Preparing to install... Extracting the JRE from the installer archive... Unpacking the JRE... Extracting the installation resources from the installer archive... Configuring the installer for this system's environment... Launching installer... Preparing CONSOLE Mode Installation... ======================================================================= ======== IMG Macrovision) (created with InstallAnywhere by ------------------------------------------------------------------------------ ======================================================================= ======== Introduction -----------InstallAnywhere will guide you through the installation of IMG 10.3.2.88. It is strongly recommended that you quit all programs before continuing with this installation. 362 Installation and Setup Guide Respond to each prompt to proceed to the next step in the installation. If you want to change something on a previous step, type 'back'. You may cancel this installation at any time by typing 'quit'. PRESS <ENTER> TO CONTINUE: ======================================================================= ======== System Configuration -------------------Is this going to be a redundant system? 1- YES ->2- NO ENTER THE NUMBER FOR YOUR CHOICE, OR PRESS <ENTER> TO ACCEPT THE DEFAULT: : 1 System IP Address ----------------What are the IP addresses of your secondary and primary hosts? Primary Host (DEFAULT: ): 10.129.50.229 Secondary Host (DEFAULT: ): 10.129.50.240 ============================================================== Pre-Installation Summary -----------------------Please Review the Following Before Continuing: Java VM Installation Folder: /jre Product GateControlEMS Install Folder /opt/cantata/IMG PRESS <ENTER> TO CONTINUE: ============================================================== 363 IMG WebHelp Installing... ------------[==================|==================|==================|======] [------------------|------------------|------------------|-----------------] ============================================================== Installation Complete --------------------Congratulations. IMG GateControl EMS has been successfully installed to: /opt/cantata ********************************************************************** ********************************************************************** To properly run this product, you must LOG OUT AND BACK IN to set up your environment. ********************************************************************** ********************************************************************** Press "Enter" to quit the installer. PRESS <ENTER> TO EXIT THE INSTALLER: [root@img229 ftpBuilds]# Cantata Technology - IMG 1010 Printable WebHelp 364 Installation and Setup Guide Installing ClientView for Windows Topic Location: Installation and Setup Guide > Software Installation Note on Re-installation If you are re-installing ClientView, make sure that you close ClientView and stop any IMG processes that are running. Steps To install ClientView on a PC running Windows, perform the following steps. 1. Transfer the IMG User Interface software file to the PC. 2. Go to the location where you stored the file and click the IMGUserInterface.exe file. This will launch the InstallAnywhere installation wizard. 3. Accept the defaults as each screen appears. NOTE: EventView is automatically installed with ClientView. Cantata Technology - IMG 1010 Printable WebHelp 365 IMG WebHelp GateControl EMS Redundancy Topic Location: Installation and Setup Guide > Software Installation Related Topics GCEMS Installation Script Starting GateControl EMS Installing Cantata GateControl EMS Software Installation 1. When installing GCEMS (Step 4 in Installing Cantata GateControl EMS Software), when asked if this is going to be a redundant system select choice 1 (Yes), as shown below in red. System Configuration -------------------Is this going to be a redundant system? ->1- YES 2- NO ENTER THE NUMBER FOR YOUR CHOICE, OR PRESS <ENTER> TO ACCEPT THE DEFAULT: : 1 2. Later you will be asked for the IP addresses of the two hosts. Enter the primary and secondary IP Addresses, as shown below in red. System IP Address ----------------What are the IP addresses of your secondary and primary hosts? Primary Host (DEFAULT: ): 10.129.50.229 Secondary Host (DEFAULT: ): 10.129.50.240 Starting GCEMS When Starting GateControl EMS you will be prompted to enter the Operation Mode (1 - Primary/Standalone, 2 - Secondary). For the Primary GCEMS, select 1. For the Secondary GCEMS, select 2. 366 Installation and Setup Guide At this point the system.cfg file will be transferred from the primary server to the secondary server at /opt/cantata/common/config NOTE: If you are changing a system that was originally configured as standalone to a redundant system, you have to manually copy the system.cfg file from /opt/cantata/common/config on the primary host and paste it into the secondary host in the same location. When the secondary host comes up as standby, the system.cfg will be automatically updated. The system is now set up for redundancy. SwitchOver If the primary GCEMS fails you must start the secondary GCEMS (StartGCEMS) and manually start the following: ./AdminManager ./DataManager ./BackupFileManager At this point you can connect to the secondary GCEMS with ClientView. When opening ClientView, select secondary host. You can only monitor the IMG through the secondary host; you cannot do any provisioning or configuration. SwitchBack Once the primary GCEMS comes back into service: 1. In ClientView, click on the Cantata IMG EMS object on the secondary GCEMS. 2. Click the Switchover button. Control will now switchback to the primary GCEMS. NOTE: If the system was initially loaded as a primary/secondary system then in the Defaults file located at /opt/cantata/common should have the entries for RLLC and LLC along with the correct IP addresses. Cantata Technology - IMG 1010 Printable WebHelp 367 IMG WebHelp Setup Overview Topic Location: Installation and Setup Guide > Setup Before You Begin If you need to install GCEMS software, see Installing Cantata GateControl EMS Software. Task Summary 1. Setup GCEMS (IP Address, Users, hostname, dhcp Server) 2. Download IMG System Software 3. Start GateControl EMS 4. Assign ClientView Users (optional). Perform this step if you want to assign user IDs, passwords, and roles. 5. Start ClientView 6. Configure Remote Desktop Cantata Technology - IMG 1010 Printable WebHelp 368 Installation and Setup Guide Setting up GateControl EMS Topic Location: Installation and Setup Guide > Setup Before You Begin You should have unpacked, mounted, and connected power to the GateControl EMS server. See the manufacturer's instructions for installation procedures. The GateControl EMS software must be installed. See Installing GateControl EMS Software. You should have the IP Addresses of the IMG and the GateControl EMS server. You should have the MAC address of the IMG. Steps Follow these steps to setup the GateControl EMS Server. 1. Connect to the GCEMS Server via Telnet or SSH (Default IP Address: 192.168.0.100) 2. Login as user: excelsw with password: excelsw 3. Configure a unique hostname. a. In the RedHat GUI, select System Settings > Network. b. Select the DNS tab and enter a unique hostname in the Hostname field. 369 IMG WebHelp c. Select the Hosts tab and enter the same hostname. 4. Create a symbolic link for dhcp automatically using the lnimg script or manually. Automatically Run the lnimg script ./lnimg NOTE: Copy the lnimg script from opt/cantata/common/osconfig to the folder containing system software (such as /home/excelsw/ftpBuilds). Manually From the /home/excelsw/ftpBuilds directory (containing img101_verXXXX_id0101.bin file), type: ln -sf img1010_ver10305_id0101.bin img1010_id0101.bin To confirm the link has been created, type: ls -la Response: lrwxrwxrwx 1 root root 27 Jun 21 09:27 img1010_id0101.bin -> img1010_ver10305_id0101.bin 370 Installation and Setup Guide Verify that the link created points to the correct bin file. 5. As Super User, create the dhcpd.conf file. a. Run the dhcpd file creation script located in /opt/cantata/common/osconfig: ./xldhcp You can also create the Linux default dhcpd.conf file manually. See Sample dhcpd.conf File. b. Enter values when prompted as appropriate for your configuration. NOTE: Assign an IP address to the IMG that is on the same subnet as the GateControl EMS server. Once this IP address is set, the GateControl EMS will be able to connect to and configure the IMG You will be prompted for the following information: [factory defaults shown in bold] Router/Default Gateway IP Address: [192.168.0.1] Router/Default Gateway Subnet Mask: [255.255.255.0] Subnet IP Address: (Router/Default Gateway IP Address - 1) [192.168.0.0] FTP Server IP Address: (This PC IP Address) [192.168.0.100] How many IMG systems are being configured? [1] T1 or E1 IMG (t/e)? [t] CODEC Profile Selection 1 = LBR 2 = LBR + iLBC 3 = LBR + iLBC + wireless [NOTE: You must have a license for wireless codecs. You must also set host flags accordingly (see Vocoder Information)] Enter CODEC profile? [2] IMG(CTRL0)[1] IP Address: [192.168.0.102] IMG(CTRL0)[1] MAC Address: (MAC shown on IMG Label) [00:20:1C:xx:xx:xx] IMG(CTRL1)[1] MAC Address: (MAC shown on IMG Label +1) [00:20:1C:xx:xx:xx+1] The following is the response after all prompts are complete: dhcpd.conf created with 1 IMG's configured... 371 IMG WebHelp The file will be created in the home/excelsw/ftpBuilds directory. c. Move the file to the /etc directory (mv dhcpd.conf /etc) d. Restart the DHCPD Service by typing: /sbin/service dhcpd restart /sbin/ chkconfig dhcpd on 6. Create the ntp.conf file a. Run the ntp configuration script: (./xlntp) (located at opt/cantata/common/osconfig) b. Enter IP Address and Subnet mask when prompted as appropriate for your configuration. c. Move the ntp file to the /etc directory. (mv ntp.conf /etc) See Sample ntp.conf File. d. Restart the SNTP Service by typing: /sbin/service ntpd restart /sbin/chkconfig ntpd on CRON Jobs The IMG includes a crontab that manages GCEMS processes. This crontab runs automatically when the GCEMS is started (StartGCEMS), and stopped when the GCEMS is stopped (StopGCEMS). This file should not be edited. There is a user crontab where you can add your own cron jobs for such tasks as file management or CDR management. The file is located at /opt/cantata/common/cron/usercron This crontab runs automatically when the GCEMS is started, and stopped when the GCEMS is stopped. To stop a service, comment it out or delete it form the file and then start the GCEMS again (StartGCEMS) Example Usercron [excelsw@lforsberg excelsw]$ cd /opt/cantata/common/cron/ [excelsw@lforsberg cron]$ more cdr #!/bin/sh # # Sample script to archive CDR's. # Files are archived if more than 1 day old # Files are deleted if more than 31 days old find /var/log/radius/radacct/*/detail* -mtime +1 -exec gzip {} \; find /var/log/radius/radacct/*/detail* -mtime +31 -exec rm -f {} \; 372 Installation and Setup Guide [excelsw@lforsberg cron]$ [excelsw@lforsberg cron]$ more usercron ####################################################################### # # User's cron task. This file will be added to the crontab. # ####################################################################### # # Add additional cron tasks after this line. 1 * * * * /opt/cantata/common/cron/cdr > /dev/null 2>&1 [excelsw@lforsberg cron]$ ___________________________________________________________________ ______0 Next Task Downloading IMG System Software Cantata Technology - IMG 1010 Printable WebHelp 373 IMG WebHelp Downloading IMG System Software Topic Location: Installation and Setup Guide > Setup The following procedure assumes you are downloading IMG system software from an FTP Server. To download using an SD Card, see the following topics: Downloading IMG System Software from an SD Card Downloading IMG System Software Using a Boot File on an SD Card Before You Begin You must have copied the IMG system software file to the GCEMS Server. See Setting Up GateControl EMS. Procedure To install IMG System Software, power-up the IMG to initiate BootP/FTP transfer of the software from the GCEMS server. Troubleshooting If the software load does not transfer to the IMG, check the following: Verify that the Linux firewall is disabled. Verify that the etc/dhcpd.conf file is correct Verify that DHCP and VSFTP services are running. Verify that the switch bin file is in the correct location (/home/excelsw/ftpBuilds). Verify that the link to the switch bin created in /home/excelsw/ftpBuilds is correct. Example: img1010_id0101.bin -> img1010_ver1032XXX_id0101.bin Note: Script Tool lnimg can be used to create this link. Diagram The following illustration shows the transfer of IMG System Software using FTP from an FTP server to each IMG with a local BootP Server. 374 Installation and Setup Guide Next Task Starting GateControl EMS Cantata Technology - IMG 1010 Printable WebHelp 375 IMG WebHelp Starting GateControl EMS Topic Location: Installation and Setup Guide > Setup Related Topics GCEMS Installation Script Steps Follow this procedure to start the GateControl EMS processes and the IMG. 1. Login as excelsw 2. Click on the StartGCEMS icon on the desktop, or run StartGCEMS from the following directory: /opt/cantata/IMG/GateControlEMS/bin/ run: StartGCEMS (./StartGCEMS) 3. Select the Operation Mode. If this is a standalone GCEMS or the Primary in a redundant setup, select 1. If it is a secondary GCEMS in a redundant setup, select 2. 1 - Primary/Standalone 2 - Secondary When StartGCEMS is first run after an upgrade, no system.cfg will be found and the system will start up without a specified configuration. The user will then be able to open a .csa file via ClientView to initiate configuration. If the system.cfg exists, StartGCEMS will prompt the user whether they want to begin a new configuration. If so, the system.cfg file will be archived if it exists (in the case of an upgrade, it will not exist) and no configuration will be executed. If not, the system.cfg file will be opened and the system configured accordingly. If the system.cfg does not exist, StartGCEMS not ask the user if they want to begin a new configuration and will begin that way. The IMG EMS will now start. You will see the following: Starting IMG ... CommManager: ....Started. GateManager: ....Started. DataManager: ....Started. AdminManager: ....Started. BackupFileManager: ....Started. 376 Installation and Setup Guide Success: StartGCEMS completed. 5. Verify That Processes are Running (Optional) To verify the processes are running, type: ps -ef |grep Manager You should see the following output: excelsw 16955 1 0 Jun13 ? 00:10:42 ./CommManager excelsw i 16965 1 0 Jun13 ? 00:01:27 ./GateManager - excelsw 16975 1 0 Jun13 ? 00:05:49 ./DataManager excelsw 16985 1 0 Jun13 ? 00:22:41 /opt/cantata/IMG/GateControlEMS/bin/../../jre/bin/java com.zerog.lax.LAX /opt/cantata/IMG/GateControlEMS/bin/AdminManager.lax /tmp/env.properties.16985 excelsw 17044 1 ./BackupFileManager 0 Jun13 ? 00:37:29 root 0 10:34 pts/0 00:00:00 grep Manager 26474 26400 Next Task Starting ClientView Cantata Technology - IMG 1010 Printable WebHelp 377 IMG WebHelp Assigning ClientView Users Topic Location: Installation and Setup Guide > Setup Unless you specifically assign user privileges, anyone can access the EMS with full Administrative Privileges using: UserName: admin Password: admin Procedure If you want to assign passwords and roles to individual users who may have access to the EMS, follow this procedure. 1. Login to AdminView a. Run AdminView <./AdminView> (located at opt/cantata/IMG/GateControlEMS/bin/ b. Login as Administrator User ID: admin Password: admin 2. Change the Admin Password To limit access to the Admin functions, perform the following steps. a. Type chpwd and press ENTER. b. Enter the Admin user ID, admin, and press ENTER. c. Enter a new password and press ENTER. d. Re-enter the new password and press ENTER. 3. Add a User and assign roles a. Type adusr and click ENTER. b. Enter a user ID and click ENTER. c. Enter a password for the user and press ENTER. d. Confirm the password and press ENTER. e. Enter values for the roles to assign to the user. 1 - Administrator 2 - Basic 3 - Configuration 4 - Provisioning 378 Installation and Setup Guide 5 - Monitoring f. Repeat steps a-e for each user. g. Quit Help For a list of commands, type help More Information For more detailed information on Administering User Privileges, see Administering User Privileges in the IMG 1010 On-line Help. Cantata Technology - IMG 1010 Printable WebHelp 379 IMG WebHelp Starting ClientView Topic Location: Installation and Setup Guide > Setup NOTE: EventView will start automatically when you start ClientView. To start ClientView and connect to the IMG, perform the following steps: 1. Launch ClientView From Linux: Click on the IMGClientView icon on the desktop, or run ClientView from the following directory: opt/cantata/IMG/IMGUserInterface/ClientView type ./ClientView From Windows Click the ClientView icon on your Desktop, or Click on the ClientView exe file located at: C:\Program Files\Cantata\IMGUserInterface\ClientView 2. When the About ClientView window appears, click CLOSE. 3. When the Client Socket window appears, enter the following: Username:admin Password: admin (or new password if you changed) Host Name or IP Address: This is the IP Address of the GCEMS Server you are connecting to. If ClientView is running on the EMS server, leave the default (localhost). 4. Click OK You are now connected to the IMG Server and ready to use ClientView. You can now access the on-line Help for detailed configuration information. 380 Installation and Setup Guide EventView will automatically be started. Restarting EventView If you close EventView and want to restart it, select Tools > Launch EventView from the ClientView menu. Cantata Technology - IMG 1010 Printable WebHelp 381 IMG WebHelp Configuring Remote Desktop (Strongly Recommended) Topic Location: Installation and Setup Guide > Setup Cantata Support uses VNC to allow its support engineers the ability to work on customer issues. Not being able to access ClientView to see what the customer is seeing severely limits the ability of Cantata Support to provide suggestions or even diagnose issues. Here are some of the benefits of VNC VNC is currently part of the Red Hat 3.0 ES Operating System. Red Hat 3.0 ES is the only OS the GCEMS is supported on. VNC allows the user and Cantata Support personnel to work together as the connection is shared. This greatly increases customer knowledge as they work issues. VNC uses known ports so fire walls can be configured to only allow VNC connections from Cantata's IP address allowing for security but still allowing for remote help. Please ensure these ports are open for access. Linux If you have purchased your GCEMS from Cantata, you can allow remote access to your GateControl EMS Server by performing the following procedure. If you have installed Linux on your own server, ensure VNC is installed and perform this procedure. 1. On the linux host run “vncserver :1” 2. The first time you run this process it will prompt you to enter a password that will be required when you connect. The factory-default password is excelsw. A hidden folder “.vnc” is added to the $HOME folder on the system. 3. Change directory to $HOME/.vnc 4. edit the file xstartup Uncomment the following two lines for normal desktop. unset SESSION_MANAGER exec /etc/X11/xinit/xinitrc 5. Restart the vncserver. a. vncserver –kill :1 b. vncserver :1 NOTE: Starting the VNC Server without the geometry setting will default the window size to 1024x768. Use the –geometry setting to set the size of the vnc window. This will need to 382 Installation and Setup Guide be the same size or smaller than the resolution of the Windows PC you are running the client on. Following are some recommended settings. ###################################### # Geometry settings # Windows: 1024x768 Linux: 1000x710 # Windows: 1280x1024 Linux: 1260x960 ###################################### Example: vncserver –geometry 1260x960 :1 Windows 1. Copy the VNC client viewer to your PC from the site: http://www.realvnc.com/download.html 2. Execute the download and save. 3. Run VNC Viewer. In the Server window, enter the IP Address followed by :1 (IP Address 1) Example: 192.168.0.100 :1 To allow another person to connect and view the same Xwindow enable the Shared Connection option. Two people can connect to the same system and what one person does the other person will see. Both users must have this option enabled. 1. Select the Options button 2. Select the Misc tab. 3. Enable the Shared Connection option. Cantata Technology - IMG 1010 Printable WebHelp 383 IMG WebHelp Changing or Deleting Cantata GateControl EMS and User Interface Topic Location: Installation and Setup Guide > Setup Changing GCEMS and User Interface Version To change to a different version of GCEMS and ClientView/EventView use the script tool changeGCEMSVersion located in: /opt/cantata/installs The tool changes the links to the executables in the /opt/cantata/IMG directory. Deleting GCEMS Version To change to a different version of GCEMS, ClientView and EventView use the script tool deleteGCEMSVersion located in: /opt/cantata/installs This tool when run will delete the specified version of GCEMS and ClientView/EventView that is stored in the /opt/cantata/installs directory. Cantata Technology - IMG 1010 Printable WebHelp 384 Installation and Setup Guide Sample dhcpd.conf File Topic Location: Installation and Setup Guide > Setup The following is a sample dhcpd.conf file. If you do not have access to the xldhcp script, you must modify this file manually. Modify the lines in bold according to your particular network settings. ################################################################# # File: dhcpd.conf # Generated by: xldhcp Revision: 1.2 # Cantata Technology, Inc. 05/16/06_16:21:23 # Cantata Support @ 508-862-3366 [email protected] ################################################################# ddns-update-style ad-hoc; # which logfile group... log to /var/log/messages LogFile = messages; allow bootp; # declare global vender options option Host_1010_Flag code 134 = signed integer 32; # 0 = FTP, T1, AB Polls disabled, CODEC Profile 5 LBR # 2 = FTP, E1, AB Polls disabled, CODEC Profile 5 LBR # 16 = FTP, T1, AB Polls disabled, CODEC Profile 6 LBR+iLBC # 24 = FTP, T1, AB Polls disabled, CODEC Profile 7 LBR+iLBC+wireless # Configured Host_1010_Flag = 0 # option routers is the same as the default gateway option routers 192.168.1.1; option subnet-mask 255.255.255.224; # subnet IP address usually default gateway address minus 1 subnet 192.168.1.0 netmask 255.255.255.224 { host IMG_CPU1_0 { hardware ethernet 00:20:1c:00:00:00; fixed-address 192.168.1.5; # ftp server name (IP Address of the LINUX PC running FTP) next-server 192.168.1.100; # IMG bin file (software load) filename "ftpBuilds/img1010_id0101.bin"; 385 IMG WebHelp option Host_1010_Flag 0; } host IMG_CPU1_1 { hardware ethernet 00:20:1c:00:00:01; fixed-address 192.168.1.5; # ftp server name (IP Address of the LINUX PC running FTP) next-server 192.168.1.100; # IMG bin file (software load) filename "ftpBuilds/img1010_id0101.bin"; option Host_1010_Flag 0; } } Cantata Technology - IMG 1010 Printable WebHelp 386 Installation and Setup Guide Setting Host Flags Topic Location: Installation and Setup Guide > Setup The following diagram shows the Host flag settings in the dhcpd.conf file and the bootup.cfg file. Calculate the boot flag by adding values based on desired system attributes TDM For a T1 system: add 0 For an E1 system: add 2 Boot To boot from a FTP Server: add 0 To boot from a SD Card: add 32 Codecs For LBR codecs (512 ch/mod): add 0 For LBR + ILBC codecs (336 ch/mod): add 16 387 IMG WebHelp For LBR + ILBC + Wireless codecs (336 ch/mod): add 24 An example host flag for a T1 system booting from the SD card with LBR + iLBC codecs would = 48 (0+32+16) Cantata Technology - IMG 1010 Printable WebHelp 388 Installation and Setup Guide Using an SD Card Downloading IMG System Software Using Boot File on an SD Card Topic Location: Installation and Setup Guide > Using an SD Card A BootP server is used to configure the following: IMG CTRL IP address gateway address subnet mask FTP server address FTP file name of the IMG system software If a BootP server is not available (but the remote FTP Server is available), the SD card can be used to configure the Boot parameters so the IMG can retrieve the system software from the FTP Server. Steps 1. Insert the SD Card into an SD Writer connected to a PC. 2. Open the bootup.cfg file. 3. Change the Host Flag in the bootup.cfg file to "Retrieve boot from server". Host Flag Values (Hex/Dec) 0x00/0 = Boot from FTP, T1 system 0x02/2 = Boot from FTP, E1 system 4. Edit the Server Address to the address of your FTP server where the IMG .bin file is located. See Default BootUP Config File. 389 IMG WebHelp 5. Make sure the Boot Filename is the same as the actual file you want to transfer. 6. Save the bootup.cfg file. 7. Insert the SD card into the slot on the Front Panel of the IMG. 8. Power-up the IMG. Next Task Starting GateControl EMS Cantata Technology - IMG 1010 Printable WebHelp 390 Installation and Setup Guide Downloading IMG System Software From an SD Card Topic Location: Installation and Setup Guide > Using an SD Card If an FTP server is not available to transfer the IMG System Software, the file can be loaded from the SD Card. Steps 1. Insert the SD Card into an SD Writer. 2. Open the bootup.cfg file. 3. Change the Host Flag to "Retrieve boot from SD Card". Host Flag Values (Hex/Dec) 0x20/32 = Boot from SD Card, T1 system 0x22/34 = Boot from SD Card, E1 system 4. Make sure the System Software Filename in the bootup.cfg file matches the .bin file on the card. 5. Save the bootup.cfg file. 6. Remove the SD card from the SD Writer. 7. Insert the SD card into the SD slot on the Front Panel of the IMG. 8. Power-up the IMG. Next Task Starting GateControl EMS Cantata Technology - IMG 1010 Printable WebHelp 391 IMG WebHelp Distributing IMG System Software Using an SD Card Topic Location: Installation and Setup Guide > Using an SD Card If you have remote IMGs that cannot obtain an IMG System Software upgrade using FTP or BootP, you can transfer the file to SD cards and distribute the SD cards to remote sites. You can edit the Bootup.cfg file on each card with the Boot configuration information for the IMG to which it will be shipped. Cantata Technology - IMG 1010 Printable WebHelp 392 Installation and Setup Guide Default bootup.cfg Configuration File Topic Location: Installation and Setup Guide > Using an SD Card # INSTRUCTIONS #1. Edit values as required, as described below. # Change IP Address, Subnet Mask, and Gateway IP Address to the actual values for the 1010. # If you change the version of 1010 System Software on the FTP Server or the SD card, #make sure you change the System Software Filename value. # Make sure Host Flag is set appropriately for your configuration and Boot method # Calculate Host Flag by adding values based on desired system attributes # For a T1 system: add 0 # For an E1 system: add 2 # # To boot from a FTP Server: add 0 # To boot from a SD Card: add 32 # # For LBR codecs (512 ch/mod): add 0 # For LBR + ILBC codecs (336 ch/mod): add 16 # For LBR + ILBC + Wireless codecs (336 ch/mod): add 24 # # An example host flag for a T1 system booting from the SD card with LBR + iLBC codecs would = 48 (0+32+16) # Change Server Address to the actual address of the FTP server. # The Server Name is not used at this time. #2. After editing this file: save file, remove SD card, insert SD card in the 1010, power-#up the 1010. ___________________________________________________________________ ________________________________________________________ # 1010 bootup configuration file # IP Address yiaddr=192.168.0.101 # Subnet Mask 393 IMG WebHelp subnet mask=255.255.255.0 # Gateway Address giaddr=192.168.0.1 # System Software Filename file=img1010_id0101.bin # Host Flag host flag=0x20 # Server Address for File transfer and SNTP operation. siaddr=192.168.0.100 # Server Name (Optional, not currently used) sname=factorydefault Cantata Technology - IMG 1010 Printable WebHelp 394 Setting Up Servers in Linux Setting Up an SNTP Server Topic Location: Setting Up Servers in Linux The IMG 1010 runs an SNTP client that sends an SNTP request every 60 seconds and adjusts its time if it receives a valid response. Note: Verify that the host time and time zone are correct and in the expected format. Universal Coordinated Time, UTC, is most commonly used. The factory default time zone is set as Eastern Standard Time, EST. The IMG uses the IP address of the FTP server as the location of the NTP server. SNTP is a subset of the NTP protocol; therefore, the server is referenced as an NTP server. Linux Redhat ES 3.0 includes an NTP server that is part of the basic installation. For windows users, XP includes an NTP service that can be configured easily. Linux These instructions assume that your 1010 has been configured to FTP transfer the software from a Linux machine. 1. Edit the ntp.conf to configure the NTP server. a. Open a terminal on the Linux machine and Login as root b. Type: vi /etc/ntp.conf c. Add the lines shown in Bold below with the IP addresses of the NTP servers. This will prohibit a SNTP server from adjusting the time on the Linux machine # Prohibit general access to this service. restrict default ignore #clock2.redhat.com 395 IMG WebHelp restrict 66.187.224.4 mask 255.255.255.255 nomodify notrap noquery #bonehed.lcs.mit.edu restrict 18.26.4.105 mask 255.255.255.255 nomodify notrap noquery #ntp.tmc.edu restrict 128.249.1.10 mask 255.255.255.255 nomodify notrap noquery d. Add the lines in Bold with the IP addresses of the NTP servers. # Undisciplined Local Clock. This is a fake driver intended for backup # and when no outside source of synchronized time is available. The # default stratum is usually 3, but in this case we elect to use stratum # 0. Since the server line does not have the prefer keyword, this driver # is never used for synchronization, unless no other # synchronization source is available. In case the local host is # controlled by some external source, such as an external oscillator or # another protocol, the prefer keyword would cause the local host to # disregard all other synchronization sources, unless the kernel # modifications are in use and declare an unsynchronized condition. # #clock2.redhat.com server 66.187.224.4 #bonehed.lcs.mit.edu server 18.26.4.105 #ntp.tmc.edu server 128.249.1.10 e. Add the line in Bold with your IP address of your 1010 switch. This will allow the 1010 to request time. # -- CLIENT NETWORK ------# Permit systems on this network to synchronize with this # time service. 396 Do not permit those systems to modify the Setting Up Servers in Linux # configuration of this service. Also, do not use those # systems as peers for synchronization. # restrict 192.168.1.0 mask 255.255.255.0 notrust nomodify notrap restrict 10.129.45.150 mask 255.255.255.224 notrust nomodify notrap f. Save the configuration: (‘ESC’ wq) 2. Restart the NTP server (service ntpd restart) OUTPUT Shutting down ntpd: [ OK ] ntpd: Synchronizing with time server: [ OK ] Starting ntpd: [ OK ] 3. Verify the Linux machine is synchronized with an NTP server (ntpstat) OUTPUT synchronized to NTP server (66.187.224.4) at stratum 2 time correct to within 939 ms polling server every 16 s 4. Verify the correct time on the 1010 via the front panel 5. To see the NTP packets for debug use the following, type tethereal port 123 OUTPUT (add –V to get more details) Capturing on eth0 0.000000 10.129.45.132 -> 66.187.224.4 NTP 0.051050 66.187.224.4 -> 10.129.45.132 NTP Cantata Technology - IMG 1010 Printable WebHelp 397 IMG WebHelp Sample ntp.conf File Topic Location: Setting Up Servers in Linux The following is a sample ntp.conf file. If you do not have access to the xlntp script, you must modify this file manually. Modify the lines in bold according to your particular network settings. #################################################### ############# # File: ntp.conf # Generated by: xlntp Revision: 1.1 # Cantata Technology 08/11/05_12:53:05 # Cantata Support @ 781-433-9603 http://www.cantata.com/support #################################################### ############# # which logfile group... log to /var/log/messages # Prohibit general access to this service. restrict default ignore # Prohibit general access to this service. restrict default ignore restrict 66.187.224.4 mask 255.255.255.255 nomodify notrap noquery restrict 18.26.4.105 mask 255.255.255.255 nomodify notrap noquery restrict 128.249.1.10 mask 255.255.255.255 nomodify notrap noquery # Permit all access over the loopback interface. This could # be tightened as well, but to do so would effect some of # the administrative functions. restrict 127.0.0.1 # -- CLIENT NETWORK ------- # Permit systems on this network to synchronize with this # time service. Do not permit those systems to modify the # configuration of this service. Also, do not use those # systems as peers for synchronization. # restrict 192.168.1.0 mask 255.255.255.0 notrust nomodify notrap # IMG1 restrict 192.168.0.102 mask 255.255.255.0 notrust nomodify notrap # --- OUR TIMESERVERS ----- # or remove the default restrict line # Permit time synchronization with our time source, but do not 398 Setting Up Servers in Linux # permit the source to query or modify the service on this system. # restrict mytrustedtimeserverip mask 255.255.255.255 nomodify notrap noquery # server mytrustedtimeserverip # --- NTP MULTICASTCLIENT --- #multicastclient # listen on default 224.0.1.1 # restrict 224.0.1.1 mask 255.255.255.255 notrust nomodify notrap # restrict 192.168.1.0 mask 255.255.255.0 notrust nomodify notrap # --- GENERAL CONFIGURATION --# # Undisciplined Local Clock. This is a fake driver intended for backup # and when no outside source of synchronized time is available. The # default stratum is usually 3, but in this case we elect to use stratum # 0. Since the server line does not have the prefer keyword, this driver # is never used for synchronization, unless no other other # synchronization source is available. In case the local host is # controlled by some external source, such as an external oscillator or # another protocol, the prefer keyword would cause the local host to # disregard all other synchronization sources, unless the kernel # modifications are in use and declare an unsynchronized condition. # server 127.127.1.0 # local clock fudge 127.127.1.0 stratum 10 server 66.187.224.4 server 18.26.4.105 server 128.249.1.10 # # Drift file. Put this in a directory which the daemon can write to. # No symbolic links allowed, either, since the daemon updates the file # by creating a temporary in the same directory and then rename()ing # it to the file. # driftfile /var/lib/ntp/drift broadcastdelay 0.008 # # Authentication delay. If you use, or plan to use someday, the # authentication facility you should make the programs in the auth_stuff 399 IMG WebHelp # directory and figure out what this number should be on your machine. # authenticate yes # # Keys file. If you want to diddle your server at run time, make a # keys file (mode 600 for sure) and define the key number to be # used for making requests. # # PLEASE DO NOT USE THE DEFAULT VALUES HERE. Pick your own, or remote # systems might be able to reset your clock at will. Note also that # ntpd is started with a -A flag, disabling authentication, that # will have to be removed as well. # keys /etc/ntp/keys Cantata Technology - IMG 1010 Printable WebHelp 400 Configuration ClientView Starting ClientView Topic Location: Configuration > ClientView To start ClientView and connect to the IMG, perform the following steps: 1. Launch ClientView From Linux: From the following directory: opt/cantata/IMG/IMGUserInterface/ClientView type ./ClientView From Windows Click the ClientView icon on your Desktop, or Click on the ClientView exe file located at: C:\Program Files\Cantata\IMGUserInterface\ClientView 2. When the About ClientView window appears, click CLOSE. 3. When the Client Socket window appears, enter the following: Username:admin Password: admin (or new password if you changed) Host Name or IP Address: This is the IP Address of the GC EMS Server you are connecting to. If ClientView is running on the EMS server, leave the default (localhost). Port: The Port Number 4. Click OK You are now connected to the IMG Server and ready to use ClientView. You can now access the on-line Help for detailed configuration information. 401 IMG WebHelp Cantata Technology - IMG 1010 Printable WebHelp 402 Configuration An Overview of ClientView Topic Location: Configuration > ClientView ClientView is a real-time Graphical User Interface that allows you to do the following, depending on the Roles a user has been assigned: Configuration Ability to graphically configure an IMG 1010 from initial setup to channel configuration. You can apply changes to the connected nodes with simple pointand-click operations. See Configuration Summary Monitoring Provisioning Real-time view of an IMG 1010 to monitor hardware status, alarm status, and calls in progress. You can examine detailed alarms and statistics without decoding log files. See Monitoring the IMG. Allows real-time changes required to maintain optimal processing, including bringing components in or out of service, busying out components, and managing channel groups. You can avoid low level channel and trunk group assignments and maintenance by creating and maintaining trunk groups through the interface. See An Overview of Provisioning the IMG. Role assignments are controlled by a system administrator using the AdminManager utility. See An Overview of User Management. Main Window 403 IMG WebHelp Panes The following panes appear in the main window. Configuration Tree (Top-Left) Configuration Pane (Top-Right) This pane contains all of the items that can be configured. You right-click an item to access additional configuration items. Creating an entry in the Configuration Tree opens the corresponding Configuration Pane (top right). This pane shows the properties of the selected object. You use this pane to view and edit your configuration. The column entitled As Configured shows the current configuration when connected to an IMG 1010. You enter or edit values in the User-Specified column. Buttons (Middle-Right) The buttons available vary depending on the configuration pane selected. Click Help to access the on-line help for the pane selected. 404 Configuration See An Overview of Provisioning the IMG for the Provisioning Buttons available for each pane. Information Pane (Lower-Right) This pane includes the following tabs: Object Table: For objects that include entries (such as Translation Tables and IP Bearer Traffic Profiles), this table shows all of the currently configured entries for the selected object. The contents vary depending on the object. If you select a row in the table, the configuration pane for that entry appears in the Configuration pane. Object Status: Shows the status messages that have been sent for the object selected. System Status: Shows all of the ConfigStatus messages sent from the IMG. The contents of this tab are the same regardless of the current pane selected. Socket Activity: Monitor Pane (Lower-Left) This pane shows the activity between ClientView and the IMGs. Configuration Tree Configuration Pane Buttons Monitor Pane Information Pane Cantata Technology - IMG 1010 Printable WebHelp 405 IMG WebHelp Using ClientView Topic Location: Configuration > ClientView Logging in to ClientView When you launch to ClientView the Client Socket dialog appears. 1. Enter a valid Username and Password. See your System Administrator if you do not know this information. 2. Enter a value in the Host Name or IP Address field. This is the IP Address of the Control port of the IMG to which you are connecting. If ClientView is running on the same server as the Gate Control EMS, you can leave the default "localhost". Login History ClientView will maintain entries in the Host Name/IP Address and Username fields so that you can easily select them from a drop-down list. By default, 5 Host Names and 5 Usernames will be retained in history. You can change these values using the Application Properties pane. See ClientView Properties. Creating a Configuration File A default configuration file called "default" is created when ClientView connects to Data Manager. To save the configuration file with a new name: 1. Click Configuration default in the Configuration Tree 2. Enter a new name in the Filename field of the Configuration default pane. Opening a Saved File To open this configuration going forward: 1. Select File - Open and Commit Configuration File. 406 Configuration 2. The available configuration files are listed with their last date of modification. You can sort files by name or date. Select the desired configuration file. NOTE: When you open a configuration file all nodes that are part of that configuration will be reset and reconfigured. Saving a Config File through a Software Upgrade To continue using a configuration file when you upgrade the IMG software do the following: 1. Save the *.csa file configuration file in the config folder to another folder. 2. After upgrading, copy the *csa file back to the config folder. 3. Start ClientView and select File - Open and Commit Configuration File and select the *.csa file. You access configuration panes via the tree in the left pane by right-clicking on existing items and selecting further configuration options from the list. When you create a new configuration entry, the configuration pane appears in the left pane. You enter values in the User-Specified column. Committing an Object After you make entries in a ClientView pane, you must commit the object to make the new configuration take effect. To Commit an object: Right-click on the entry in the Configuration Tree and select Commit Or simple select any other object in the tree. ClientView Tips You access configuration panes via the tree in the left pane by right-clicking on existing items and selecting further configuration options from the list. When you create a new configuration entry, the configuration pane appears in the left pane. You enter values in the User-Specified column. IMG Network-wide objects such as Routing Configuration and External Network Elements are accessed under Cantata IMG EMS. Objects configured for individual IMGs (Facilities, Signaling) are accessed under the Physical IMG entry you created. For some objects (such as Routing Tables), you first create a container object (Routing Tables) and then you add actual Route Tables. To de-select an item in a drop-down list, press CTRL and click on the item. 407 IMG WebHelp The last entry in each tree is the Object ID and Position information for internal use and does not result in any action if you select it. Cantata Technology - IMG 1010 Printable WebHelp 408 Configuration The ClientView Main Window Topic Location: Configuration > ClientView Panes The following panes appear in the main window. Configuration Tree (Top-Left) Configuration Pane (Top-Right) This pane contains all of the items that can be configured. You right-click an item to access additional configuration items. Creating an entry in the Configuration Tree opens the corresponding Configuration Pane (top right). This pane shows the properties of the selected object. You use this pane to view and edit your configuration. The column entitled As Configured shows the current configuration when connected to an IMG 1010. You enter or edit values in the User-Specified column. Status Pane (Lower-Right) Client/Server Monitor Pane (Lower-Left) This pane shows status information for the item selected. The contents varies depending on the item. If you select a row in the status table, the configuration pane for that entry appears in the top right pane. This pane shows the level of activity between ClientView and the IMGs. Changing Pane Display If you want to display only the top or bottom pane, you can click the corresponding arrow button on the bar between the upper pane and the lower pane. These arrow buttons also display vertically to allow you to manipulate the display of the left and right panes. Related Topics ClientView Menus ClientView Indicators Using ClientView Cantata Technology - IMG 1010 Printable WebHelp 409 IMG WebHelp ClientView Menus Topic Location: Configuration > ClientView Menu Selection File Open and Commit Configuration File Open a configuration file. The configuration is automatically sent to the IMG. Save Configuration File Save the Configuration File you are working on. Exit Exit ClientView Delete Current Object Delete the object currently selected in the Configuration Tree. Commit Current Object Commit the currently selected object. Undo Changes Reverts the values in the current pane back to the previous state. Expand Tree Opens all entries in the Configuration Tree. Collapse Tree Closes all entries in the Configuration Tree. View Socket Activity Opens a Client Socket window showing messaging between ClientView and the IMG. Edit View Communications 410 Description Configuration Tools Auto-Commit When AutoCommit is enabled, the entries you make in a pane are automatically saved and downloaded to the IMG when click on another entry in the Configuration Tree. AutoCommit is enabled by default and cannot be disabled by the user. Launch EventView Select this option to launch the EventView utility. Properties Configure Various ClientView Properties IMPORTANT NOTE: Under certain circumstances involving complex messaging between ClientView and GCEMS, AutoCommit may be disabled and changes you make will not be automatically sent to the IMG. The fields in the Configuration Pane will be orange when this condition exists and the box next to the Auto-Commit selection will not be checked (as shown above). You should reenable AutoCommit by selecting AutoCommit from the Tools menu. See Introduction to EventView. See ClientView Properties 411 IMG WebHelp Validation Report Confirm that your configuration does not contain any errors that may prohibit proper operation. See Validating Your Configuration Create Tree Automatically create basic objects to begin your configuration. See Auto-create ClientView Configuration Tree Help Visit Cantata Website Opens the Cantata website in a browser. About ClientView Provides information on Java Heap statistics, ClientView version, and Environment Variables. IMG Help Launches the IMG 1010 On-line Help. www.Cantata.com The HTML-based Help format is designed to run on a wide variety of browsers and platforms. When you click the Help button you will be presented with specific information about the configuration pane that you are currently working on. Update IMG Help You can retrieve WebHelp updates from the Cantata Support site that will replace the WebHelp version launched from ClientView. You will always have the option to revert back to the original Help version. Cantata Technology - IMG 1010 Printable WebHelp 412 Configuration ClientView Menu buttons Topic Location: Configuration > ClientView Open Open a new configuration File. You cannot open a new configuration file for a currently configured system. Save Save the configuration. Delete Current Object Delete the object currently selected. Open Help Launch the IMG WebHelp. Commit Current Object Commit the currently selected object. Move Selected Object Up Move the currently selected object up in the ClientView tree. An example of this would be moving all of the Logical IMGs to the top of the tree so they can be viewed together. Move Selected Object Down Move the currently selected object down in the ClientView tree. Undo Changes Reverts the values in the current pane back to the previous state. Cantata Technology - IMG 1010 Printable WebHelp 413 IMG WebHelp ClientView Indicators Topic Location: Configuration > ClientView Configuration Fields The following are the color indicators in Configuration pane fields. Green Indicates a field that has been committed and is read-only (cannot be changed). Orange Indicates a field that has been committed and can be changed. Yellow Indicates a field that is for informational purposes only and is not configurable. Progress Indicator The progress indicator window pops up between configuration of different objects. The colors indicate the status of a commit attempt. When a certain object is being configured on the IMG 1010, the user is blocked from adding new configuration. Flashing Yellow/Orange Gray Red When you send a configuration, the progress indicator flashes yellow/orange and provides text on what process is occurring. When the progress indicator is gray, the configuration was successful. When the progress indicator is red, the configuration was unsuccessful. At this point you must either fix the problem with the configuration or delete the object. Object State Icons The following icons appear to indicate various object states. Icon Description This is the initial state before you commit a configuration. These icons indicate that the IMG is in the process of performing the requested configuration. Distinctions between the icons are for Customer Support use. Contact Customer Support if the object fails to transition to a configured state. The object is in a cached state. To send the configuration to the IMG you must click on the parent object. See Cached Objects below to see a list of objects that may be in this state, and their parent object. 414 Configuration The object has been successfully configured. An error has occurred during the configuration of this object. Check the Object Status tab at the bottom of the screen for error log. A license validation has failed. Make sure you have the required license and that it is configured on the IMG. See Downloading a New License and the License Info pane. The hardware has failed. ClientView/GC EMS is not currently connected to the node or the node is temporarily frozen (approximately 1 minute) while a new IMG node is being added to the GC EMS. Cached Objects The following objects are stored in cache until you send the configuration to the IMG by clicking on the parent object. The Cached State icon ( state. Child Object IP Bearer Profile TOS Configuration ) appears in the ClientView tree when an object is in this Parent Object IP Bearer Profiles IP Bearer Profiles Supported Vocoders Channel Group Route List Route Entry Route Table Time of Day Entry Time of Day Table Translation Entry Translation Table Advanced Billing Number Translation Advanced Carrier Number Translation Advanced Dialed Number Translation 415 IMG WebHelp Advanced Originating Number Translation Treatment Entry Treatment Table Treatment Phrase Vocabulary index Entry Lost Connection Admin Manager Data Manager 416 Vocabulary index Files Configuration Mandatory fields When you have not entered values for all of the mandatory fields of an object and then try to select another object, a dialog box, <object name> Mandatory Fields Empty opens. You can go back to the object by clicking Continue Editing Object or you can select Delete Object and Children. Cantata Technology - IMG 1010 Printable WebHelp 417 IMG WebHelp Configuring ClientView Properties Topic Location: Configuration > ClientView You can configure various attributes of ClientView using the ClientView Properties pane (Tools > Properties) Accessing this Pane Pane Field Descriptions Number of Hosts Retained in History The number of Host Name/IP Address entries retained in the Login pane history. Auto-Launch EventView If enabled, EventView will launch automatically when you log in to ClientView. Product Name The Product to which you are connecting (auto-populated with IMG). Number of Usernames Retained in History The number of Username entries retained in the Login pane history. Cantata Technology - IMG 1010 Printable WebHelp 418 Configuration ClientView Search Capabilities Topic Location: Configuration > ClientView Description The Search feature in ClientView allows you to search your configuration for specific text strings. Search can be performed in forward or backward direction. You can search on partial strings (ex. a search on "IM" will find "IMG"). You can apply various filters to the search. Wildcards are not supported. Accessing the Search Toolbar To access the search tool bar, click on the Search Button: or select View > Toolbars > Search Search Toolbar Find text box - Enter the string to search on. Use the drop-down icon previously entered strings. to select Next - Press to initiate the search and then to proceed to the next match. Previous - Press to return to the previous match Filters - See below. 419 IMG WebHelp Search Filters Match Case - the search will be case sensitive. Object Name - the search is based on the ‘Object Name’ in the configuration tree (left pane). As-Configured - search based on the ‘As-Configured’ values of the Properties (second column in main configuration pane). User-Specified - search based on ‘User-Specified’ values of the Properties (third column in main configuration pane). Property- the search is based on the ‘Property Name’ (first column in main configuration pane). OID/POS (Object ID/Position) - This is used for internal debugging with Cantata Technical Support. Example When the text string is found in an object, the specific pane where the string is found is displayed in the pane window and the object name is highlighted in the configuration tree, as shown below. Cantata Technology - IMG 1010 Printable WebHelp 420 Configuration Assigning ClientView Users Topic Location: Administration > User Management Unless you specifically assign user privileges, anyone can access the GCEMS with full Administrative Privileges using: UserName: admin Password: admin Procedure If you want to assign passwords and roles to individual users who may have access to the EMS, follow this procedure. 1. Login to AdminView a. Run AdminView <./AdminView> (located at opt/cantata/IMG/GateControlEMS/bin/ b. Login as Administrator User ID: admin Password: admin 2. Change the Admin Password To limit access to the Admin functions, perform the following steps. a. Type chpwd and press ENTER. b. Enter the Admin user ID, admin, and press ENTER. c. Enter a new password and press ENTER. d. Re-enter the new password and press ENTER. 3. Add a User and assign roles a. Type adusr and click ENTER. b. Enter a user ID and click ENTER. c. Enter a password for the user and press ENTER. d. Confirm the password and press ENTER. e. Enter values for the roles to assign to the user. 1 - Administrator 2 - Basic 3 - Configuration 4 - Provisioning 421 IMG WebHelp 5 - Monitoring f. Repeat steps a-e for each user. g. Quit Help For a list of commands, type help More Information For more detailed information on Administering User Privileges, see Administering User Privileges in the IMG 1010 On-line Help. Cantata Technology - IMG 1010 Printable WebHelp 422 Configuration Changing the Order of Objects in ClientView Tree Topic Location: Configuration > ClientView For some objects you can use the Up/Down arrows in the Menu to re-order the objects in the ClientView tree. For example, you could group all of your Logical IMGs together at the top of the tree, as shown below. Cantata Technology - IMG 1010 Printable WebHelp 423 IMG WebHelp Upgrading ClientView Topic Location: Configuration > ClientView When you upgrade to a newer version of ClientView, there may be some changes to panes or fields that affect your existing configuration. If there are any such changes detected, a report is generated and displayed in a Configuration File Conversion Report, shown below. The report includes the following information for each change: Reference Object - The ClientView object that has changed (for example, IMG EMS) Description - Identifies what has changed or is missing. Action - Indicates how ClientView will handle the discrepancy. After reviewing the report, you will have the following options: Do Not Configure or save Save with changes but do not configure Configure with changes but do not save Configure and save with changes NOTE: When you open a configuration file all nodes that are part of that configuration will be reset and re-configured. 424 Configuration Once you select an option, the Configuration File Conversion window no longer appears. Report Files File Syntax "filename_timestamp.html" Directory Reports are saved in the following directory: opt\cantata\common\log\ File Changes/Actions Change Action Config file has a property that ClientView does not recognize. Property ignored. ClientView has a property that the Config File does not contain a value for. Property is set with the default value. Config file has a property value that is no longer allowed by ClientView. Property is set with the default value. Invalid XML attribute added to Config file by user. Added attribute will be ignored and reported in the log file Required XML attribute/element removed from Config file by user Attributes/elements are populated with the default value. Property renamed. Property is ignored. Config file has an object that is no longer in ClientView Object and all children ignored Object changed position in the new ClientView hierarchy Object ignored. Config file format changes to remove another attribute or element If it is a mandatory attribute; removed attribute will be set with empty string. No report generated. No reported generated. Log generated. Removed element will be set with the default value in the definition file. 425 IMG WebHelp Config File Missing Mandatory Value In rare cases, an object may have a mandatory field added where there is no default value populated. In this case you will not be able to open your existing configuration file. The only option available is "Do not configure or save". Contact Technical Support if you see this condition. Cantata Technology - IMG 1010 Printable WebHelp 426 Configuration Introduction Configuration Summary Topic Location: Configuration > Introduction The following is a summary of the areas that require configuration on an IMG. See the TOC for individual task within each area. 1. Basic Configuration 2. Network Interfaces 3. Facilities 4. VoIP 5. External Elements 6. Signaling 7. Routing 8. RADIUS Cantata Technology - IMG 1010 Printable WebHelp 427 IMG WebHelp Validating Your Configuration Topic Location: Configuration > Introduction Use the Validation Report utility to confirm that your configuration does not contain any errors that may prohibit proper operation. Analyze the report for possible errors found and modify your configuration accordingly. Running a Validation Report To validate your configuration, in the configuration tree right-click Cantata IMG EMS and select Validation Report. Report Location The resulting validation report is stored at the following location: /opt/cantata/IMG/reports Report Filename ValidationReport_YYYY.MM.DD.HH.MM.SS.txt Report Contents The report includes three sections: Section 1: High Probability of an error Section 3: Informational Section 2: Possible Error In each section, there are a number of possible error conditions listed. If the condition exists in your configuration, there will be a subentry indicating the source of the error. For example: 1.2) Outgoing Channel Groups that are not in a route 1.2.1) Channels Group: isdn - ID: 0 See Sample Validation Report 428 Configuration Cantata Technology - IMG 1010 Printable WebHelp 429 IMG WebHelp ClientView Objects Tree (with maximums) Topic Location: Configuration > Introduction The IMG Quick Reference Poster includes a diagram showing all of the ClientView objects and indicates the maximum number of the object that can be created. Cantata Technology - IMG 1010 Printable WebHelp 430 Configuration Sample Validation Report Topic Location: Configuration > Introduction The following is a sample of a validation report returned when you run the Validation utility. Section 1: High Probability of an error 1.1) Incoming Channels Groups without a Route Table assigned 1.1.1) Channels Group: isdn - ID:0 1.2) Outgoing Channel Groups that are not in a route 1.2.1) Channels Group: isdn - ID: 0 1.3) VoIP Channels Groups without an IP Network Element 1.4) TDM Channel Group without any circuits 1.4.1) Channels Group: isdn - ID:0 1.5) SS7 Route not assigned to a Channel Group 1.5.1) SS7 Route: StackId: 0 - OPC: 1-1-1 - DPC: 1.6) SS7 Linkset without Routes or Links 1.7) ISDN D-Channels not assigned to a Channel Group 1.8) VoIP Interfaces without a Module assigned to it 1.9) CPU Interfaces with nothing assigned to it 1.10) Variants Configured but not used 1.10.1) Variant Table Name: Variant Name ID: 1 1.11) GateKeepers configured but not used 1.12) Gateways assigned but not used 1.12.1) External Gateway: sip gw 1 1.13) NFS Servers Configured but not used 1.14) Radius Servers Configured but not used 1.15) DNS Servers Configured but not assigned 1.16) Nodes without a Radius Client if a Radius Server is configured 1.17) Nodes without a Media Client if a NFS Server is configured 1.18) Nodes without a DNS Client if a DNS Server is configured Section 2: Possible Error 2.1) Route Tables that are not used 2.2) Cause Code Tables that are not used 2.3) Translation Tables that are not used 431 IMG WebHelp 2.4) Route Lists that are not used 2.4.1) Route List: rt 1 - ID: 1 2.5) Time of Day Tables that are not used 2.5.1) Time of Day Table: TOD 1 - ID: 1 2.6) Route Tables without any route entries 2.7) Cause Code Tables without any route entries 2.8) Translation Tables without any translation entries 2.9) Route Lists without any Channel Groups assigned 2.9.1) Route List: rt 1 - ID:1 2.9.2) Route List: rl2 - ID:2 2.10) Time of Day Tables without any route entries 2.11) TDM Channels assigned but not used 2.11.1) Node Name: Boston, Bearer - ID:0, Channel: 1 2.11.2) Node Name: Boston, Bearer - ID:0, Channel: 2 Section 3: Informational 3.1) List of GateKeepers configured 3.2) List of Gateways configured 3.2.1) SIP GW Name: sip gw 1, Transport: UDP, Port: 5060, IP Address: 0d:1.1.1.1 3.3) List of NFS Servers configured 3.4) List of DNS Servers configured 3.5) List of Radius Servers configured Cantata Technology - IMG 1010 Printable WebHelp 432 Configuration Basic Configuration An Overview of Basic Configuration Topic Location: Configuration > Basic Configuration 1. Create a Logical IMG 2. Add a Physical IMG 3. Configure Media 4. Configure Synchronization Cantata Technology - IMG 1010 Printable WebHelp 433 IMG WebHelp Auto-create ClientView Configuration Tree Topic Location: Configuration > Basic Configuration When you first open a new configuration file, you can automatically populate the ClientView Configuration Tree with the basic IMG objects. From the Main Menu, select Tools > Create Tree. The Configuration Tree will be populated with the following objects using their default values. Cantata Technology - IMG 1010 Printable WebHelp 434 Configuration Creating a Logical IMG Topic Location: Configuration > Basic Configuration Before you can add and configure Physical IMGs, you must create a Logical IMG to which you then add Physical IMGs. Physical IMGs in the same Logical IMG do not have to be co-located. Physical IMGs do not have to be in the same Logical IMG unless you are doing SS7 signaling and they are controlled by the same SS7 stack. Prerequisites Creating a Configuration File Steps 1. Right-click IMG EMS and select New Logical IMG. The Logical IMG pane appears 2. In the Name field, enter a name for the Logical IMG. 3. Right-click the Logical IMG entry and select Commit. See the Logical IMG pane reference for more details. Next Task Adding a Physical IMG Cantata Technology - IMG 1010 Printable WebHelp 435 IMG WebHelp Adding a Physical IMG Topic Location: Configuration > Basic Configuration 1. Right-click the Logical IMG you just created and select New Physical IMG. The Physical IMG pane appears. Automatically Populated Field: Logical IMG ID = Next Available Number 2. In the IMG Name field, enter a name. 3. In the IP Address field, enter the IP Address of this physical IMG. This is the same IP Address assigned to the CTRL 0 port on the back of the IMG. Automatically Populated Field: IMG Type = 1010 NOTE: The IP Address entered in step 3 is the IP address assigned to the CTRL 0 port on the IMG. Next Topics Network Interface Scenarios Creating Network Interfaces Cantata Technology - IMG 1010 Printable WebHelp 436 Configuration Configuring a Synchronization Priority List Topic Location: Configuration > Basic Configuration Before running the IMG, you must synchronize T1 and E1 spans to the network. You can either configure a timing synchronization priority list that the IMG uses when it selects a synchronization clock source or accept the defaults. Refer to Synchronization Priority List for the defaults. Refer to the steps below to configure. Prerequisites Creating a Logical IMG Steps 1. Right-click the Physical IMG and select New Timing Synchronization Priority List. The Timing Synchronization Priority List pane appears. 2. Select the appropriate clock source for each property. See the Timing Synchronization Priority pane reference. Related Topic About Synchronization Priority Lists Cantata Technology - IMG 1010 Printable WebHelp 437 IMG WebHelp About Synchronization Priority Lists Topic Location: Configuration > Basic Configuration Before running the IMG, you must synchronize T1 and E1 spans to the network. Refer to Configuring Synchronization Priority List to configure a prioritized list of clock sources. The IMG uses this list when it selects a synchronization clock source. Default Priority The default priority for synchronization resources is as follows: 1. External Reference Clock 1 (Primary) 2. External Reference Clock 2 (Secondary) 3. Loop Timing 1 (Primary) 4. Loop Timing 2 (Secondary) 5. Free Running clock (Internal) The IMG continuously monitors all synchronization clock sources and uses the highest priority clock source currently available. For example, if you use the default configuration above, the IMG first determines if the Primary External Reference Clock is available. If it is not available, the IMG determines if the Secondary reference Clock is available. The IMG continues to check each source, in succession, until it finds an available source. When a higher priority source becomes available, the IMG automatically changes to the higher priority clock source. Clock Sources Descriptions of the synchronization sources are as follow: External Reference Clock Reference Timing is generated by an external clock source to the IMG Loop Timing Loop timing synchronizes the system to an incoming T1 or E1 span. You must first designate which span you want to use to extrapolate the clock. Free Running Clock Free running timing is based on the internal clock source of 2.048 Mbps. Free running timing is for test environments only. Do not use this timing method for network operations. You can determine the current active timing by performing a synchronization priority list query. Next Topic Configuring Synchronization Priority List Cantata Technology - IMG 1010 Printable WebHelp 438 Configuration Setting Local Time Topic Location: Configuration > Basic Configuration 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. You configure the local time on an IMG using the Time Zone Setting pane. If you configure your RADIUS Client to use local time, it will be used in the Radius fields that use time: setup time disconnect time connect time Format The local time is on the offset from GMT (Greenwich Meantime) Example 1 EST (Eastern Standard Time THU JAN 01 00:03:55:850 2007 -0500 Where -0500 represents 5 hours behind GMT Example 2 There is a time zone in Australia that is nine and half hours ahead of GMT time. This would be represented as: THU JAN 01 00:03:55:850 2007 +0930 Configuration You configure the local time on an IMG using the Time Zone Setting pane. You configure the format for time to be represented in RADIUS CDRs in the RADIUS Client pane. Time of Day Tables If a TOD table is configured and can be used across multiple IMGs, each IMG will use its own local time. Cantata Technology - IMG 1010 Printable WebHelp 439 IMG WebHelp Configuring Media Topic Location: Configuration > Basic Configuration These tasks will configure DSPs on the IMG. Prerequisites You must have an NFS Server configured. See Configuring an NFS Server. ClientView Tree The graphic below shows the ClientView tree of panes used to configure media. Task Summary 1. Indicate Configured NFS Servers 2. Configure Media Modules 3. Configure DSP Functions Indicating Configured NFS Servers 1. Right-click the physical IMG you are configuring and select New Media. The Media pane appears. 2. In the Media Name field, enter the name of the NFS server. 3. In the User ID field, enter the User ID for UNIX permissions. 4. In the Group ID field, enter the Group ID for UNIX permissions. The Network Interface field is automatically populated with the IP Address of the IMG you are configuring. 440 Configuration The Primary Vocabulary Index File Name field is automatically populated with the name of the default file that is downloaded to the NFS Server as part of the IMG EMS installation process. 5. If you have a secondary NFS server configured, enter the Secondary Vocabulary Index File Name and the Secondary Server ID. See the Media pane reference for details. Configuring Media Modules The fields in this pane are automatically populated. Module Interface ID = 0 Module Name = On-board. 1. Right-click the Media entry you created and select New Media Module. The Media Module pane appears. For field descriptions see the Media Module pane reference. 2. Proceed to the next task. Configuring DSP Functions 1. Right-click the Module you just configured and select New Media DSP. The Media DSP pane appears. 2. In the DSP Id field, select the DSP you are configuring. 3. In the remaining fields, select the function you want to configure for the Receive and Transmit for each of the two DSP streams. The following function types are supported Receive u-law DTMF u-law MFR1 a-law DTMF a-law MFR1 u-law MFR2 441 IMG WebHelp a-law MFR2 a-law CPA u-law CPA Playback/Record Transmit u-law Universal Generator a-law Universal Generator For field descriptions, see the Media DSP pane reference. NOTE ON CAS: For DTMF reception configure an a-law or u-law Universal Receiver. For MFR1 or MFR2 reception you must configure the specific MFR1 or MFR2 receiver accordingly. If you try to perform MFR1 or MFR2 using a Universal Receiver, you will get a Call Trace indication of "No DSP of this type configured". Next Topic A Summary of Routing Configuration Tasks Cantata Technology - IMG 1010 Printable WebHelp 442 Configuration Importing Data Topic Location: Configuration > Basic Configuration A dialog box will appear at the start of import to gather the user choices for how the import is to be processed. This GUI is simply a reflection of the data stored by the Import Manager. Here is the dialog box for the merge handling options, presented at the start of the import. Here is the dialog box for the import error handling options, presented when a conditional import error is encountered: 443 IMG WebHelp Cantata Technology - IMG 1010 Printable WebHelp 444 Configuration Network Interfaces Configuring Network Interfaces Topic Location: Configuration > Network Interfaces When you configure the Network Interfaces using ClientView, you provide physical and logical interface data which configures how the network traffic is organized over the subnets. NOTE: The IP Address 10.31.42.X (Subnet: 255.255.255.0) is reserved for the IMGs. Do not attach to any external network with this address. Overview There are three types of IMG streams: Control (management) NOTE: You do not need to configure a Network Interface for Network Management (Control). It is configured automatically during the BootP process and the connection is made when you login to ClientView. Signaling (H.323/SIP) Data (RTP) You can separate the streams into separate network interfaces, have them all combined, or have the signaling and RTP combined with management separate. IMPORTANT: Your Data and Control ports must be segregated (on separate hubs). See Network Interfaces Scenarios for sample scenarios that you should consider when configuring your network interfaces. Prerequisites Adding a Physical IMG Guidelines When you configure the Network Interface for H.323 or SIP Signaling you provide the IP address. When you configure H.323 or SIP Signaling, you select this IP address from the drop down list. This associates the signaling to the physical IP address over which it is running. The two VoIP modules are allowed only on data ports so their IP addresses must be on the same subnet. If the CPU is configured to go through the Control port, the IP address of that profile should be on the same subnet as the IMG's IP address (CTRL 0/1 IP addresses). If the CPU is configured to go through the Data ports, the IP address of that profile should be on a different subnet from the IMG's CTRL 0/1 subnet. This IP can be on the same subnet as the VoIP modules or a different one. 445 IMG WebHelp Do not delete the VoIP module 0/1 if that profile is used to configure the VoIP modules 0/1 under Facility. Also, if a CPU network interface is configured and used for NFS traffic, do not delete it. Steps 1. Right-click the Physical IMG and select New Network Interfaces. 2. Right-click the Network Interface and select New Network Interfaces. The Network Interface pane appears. 3. Complete the fields as described in the Network Interface pane reference. 4. Right-click the entry and select Commit. 5. Repeat these steps for the other network interfaces as required. See Also Network Interface Scenarios Next Task Creating a Facility Object Cantata Technology - IMG 1010 Printable WebHelp 446 Configuration Network Interface Scenarios Topic Location: Configuration > Network Interfaces When you configure the Network Interfaces, you provide physical and logical interface data which helps configure how the network traffic is organized over the subnets. Related Topics Configuring Network Interfaces Configuring H.323 Signaling Configuring SIP Signaling Scenarios The following four scenarios provide the information you use when configuring the Network Interfaces. Each scenario contains the sample information and a diagram to help you configure your network interfaces. The port on the back plane is also included to tie configuration to the actual I/O connections. One Subnet Two Subnets (Data/Signaling and Control) Two Subnets (Control/Signaling and Data) Three Subnets Cantata Technology - IMG 1010 Printable WebHelp 447 IMG WebHelp Scenario 1 - One Subnet Topic Location: Configuration > Network Interfaces In this scenario all traffic runs over one subnet. You do not need to configure the CPU Physical Interface for Redundant Control. It is configured automatically during the BootP process. When you configure H.323 or SIP Signaling, you select 10.10.25.2 for the IP Address in the H.323 Signaling or SIP Signaling pane. Stream Type and Where Assigned Sample IP Address Physical Interface Logical Interface Port on Back Plane Control and Signaling 10.10.25.2 CPU/CPU H.323/SIP Redundant Control CTRL 0 or 1 IP Bearer Data 10.10.25.100 VoIP Module 0 Redundant Data DATA 0 or 1 IP Bearer Data 10.10.25.101 VoIP Module 1 Redundant Data DATA 0 or 1 Assigned at BootP not Pane Assign in Network Interface Pane Assign in Network Interface Pane 448 Configuration ClientView Panes 449 IMG WebHelp Cantata Technology - IMG 1010 Printable WebHelp 450 Configuration Scenario 2 - Two Subnets: Control/Signaling and Data Topic Location: Configuration > Network Interfaces In the following scenario, you combine control and signaling on one subnet and data on another subnet. This network interface scenario assigns a second address to the CPU (in addition to the one assigned at BootP) for H.323 or SIP Signaling. When you configure H.323 or SIP Signaling, you select 10.10.25.2 for the IP Address in the H.323 Signaling or SIP Signaling pane. Note that this scenario does not interoperate with Cisco Gatekeepers. Stream Type and Where Assigned Sample IP Address Physical Interface Logical Interface Port on Back Plane Control 10.10.25.1 CPU Redundant Control CTRL 0 or 1 H.323/SIP Signaling 10.10.25.2 CPU/ H.323 or SIP Redundant Control CTRL 0 or 1 IP Bearer Data 10.10.30.100 VoIP Module 0 Redundant Data DATA 0 or 1 IP Bearer Data 10.10.30.101 VoIP Module 1 Redundant Data DATA 0 or 1 (Assigned at BootP) Assigned in Network Interface Pane Assigned in Network Interface Pane 451 IMG WebHelp ClientView Panes 452 Configuration Cantata Technology - IMG 1010 Printable WebHelp 453 IMG WebHelp Scenario 3 - Two Subnets B: Data/Signaling and Control Topic Location: Configuration > Network Interfaces In the following scenario, you combine the signaling and data on one subnet and the control on another subnet. When you configure H.323 or SIP Signaling, you select 10.10.30.70 for the IP Address in the H.323 Signaling or SIP Signaling pane. Stream Type and Where Assigned Sample IP Address Physical Interface Logical Interface Port on Back Plane Control 10.10.25.2 CPU Redundant Control CTRL 0 or 1 H.323 or SIP Signaling 10.10.30.70 CPU (H.323/SIP) Redundant Data DATA 0 or 1 IP Bearer Data 10.10.30.100 VoIP Module 0 Redundant Data DATA 1 or 0 IP Bearer Data 10.10.30.101 VoIP Module 1 Redundant Data DATA 1 or 0 Assigned at BootP Assigned at Network Interfaces Pane Assigned at Network Interfaces Pane Assigned at Network Interfaces Pane 454 Configuration ClientView Panes 455 IMG WebHelp Cantata Technology - IMG 1010 Printable WebHelp 456 Configuration Scenario 4 - Three Subnets Topic Location: Configuration > Network Interfaces In the following scenario, you separate control, data, and signaling each on their respective subnets. When you configure H.323 or SIP Signaling, you select 10.10.30.70 for the IP Address in the H.323 Signaling or SIP Signaling pane. Stream Type and Where Assigned Sample IP Address Physical Interface Logical Interface Port on Back Plane Control 10.10.25.2 CPU Redundant Control CTRL 0 or 1 H.323 or SIP Signaling 10.10.30.70 CPU (H.323/SIP) Redundant Signaling SIG 0 or 1 IP Bearer Data 10.10.50.100 VoIP Module 0 Redundant Data DATA 0 or 1 IP Bearer Data 10.10.50.101 VoIP Module 1 Redundant Data DATA 0 or 1 Assigned at BootP Assigned in Network Interface Pane Assigned in Network Interface Pane Assigned in Network Interface Pane 457 IMG WebHelp ClientView Panes 458 Configuration Cantata Technology - IMG 1010 Printable WebHelp 459 IMG WebHelp Configuring IP Interface Mode Topic Location: Configuration > Network Interfaces The interfaces on the IMG default to 10.100 with Auto-negotiation. You can change the setting to Full Duplex, in which case it will be negotiated to half-duplex. NOTE: Full Duplex is not supported for CTRL 0/1. Steps 1. Right-click Network Interfaces and Select New Physical Port Configuration. The Physical Port Configuration pane appears. 2. For each port, select the desired interface mode: Auto or 100 Full. See the Physical Port Configuration pane reference for details. Cantata Technology - IMG 1010 Printable WebHelp 460 Configuration Facilities Creating a Facility Object Topic Location: Configuration > Facilities You create the facility object once and then configure individual TDM and VoIP facilities. Prerequisites Configuring a Physical IMG Steps 1. Right-click the Physical IMG entry and select New Facility. 2. Right-click Facility and select Commit. Related Tasks Configuring Signaling Spans Configuring a Range of Signaling Spans Configuring a TDM Bearer Span Cantata Technology - IMG 1010 Printable WebHelp 461 IMG WebHelp Using the Facility Wizard Topic Location: Configuration > Facilities Steps 1. Right-click Facility 2. Click the Facility Wizard button. 3. The first pane that appears is the TDM DS1 Wizard pane, shown below. Complete the fields as required and click OK. The next pane that appears depends on whether the span is E1 or T1. See the T1 Physical Span pane reference or E1 Physical Span pane reference. Cantata Technology - IMG 1010 Printable WebHelp 462 Configuration T1/E1 Facility Wizard Topic Location: Configuration > T1/E1 Use the Facility Wizard to configure a range of spans. From the Facility pane, click the Facility Wizard button. This will launch a pane to configure the range. When you click OK, the appropriate configuration pane will be launched depending on the Trunk Type. Cantata Technology - IMG 1010 Printable WebHelp 463 IMG WebHelp Configuring a T1 or E1 Bearer Span Topic Location: Configuration > T1/E1 Pre-requisite Creating a Facility Object Steps 1. Right-click Facility and select New TDM DS1. The Trunk Type field is automatically populated with the Trunk Type (T1 or E1) that your system type is configured for. 2. In the Component ID field select Bearer. Auto-populated Field: Interface ID 3. Right-click the Bearer-ID entry and select Commit. 4. Right-click the Bearer-ID entry and select New T1 Physical Span or New E1 Physical Span. The T1 Physical Span pane or E1 Physical Span pane appears. 5. Complete the fields as described in the T1 Physical Span pane reference or E1 Physical Span pane reference. Cantata Technology - IMG 1010 Printable WebHelp 464 Configuration Configuring a Range of TDM Bearer Spans Topic Location: Configuration > T1/E1 You can create up to 21 E1 bearer spans and 28 T1 bearer spans. Steps 1. Right-click the IMG entry and select New Facility. The Facility Pane appears For more details see the Facility GUI reference. 2. Click the Facility Wizard button. The Facility Wizard pane appears. 3. Enter values in the fields as required. 4. Click OK. 5. The next pane that appears depends on whether you are configuring a T1 or E1 span. See the T1 Physical Span pane reference or E1 Physical Span pane reference accordingly. Next Topic Configuring VoIP Modules Cantata Technology - IMG 1010 Printable WebHelp 465 IMG WebHelp Configuring a Signaling Span Topic Location: Configuration > T1/E1 Prerequisites Configuring a Physical IMG Creating a Facility Object Steps 1. Right-click Facility and select New TDM DS1. Auto-populated Field: Trunk Type - automatically populated with T1 or E1 based on the type of IMG you have. 2. In the Component ID field select Signaling. Auto-populated Field: Interface ID - automatically populated with next available number. 2. Right-click the Bearer-ID entry and select New T1 Physical Span or New E1 Physical Span. The T1 Physical Span pane appears. 3. Complete the fields as described in the T1 Physical Span pane reference or E1 Physical Span pane reference. Cantata Technology - IMG 1010 Printable WebHelp 466 Configuration Configuring a Range of Signaling Spans Topic Location: Configuration > T1/E1 You configure a range of signaling spans with the Facility Wizard. To configure individual spans, see Configuring a Signaling Span. Prerequisites Configuring a Physical IMG Configuring a New Facility Steps 1. Right-click Facility. 2. Click the Facility Wizard button. The Facility Wizard pane appears. 3. Complete the fields as described in the Facility pane reference. Be sure to select Signaling for the Component ID. 4. Click OK. 5. The next pane depends on whether you are configuring a T1 span or E1 span. Complete the fields as required. See the T1 Physical Span pane reference or E1 Physical Span pane reference. Next Topic Configuring TDM Bearer Spans Cantata Technology - IMG 1010 Printable WebHelp 467 IMG WebHelp DS3 DS3 Overview Topic Location: Configuration > DS3 A DS3 has a bandwidth of 44.736 Mbps, which is the capacity of 28 T1 spans. Every 85th bit in a DS3 bit sequence is used for overhead functions such as frame alignment, error detection, and terminal-to-terminal data communication. All other bits are payload bits. The DS3 signal format typically transports 672 channels at 64 Kbps per channel. The DS3 signaling interface is bipolar with Bit 3 Zero Substitution (B3ZS). The IMG supports the following: Loop Timing for DS1's residing on the DS3. The DS3 uses the M-Frame format and supports the following framing modes: M13 (default) C-bit The IMG supports the following type of DS3 diagnostics: local loop back BERT remote loop back from the far-end switch Related Topics DS3 Diagnostics Cantata Technology - IMG 1010 Printable WebHelp 468 Configuration Configuring a DS3 Topic Location: Configuration > DS3 Steps 1. Right-click Facility and select New TDM DS3. The TDM DS3 pane appears. 2. In the DS3 Framing Type field, leave the default (M13) or select CBIT. 3. Right-click the Bearer-ID entry and select New DS3 Physical Span. The DS3 Physical Span pane appears. 4. Complete the fields as described in the DS3 Physical Span pane reference. Cantata Technology - IMG 1010 Printable WebHelp 469 IMG WebHelp Configuring a Range of DS3s Topic Location: Configuration > DS3 To configure a range of DS3s, use the Facility Wizard. 1. Right-click Facility and select New TDM DS3. The TDM DS3 pane appears. 2. Complete the fields as required. See the TDM DS3 pane reference for details. 3. Click the Facility Wizard button at the bottom of the TDM DS3 pane. The DS3 Wizard pane appears. 4. Enter the Starting Offset and the Span Count to identify the range of DS3s you are configuring. 5. Click OK. The DS3 Physical Span pane appears. 6. Complete the fields as required. See the DS3 Physical Span pane reference for details. Cantata Technology - IMG 1010 Printable WebHelp 470 Configuration DS3 Diagnostics Topic Location: Configuration > DS3 Loopback Testing To test Layer 1 signal integrity, you can enable local or remote loopback on a DS3 or DS1s. DS3 You Enable local or remote loopback with the DS3 Loopback Mode field in the TDM DS3 pane. To allow loop-back to be configured from the far-end, enable the DS3 and DS1 FEAC Responses option in the TDM DS3 pane. TDM T1 To enable local or remote loopback on a T1 span, set the Loopback Mode field in the T1 Physical Span pane. E1 To enable local or remote loopback on an E1 span, set the Loopback Mode field in the E1 Physical Span pane. NOTE: When you place a span in loopback mode the Span Status will indicate Out Of Service. Following the test you must manually put the span back in service by selecting the In Service button. BERT Use Bit Error Rate Testing (BERT) to test the quality of DS3 links and to troubleshoot problems. You send out a known bit pattern and verify the received bits against the sent pattern. A high bit error rate indicates noise on the circuit. You can configure the IMG to run Bit Error Rate Tests (BERT) on a DS3 or on individual DS1s in a DS3, including: Generate a test pattern to be verified by a piece of external test equipment or another IMG Monitor a test pattern when configuring both the transmit and receive. Insert bit errors Starting and Stopping a BERT Test 1. Right-click on the desired DS3 entry and select New BERT Test. The BERT pane appears. 471 IMG WebHelp 2. Select options as required in the fields. See the BERT pane reference for more information. Note: DS1’s do not need to be configured when testing the entire DS3 circuit. 3. When you have finished configuring options, commit the configuration. Testing starts as soon as the configuration has been committed. While in test mode, the span status LED for the DS3 or DS1s will flash orange. Results The results of the test are shown in the Status fields of the BERT pane. The following information is reported: Monitor Status This is the status of the object that is being monitored, since this is a BIT map these fields could be concatenated together. Bits Received This is the amount of Bits received in Megabits. Errors Received This is the amount of bit errors received. Elapsed Time Cantata Technology - IMG 1010 Printable WebHelp 472 Configuration VoIP An Overview of IP Configuration Topic Location: Configuration > VoIP Summary of Tasks 1. Configure IP Bearer Network Interface 2. Configure IP Interface Mode (Optional) 3. Configure VoIP Modules 4. Configure IP Bearer Profiles 5. Assign IP Bearer Profiles to Channel Groups 6. Configure Comedia NOTE on VoIP Channel Distribution: If the IMG has two VoIP modules installed, channels are assigned to each module in groups of 32. For example if the IMG is licensed for 96 channels, 64 will be on the first module and 32 will be on the second module. Cantata Technology - IMG 1010 Printable WebHelp 473 IMG WebHelp ClientView Panes used for VoIP Configuration Topic Location: Configuration > VoIP Cantata Technology - IMG 1010 Printable WebHelp 474 Configuration Configuring VoIP Topic Location: Configuration > VoIP Steps Perform the following steps to configure a VoIP module to the IMG: 1. Configure Network Interface a. Right-click the Physical IMG and select New Network Interfaces. b. Right-click Network Interfaces and select New Network Interface. The Network Interface pane appears. c. In the Physical Interface field select VoIP Module 0: Port 0 d. In the Logical Interface field select Redundant Data. e. In the IP Address, Subnet and Default Gateway fields, enter the appropriate values. f. Right-click the entry and select Commit. For more details see the Network Interface pane reference. 2. Configure VoIP Facilities a. Right-click Facility and select New Bearer - IP. The VoIP Module pane appears. Automatically populated fields: The Module ID field is automatically populated with 0 The Network Interface field is automatically populated with VoIP Module 0: Port 0 The Network IP Address field is automatically populated with the IP Address of the module. The Module Configuration Profile field is automatically populated with Any Vocoder. b. Right-click the entry and select Commit. For more details see the VoIP Module pane reference. Next Topics Configuring H.323 Signaling 475 IMG WebHelp Configuring SIP Signaling Cantata Technology - IMG 1010 Printable WebHelp 476 Configuration Configuring a Second VoIP Module Topic Location: Configuration > VoIP Related Topic Adding a VoIP Module Procedure Perform the following steps to configure a second VoIP module to the IMG: 1. Configure Network Interface a. Right-click the Physical IMG and select New Network Interfaces. b. Right-click Network Interfaces and select New Network Interface. The Network Interface pane appears. c. In the Physical Interface field select VoIP Module 1: Port 0 d. In the Logical Interface field select Redundant Data. e. In the IP Address, Subnet and Default Gateway fields, enter the appropriate values. f. Right-click the entry and select Commit. For more details see the Network Interface pane reference. 2. Configure VoIP Facilities a. Right-click Facility and select New Bearer - IP. The VoIP Module pane appears. Automatically populated fields: The Module ID field is automatically populated with 1 The Network Interface field is automatically populated with VoIP Module 1: Port 0 The Network IP Address field is automatically populated with the IP Address of the module. The Module Configuration Profile field is automatically populated with Any Vocoder b. Right-click the entry and select Commit. For more details see the VoIP Module pane reference. 477 IMG WebHelp Cantata Technology - IMG 1010 Printable WebHelp 478 Configuration Configuring IP Bearer Profiles Topic Location: Configuration > VoIP You can define up to 16 IP Bearer Profiles that define the inbound and outbound behavior of a call. You assign IP Bearer Profiles to SIP or H.323 channel groups. Configure IP Bearer Profiles 1. Right-click Cantata IMG EMS and select New IP Bearer Profiles. 2. Right-click IP Bearer Traffic Profiles and select New IP Bearer Profile. The IP Bearer Profile pane appears. 3. Complete the fields as described in the IP Bearer Profile pane reference. If required, use the Comedia Mode field to enable Comedia. See Comedia for more information. Assigning Vocoders to Profile 1. To assign vocoders to the profile, right-click on the profile and select New Supported Vocoders. The Supported Vocoder pane appears. 2. Select the desired vocoder from the Payload Type field and change default payload size settings if required. IMPORTANT NOTE: You must have your Host Flags set correctly to enable certain vocoders. Additionally, you must have a valid license for AMR and EVRC. NOTE: The order that the vocoders appear in the table are the order they are used in the H.245 Terminal Capability Exchange for the IP Bearer Profile. The entries are listed in descending priority. You can change the order using the up and down buttons on the toolbar. 3. Repeat steps 4-5 to add additional vocoders to the profile. See the Supported Vocoders pane reference for details. Configure Type of Service 1. Right-click the IP Bearer Profile entry and select New TOS Configuration. 479 IMG WebHelp The TOS Configuration pane appears. 2. Select values as required. See the TOS Configuration pane reference for more details. Cantata Technology - IMG 1010 Printable WebHelp 480 Configuration Changing the Order of Codecs in an IP Bearer Profile Topic Location: Configuration > VoIP The order that the vocoders appear in the table are the order they are used in the H.245 Terminal Capability Exchange for the IP Bearer Profile. The entries are listed in descending priority. You can change the order using the up and down buttons on the toolbar. Cantata Technology - IMG 1010 Printable WebHelp 481 IMG WebHelp External Elements Configuring External Network Elements Topic Location: Configuration > External Elements Steps 1. Right-click Cantata IMG EMS and select New External Network Elements. 2. Right-click External Network Elements and select the desired option, as shown below: 3. Complete the specific pane as required. Related Topics Adding an External Gateway Adding an External H.323 Gatekeeper Configuring_a_RADIUS_Accounting_Server Configuring an NFS Server Configuring an External SIP Gateway Configuring DNS for SIP Cantata Technology - IMG 1010 Printable WebHelp 482 Configuration Adding an External H.323 Gatekeeper Topic Location: Configuration > Routing > H.323 Routing You can add up to 1024 external gatekeepers to which the H.323-configured IMGs will communicate. For each gatekeeper you can also configure up to six alternative gatekeepers. Steps 1. Right-click Cantata IMG EMS and select New External Network Elements. 2. Right-click External Network Elements and select New External Gatekeepers. 3. Right-click External Gatekeepers and select New External Gatekeeper. The External Gatekeeper pane appears. See the External GateKeeper pane reference for details. 4. Enter the Gatekeeper Name and Gatekeeper IP Address. If you don't know the IP Address you can enter 224.0.1.41 to broadcast for an available gatekeeper. 5. Enable Gatekeeper Auto Discovery if desired. The IMG will automatically send GRQ - Gatekeeper Request and RRQ - Registration Request to the external gatekeeper. You can also Discover and Register with a gatekeeper manually using the buttons on the H.323 Signaling pane. 6. To add alternate gatekeepers (up to 6 per primary gatekeeper), right click the External Gatekeeper entry and select New Alternate Gatekeepers. The Alternate Gatekeeper pane appears. 7. Enter the Gatekeeper ID, Gatekeeper Name and Gatekeeper IP Address. See the Alternate Gatekeeper pane reference for details. 483 IMG WebHelp Related Topics Configuring H.323 Signaling Cantata Technology - IMG 1010 Printable WebHelp 484 Configuration Adding an External Gateway Topic Location: Configuration > External Elements Use this pane to configure up to 1024 External SIP or H.323 Gateways from which the IMG may receive calls. To configure a group of gateways, use the Gateway Mask field to validate a range of IP addresses. Steps 1. Right-click External Elements and select New External Gateways. 2. Right-click External Gateways and select New External Gateway. The External Gateway pane appears. 3. In the Gateway Signaling Protocol field select H.323 or SIP. 4. In the Gateway IP Address, enter the IP address of the gateway. 5. To validate a range of IP addresses for multiple gateways, use the Gateway Mask field. See the External Gateway pane reference for details. Related Topics Configuring H.323 Signaling Configuring SIP Signaling Cantata Technology - IMG 1010 Printable WebHelp 485 IMG WebHelp Configuring an NFS Server Topic Location: Configuration > External Elements To download announcements and tones to the IMG, you must configure an NFS Server. 1. Right-click External Network Elements and select NFS Server. 2. Right-click NFS Servers and select New NFS Server. The NFS Server pane appears. 3. The NFS Server ID field is automatically populated with the next available number, but you can change it (1-8). 4. The server is enabled by default. To disable it, change the NFS Server Enabled field to Disabled. 5. In the NFS Server Name field, enter a descriptive name for the server. 6. In the NFS Server IP Address field, enter the IP address of the server. 7. In the NFS Mount Directory field, enter the directory where the media files are located. The directory must start with “/” or “\\”. For more information, see the NFS Server pane reference. Next Topic Configuring Media Cantata Technology - IMG 1010 Printable WebHelp 486 Configuration Signaling Configuring Signaling Topic Location: Configuration > Signaling 1. Right-click the desired Physical IMG and select New Signaling. 2. Right-click Signaling and select one of the options, shown below: 3. Complete the specific pane as required. Related Topics Configuring SIP Signaling Configuring H.323 Signaling Configuring SS7 Signaling Configuring ISDN Signaling Cantata Technology - IMG 1010 Printable WebHelp 487 IMG WebHelp SIP An Overview of SIP Configuration Topic Location: Configuration > Signaling > SIP Related Topic An Introduction to SIP Prerequisites Configure IP Bearer Profiles Configure VoIP Configure Facilities Summary of Tasks 1. Configure an External SIP Gateway 2. Configure a SIP Profile (Optional) 3. Configure SIP Signaling 4. Configure SIP Routing 5. Configure DNS for SIP (Optional) ClientView Panes for SIP Configuration SIP Signaling SIP Timers External Gateway Channel Group DNS Server 488 Configuration First Task Configuring SIP Signaling Cantata Technology - IMG 1010 Printable WebHelp 489 IMG WebHelp Configuring SIP Signaling Topic Location: Configuration > Signaling > SIP Before you Begin Configure SIP Profile (Optional) A SIP Profile allows you to easily assign a number of SIP features to a Physical IMG. 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. 1. Right-click Cantata IMG EMS and select New SIP Profile 2. Enable desired features and enter values in fields where required. See the SIP Profile pane reference for details. You can assign the profile to an external gateway (in the Remote IMG SIP Profile field in the External Gateway pane), or to a SIP Signaling object (see next procedure) Configure SIP Signaling 1. Right-click the Physical IMG and select New Signaling. 2. Right-click Signaling and select New SIP. The SIP Signaling pane appears. 3. Complete the fields as described in the SIP Signaling pane reference. You can assign a SIP Profile in the SIP Profile field. If you are enabling SIP-T, see Configuring SIP-T. Configuring SIP Timers (Optional) 1. 490 Right-click SIP Signaling and select New SIP Timers. Configuration The SIP Timers pane appears. 2. Change default values for timers as required. Next Task Configuring SIP Routing Cantata Technology - IMG 1010 Printable WebHelp 491 IMG WebHelp Configuring SIP-Based Load Balancing Topic Location: Configuration > Signaling > SIP This feature allows you to distribute SIP traffic between IMGs configured as “SIP Servers” using Virtual IP Addresses and a SIP load balancer. The Load Balancer and all SIP Server nodes to contain the same IP address. The Load Balancer is the only node which is allowed to respond to ARPs for this Virtual IP Address. This prevents external network elements from obtaining the MAC address of the SIP Servers, and forces all external inbound traffic to/through the Load Balancer and then to the SIP Servers. The Load Balancer is configured with the MAC address of it’s SIP Servers, and when it receives a SIP message it determines which SIP Server to send it to and then exchanges the Destination MAC address in the frame with the desired SIP Server’s MAC address. The frame is then placed on the Ethernet and arrives at the desired SIP Server. Configuration Pre-requisite You must configure your Load Balancer’s routing tables with the MAC addresses of its SIP Servers (IMGs), corresponding to the virtual IP address. Steps To implement SIP Based Load Balancing, perform the following: 1. Create a Network Interface for CPU with Gratuitous ARP and ARP Responses set to Disable. 2. Under the SIP Signaling object, create a new SIP Virtual Address object. 492 Configuration 3. In the SIP Virtual Address pane, select the Network Interface you just created. 4. To configure another virtual IP Address for this IMG, repeat steps 2 and 3. 5. Repeat steps 1-4 for each IMG that requires a virtual SIP Address. CDRs Even if the VIP is used to initiate a call, the primary IP address is used in the CDR containing the local IP. Cantata Technology - IMG 1010 Printable WebHelp 493 IMG WebHelp Configuring SIP-T Topic Location: Configuration > Signaling > SIP Enable SIP-T To enable SIP-T: 1. Right-click the Physical IMG and select New Signaling. 2. Right-click Signaling and select New SIP. The SIP Signaling pane appears. 3. In the Enable SIP-T field, select Yes. 4. In the SIP-T Behavior field, select Optional or Mandatory. When you enable SIP-T you can make it Optional (default) or Required. If you make it Required and the far end does not support SIP-T the call will be released. Modify outgoing ISUP variant name in ISUP MIME body (Optional) The ISUP variant names used by the IMG in the ISUP MIME body are listed below. Cantata ISUP MIME Nomenclature ANSI-92 ANSI-97 494 ANSI-95 CCITT-88 ETSI-V1 ETSI-V2 ETSI-V3 ITU-93 Configuration ITU-97 If you need to modify the name sent in ISUP MIME messages to match the far end, you can create a new signaling variant and then assign it to a stack in the SIP-T Entity pane. 1. Create a custom SS7 variant using the desired base variant and enter the exact name required by the far end. a. Right click Cantata IMG EMS and select New Signaling Variants. b. Right click Signaling Variants and select New Signaling Variant. The Signaling Variant pane appears. c. In the Variant Name field, enter the name for the variant expected by the far end. d. In the Variant Type field select SIP-T. e. In the Base Variant field, select the base variant to use for this custom variant. Automatically Populated Field: Variant ID = next available number in sequence. See the Signaling Variant pane reference for more details. 2. Assign the variant to an SS7 Stack. a. Right-click the SIP signaling entry and select New SIP T Entity. The SIP T Entity pane appears. b. Select the SIP Stack and the custom variant as required. See the SIP T Entity pane reference. Cantata Technology - IMG 1010 Printable WebHelp 495 IMG WebHelp Configuring SIP Privacy Topic Location: Configuration > Signaling > SIP Related Topics SIP Privacy SIP Signaling To enable Privacy for the entire GC EMS, set the Privacy Support field in the SIP Signaling pane for the method supported by the proxy. All calls will be handled according to this setting, regardless of other SIP Privacy settings on an External Gateway or ISDN/ISUP Group. External Gateway Set the Privacy Info field in the External Gateway field according to what is supported by the SIP Proxy to which the IMG is connected. ISDN Group/ISUP Group To enable Privacy for an ISDN Group or an ISUP Group, set the Discard Privacy Info field in the ISDN Group pane or the ISUP Group pane to Yes. Diagram 496 Configuration Cantata Technology - IMG 1010 Printable WebHelp 497 IMG WebHelp H.323 An Overview of H.323 Configuration Topic Location: Configuration > Signaling > H.323 H.323 Configuration involves the following tasks: Configuring H.323 Signaling Configuring H.323 Routing Configuring an External H.323 Gateway Adding an External H.323 Gatekeeper Cantata Technology - IMG 1010 Printable WebHelp 498 Configuration Configuring H.323 Signaling Topic Location: Configuration > Signaling > H.323 Prerequisites Configuring VoIP Modules Steps 1. Right-click Physical IMG and select New Signaling. 2. Right-click Signaling and select New H.323. The H.323 Signaling pane appears. 3. Complete the fields as noted below. See the H.323 Signaling pane reference for details. H.323 ID H.245 Tunneling (if required). H.323 Signaling Address This enables inbound tunneling. You can enable outbound tunneling in the IP Bearer Traffic Profile used for outbound calls. See H245 Tunneling. The following fields currently have only one option so are not configurable: H.323 Variant (ITU) H.323 Terminal Type (GW with no MC) H.323 Version (H.323 V2) The following fields are only required if you are connecting to an external gatekeeper (which you must configure with the External GateKeeper pane. Gatekeeper Support (change to Enable) Gateway URL E.164 Number Gateway EMail Gateway Terminal Prefix (if the external gateway requires one) 4. To change the default H.323 timers, right-click the H.323 Signaling entry and select New H.323 Timers. Refer to H.323 Timers pane reference. Gateway Discovery/Registration 499 IMG WebHelp You can Discover and Register with a gatekeeper manually using the Gateway buttons in the H.323 Signaling pane. To automatically Discover and Register with a gatekeeper, enable Gatekeeper Auto Discovery in the External Gatekeeper pane. Related Topics IP Bearer Profiles Adding an External Gatekeeper H.323 Signaling pane External Gatekeeper pane Cantata Technology - IMG 1010 Printable WebHelp 500 Configuration SS7 An Overview of SS7 Configuration Topic Location: Configuration > Signaling > SS7 Related Topic An Overview of SS7 Guidelines The GC EMS supports up to 4 SS7 Stacks, which can be on the same IMG or distributed across 4 IMGs. Each stack must have a unique OPC. SS7 CICs for all 16 IMGs in a Logical IMG can be controlled by signaling links on one IMG configured as an SS7 Server node (or a pair of redundant IMG SS7 Server nodes). Links in a redundant link set can be on the same IMG, or on a redundant pair of IMGs. Tasks See the following procedures: Configuring SS7 Signaling Configuring SS7 CIC Routing ClientView Panes used for SS7 configuration The following diagram shows the ClientView Panes used for SS7 Configuration. 501 IMG WebHelp Cantata Technology - IMG 1010 Printable WebHelp 502 Configuration Configuring SS7 Signaling Topic Location: Configuration > Signaling > SS7 Follow the procedures below to configure SS7 Signaling on the IMG. Prerequisites 1. Acquire the Originating Point Code (OPC) and Adjacent Point Code (APC) before configuring the SS7 stack. 2. Assign and configure spans. Set the span Signaling to Clear Channel. See Configuring Signaling Spans. Summary of Steps The following is a summary of the basic SS7 configuration. You must perform the steps in this order. Click each one for the details. 1. Create an SS7 Signaling Entry 2. Configuring Signaling Stacks 3. Configuring Signaling Link Sets 4. Configuring Signaling Links 5. Configure SS7 Routes Creating an SS7 Signaling Entry Steps 1. Right-click Physical IMG and select New Signaling. 2. Right-click Signaling and select New SS7 Signaling. The SS7 Signaling Pane appears. If you are not configuring redundant SS7 nodes, leave the Redundancy Configuration field at Standalone. The Peer Logical Node ID field does not apply. If you are configuring SS7 Redundancy, set the Redundancy Configuration field to Primary and in the Peer Logical Node ID field select the Secondary SS7 node. See Configuring SS7 Redundancy for more information. Configuring SS7 Signaling Stacks Configuring multiple signaling stacks allows the IMG to interface with multiple SS7 networks. The IMG supports up to four signaling stacks. Signaling stacks are automatically assigned to SS7 objects (links, link sets, routes) as each object is configured. Steps 503 IMG WebHelp 1. Right-click the SS7 node you just configured and select New SS7 Stack. The SS7 Stack pane appears 2. The Stack ID field is automatically populated with the next available number (0-3). 3. Refer to the SS7 Stack pane reference to complete the rest of the fields. Configuring SS7 Signaling Link Sets A signaling link set is an abstract path between the IMG and an APC (Adjacent Point Code), to which physical signaling links are added. The same signaling stack must be assigned to all links in a link set. A typical configuration consists of two link sets. Signaling links in a link set are “load sharing” that is, signaling traffic is distributed equally on the links to optimize efficiency. When you configure multiple stacks, the Link Set IDs assigned to each signaling stack must be different. For example, if Link Set ID is assigned to Stack 1, it cannot also be assigned to Stack 2. Steps 1. Right-click the desired SS7 Stack entry and select New Link Set. The SS7 Link Set pane appears. 2. The Link Set ID field is automatically populated with the next available number. 3. In the APC (Adjacent Point Code) field, enter the point code of the adjacent node to which this link set will be connected. The format of the APC will follow the same rules in the SS7 stack. For example if the OPC is ITU 97, which follows the format of 3-8-3, the APC should also be running ITU 97 and should follow the format of 3-8-3. See the SS7 Link Set pane reference for more information. Configuring SS7 Signaling Links A signaling link is a point-to-point connection between two SS7 point codes (in this case, an IMG and an STP). The place holder assigns a physical location in the IMG (timeslot) and a previously configured Signaling Link Set to a signaling link. When you configure multiple stacks on the IMG, the Link IDs assigned to each signaling stack must be different. For example, if Link ID is assigned to Stack 1, it cannot also be assigned to Stack 2. SS7 Redundancy When configuring Primary and Secondary IMGs for SS7 Redundancy you must assign SS7 Signaling Links 0-63 to the primary IMG and Signaling Links 64-128 to the secondary IMG. Note that you send all SS7 configuration to the primary IMG. See Configuring SS7 Redundancy for more information. Steps 504 Configuration 1. Right-click the desired Link Set and select New SS7 Link. The SS7 Link pane appears. 2. The Primary/Secondary field is set to Primary be default. If you are configuring links on a secondary IMG for redundancy, select Secondary 3. The Link ID field is automatically populated with the next available number. If the links are on a Primary IMG, the available range is 0-63. If the links are on a Secondary IMG, the available range is 64-127. 4. The Interface - Offset field drop-down will include spans configured on the IMG you are configuring (Primary or Secondary) and default to the first available span. Refer to the SS7 Link pane reference for information on the other fields. Configure Signaling Routes See Configuring SS7 Signaling Routes Cantata Technology - IMG 1010 Printable WebHelp 505 IMG WebHelp Configuring SS7 Signaling Routes Topic Location: Configuration > Signaling > SS7 A signaling route defines a path between a signaling stack and a DPC. Guidelines The IMG supports up to 255 routes, identified by a Route ID. When you configure multiple SS7 stacks, the Route IDs assigned to each signaling stack must be different. For example, if Route ID is assigned to Stack 1, it cannot also be assigned to Stack 2. A Destination ID defines the relationship of a signaling stack and a specific DPC. The IMG supports up to 128 distinct Destination IDs. All routes between a specific signaling stack/DPC pair must use the same Destination ID. Multiple stacks on the same IMG must have unique Destination IDs. Steps Perform one the following procedures, depending on the type of route, to configure routes for SS7 Signaling. Configuring a New Route 1. Right-click SS7 Stack and select New SS7 Route. The SS7 Route pane appears. 2. The Route ID field is automatically populated with the next available number. You can change it if you require (valid range:0-511). 3. The Route Type field is automatically populated with New Route. 4. The Link Set ID field is automatically populated with the ID of the Link Set to which you are adding the route. 5. In the New DPC field, enter the DPC. For ITU, the point codes range from 0-0-0 to 7-255-7. For ANSI, the point codes range from 0-0-0 to 255-255-255. 6. The Existing DPC field is automatically populated with the same value as you entered in the New DPC field. 7. In the Priority field, select the priority to assign to the route when there are multiple routes to the same destination (valid range:0-35). 8. Use the Comments field to enter a meaningful name to identify the route. See the SS7 Route pane reference for more information. Configuring an Existing Route with no Combined Link Set 506 Configuration 1. Right-click SS7 Stack and select New SS7 Route. The SS7 Route pane appears. 2. The Route ID field is automatically populated with the next available number. You can change it if you require (valid range:0-511). 3. In the Route Type field, select Existing Route (Combined Link Set Disabled). 4. The Link Set ID field is automatically populated with the ID of the Link Set to which you are adding the route. 5. In the Existing DPC field, select the desired DPC for the route. 6. In the Priority field, select the priority to assign to the route when there are multiple routes to the same destination (valid range:0-35). 7. Use the Comments field to enter a meaningful name to identify the route. See the SS7 Route pane reference for more information. Configuring an Existing Route with a Combined Link Set 1. Right-click SS7 Stack and select New SS7 Route. The SS7 Route pane appears. 2. The Route ID field is automatically populated with the next available number. You can change it if you require (valid range:0-511). 3. In the Route Type field, select Existing Route (Combined Link Set Enabled). 4. In the Link Set ID field, select the other Link Set for the Combined Link Set. 5. In the Existing DPC field, select the desired DPC for the route. 6. Use the Comments field to enter a meaningful name to identify the route. See the SS7 Route pane reference for more information. Cantata Technology - IMG 1010 Printable WebHelp 507 IMG WebHelp Configuring SS7 Redundancy Topic Location: Configuration > Signaling > SS7 You can configure two Physical IMGs in the same Logical IMG to be a redundant pair for SS7 signaling. All subsequent IMGs added to the Logical IMG are automatically considered Remote SS7 Nodes and will have CICs controlled by the Primary and Secondary nodes. Pre-requisite If you have not already done so, 1. Create the Logical IMG to which the SS7 nodes will be assigned. 2. Create the two Physical IMGs that will be the Primary and Secondary SS7 nodes. 3. Add facilities to each IMG. Configure Redundant SS7 Signaling on the Primary IMG See Configuring SS7 Signaling for the general procedure, setting specific fields in panes as noted below. 1. SS7 Signaling See Creating_an_SS7_Signaling_Entry In the Redundancy Configuration field, select Primary. In the Peer Logical Node ID field, select the secondary IMG. If there is only one other IMG in the Logical IMG it will be automatically populated with that Node. 2. Primary SS7 Links See Configuring_SS7_Signaling_Links. In the Primary/Secondary field select Primary. The Interface - Offset field drop-down will include spans configured on the Primary IMG and default to the first available span. The Link ID field drop-down will include IDs 0-63, and will be populated with the first available number. 3. Secondary SS7 Links See Configuring_SS7_Signaling_Links. NOTE: These links are configured on the Primary IMG. 508 In the Primary/Secondary field select Secondary. The Link ID field drop-down will include IDs 64-127, and will be populated with the first available number. Configuration The Interface - Offset field drop-down will include spans configured on the Secondary IMG and default to the first available span. Cantata Technology - IMG 1010 Printable WebHelp 509 IMG WebHelp Configuring SS7 Redundancy with Remote Control of CICs Topic Location: Configuration > Signaling > SS7 Pre-requisite Before configuring SS7 Redundancy, create the two Physical IMGs that will be the Primary and Secondary SS7 Signaling nodes. Steps 1. Configure the Primary IMG/Server Node 2. Configure the Secondary IMG 3. Configure SS7 Signaling on the Primary IMG 4. Add Remote SS7 Node IMGs Configuring the Primary IMG/Server Node On the IMG to be the primary IMG, create an SS7 Signaling Entry. 1. Right-click on the Physical IMG entry and select New Signaling. 2. Right-click Signaling and select New SS7 Signaling. The SS7 Signaling pane appears. 3. In the Redundancy Configuration field select Primary. Automatically Populated Field: Peer Logical Node ID = the other IMG you have created See the SS7 Signaling pane reference for more details. Configuring the Secondary IMG On the IMG to be the Secondary IMG, create an SS7 Signaling Entry. 1. Right-click on the Physical IMG entry and select New Signaling. 2. Right-click Signaling and select New SS7 Signaling. The SS7 Signaling pane appears. 3. In the Redundancy Configuration field, select Secondary. Automatically Populated Field: Peer Logical Node ID = the ID of the IMG that was configured as Primary. See the SS7 Signaling pane reference for more details. Configuring SS7 Signaling on the Primary IMG 510 Configuration See Configuring SS7 Signaling. Adding Remote SS7 IMGs Any Physical IMGs you add to the same Logical IMG as the Server Node are automatically considered Remote SS7 nodes. SS7 Signaling for their CICs is automatically handled by the SS7 Server node. You do not need to perform any SS7 Signaling configuration on these IMGs. 1. Right-click the Logical IMG entry select New Physical IMG. The Physical IMG pane appears. 2. Complete the fields as described in the Physical IMG GUI reference. 3. Configure SS7 CICs on the node. 4. Repeat steps 1-3 for any other IMG in the Logical IMG. Query Remote Node Info You can query remote Node information by selecting The following pop-up will appear indicating the LNI and IP Address of the remote node. 511 IMG WebHelp Cantata Technology - IMG 1010 Printable WebHelp 512 Configuration Configuring Multiple IMGs for SS7 Topic Location: Configuration > Signaling > SS7 SS7 Redundancy Remote Control of CICs SS7 Redundancy with Remote Control of CICs Two IMGs load-share SS7 signaling links. If the Primary IMG is lost, the Secondary IMG takes over all signaling requirements. One IMG is an SS7 Server Node and handles all SS7 signaling for other IMGs in the same Logical IMG. The Remote IMGs do not require any SS7 signaling connections or SS7 signaling configuration. Two IMGs load-share SS7 signaling links. If the Primary IMG is lost, the Secondary IMG takes over all signaling requirements. The Primary IMG is also an SS7 Server Node and handles all SS7 signaling for other IMGs in the same Logical IMG. The Remote IMGs do not require any SS7 signaling connections or SS7 signaling configuration The following illustration shows a scenario where SS7 Redundancy and Remote Control of CICs are both employed. 513 IMG WebHelp Cantata Technology - IMG 1010 Printable WebHelp 514 Configuration Configuring Control of Remote CICs Topic Location: Configuration > Signaling > SS7 You can configure an IMG with SS7 Links to control CICs on other nodes in the same Logical IMG. This procedure assumes you are not configuring SS7 Signaling Redundancy. Steps 1. Configure an IMG as an SS7 Server node. 2. Configure SS7 Signaling on the Server Node 3. Add SS7 Client IMGs Configuring an IMG as an SS7 Server Node On the IMG to be the SS7 server, create an SS7 Signaling Entry and configure signaling. 1. Right-click on the Physical IMG entry and select New Signaling. 2. Right-click Signaling and select New SS7 Signaling. The SS7 Signaling pane appears. Automatically Populated Field: Redundancy Configuration = Standalone. Keep this setting. Peer Logical Node ID field = does not apply. See the SS7 Signaling pane reference for more details. Configure Signaling on the Server Node See Configuring SS7 Signaling. Add SS7 Client IMGs Any Physical IMGs you add to the same Logical IMG as the Server Node are automatically considered Remote SS7 nodes. SS7 Signaling for their CICs is automatically handled by the SS7 Server node. You do not need to perform any SS7 Signaling configuration on these IMGs. 1. Right-click the Logical IMG entry select New Physical IMG. The Physical IMG pane appears. 2. Complete the fields as described in the Physical IMG pane reference. 3. Configure SS7 CICs on the node. 4. Repeat steps 1-3 for any other IMG in the Logical IMG. 515 IMG WebHelp To view the status of a remote SS7 node, right-click on the Physical IMG entry and select SS7 Remote Node Info. Cantata Technology - IMG 1010 Printable WebHelp 516 Configuration Provisioning SS7 CICs Topic Location: Configuration > Signaling > SS7 You provision CICs from the Status Pane under the Circuit Group Configuration Pane, by right-clicking the CIC entry and selecting the desired operation: In Service Maintenance Block Out of Service Maintenance Unblock Reset You can select a group of CICs by dragging the cursor. Cantata Technology - IMG 1010 Printable WebHelp 517 IMG WebHelp Configuring Custom SS7 Variants Topic Location: Configuration > Signaling > SS7 To create a new SS7 signaling variant: 1. Right click Cantata IMG EMS and select New Signaling Variants. 2. Right click Signaling Variants and select New Signaling Variant. The Signaling Variant pane appears. 3. In the Variant Name field, enter a name for the variant. Automatically Populated Field: Variant Type = SS7. 4. In the Base Variant field, select the base variant to use for this custom variant. Automatically Populated Field: Variant ID = next available number in sequence. See the Signaling Variant pane reference for more details. 5. Right click the entry you just configured in the Configuration Tree and select New Variant Entry. The Variant Entry pane appears. 6. Configure fields as required. See the Variant Entry pane reference for more details. Importing Variant Entries To import a variant entries, store the variant file ("variantname".cfg) in the path /opt/cantata /IMG/config/Variant/"VariantName"/ on the linux host. 518 Configuration The CSV file to load the variant into GCEMS needs to be on the same machine that the ClientView is running on, either Linux or Windows. Right-click the Variant Name you created and select Import Variant Entry, then select the desired file.. Cantata Technology - IMG 1010 Printable WebHelp 519 IMG WebHelp ISDN An Overview of ISDN Configuration Topic Location: Configuration > Signaling > ISDN Prerequisites Creating a Facility Object Summary of Steps The following is a summary of the basic ISDN configuration. 1. Configure ISDN Signaling 2. Configure ISDN Routing ClientView Panes for ISDN Configuration ISDN Signaling ISDN D Channel ISDN Group ISDN Circuits ISDN Timers Channel Group The following illustration shows the objects in the Client View Configuration Tree that relate to ISDN Configuration. 520 Configuration Cantata Technology - IMG 1010 Printable WebHelp 521 IMG WebHelp Configuring ISDN Signaling Topic Location: Configuration > Signaling > ISDN Follow the procedures below to configure a D Channel on the IMG. Configuring a D Channel 1. Right-click Signaling and select New ISDN. 2. Right-click ISDN D Channels and select New ISDN D Channel. The ISDN D Channel pane appears. 3. Complete the fields as required. Refer to the ISDN D Channel pane reference for details. Configuring ISDN Timers To change the default timer values on a D Channel, perform the following: 1. Right-click the ISDN entry and select New ISDN Timers. The ISDN Timers pane appears. 2. Change timer values as required. 522 Configuration Next Task Configuring ISDN Routing Cantata Technology - IMG 1010 Printable WebHelp 523 IMG WebHelp CAS CAS Quick Configuration Guide Topic Location: Configuration > Signaling > CAS Cantata Technology - IMG 1010 Printable WebHelp 524 Configuration Configuring CAS Topic Location: Configuration > Signaling > CAS Related Topic CAS Quick Configuration Guide Steps To setup the IMG for CAS Signaling perform the following: 1. Configure Media. See Configuring Media. NOTE: For DTMF reception configure an a-law or u-law Universal Receiver. For MFR1 or MFR2 reception you must configure the specific MFR1 or MFR2 receiver accordingly. If you try to perform MFR1 or MFR2 using a Universal Receiver, you will get a Call Trace indication of "No DSP of this type configured". 2. Create CAS Facilities See Creating a Facility Object. 3. Configure Spans See Configuring a T1 or E1 Bearer Span. Set Signaling Method to CAS and make any other changes to the default as required. 4. Configure CAS Signaling Variant See Channel Associated Signaling pane. a. Right click Cantata IMG EMS and select New Signaling Variants. b. Right click Signaling Variants and select New Signaling Variant. 525 IMG WebHelp The Signaling Variant pane appears. c. In the Variant Name field, enter a name for the variant. d. In the Variant Type field, select CAS. The Base Variant is automatically set to T1 or E1 depending on your system configuration. e. Make changes to defaults as required. Modify the settings in the following panes if required. Important Note: When configuring Inseize and Outseize Instructions, the order in which the instructions appear in the ClientView tree is the order in which they will be sent. Inpulsing Parameters. Inseize Instructions. Digit Mapping Outseize Instructions. Filter/Timers Variant Entries (PPL Tables, PPL Config Bytes) Cantata Technology - IMG 1010 Printable WebHelp 526 Configuration Importing a CAS Variant Topic Location: Configuration > Signaling > CAS The following CAS variants are automatically installed at /opt/cantata/common/congif/Imports when you install GCEMS: T1 Feature Group D - MFR1 (FGD_mfr1.xml) Feature Group B - MFR1 (FGB_mfr1.xml) E1 MFR2, Dialed Number, ANI, Category (E1_DNANICAT.xml) MFR2, Dialed Number, ANI, Category with Overlap (E1DNANICATOV.xml) You must import a variant into your configuration file before you can assign it to a Channel group. Steps 1. Right click Cantata IMG EMS and select New Signaling Variants. 2. Right click Signaling Variants and select New Signaling Variant. The Signaling Variant pane appears. 3. Click on Import Variant. Cantata Technology - IMG 1010 Printable WebHelp 527 IMG WebHelp Deleting a CAS Variant Topic Location: Configuration > Signaling > CAS 528 Configuration Cantata Technology - IMG 1010 Printable WebHelp 529 IMG WebHelp Variants CAS E1 R2 DN-ANI-CAT Topic Location: Configuration > Signaling > CAS You must import the variant into your configuration file in ClientView. See Importing a CAS Variant. Call Flows Inbound 530 Configuration Outbound 531 IMG WebHelp Default Configuration The following is the default configuration for the variant as installed. Variant ID: 1 Variant Name: E1_DNANICAT 532 Configuration Inpulse Parameters Stage 1: MFR2, compelled, R2 Inpulse Parameters Stage 2: MFR2, compelled, R2 Inpulse Parameters Stage 4: MFR2, fixed, 1 Digit Mapping Called Party: Use unconditional-Stage 1, String 1 Digit Mapping Calling Party: Use unconditional- Stage 2, String 1, ANI only Digit Mapping Calling Party Category: Use unconditional Stage 4, String 1 Inseize Call Control Instruction List: 1: GenInszAck(0,0) 2: RcvStageN(1,0) 3: RcvStageN(2,0) 4: GenCPEvent(PPL Event,3) 5: RcvStageN(4,0) 6: GenCPEvent(BWD R2 Signal,6) 7: ReportICWithAddrData(0,0) 8: WaitForHostCtrl(0,0) Outseize Call Control Instruction List 1: OutpulseStageN(1,0) 2: SendHostAck(0,0) 3: WaitForHostCtrlWithAnsSuper(0,0) Cantata Technology - IMG 1010 Printable WebHelp 533 IMG WebHelp E1 R2 DN-ANI-CAT Overlap Topic Location: Configuration > Signaling > CAS You must import the variant into your configuration file in ClientView. See Importing a CAS Variant. Call Flows Inbound Inpulse Parameters Stage 1: MFR2, compelled, R2 Inpulse Parameters Stage 2: MFR2, compelled, R2 Inpulse Parameters Stage 4: MFR2, fixed, 1 Outbound Default Configuration The following is the default configuration for the variant as installed. Variant ID: 2 Variant Name: E1_DNANICATov.xml Digit Mapping Calling Party: Use unconditional- Stage 2, String 1, CAT & ANI Digit Mapping Called Party: Use unconditional-Stage 1, String 1 Inseize Call Control Instruction List: 1: GenInszAck(0,0) 2: RcvStageN(1,0) 3: RcvStageN(2,0) 4: GenCPEvent(PPL Event,3) 5: RcvStageN(4,0) 6: GenCPEvent(BWD R2 Signal,6) 7: ReportICWithAddrData(0,0) 8: WaitForHostCtrl(0,0) Outseize Call Control Instruction List 1: OutpulseStageN(1,0) 2: SendHostAck(0,0) 3: WaitForHostCtrlWithAnsSuper(0,0) 534 Configuration Cantata Technology - IMG 1010 Printable WebHelp 535 IMG WebHelp T1 FGD Topic Location: Configuration > Signaling > CAS You must import the variant into your configuration file in ClientView. See Importing a CAS Variant. Call Flows Inbound Outbound Default Configuration The following is the default configuration for the variant as installed. 536 Configuration Variant ID: 1 Variant Name: FGD_mfr1 Inpulse Parameters Stage 1: MFR1, 2 strings, KP/ST & KP/ST Digit Mapping Called Party: Use unconditional-Stage 1, String 2 Digit Mapping Calling Party: Use unconditional- Stage1, String 1 Inseize Call Control Instruction List 1: GenInszAck(0,0) 2: RcvStageN(1,0) 3: ReportICWithAddrData(0,0) 4: WaitForHostCtrl(0,0) Outseize Call Control Instruction List 1: OutpulseStageN(1,0) 2: SendHostAck(0,0) 3: WaitForHostCtrlWithAnsSuper(0,0) Cantata Technology - IMG 1010 Printable WebHelp 537 IMG WebHelp T1 FGB Topic Location: Configuration > Signaling > CAS You must import the variant into your configuration file in ClientView. See Importing a CAS Variant. Call Flows Inbound Outbound Default Configuration The following is the default configuration for the variant as installed. Variant ID: 2 Variant Name: FGB_mfr1 538 Configuration Inpulse Parameters Stage 1: MFR1, 1 strings, KP/ST Digit Mapping Called Party: Use unconditional-Stage 1, String 1 Inseize Call Control Instruction List 1: GenInszAck(0,0) 2: RcvStageN(1,0) 3: ReportICWithAddrData(0,0) 4: WaitForHostCtrl(0,0) Outseize Call Control Instruction List 1: OutpulseStageN(1,0) 2: SendHostAck(0,0) 3: WaitForHostCtrlWithAnsSuper(0,0) Cantata Technology - IMG 1010 Printable WebHelp 539 IMG WebHelp Routing 540 Configuration Introduction An Overview of Routing Configuration Topic Location: Configuration > Routing > Introduction Configuring routing involves the following tasks. You must follow this order. NOTE: If you have a centralized routing model and do not need the IMG to perform routing lookups, you do not need to create Route Tables and Route Lists. 1. Configure Protocol-Specific Routing Configuring SIP Routing Configuring H.323 Routing Configuring SS7 Routing Configuring ISDN Routing 2. Create Channel Groups 3. Create Routing Tables 4. Create Route Lists 5. Configuring Digit Matching and Translation 6. Configuring Advanced Matching Parameters for Incoming Calls 7. Configuring Error Handling Related Topic ClientView Panes for Routing Cantata Technology - IMG 1010 Printable WebHelp 541 IMG WebHelp Configuring Routing Topic Location: Configuration > Routing > Introduction 1. Right-click Cantata IMG EMS and select New Routing Configuration. 2. Right-click Routing Configuration and 3. After selecting an object the ClientView pane for that object appears. Complete fields as required. Related Topics Creating a Channel Group Creating a Route Table Configuring Route Lists Configuring Digit Matching and Translation Configuring Error Handling Configuring SIP Routing 542 Configuration Configuring H.323 Routing Configuring SS7 CIC Routing Configuring ISDN Routing Cantata Technology - IMG 1010 Printable WebHelp 543 IMG WebHelp ClientView Panes Used for Routing Topic Location: Configuration > Routing > Introduction The following diagram shows the ClientView panes used to configure routing. Next Topic Creating an SS7 Channel Group Cantata Technology - IMG 1010 Printable WebHelp 544 Configuration Basic Routing ClientView Panes used to Configure Routing Tables and Route Lists Topic Location: Configuration > Routing > Basic Routing The following diagram shows the ClientView panes used to configure Routing Tables and Route Lists. Next Topic Configuring Error Handling Cantata Technology - IMG 1010 Printable WebHelp 545 IMG WebHelp Creating a Channel Group Topic Location: Configuration > Routing > Basic Routing 1. Right-click Routing Configuration and select New Channel Groups. 2. Right-click Channel Groups and select New Channel Group. The Channel Group pane appears. 3. In the Name field, enter a name for the channel group. 4. The ID field is automatically populated with the next available ID. You can change it if you want. 5. In the Channel Group Function field, select Incoming Trunks, Outgoing Trunks or Incoming/Outgoing Trunks 6. In the Signaling Type field, select the signaling type. 7. Select other fields as required. See the Channel Group pane reference for a description of each field NOTE: Do not select a Route Table in the Route Table field at this point. After you configure Route Tables, (see Creating Routing Tables) you come back to the Channel Group pane and associate a Route Table with the channel group. Cantata Technology - IMG 1010 Printable WebHelp 546 Configuration Overlap Signaling Topic Location: Configuration > Routing > Basic Routing By default, the IMG passes digits to the outbound side as they are received. If the outbound channel group does not support Overlap Signaling (SIP, H.323), you should enable overlap signaling on inbound channel groups. You enable Overlap Signaling in the Channel Group pane. When Overlap signaling is enabled, the IMG will collect address digits until a Termination Condition is met and then continue call processing. See below for protocol-specific information. Overlap is only applied to the inbound channel, even on an Incoming/Outgoing Trunk. SS7 When Overlap Signaling is enabled, the IMG will collect digits until one of the following termination conditions is met: Termination Digit Received (default = #) Inter SAM Timeout Minimum # of Digits Total Overlap Timeout Overlap needs to be enabled for inbound SS7 SAM digits only if the outgoing side is IP or SS7 ANSI. Example Call Flow 547 IMG WebHelp Euro ISDN (E1) When Overlap Signaling is enabled, the IMG will collect digits until one of the following termination conditions is met, and then send CALL PROCEEDING and attempt to route the call. Minimum # of Digits Received. - The value chosen should be equal to or greater than the maximum number of digits expected Total Overlap Timeout T302 Timer Expiry (Wait for INFO ISDN Timer) Reception of an INFO message with a Sending Complete Information Element Reception of a SETUP message with a Sending Complete IE Inter SAM Timeout The time the IMG will wait for an indication from its internal ISDN layer that an INFO message has been received. This value should be greater than 15 seconds. If the Inter SAM Timeout value is less than 15 seconds and expires before T302, the IMG will send CALL PROCEEDING and attempt to route the call with the digits it has at that point All of these except the T302 Timer are configured in the ISDN Group pane. The T302 Timer is not configurable and per specification is set at 15 seconds. If a call is received and T302 expires, Cause 28 will be sent to the network. Should you choose to make your Inter SAM Timeout smaller than 15 seconds you will attempt to process calls with most likely less than the number of digits you want. It is incumbent on the side that is sending you digits to send a Sending Complete IE to indicate the sending of digits is completed. Overlap needs to be enabled for inbound ISDN INFO digits only if the outgoing side is IP or SS7 ANSI. Cantata Technology - IMG 1010 Printable WebHelp 548 Configuration Configuring Routing Table Topic Location: Configuration > Routing > Basic Routing These tasks configure Route Tables for routing calls that come in on a specific channel group. You can route calls based on: Calling Number Channel Group Called Number Nature of Address (NOA) IMPORTANT NOTE: A Route Table is not sent to the IMG until you click Save Route Table. After you add or modify entries in a Route Table, click Save Route Table to send the table to the IMG. Task Summary 1. Create a Route Table 2. Add Entries to Route Table 3. Assign Route Table to Channel Group Creating a Route Table 1. Right-click on the Routing Configuration and select New Routing Tables. 2. Right-click on Routing Tables and select New Route Table. 549 IMG WebHelp The Route Table pane appears. 3. Enter a descriptive name in the Name field. 4. In the Routing Criteria Order field you specify the order in which the router searches the available criteria types. To change a location in the list, click the item you are moving and then click the Up or Down button. When finished ordering, click OK. The router searches from top to bottom and uses the first criteria type for which it finds a match. Specify the criteria types in the sequence that is most appropriate for the call processing. For example, if the primary routing criteria is dialed number and the next criteria type based on importance is Channel Group, position Dialed Number in the first position and Channel Group in the second position. This helps to ensure proper processing and improves routing performance. The IMG ignores any criteria type that you do not define. See the Route Table pane reference for more details. Adding an Entry to a Route Table 1. Right-click on the Route Table name and select Add Route Element. 550 Configuration The Route Element dialog box appears. See Route Element for details. 2. In the Route Action Type field, select an option. The remaining fields and options you have to make depends on this selection, as shown below. See the Route Table pane reference for more information. 3. Return to the Route Table pane and click Save Route Table. Options Field Entry ID Automatically populated. You can override this number by entering any unused number between 1-20. Enable Route Criteria Type Dialed Number Channel Group Originating Number Called NOA Calling NOA Router String Enter String Not Applicable Not Applicable In Channel Group Not Applicable Select Channel Group Not Applicable Criteria Values Not Applicable Not Applicable Select Value Route Action Type See Router String Wildcards Channel Group Treatment Table NOA Criteria Values Route List 551 IMG WebHelp Outgoing Channel Group Select the desired Channel Group. Only applies if Route Action Type is Channel Group. Outgoing Route List Select the desired Route List. Only applies if Route Action Type is Route List. To create a Route List, see Configuring Route Lists. Outgoing Treatment Table Select a Treatment Table. Only applies if Route Action Type is Treatment Table Treatment Select a Treatment. Only applies if Route Action Type is Treatment Table Associate Route Table with Channel Group 1. Return the list of Channel Groups you have created and select the desired Channel Group. 2. From the Route Table field, select the Route Table that you created above. Next Topic Configuring Route Lists Cantata Technology - IMG 1010 Printable WebHelp 552 Configuration Configuring Route Lists Topic Location: Configuration > Routing > Basic Routing Before you begin You must create your channel groups before you create your route lists. Do not select a Route Table in the Channel Group. You will return to the Channel Group at the end of this procedure to assign the Route Table. See Creating_an_SS7_Channel_Group or Creating_an_H_323_Channel_Group. IMPORTANT NOTE: A Route List is not sent to the IMG until you click Save Route Table. After you add or modify entries in a Route Table, click Save Route Table to send the table to the IMG. Steps 1. Right-click Routing Configuration and select New Route List. 2. Right-click Route List and select New Route List. 3. Enter a Name for the route list. 4. Select the Hunting Option. 5. The Route List ID is automatically populated with the next available number. Adding Channel Groups to a Route List 1. Right-click the Route List entry and select New Channel Group. The Channel Group (in Route List) pane appears. 2. Select the Channel Group to add to this Route List from the Group Name field. The router hunts through the channel groups in a sequence that is based on the hunting option that you specified in Step 4. 3. To add additional Channel Groups, repeat steps 6 and 7 for each. 553 IMG WebHelp See the Channel Group (Added to Route List) pane reference for details. Assigning Route Lists to a Route Table 1. From the list of Route Tables you have created, right-click the desired Route Table and select New Route List. 2. In the Routing Action Type field, select Route List. 3. In the Route List field, select this Route List. Assigning a Route Table to Channel Group Return to the Channel Group and select the Route Table from the drop-down list in the Route Table field. See Creating_an_SS7_Channel_Group or Creating_an_H_323_Channel_Group. Related Topic ClientView Panes for Routing Tables and Route Lists Cantata Technology - IMG 1010 Printable WebHelp 554 Configuration Configuring Time of Day Routing Topic Location: Configuration > Routing > Basic Routing Task Summary 1. Create a Time of Day Route Table 2. Add Entries to Route Table 3. Assign Route Table to Channel Group Creating a Time of Day Route Table 1. Right-click on the Routing Configuration and select New Time of Day Routing Tables. 2. Right-click on Time of Day Tables and select New Time of Day Table. The Time of Day Table pane appears. 3. Enter a descriptive name in the Name field. 4. In the Routing Criteria Order field you specify the order in which the router searches the available criteria types. To change a location in the list, click the item you are moving and then click the Up or Down button. When finished ordering, click OK. See the Time of Day Table pane reference for more information. Adding an Entry to a Time of Day Route Table 1. Right-click on the table name and select New Time of Day Entry. The Time of Day Entry pane appears. 2. In the Route Action Type field, select an option. The remaining fields and options you have to make depends on this selection. Complete fields as required. See the Time of Day Entry pane reference for more information. 555 IMG WebHelp Associate Route Table with Channel Group 1. Return to the Channel Groups you have created and select the desired Channel Group. 2. From the Route Table field, select the Time of Day Route Table that you created above. Cantata Technology - IMG 1010 Printable WebHelp 556 Configuration Importing Route Table Entries Topic Location: Configuration > Routing > Basic Routing If you have a route table requiring a large number of entries you can use any text editor to quickly create the entries and then import them into a Route table in ClientView. Summary of Steps 1. Create Route Table template in ClientView 2. Export File 3. Add Entries to File 4. Import File into Route Table Procedure Create Route Table Template in ClientView 1. Right-click Routing Configuration and select New Routing Tables. 2. Right-click Routing Tables and select New Route Table. 3. Name the table and change the default ID and Routing Criteria Order if desired. 557 IMG WebHelp 4. Commit the configuration. 5. Right-click on the table name in the object tree and select Add Route Entry. 6. Configure the entry to closely match the requirements of all of the entries you will be creating. When you export the file and use a text editor, you will be creating multiple versions of this entry and then changing fields, such as Router String, in each entry as required. 558 Configuration 7. Commit this configuration. Export File 1. Right-click the Route Table in the object tree and select Export To CSV. 2. In the Export to CSV dialog box, name the file and click OK. The file is saved to the opt/cantata/common/import_export folder. 559 IMG WebHelp Add Entries to File 1. Locate the *csv file and open it in any text editor. 2. Select the row containing the entry that you configured in ClientView and select File - Copy 3. Paste the number of rows for the entries you require. 4. Edit entries is required. Make sure you give each entry a unique Entry ID. 5. Save and close the file. Import File into Route Table 1. Return to ClientView 2. Right-click on the Route Table you are adding the entries to and select Import From CSV. 3. In the Import From CSV Dialog Box, browse to the file, select it, and click Open. 560 Configuration 4. In the next dialog box that appears, select Use Import File Entries. 5. In the next dialog box that appears, select the desired action if errors occur during the import process. 561 IMG WebHelp A dialog box will appear indicating the records were successfully imported. It will also indicate the location of the report file created during this import process. 6. Click OK to proceed. The Route Table will be populated with the entries you added to the file. Cantata Technology - IMG 1010 Printable WebHelp 562 Configuration 563 IMG WebHelp Route String Wildcards Topic Location: Configuration > Routing > Basic Routing You can use the following digits and wildcards in the Router String field of the Route Entry pane. Digit 0-9 X Description Digits 0 through 9 Indicates that the digit represented by X can be any single digit. The "X" wild card is allowed only when it is the last character or followed by another "X" wild card. The "X&" combination of wildcards is not supported in the route table but is allowed in the translation table. For example, the string 50886232XX will match 5088623200, 5088623290, or any other number that begins with 50886232. & Indicates that the digits represented by & can be one or more digits of any value. For example, the string 508& will match 5088623000, 5087783920, 50812, 508, or any other number that begins with 508. The & must be the last character in the string. Cantata Technology - IMG 1010 Printable WebHelp 564 Configuration Translation ClientView Panes Used for Translation Topic Location: Configuration > Routing > Translation The diagram below shows the ClientView panes used for configuring Digit Matching and Translation. Next Topic Configuring Advanced Number Matching Parameters for Incoming Calls Cantata Technology - IMG 1010 Printable WebHelp 565 IMG WebHelp Configuring Digit Matching and Translation Topic Location: Configuration > Routing > Translation This task configures digit matching and translation. This task is optional. You can translate a Dialed Number or an Originating Number. You can translate from a number to a null string. You cannot translate a null string to digits however. To translate on both Dialed Number and Originating Number, see Advanced Translation Features. Example Uses for Translation Translate a Dialed Number to a different Dialed Number Translate an Originating Number based on the Dialed Number Translate an Originating Number to a different Originating Number Creating a Translation Table 1. Right-click Routing Configuration and select New Incoming Translation Tables or New Outgoing Translation Tables. 2. Right-click Incoming Translation Tables or New Outgoing Translation Tables and select New Translation Table. The Translation Table pane appears. 3. Enter a descriptive name in the Translation Table Name field. Adding Entries to a Translation Table 1. Right-click the table name you just created and select New Translation Entry. 566 Configuration The Translation Entry pane appears. 2. Enter or select values for fields as required, as described below: Options Field Entry ID Automatically populated. Enable Type of Operation Translation Error Detection String to Match Dialed Number String Enter a digit string. Dialed Number Translation Specify the translation mask that describes how the IMG translates a dialed number to a new value. This field can be left empty to translate to a null string. The IMG assigns the error code (indicated in the Error Code field) to a digit string that matches the matching criteria and performs the appropriate treatment for the call based on the error condition. Originating Number See Digit Translation Wildcards. Originating Number Translation Specify the translation mask that describes how the IMG translates an originating number to a new value. This field can be left empty to translate to a null string. See Digit Translation Wildcards. Error Code If the Type of Operation is Errror Detection, select the error condition that the IMG assigns to a digit string that matches the matching criteria. The IMG performs the appropriate treatment for the call based on the cause code it assigns. Next Topic ClientView Panes used for Translation Related Topic 567 IMG WebHelp Translation Errors Cantata Technology - IMG 1010 Printable WebHelp 568 Configuration Advanced Translation Features Topic Location: Configuration > Routing > Translation These features are configurable for both the incoming and outgoing translation tables. ANI and DNIS Translation on Same Call To translate on both Dialed Number and Originating Number, configure the following fields in the Translation Entry pane: Type of Operation: Translation String to Match: Dialed Number String: Dialed Number Translation: Originating Number Translation: Re-run Option: Originating Number Appending Info Digits to ANI or DNIS This feature is valid for SS7 ANSI and SIP-T only. Info Digits are included in the Originating Line Info Parameter (OLIP) from SS7 or in the ISUP MIME body included in a SIP message when SIP-T is enabled. To append the INFO Digits to the after translation, configure the following fields in the Translation Entry pane: String Second String for Translation Dialed Number Translation Second String Example String: & Dialed Number Translation: &jj Second String for Translation: Info Digits Second String: jj Translate on Incoming Channel Group To add a prefix to an incoming number based on the incoming channel group, use the Match Channel Group as Well field in the Translation Entry pane. Only numbers that also are from the indicated Channel Group will match. This allows you 569 IMG WebHelp to have different matching criteria entries for multiple gateways without creating separate Translation tables. Not Used A list of all the Channel Groups configured as Outgoing or Incoming/Outgoing (for Outgoing Translation Table) A list of all the Channel Groups configured as Incoming or Incoming/Outgoing (for Incoming Translation Table) Cantata Technology - IMG 1010 Printable WebHelp 570 Configuration Translation Configuration Example Topic Location: Configuration > Routing > Translation Scenario You want to translate all digit stings that begin with 603 to 011603. Accessing the Translation Entry Pane Cantata IMG EMS -> New Routing Configuration -> New Incoming Translation Tables -> New Incoming Translation Table -> New Incoming Translation Table Entry Filling Out Fields You would fill out the fields in the pane as shown below to configure the scenario described. Field: Type of Operation Select: Translation Field: String to Match Select: Dialed Number Field: String Enter: 603& Any digit string beginning with 603 will be a match. 571 IMG WebHelp Field: Dialed # Translation Enter: 011603& To see how the IMG would process digits based on this configuration, see Example of Translation Process. Next Topic Creating a Route Table Cantata Technology - IMG 1010 Printable WebHelp 572 Configuration Configuring Advanced Number Matching Parameters for Incoming Calls Topic Location: Configuration > Routing > Translation For incoming channels, you can configure advanced parameters for digit matching on the following: Dialed Number Originating Number By default, no translation is performed on any of the advanced parameters. Dialed Number Matching For Dialed Number matching, the following parameters are supported: nature of address Internal Network Number Indicator (INN) Steps numbering plan 1. Right-click the desired Incoming Translation table and select New Advanced Dialed Number Parameters. 2. To include any of the supported parameters in digit matching, select the appropriate value for each field. Originating Number Matching For Originating Number matching, the following parameters are supported: nature of address calling party category numbering plan number incomplete indicator screening indicator presentation indicator Steps 1. Right-click the desired Incoming Translation table and select New Advanced Dialed Number Parameters. 2. To include any of the supported parameters in digit matching, select the appropriate value for each field. 573 IMG WebHelp Next Topic Translation Configuration Example Cantata Technology - IMG 1010 Printable WebHelp 574 Configuration Digit Translation Wildcards Topic Location: Configuration > Routing > Translation You can use the following wildcards in the String field in the Translation Entry pane. Wildcard Description P The digits represented by a P in the match string can be either 0 or 1. For example, the string P5088623000 will match either 05088623000 or 15088623000. N The digits represented by an N in the match string can be any number between 2 and 9. For example, the string 508NN2N000 will match 5088623000, 5087724000, or any number that begins with 508, followed by two digits that can be any number between 2 and 9, followed by the number 2, followed by a single digit between 2 and 9 and ending with 000. X, Y, Z The digits represented by an X, Y, or Z in the match string can be any digit. These wildcards are interchangeable; however, X is generally preferred unless you are specifying various parts of a number. For example, you can specify the string XXXYYY1234 to indicate that the first three digits can be any value, the next three digits can be any value and the remaining digits must be 1234. This is useful for translation purposes. For example, if you use the match string XXXYYY1234 and the translation string YYY&, the DPE strips the first three digits (XXX) from the digit string. & The ampersand (&) specifies that all remaining digits can have any value. For example, the match string 508& will match any digit string that begins with 508 such as 5088623000, 5087783000, or 5081234. Generally you should always place the & at the end of the match string to indicate that all remaining digits can be of any value. However, the IMG supports match strings that include one character following an & as in 508&#. This enables you to strip a terminating digit or character. Supported Digits and Wildcards: 0 - 9, #, *, N, P, X, Y, Z, & In addition, the IMG supports the use of J, K and L wildcards in the same manner that it uses the X, Y and Z characters in the String field in the Operations group box. NOTE: The pound (#) character is generally used to terminate a digit string and the asterisk (*) character is generally used to trigger a service, such as *70 to disable call waiting. Internally, the IMG maps the asterisk (*) character to a value of hexadecimal E and the pound (#) character to hexadecimal F. This can result in improper digit processing if your digit strings contain hexadecimal E or F. 575 IMG WebHelp Cantata Technology - IMG 1010 Printable WebHelp 576 Configuration Translation Errors Topic Location: Configuration > Routing > Translation The following errors may be reported in the case of a translation/routing failure. "DPE response: Internal Error xx" 1 - Transfer Input B String Failure 2 - Transfer Input C String Failure 3 - Transfer Input D String Failure 4 - Transfer Input O String Failure 5 - B String Manipulation Failure 6 - C String Manipulation Failure 7 - D String Manipulation Failure 8 - O String Manipulation Failure 9 - Process Command Failure 10 - Transfer Output B String Failure 11 - Transfer Output C String Failure 12 - Transfer Output D String Failure 13 - Transfer Output O String Failure 14 - Transfer Command Failure 15 - Invalid Translation Table ID Cantata Technology - IMG 1010 Printable WebHelp 577 IMG WebHelp Treatments ClientView Panes for Configuring Error Handling Topic Location: Configuration > Routing > Treatments There are two options for responding to an error condition (Cause Code) in the IMG. Release with Cause Play Treatment The diagram below shows the ClientView panes used for configuring Error Handling. Only fields relevant to this topic are shown for each pane. Cantata Technology - IMG 1010 Printable WebHelp 578 Configuration Configuring Error Handling Topic Location: Configuration > Routing > Treatments There are two options for responding to an error condition (Cause Code) in the IMG. Release with Cause Play Treatment Related Topics An Overview of Error Handling Default Cause Code Values Default Treatment Table ClientView Panes for Configuring Error Handling There are two options for responding to an error condition (Cause Code) in the IMG. Release with Cause Play Treatment The diagram below shows the ClientView panes used for configuring Error Handling. Only fields relevant to this topic are shown for each pane. 579 IMG WebHelp Next Topic Configure a Channel to Release with Cause Cantata Technology - IMG 1010 Printable WebHelp 580 Configuration Configuring a Channel Group to Play a Treatment Topic Location: Configuration > Routing > Treatments Prerequisites Before you start to configure Treatments, you must download the default Treatment Table using an NFS Server. You can also add custom announcements and treatments. Steps To configure a channel group to Release with Cause, perform the following steps: 1. Configure Cause Code Table 2. Add Cause Code Table Entry 3. Assign Cause Code Table to Channel Group Creating a Cause Code Mapping Table Create a cause code mapping table: 1. Right-click Routing Configuration and select New Cause Code Tables. 2. Right-click Cause Code Table and select New Cause Code Table. The Route Table pane appears. 3. Enter a Name for the table. 4. The ID is automatically populated with the next available table number. 5. In the Routing Criteria Order field, order the criteria as required and click OK. Adding Entries to a Cause Code Mapping Table Create a table entry that maps a Cause Code to a Treatment. 1. Right-click the Cause Code Table you just created and select New Route Entry. The Route Table Entry pane appears. 2. The Entry ID field is automatically populated. 3. The Route Criteria Type field is automatically populated with Cause Code. 4. From the drop-down list in the Criteria Values field, select a Cause Code (incoming Cause Code to match). 5. From the drop-down list in the Route Action field, select Treatment Table. 6. From the drop-down list in the Outgoing Treatment Table field, select a Treatment Table. 581 IMG WebHelp 7. From the Outgoing Treatment field, select a treatment from the drop-down list. Assigning a Cause Code Table to Channel Group 1. Go to the pane for the channel group you are configuring. 2. In the Incoming Treatment field, select Play Treatment 3. In the Cause Code Mapping Table field, select the Cause Code Table you created. 4. In the Outgoing Treatment field, select Play Treatment. Cantata Technology - IMG 1010 Printable WebHelp 582 Configuration Configuring a Channel to Release With Cause Topic Location: Configuration > Routing > Treatments Steps To configure a channel to release with Cause, perform the following steps: 1. Configure Cause Code Table 2. Add Cause Code Table Entry 3. Assign Cause Code Table to Channel Group Configuring a Cause Code Mapping Table Complete the following steps to create a cause code mapping table: 1. Right-click Routing Configuration and select New Cause Code Tables. 2. Right-click Cause Code Table and select New Cause Code Table. The Route Table pane appears. 3. Enter a Name for the table. 4. The ID is automatically populated with the next available table number. 5. The Routing Criteria Order field is automatically populated with Cause Code. See the Route Table pane reference for more information. Adding Entries to a Cause Code Mapping Table Complete the following steps to add entries to a cause code mapping table: 1. Right-click the Cause Code Table you just created and select New Route Entry. The Route Entry pane appears. 2. The ID field is automatically populated. 3. The Route Criteria Type field is automatically populated with Cause Code. 4. From the drop-down list in the Criteria Values field, select a Cause Code (incoming Cause Code to match). 5. From the drop-down list in the Router Action field, select Cause Code. 6. From the drop-down list in the Outgoing Cause Code field, select a Cause Code (outgoing Cause Code to send). See the Route Entry pane reference for more information. Assign Cause Code Table to Channel Group 1. Go to the pane for the channel group you are configuring. 2. In the Incoming Treatment field, select Release w/Cause 583 IMG WebHelp 3. In the Cause Code Mapping Table field, select the Cause Code Table you created. 4. In the Outgoing Treatment field, select Release w/Cause. Next Topic Configuring a Channel to Play Treatment Cantata Technology - IMG 1010 Printable WebHelp 584 Configuration Adding Custom Announcements Topic Location: Configuration > Routing > Treatments You can download custom treatments to the NFS server and add them to the Treatments Table provided with the IMG System Software. You can then assign the treatments to channel groups in a Route Table. Before You Begin Before you start this procedure, record your new treatments and download them to the NFS server(s). Task Summary 1. Create a VIF File 2. Import Default Entries into the VIF File 3. Add Entries to the VIF Creating a VIF File 1. Right-click Routing Configuration and select New Vocabulary Index Files. 2. Right-click Vocabulary Index Files and select New Vocabulary Index File. The Vocabulary Index File pane appears. The Vocabulary Index File ID and Vocabulary Index Filename fields are 585 IMG WebHelp automatically populated with the default file information. See the Vocabulary Index File pane reference for field details. Importing Default Entries into the VIF File 1. Right-click Vocabulary Index File and select Import Vocabulary Index Entry File. This populates the VIF File with the default entries. Adding Entries to the VIF 1. Right-click Vocabulary Index File 1 and select New Vocabulary Index Entry. The VIF Entry pane appears. 2. Enter the values as required for each new announcement. See the Vocabulary Index Entry pane reference for field details. Next Topic Adding Custom Treatments Cantata Technology - IMG 1010 Printable WebHelp 586 Configuration Adding Custom Treatments Topic Location: Configuration > Routing > Treatments Before You Begin See Adding Custom Announcements Task Summary 1. Create a Treatment Table 2. Add Entries to a Treatment Table 3. Add Phrases to a Treatment Table Entry 4. Assign Treatments to Channel Groups or Route Lists Creating a Treatment Table 1. Right-click Routing Configuration and select New Treatment Tables. 2. Right-click Treatment Tables and select New Treatment Table. The Treatment Table pane appears. The Treatment Table ID field is automatically populated with the next number in sequence. 587 IMG WebHelp 3. Enter a descriptive name for the table in the Treatment Table Name field. See the Treatment Table pane reference for field details. Adding Entries to a Treatment Table 1. Right-click the Treatment Table and select New Treatment Table Entry. The Treatment Table Entry pane appears. The Treatment Entry ID field is automatically populated with the next available number in sequence. 2. Enter values in the other fields as required. See the Treatment Entry pane reference for field descriptions. Adding Phrases to a Treatment Table Entry You can string multiple phrase to create an entry. A phrase can consist of announcement, tones, and originating or dialed digits. 1. Right-click on the entry and select New Treatment Phrase. The Treatment Phrase pane appears. The Partial Phrase Entry field is automatically populated with the next available number. 2. Select either Announcement, Tone, Originating Digits, or Dialed Digits from the Treatment Phrase Type field. 588 Configuration 3. Select the desired option from the Partial Phrase ID field. If the Treatment Phrase Type is Announcement, this drop-down list is populated with all of the announcements available. If the Treatment Phrase Type is Tone, this drop-down list is populated with all of the tones available. If the Treatment Phrase Type is Originating Digits or Dialed Digits, this field does not apply. 4. If the Treatment Phrase Type is Tone, select the desired value from the dropdown list in the Cycles to Play Tone field. This field does not apply for any other Treatment Phrase Types. See the Treatment Phrase pane reference for field descriptions. 5. Assign Treatments to Channel Groups or Route Lists. See the following: Configuring SS7 Routing Configuring H.323 Routing Configuring Route Lists Cantata Technology - IMG 1010 Printable WebHelp 589 IMG WebHelp Configuring Pre-call Announcements Topic Location: Configuration > Routing > Treatments Pre-requisite Configure Media and NFS with the required announcement file(s). Configuration Announcements based on destination number 1. Configure a service route table having entries with criteria as dialed number and required treatments. Right-click Routing Configuration and select New Service Routing Tables. Right-click Service Route Tables and select New Service Route Table 1. Configure a translation entry selecting the service route table from step 2. 2. In the incoming channel group select the translation table from step 3. Announcements based on time 1. Configure a service TOD table having entries with required treatments 2. Configure a service route table having entries routing to service TOD table from step 2. 3. Configure a translation entry selecting the service route table from step 3. 4. In the incoming channel group select the translation table from step 4. Cantata Technology - IMG 1010 Printable WebHelp 590 Configuration Customizing SIP-to-SS7 ISUP Cause Codes Topic Location: Configuration > Routing > Treatments To change Cause Code Mapping from the RFC 3398 default, 1. Create a Cause Code Table. 2. Add an entry to the Cause Code Table. a. In the Criteria Values field, select the original Cause Code for which you want to change the mapping. b. In the Outgoing Cause Code field, select the value to which you want the original value mapped. c. Add other entries to the Cause Code Table as desired. 3. Assign the Cause Code Table to a Channel Group. Cantata Technology - IMG 1010 Printable WebHelp 591 IMG WebHelp Default Cause Code Values Topic Location: Configuration > Routing > Treatments The following tables list the Cause Codes supported by the IMG, along with the Treatment that the IMG will perform in response to each. These Cause Codes appear in the following drop-down lists in the Cause Code Table Entry pane: Criteria Values Outgoing Cause Code See Default Treatment Table Cause Code Value Description Default Treatment ID 000 Reserved 5 001 Unallocated 7 002 No Route to Specified Transit Network 5 003 No Route to Destination 5 004 Send Special Information Tone 5 005 Mis-dialed Trunk Prefix 5 006 Channel Unacceptable 5 007 Call Awarded 5 008 Preemption 5 009 Preemption Circuit Reserved for Reuse 5 010-015 Unknown Cause Code - 016 Normal Call Clearing 5 017 User Busy - 018 No User Responding 5 019 No Answer from User 5 020 Subscriber Absent 5 021 Call Rejected 5 022 Number Changed 5 Unknown Cause Code - 023-025 592 Configuration 026 Non-Selected User Clearing 5 027 Destination Out of Order 5 028 Invalid Number Format 5 029 Facility Rejected 5 030 Response to STATUS ENQUIRY 5 031 Normal, Unspecified 5 Unknown Cause Code - No Circuit/Channel Available 1 035-037 Unknown Cause Code - 038 Network Out of Order 5 039 Frame Mode Connection Out of Service 5 040 Frame Mode Connection Operational 5 041 Temporary Failure 5 042 Switching Equipment Congestion 1 043 Access Information Discarded 5 044 Requested Circuit/Channel Unavailable 5 045 Unknown Cause Code - 046 Precedence Call Blocked 5 047 Resource Unavailable, unspecified 5 048 Unknown Cause Code - 049 Quality of Service Unavailable 5 050 Requested Facility Not Subscribed 5 Unknown Cause Code - 053 Outgoing Calls Barred Within CUG 5 054 Unknown Cause Code - 055 Incoming Calls Barred Within CUG 5 056 Unknown Cause Code - 057 Bearer Capability Not Authorized 5 058 Bearer Capability Not Available 5 Unknown Cause Code - Inconsistency b/w access info and sub 5 032, 033 034 051, 052 059-061 062 593 IMG WebHelp class 063 Service of Option Not Available, unspecified 5 064 Unknown Cause Code - 065 Bearer Capability Not Implemented 5 066 Channel Type Not Implemented 5 Unknown Cause Code - 069 Requested Facility Not Implemented 5 070 Restricted Digital Info Bearer Only 5 Unknown Cause Code - 079 Service or Option Not Implemented, unspecified 5 080 Unknown Cause Code - 081 Invalid Call Reference Value 5 082 Identified Channel Does Not Exist 5 083 Call Identity Does Not Exist 5 084 Call Identity In Use 5 085 No Call Suspended 5 086 Call Identity Has Been Cleared 5 087 User Not Member of CUG 5 088 Incompatible Destination 5 089 Unknown Cause Code - 090 Non existent CUG 5 091 Invalid Transit network Selection 5 Unknown Cause Code - 095 Invalid Message, unspecified 5 096 Mandatory Information Element Missing 5 097 Message Type Non existent or Not Implemented 5 098 Message Not Compatible with Call State 5 099 Information Element/Parameter Non existent 5 100 Invalid Information Element Contents 5 067, 068 071-078 092-094 594 Configuration 101 Message Not Compatible with Call State 5 102 Recovery on Timer Expired 5 103 Parameter Non existent or Not Implemented 5 Unknown Cause Code - 110 Message with Unrecognized Parameter 5 111 Protocol Error, unspecified 104-109 112+ Unknown Cause Code - Cantata Technology - IMG 1010 Printable WebHelp 595 IMG WebHelp Default Treatment Table Topic Location: Configuration > Routing > Treatments The following table shows the treatments in the default Treatment Table on the IMG. You cannot modify this table. These treatments are played in response to Cause Codes if so configured. These Treatments appear in the Treatment drop-down list in the following ClientView panes, if the Route Action Type is Play Treatment: Cause Code Table Entry Route Table Entry See Default Cause Code Values Treatment ID Type Treatment 0000 Announcement We're sorry your call could not be completed as dialed. Please check the number and dial again 0001 Announcement We're sorry all circuits are busy now. Please hang up and try again latter 0002 Announcement We're sorry you must dial a 1 before calling numbers outside of your calling area 0003 Announcement We're sorry it's not necessary to dial a 1 or 0 when calling numbers within your calling area 0004 Tone Reorder-Carrier 0005 Tone No Circuit-Carrier 0007 Announcement We're sorry the number you have dialed is no longer in service. Please check the number and dial again 0020 Tone Reorder 0021 Announcement We're sorry, you call did not go through. Please check the number and dial again Cantata Technology - IMG 1010 Printable WebHelp 596 Configuration SIP Routing Configuring SIP Routing Topic Location: Configuration > Routing > SIP Routing Creating a SIP Channel Group 1. Right-click Cantata IMG EMS and select New Routing Configuration. 2. Right-click Routing Configuration and select New Channel Groups. 3. Right-click Channel Groups and select New Channel Group. The Channel Group pane appears. 4. In the Signaling Type field select SIP. 5. Select other fields as required. See the Channel Group pane GUI Reference for details. Associating a SIP Gateway with the SIP Channel Group 1. Right-click the channel entry and select New IP Network Element. The IP Network Element pane appears. 2. In the IP Network Element field, select the SIP Gateway associated with this channel group. 597 IMG WebHelp Configuring SIP Proxy Handling 1. Create a SIP Profile and configure Proxy Handling fields as required. 2. Assign the SIP Profile to the gateway in the External Gateway pane. Configuring a SIP Redirect Server 1. Create a SIP Profile and configure Proxy Handling fields as required. 2. Assign the SIP Profile to the gateway in the External Gateway pane. Cantata Technology - IMG 1010 Printable WebHelp 598 Configuration Configuring an External SIP Gateway Topic Location: Configuration > Routing > SIP Routing Use this pane to configure External SIP Gateways from which the IMG may receive calls. To configure a group of gateways, use the Gateway Mask field to validate a range of IP addresses. 1. Right-click External Elements and select New External Gateways. 2. Right-click External Gateways and select New External Gateway. The External Gateway pane appears. 3. In the Gateway Signaling Protocol field select SIP. 4. In the Gateway IP Address, enter the IP address of the gateway. 5. In the Gateway Transport Type field, leave the default (UDP) or select TCP. NOTE: Must match Default Transport Type in the SIP Signaling configuration. 6. Change the Gateway Remote Port if required. Default = 5060. 7. If Gateway Registration is required, change the Gateway Registration field to Yes. Default = No. 8. To validate a range of IP addresses for multiple gateways, use the Gateway Mask field. 9. Use the Trusted and Privacy fields to configure SIP Privacy. See SIP Privacy for more information. See the External Gateway pane reference for details. Cantata Technology - IMG 1010 Printable WebHelp 599 IMG WebHelp SIP Call Flows Topic Location: Configuration > Routing > SIP Routing Basic SIP Call Flow Basic SS7 ISUP to SIP Call_Flow Basic SIP to SS7 ISUP Call Flow Basic SIP to ISDN Call Flow Basic ISDN to SIP Call Flow SIP Bridging using SIP-T Basic SIP Call Flow Basic SS7 ISUP to SIP Call Flow 600 Configuration Basic SIP to SS7 ISUP Call Flow Basic ISDN to SIP Call Flow 601 IMG WebHelp Basic SIP to ISDN Call Flow 602 Configuration SIP Bridging using SIP-T Cantata Technology - IMG 1010 Printable WebHelp 603 IMG WebHelp H.323 Routing Configuring H.323 Routing Topic Location: Configuration > Routing > H.323 Routing Task Summary 1. Create an H.323 Channel Group 2. Assigning_a_Channel_Group_to_an_H.323_Endpoint Creating an H.323 Channel Group 1. Right-click Routing Configuration and select New Channel Groups. You can skip this step if you already created an SS7 Channel Group. 2. Right-click Channel Groups and select New Channel Group. The Channel Group pane appears. 3. Enter the Name and ID of this channel group. 4. In the Channel Group Function field, select Incoming Trunks, Outgoing Trunks or Incoming/Outgoing Trunks. 5. In the Signaling Type field, select H.323. 6. Select an Incoming IP Profile and an Outgoing IP Profile for this channel group. 7. Select other fields as required. See the Channel Group GUI Reference for detailed field descriptions. NOTE: Do not select a Route Table in the Route Table field at this point. After you configure Route Tables, (see Creating Routing Tables) you come back to the Channel Group pane and associate a Route Table with the channel group. Assigning a Channel Group to an IP Network Element You can assign the H.323 Channel Group to a specific H.323 endpoint. Calls routed to or from this endpoint will use the incoming or outgoing configuration defined by the Channel Group. 1. Right-click the H.323 Channel Group and select New IP Network Element. The IP Network Element pane appears. 2. From the H.323 Network Element field, select the desired endpoint from the drop-down list, which is populated with all configured IMGs, external gateways, and external gatekeepers. See the IP Network Elements GUI reference for more information. Cantata Technology - IMG 1010 Printable WebHelp 604 Configuration Configuring an External H.323 Gateway Topic Location: Configuration > Routing > H.323 Routing Use this pane to configure External H.323 Gateways from which the IMG may receive calls. To configure a group of gateways, use the Gateway Mask field to validate a range of IP addresses. 1. Right-click External Elements and select New External Gateways. 2. Right-click External Gateways and select New External Gateway. The External Gateway pane appears. 3. In the Gateway Signaling Protocol field select H.323. 4. In the Gateway IP Address, enter the IP address of the gateway. 5. In the Gateway Transport Type field, leave the default (UDP) or select TCP. 6. Change the Gateway Remote Port if required. Default = 5060. 7. If Gateway Registration is required, change the Gateway Registration field to Yes. Default = No. 8. To validate a range of IP addresses for multiple gateways, use the Gateway Mask field. See the External Gateway pane reference for details. Cantata Technology - IMG 1010 Printable WebHelp 605 IMG WebHelp Adding an External H.323 Gatekeeper Topic Location: Configuration > Routing > H.323 Routing You can add up to 1024 external gatekeepers to which the H.323-configured IMGs will communicate. For each gatekeeper you can also configure up to six alternative gatekeepers. Steps 1. Right-click Cantata IMG EMS and select New External Network Elements. 2. Right-click External Network Elements and select New External Gatekeepers. 3. Right-click External Gatekeepers and select New External Gatekeeper. The External Gatekeeper pane appears. See the External GateKeeper pane reference for details. 4. Enter the Gatekeeper Name and Gatekeeper IP Address. If you don't know the IP Address you can enter 224.0.1.41 to broadcast for an available gatekeeper. 5. Enable Gatekeeper Auto Discovery if desired. The IMG will automatically send GRQ - Gatekeeper Request and RRQ - Registration Request to the external gatekeeper. You can also Discover and Register with a gatekeeper manually using the buttons on the H.323 Signaling pane. 6. To add alternate gatekeepers (up to 6 per primary gatekeeper), right click the External Gatekeeper entry and select New Alternate Gatekeepers. The Alternate Gatekeeper pane appears. 7. Enter the Gatekeeper ID, Gatekeeper Name and Gatekeeper IP Address. See the Alternate Gatekeeper pane reference for details. 606 Configuration Related Topics Configuring H.323 Signaling Cantata Technology - IMG 1010 Printable WebHelp 607 IMG WebHelp SS7 Routing Configuring SS7 CICs Topic Location: Configuration > Routing > SS7 Routing Task Summary Configuring SS7 routing involves the following tasks: 1. Configure an SS7 Channel Group 2. Configure an ISUP Group 3. Configure TMR-USI Override (if required) 4. Configure BCI Override (if required) 5. Configure Location Override (if required) 6. Assign Circuits (CICs) to the ISUP Group 7. Configure SS7 Parameter Filters ClientView Tree The following graphic shows the tree of ClientView panes used for configuring SS7 routing. Configuring an SS7 Channel Group 1. Right-click Routing Configuration and select New Channel Groups. 2. Right-click Channel Groups and select New Channel Group. The Channel Group pane appears. 3. In the Name field, enter a name for the channel group. 608 Configuration 4. The ID field is automatically populated with the next available ID. You can change it if you want. 5. In the Channel Group Function field, select Incoming Trunks, Outgoing Trunks or Incoming/Outgoing Trunks 6. In the Signaling Type field, select SS7. 7. Select other fields as required. See the Channel Group GUI Reference for a description of each field NOTE: Do not select a Route Table in the Route Table field at this point. After you configure Route Tables, (see Creating Routing Tables) you come back to the Channel Group pane and associate a Route Table with the channel group. Configuring an ISUP Group 1. To add ISUP groups to the SS7 Channel Group, right-click the SS7 Channel Group you created and select New ISUP Group. The ISUP Group pane appears. 2. Ensure that the OPC-DPC that defaults in is correct. These values come from the Stack ID and the associated SS7 Route. You associate the stack with the ISUP Group here. 3. Select entries in all fields as required. See the ISUP Group GUI Reference for a description of each field. Configuring FCI Override 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. To configure the IMG to override various Forward Call Indicators parameters with specified values: 1. Right-click the SS7 ISUP Group entry and select New FCI Override. The FCI Override pane appears. 2. Enable FCI Override by selecting Override in the FCI Override field. 3. Select the desired override value for each parameter. See the FCI Override pane reference for details. Configuring TMR-USI Override 609 IMG WebHelp To set Transmission Medium Requirements (TMR) and User Service Indicator (USI) parameters: 1. Right-click the SS7 ISUP Group entry and select New TMR_USI Override. The TMR-USI Override pane appears. 2. Make selections in each field as required. See the TMR-USI Override pane for details. Configuring Location Override 1. Right-click the SS7 ISUP Group entry and select New Location Override. The Location Override pane appears. 2. In the Location Override field, select Override. 3. If required, change defaults in the Location and Coding Standard fields. See the Location Override pane for details. Assigning SS7 Circuits to an ISUP Group (CICs) 1. Right-click the ISUP Group you created and select New Circuits. The Circuit pane appears. 2. In the IMG Name field, select the physical IMG. 3. In the IMG Interface field, select Bearer or Signaling. 4. In the Start Interface Offset field, enter a value from 0-27 to define where the CICs are going out of the IMG. Make sure this value matches the Interface ID defined for the physical spans. That is, make sure bearer CICs go out over bearer spans and signaling CICs go out over signaling spans. 5. In the Trunk Type field, select T1 or E1. Make sure this matches what you defined for physical spans). 6. In the Start Channel field, select the first channel where the CICs will get assigned. 7. In the Start CIC field, enter the first CIC in the group. 8. In the CIC Count field, enter the total number of CICs in the group. See the Circuit Group pane reference for a description of each field. 610 Configuration Configuring SS7 Parameter Filters This pane indicates which SS7 parameters are passed on to the outbound side and which are not. By default, all parameters are passed except for Transit Network Select. 1. Right-click the ISUP Group that you created and select New SS7 Parameter Filter. The SS7 Parameter Filter pane appears. 2. If you want to change the default for any of the parameters, select the desired setting from its drop-down list. Related Topic Provisioning CICs Next Topic Configuring H.323 Routing Cantata Technology - IMG 1010 Printable WebHelp 611 IMG WebHelp ISDN Routing Configuring ISDN Routing Topic Location: Configuration > Routing > ISDN Routing Summary of Tasks 1. Create an ISDN Channel Group 2. Define an ISDN Channel Group 3. Configure Bearer Capabilities Override 4. Assign B-Channels (Circuits) to be controlled by the D Channel Creating an ISDN Channel Group 1. Under Cantata IMG EMS, right-click Routing Configuration and select New Routing Configuration. 2. Right-click Routing Configuration and select New Channel Groups. 3. Right-click Channel Groups and select New Channel Group. The Channel Group pane appears. 4. In the Signaling Type field select ISDN. 5. Select other fields as required. See the Channel Group pane reference for details. Defining an ISDN Channel Group 1. Right-click the ISDN channel entry and select New ISDN Group. 612 Configuration The ISDN Group pane appears. 2. Select values as required. See the ISDN Group pane reference for details. Configuring Bearer Capabilities Override To set Transmission Medium Requirements (TMR) and User Service Indicator (USI) parameters: 1. Right-click the ISDN Group entry and select Bearer Capabilities Override. The Bearer Capabilities Override pane appears. 2. Make selections in each field as required. See the Bearer Capabilities Override pane for details. Assigning B-Channels (Circuits) to be controlled by the D Channel 1. Right-click the ISDN group entry and select New ISDN Circuits. The ISDN Circuits pane appears. 2. Fill in fields as required. See the ISDN Circuits pane GUI Reference for details. Cantata Technology - IMG 1010 Printable WebHelp 613 IMG WebHelp NFAS Examples Topic Location: Configuration > Routing > ISDN Routing Both these examples do not affect the already configured channels running calls. Both these scenarios show a single Channel Group called ISDN_Inbound. You could also have separate Channels Groups with the 2 scenarios mentioned with the same results. Example 1: Multiple ISDN Circuits within the same ISDN Group Step #1: Create 2 spans (Span 0, Span 1). The D-Channel is on span 0 and the first facility span is 1. Step #2: Add another Facility (Span 2) to the ISDN Group. Example 2: Multiple ISDN Groups Step 1: Configure 2 spans (Span 0, Span 1). The D-Channel is on span 0 and the first facility span is 1. 614 Configuration Step 2: Add another Facility (span 2) to the new ISDN Group. This allows you to set attributes such as Bearer Capabilities and Network Type differently from the other ISDN Group. Cantata Technology - IMG 1010 Printable WebHelp 615 IMG WebHelp ISDN Call Flows Topic Location: Configuration > Routing > ISDN Routing Basic ISDN to SIP Call Flow Basic SIP to ISDN Call Flow Basic ISDN to H.323 Basic ISDN to SIP Call Flow Basic SIP to ISDN Call Flow 616 Configuration Basic ISDN to H.323 Cantata Technology - IMG 1010 Printable WebHelp 617 IMG WebHelp RADIUS Configuring RADIUS Topic Location: Configuration > RADIUS You can configure a total of 256 RADIUS servers. Before You Begin Make sure you have moved the Cantata RADIUS dictionary files (dictionary and dictionary.cantata) to your RADIUS installation folder. The files are located in the following directory: /opt/cantata/common/Radius Task Summary 1. Configuring a RADIUS Authentication Server 2. Configuring a RADIUS Accounting Server 3. Configuring a RADIUS Client Configuring a RADIUS Authentication Server (Optional) The IMG only verifies if authentication is accepted or rejected by the RADIUS Server; it does not act on any other information returned by the server. 1. Right-click External Network Elements and select New Radius Servers. 2. Right-click Radius Servers and select New Radius Server. The Radius Server pane appears. The following fields are automatically populated: Radius ID - the next number in sequence 618 Configuration Radius Server Type - Authentication The Radius Server Port field is automatically populated with 1812. 4. Enter the IP address of the Radius Server in the Radius Server IP Address field. 5. Enter the User Name and Password as configured on the Radius Server in the Radius Server UserName and Radius Server Password fields. 6. Select the desired Authentication Type in the Radius Server Authentication Type field. 7. Enter the Radius Server Secret configured on the Radius Server in the Radius Server Server Secret field. See the Radius Server pane reference for field details. Configuring a RADIUS Accounting Server 1. Right-click External Network Elements and select New Radius Servers. 2. Right-click Radius Servers and select New Radius Server. The Radius Server pane appears. The following fields are automatically populated: Radius Server ID - the next number in sequence 3. Select Accounting in the Radius Server Type field. 4. In the Radius Server IP Address field, enter the IP address of the Radius Server. The Radius Server Port field is automatically populated with 1813. 619 IMG WebHelp The following fields do not apply for an Accounting Server: Radius Server UserName Radius Server Password Radius Server Authentication Type Radius Server Server Secret See the Radius Server pane reference for field details. Configuring a RADIUS Client 1. Right-click the desired Physical IMG and select New Radius Client. The Radius Client pane appears. 2. The following fields are automatically populated. Change any default values, if required. Radius Client Network Interface - IP Address of the Physical IMG. Authentication Port - 1812 Accounting Port - 1813 Primary Authentication Server - First Authentication Server Configured Primary Accounting Server - First Accounting Server Configured 3. Select a Secondary Authentication Server from the Secondary Authentication Server field, if required. 4. Select a Secondary Accounting Server from the Secondary Accounting Server field, if required. 5. To enable RADIUS Client Debug Mode, select On in the RADIUS Client Debug Mode field. When Debug Mode is On, calls will be completed whether the RADIUS server is active or not. The IMG will not require authentication from the RADIUS server to complete a call and no billing information will be logged. 620 Configuration See the Radius Client pane reference for field details. Cantata Technology - IMG 1010 Printable WebHelp 621 IMG WebHelp Configuring Free RADIUS using GCEMS as a RADIUS Server Topic Location: Configuration > RADIUS The IMG 1010 runs a RADIUS client that is configured to send CDR start & stop events to the RADIUS server, which can be the GCEMS Linux server or another RADIUS server. Requirements GCEMS server running Linux Redhat ES 3.0 with freeradius installed, or another server running Radius. For RADIUS authentication, the username and password specified in ClientView for the Radius server authentication either needs to be in the /etc/raddb/users configuration or if using the Linux server for authentication should be added as a Linux user. Steps To add a RADIUS user using the users file add the following to /etc/raddb/users file If you are using a Linux username for authentication, skip to step 2. If you are not using RADIUS authentication (accounting only), you can skip to step 3. 1. Add the following to the freeRADIUS users file (/etc/raddb/users), replacing <your_username> and <your_password> with the RADIUS username and password you will use on the IMG. <your_username> Auth-Type:=Local, User-Password==<"your_password"> Fall-Through = No 2. Verify the DEFAULT Authorization Type is REJECT Edit the freeRadius users file (/etc/raddb/users) Add the following line at the end of the file, if missing # IF NOTHING ELSE MATCHES, REJECT USER DEFAULT Auth-Type:= Reject 3. Modify the Detail File Rollover Interval (/etc/raddb/radiusd.conf) This is required for users doing load testing as yoursystems with high call rates as the detail files will could reach the max file size in less than 24 hours depending on the call rate and then calls will stop being processed. a. Look for the following line around line 1030: # Write a detailed log of all accounting records received 622 Configuration b. Look for the following line around line 1056: detailfile =”, c. at the end of this line add the %H to have the log files roll over every hour. 4. Add access for each IMG Edit the freeRadius clients.conf file (/etc/raddb/clients.conf) If you have multiple IMG’s, the Username should be different for each IMG. Shortname = the Your username configured in the RADIUS users file and ClientView A unique username is recommended for each IMG.username Secret = a password that you choose for each IMG that is used in the ClientView RadiusServer Authentication & Accounting configuration.Key used to encrypt sensitive account information transmitted between the IMG and the RADIUS server. Password = Your RADIUS password configured in the RADIUS users file and ClientView client 10.129.44.240 { # IMG IP secret = server_secret shortname = your_username password = your_password } 5. Copy the Cantata VSA Dictionary file. .a. Copy the dictionary.cantata file from /opt/cantata/common/radius to /usr/share/freeradius. a.b. In the /usr/share/freeradius/ folder, edit the dictionary file and add the following include line. $INCLUDE dictionary.cantata 6. Start the Radius service: service radiusd restart 7. Set the Radius service to restart when the system restarts: chkconfig radiusd on 8. In ClientView, Configure a Radius Client and Servers on the IMG. See Configuring Billing and Authentication. 9. Verify CDR’s are being generated 623 IMG WebHelp By default the files will roll over once a day. Follow the instructions in step 3 to roll the log files over once an hour. CDR's stored at: /var/log/radius/radacct/<IMG_IP>/ file names are: detail-YYYYMMDDHH detail-2005081801 10. Archive & delete CDR detail files. A copy of the following files can be found at /opt/cantata/IMG/radius . a. In the /var/log/radius/radacct folder create a script to archive files. Name the file “CDR” #!/bin/sh # CDR # Sample script to archive CDR's. # Files are deleted if more than 31 days old # Files are archived if more than 1 days old find /var/log/radius/radacct/*/detail* -mtime +1 -exec gzip {} \; find /var/log/radius/radacct/*/detail* -mtime +31 -exec rm -f {} \; b. Create a cron task to run this script. This cron task can be run hourly or daily. The example below will run it hourly. After creating this script restart the cron service or restart the server. In the /etc/cron.hourly folder create a file to run the script created in the previous step. #!/bin/bash crontab<<EOF # cron.dat-cdr - cron file for CDR's # # This script restarts the CDR log files each hour. 0 * * * * /var/log/radius/radacct/CDR # EOF To e-mail this topic, click here Copyright © 2007 Cantata Technology All rights reserved. Cantata Technology - IMG 1010 Printable WebHelp 624 Configuration SNMP Configuring SNMP Topic Location: Configuration > SNMP Related Topic An Overview of SNMP Before You Begin Compile MIBs The IMG SNMP solution supports the following standard MIBs. RFC 1213 RFC 3896 RFC 3895 RFC 2571 RFC 1907 These MIB libraries should be included with your NMS, however, should you need to compile a standard MIB you can access them at the following web site: http://www.rfc-editor.org/rfc.html. There are currently no Cantata Enterprise MIBs for the IMG. Configuring SNMP on the IMG 1. Configure SNMP Agent for all Physical IMGs For each IMG that you want to monitor, configure an SNMP Agent a. Right-click on the desired Physical IMG entry and select New SNMP Agent The SNMP Agent pane appears. b. Enter information in the fields as required. See the SNMP Agent pane reference for more information. c. Repeat steps a and b for each SNMP Agent on a physical IMG. 625 IMG WebHelp 2. Configure SNMP Managers (up to 3) a. Right-click External Network Elements and select New SNMP Managers b. Right-click SNMP Managers and select New SNMP Manager The SNMP Manager pane appears. c. Enter information in the fields as required. See the SNMP Manager pane reference for more information. d. To configure a second or third SNMP Manager, repeat steps a - c. Cantata Technology - IMG 1010 Printable WebHelp 626 Provisioning the IMG An Overview of Provisioning the IMG Topic Location: Provisioning the IMG Before You Begin You must have an assigned role of Provisioning or Configuration to perform provisioning tasks. Methods Provisioning on the IMG is performed in one of two ways: Buttons Select Options from Configuration Tree You can perform provisioning by clicking buttons on the bottom of the Configuration pane. You can perform provisioning by right-clicking on an entry in the Configuration tree and selecting the desired action. Provisioning Tasks System (Cantata IMG EMS) 627 IMG WebHelp Clear Logs Rest Node Download Raw File Physical IMG Clear Software Download Node License Facility Bring Span in Service Take Span out of Service SS7 Signaling Switchover SS7 Link Bring in Service Inhibit Take out of Service Uninhibit H.323 Signaling Discover GK Unregister with GK Register with GK VoIP Module Update Status IP Bearer Profiles Save Profiles Routing Download Translations Incoming GW Table 628 Resource Table GW ID Table Provisioning the IMG Update Circuit Status Save Treatment Table Save Translation Table Save Route List Save VIF (Vocabulary Index File) Telnet Enable Reset Telnet Client Update Status Cantata Technology - IMG 1010 Printable WebHelp 629 IMG WebHelp Bringing Spans into (or out of) Service Topic Location: Provisioning the IMG 1. Click the Clear Channel associated with the spans that you want to bring in service. 2. The Clear Channel pane appears. 3. Click the In Service button. 4. Click the Out Of Service button to take spans out of service. Cantata Technology - IMG 1010 Printable WebHelp 630 Provisioning the IMG Clearing the Configuration Topic Location: Provisioning the IMG To clear the configuration of the physical IMG and do a hard reset of the node, follow the steps below. Steps 1. Click the Physical IMG that you want to clear its configuration. 2. Click the Clear Software button. Cantata Technology - IMG 1010 Printable WebHelp 631 Monitoring the IMG Monitoring the IMG Topic Location: Monitoring the IMG Using ClientView All users are assigned the ability to perform monitoring functions by default. You are allowed to view configuration and status panes in ClientView, but you are not allowed to make configuration changes or perform provisioning functions. There are three types of panes that you can use to monitor the IMG: Configuration Pane (Top Right) Info Pane (Bottom Right) Status Pane (Bottom Right) Shows the configuration settings for an object. May also include Status information, such as EMS Connection State. Shows the entries that are included in an object, such as the Channel Groups included in a Route List. Shows status information for an object, such as an SS7 CIC (In Service/Out of Service). See Monitoring the IMG Using ClientView. EventView EventView is a companion product of ClientView that displays system alarms, filters alarms related to severity and various entities, and logs alarms to files. See An Overview of EventView. Using SNMP 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. See An Overview of SNMP and Configuring SNMP. Using the Multi Router Traffic Grapher (MRTG) Tool The Multi Router Traffic Grapher (MRTG) Tool is used to monitor various areas on network links. MRTG generates HTML pages containing PNG images which provide a live visual representation of this traffic. 632 Monitoring the IMG See Using the Multi Router Traffic Grapher (MRTG) Tool. Cantata Technology - IMG 1010 Printable WebHelp 633 IMG WebHelp MRTG An Overview of MRTG Topic Location: Monitoring the IMG > MRTG The Multi Router Traffic Grapher (MRTG) is a tool to monitor various items in the IMG (such as temperature, CPU, memory), on the GCEMS (such as CPU, disk space, memory) and on network links. MRTG generates HTML pages containing PNG images which provide a live visual representation of data. MRTG log files are stored in the following directory: /opt/cantata/common/mrtg_logs Data is refreshed every 5 minutes. The following information is reported for different IMG components: Traffic Memory Data CPU Utilization Temperature Data See Sample MRTG Main Page. Using MRTG Perform the following steps to install and use MRTG. 1. Install MRTG 2. Setup an MRTG Web Host (optional) 3. To generate MRTG logs, press the MRTG Scripts button on the Cantata EMS pane in ClientView. You can update MRTG from the Channel Groups pane after you add channel groups. NOTE: If you add a Channel Group in ClientView, you must re-generate the MRTG scripts to include those Channel Groups in the MRTG log files. 634 Monitoring the IMG 4. To view logs, connect to the Apache Web Server (from step 2), or go to opt/cantata/common/mrtg_logs/ and view individual logs with a web browser. MRTG Log Files The following html files are generated by MRTG: Level 1: System Index This file shows a single graph for each IMG that is configured in the GCEMS. The main graph for each IMG is the Total Traffic single day graph. Click on a graph to view additional graphs for that IMG. This will take you to the IMG Index graph for that IMG. Level 1: Local Host The following graphs are generated for the local host: CPU Utilization Memory Utilization Disk Utilization Memory Swap Usage Swap Statistics Level 2: Individual IMGs There is one IMG Index graph for each IMG. This page contains four graphs, shown below in red with sub-graphs: Traffic Total Traffic Total Outgoing traffic Total Incoming Traffic All the incoming and outgoing traffic graphs for all the channel groups (SS7, ISDN, SIP, H.323), each of which has the following sub-graphs: Daily 5 Minute Average Monthly 2 Hour Average CPU Utilization Weekly 30 Minute Average Yearly 1 Day Average Average Call Duration Daily 5 Minute Average Monthly 2 Hour Average Weekly 30 Minute Average Yearly 1 Day Average 635 IMG WebHelp Memory Data Total Free Memory 32 Byte Memory Pool Buffers 16 Byte Memory Pool Buffers 64 Byte Memory Pool Buffers 128 Byte Memory Pool Buffers 256 Byte Memory Pool Buffers 512 Byte Memory Pool Buffers 1024 Byte Memory Pool Buffers 2048 Byte Memory Pool Buffers Each of these has the following subgraphs: Daily 5 Minute Average Monthly 2 Hour Average Weekly 30 Minute Average Yearly 1 Day Average Temperature Data Average Temperature Temperature under DSP Module Temperature under VoIP Modules Temperature at CPU Each of these has the following subgraphs: Daily 5 Minute Average Monthly 2 Hour Average Weekly 30 Minute Average Yearly 1 Day Average Cantata Technology - IMG 1010 Printable WebHelp 636 Monitoring the IMG Installing MRTG Topic Location: Monitoring the IMG > MRTG Prerequisite Upgrade GCEMS to the latest version (minimum of GCEMS 10.3.1.121) Steps 1. Login as root 2. Go to the following directory: /usr/local/src 3. Run the installMrtg.sh script ./installMrtg.sh 4. Verify contents of directory by typing: ls there should be 5 directories: gd libpng zlib mrtg tarFiles 5. Start GCEMS 6. Create the MRTG configuration file and HTML files In ClientView, go to the Cantata EMS pane and click the “MRTG Scripts” button 7. Setup an MRTG Web Host. See Setting Up An MRTG Web Host. Troubleshooting Are the mrtg output files in the directory ? a. Go to directory /opt/cantata/common/mrtg_logs b. Do an ls c. There should be many .png and .html files If the files are not there, then continue on with this troubleshooting guide 637 IMG WebHelp If the files are there you can open them with a local Web Browser, or you can configure the Apache Web server, please see the other installation document for that. Is MRTG installed correctly ? a. Go to directory /usr/local/src b. Do an ls You should see 5 directories: gd, llibpng, zlib, mrtg and tarFiles if not, something went wrong with the MRTG installation do a “whereis gcc” it should show gcc: /usr/bin/gcc if it can’t find gcc, then there is no compiler and you need to download a compiler on to the GCEMS, this also indicates that this was not a standard install. If it can find it make sure the directory is in the PATH by “printenv PATH” You should see the /usr/bin in the path If not you have to add this directory to the path by typing: PATH=$PATH:/usr/bin Are the Stats Files being created ? 1. Go to directory /opt/cantata/common/stats 2. Show the directory contents by typing: ls You should see a number of .csv files. If you open one you should see entries that are every 5 minutes. Is the stats frequency setup correctly 1. Go to directory /opt/cantata/common 2. Edit the Defaults file – the file should have the following line in it STATS_FREQUENCY:5 3. If it is not set correctly change it and restart the GCEMS. Check the cronjob 1. Open the cronjob file by typing: crontab –l You should see a line like the following 638 Monitoring the IMG */5 * * * * env LANG=C /usr/local/src/mrtg/bin/mrtg /opt/cantata/common/mrtg_bin/cantatamrtg.cfg -- logging /opt/cantata/common/log/mrtg.log > /dev/null 2>&1 Manually starting the Cronjob if needed 1. Type the following: crontab<<EOF */5 * * * * env LANG=C /usr/local/src/mrtg/bin/mrtg /opt/cantata/common/mrtg_bin/cantatamrtg.cfg -- logging /opt/cantata/common/log/mrtg.log > /dev/null 2>&1 EOF Make sure the mrtg_bin and mrtg_logs directories have write access 1. Go to directory /opt/cantata/common 2. Show all directory settings by typing: ls -al 3. If all the directories do not have read/write/execute privileges change it a. Login as ROOT b. chmod 777 mrtg_bin c. chmod 777 mrtg_log Make sure the cantamrtg.cfg was created 1. Go to directory /opt/cantata/common/mrtg_bin 2. Show the directory contents by typing: ls 3. Make sure there is a file called cantatamrtg.cfg If this file is not here, then see step 3 of the installation section. Cantata Technology - IMG 1010 Printable WebHelp 639 IMG WebHelp Setting Up an MRTG Web Host Topic Location: Monitoring the IMG > MRTG Steps Create .htaccess file 1. Login as root 2. Go to directory /opt/cantata/common/mrtg_logs 3. Create a file called “.htaccess” 4. Add the following lines to the file AuthName "Please enter your UserName and Password." AuthType Basic AuthUserFile /opt/cantata/common/mrtg_logs/.htpasswd AuthGroupFile /dev/null Require user excelsw (Where excelsw is the username) 5. Save the file 6. Change the privileges on .htaccess chmod 777 .htaccess Create a password for the UserName 1. Login as root 2. Go to directory /opt/cantata/common/mrtg_logs 3. Type the following where excelsw is the username from procedure 1 htpasswd –c /opt/cantata/common/mrtg_logs/.htpasswd excelsw Edit the httpd.conf file 1. Login as root 2. Go to directory /etc/httpd/conf 3. Change the DocumentRoot as shown in bold below: DocumentRoot "/opt/cantata/common/mrtg_logs" 4. Setup for password protection: 640 Monitoring the IMG a. Find the section that begins with the line “This should be changed to whatever you set DocumentRoot to.” b. Change the areas shown in bold below (notice the comment (#) added to the last two lines): # # This should be changed to whatever you set DocumentRoot to. # <Directory "/opt/cantata/common/mrtg_logs"> # # Possible values for the Options directive are "None", "All", # or any combination of: # Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews # # Note that "MultiViews" must be named *explicitly* --"Options All" # doesn't give it to you. # # The Options directive is both complicated and important. Please see # http://httpd.apache.org/docs-2.0/mod/core.html#options # for more information. # Options FollowSymLinks # # AllowOverride controls what directives may be placed in .htaccess files. # It can be "All", "None", or any combination of the keywords: # Options FileInfo AuthConfig Limit # AllowOverride All # # Controls who can get stuff from this server. # # Order allow,deny # Allow from all </Directory> 641 IMG WebHelp 5. Change the DirectoryIndex as follows: DirectoryIndex systemindex.html index.html.var 6. Save the httpd.conf file Restart the Apache Web Server 1. Restart the Apache Server by typing the following: /sbin/service httpd restart /sbin/chkconfig httpd on Cantata Technology - IMG 1010 Printable WebHelp 642 Monitoring the IMG Sample MRTG Main Page Topic Location: Monitoring the IMG > MRTG The Main MRTG page is shown below. When you view the actual MRTG HTML page, click on a specific graphic to see more information about that area. 643 IMG WebHelp Cantata Technology - IMG 1010 Printable WebHelp 644 Monitoring the IMG ClientView Monitoring the IMG Using ClientView Topic Location: Monitoring the IMG > ClientView Monitoring Panes EMS_Configuration IMG_Configuration CIC_Status IP_Bearer_Profile_Info SS7_Link_Info Route_Table_Info Route_List_Info Translation_Table_Info Vocabulary_Index_File_Info EMS Configuration Click on Cantata IMG EMS in the Configuration Tree to see the EMS Configuration pane. IMG Configuration Click on an IMG entry in the Configuration Tree to see the IMG Configuration pane which includes the following information pertaining to the IMG, including Serial Number, Software Version, VoIP Module Status, and Connection State. 645 IMG WebHelp CIC Status Click on Circuit Group entry in an SS7 Channel Group to see the Status pane for the CIC, which includes the following SS7 Link Info IP Bearer Profile Info Click on an IP Bearer Profile in the Configuration Tree to see the Info Pane showing information for all of the entries in the profile. Route Table Info Click on a Route Table entry in the Configuration Tree to see the Status Pane for the table, showing all of the entries in the table with their configuration settings. 646 Monitoring the IMG Route List Info Click on a Route List in the Configuration Tree to see the Info pane, which shows all of the Channel Groups included in the route list. To view the Status pane for the Route List, click the Status pane. Translation Table Info Click on a Translation Table entry in the Configuration Tree to see the Info Pane for the table, which shows the configuration information for all of the entries in the table. Vocabulary Index File Info Click on a Vocabulary Index File entry in the Configuration Tree to see the Info Pane which shows all of the voice files included in the VIF with their configuration settings. Cantata Technology - IMG 1010 Printable WebHelp 647 IMG WebHelp Viewing IMG Status and Information Topic Location: Monitoring the IMG > ClientView When you click on a Logical IMG entry in the Configuration Tree, the Status Pane displays a list of all of the Physical IMGs in that Logical IMG. Click on a Physical IMG entry in the table to display information about that IMG, including the Chassis Serial Number, Software Version, and the Connection State. Cantata Technology - IMG 1010 Printable WebHelp 648 Monitoring the IMG Viewing Channel Group Call Statistics Topic Location: Monitoring the IMG > ClientView In the Object Table in the Status Panel of the Channel Groups pane you can view the following call statistics for all configured channel groups. Incoming Calls (last 15 minutes) Outgoing Calls (last 15 minutes) Incoming Calls Answered (last 15 minutes) Outgoing Calls Answered (last 15 minutes) Average Hold Time for Answered Calls (last 15 minutes) Cantata Technology - IMG 1010 Printable WebHelp 649 IMG WebHelp Viewing Licensing Information Topic Location: Monitoring the IMG > ClientView You can view an IMG 1010's current licensing information as follows: 1. Right-click the Physical IMG and select IMG Licensing Info. 2. Right-click IMG License Info and select Commit. 3. The IMG Licensing Info ClientView pane appears. Confirm your licensing information. Related Topic Downloading a New License Cantata Technology - IMG 1010 Printable WebHelp 650 Monitoring the IMG EventView An Overview of EventView Topic Location: Monitoring the IMG > EventView EventView is a companion product of ClientView that displays system alarms, filters alarms related to severity and various entities, and logs alarms to files. Launching EventView EventView is automatically launched when you login to ClientView. You can change this and log into EventView manually. Manual You can launch EventView from within ClientView by selecting Launch EventView from the Tools menu. Auto-Launch EventView is automatically launched when you login to ClientView. To disable autolaunch, select Properties from the Tools menu and change the Auto-Launch EventView field to false. Accessing the ClientView Properties Dialog Box ClientView Properties Dialog Box 651 IMG WebHelp EventView Main Window NOTE: The default maximum number of events stored is 200. You can change this value with Environment variable SK_MAX_NUM_EVENTS_STORED. Getting Help in EventView You can view the online help for EventView in a web browser from the EventView application. The HTML-based Help format is designed to run on a wide variety of browsers and platforms. To access, select Open Help from the Help Menu. The Monitoring the IMG with EventView book is at the bottom of the IMG help topics. 652 Monitoring the IMG Log EventView messages are logged to a comma separated file which can be easily imported into excel. File Location: opt/cantata/common/log File Name: EventLog*.csv Next Topic Filtering Alarms Cantata Technology - IMG 1010 Printable WebHelp 653 IMG WebHelp Filtering Alarm Views Topic Location: Monitoring the IMG > EventView To filter the display of alarms according to entities and severity in EventView, do the following: 1. Click on the Filtered Alarms tab. 2. From the left pane, select the Severity of the alarms that you want to show. 3. Select each Entity for which you want to show alarms. The right pane becomes populated after you have selected an entity. EventView shows data in either alphabetical or numerical order, whichever is relevant. Sorting Alarm Fields To sort the fields shown in the columns displayed, select the desired column heading and drag it to the position you want. Interpreting Alarms Mapping Span/Channel to VoIP Module Errors on a VoIP channel are reported as a span/channel. To map the span channel to a VoIP Module/Port, see Span/Channel to VoIP Module Mapping 654 Monitoring the IMG Next Topic Exporting Alarms Cantata Technology - IMG 1010 Printable WebHelp 655 IMG WebHelp Exporting Alarms to a Text File Topic Location: Monitoring the IMG > EventView After you have filtered the alarms being displayed in the EventView, you may want to export these alarms to a text file. Do the following to export the alarm information that is currently on display in the EventView to a text file. 1. Create a text file and save it with an appropriate name. 2. In the Event Viewer select the menu option File-Export Alarms to a Text File. 3. Browse to the file that you created earlier and click Open. Next Topic Forcing a Log File to Roll-Over Cantata Technology - IMG 1010 Printable WebHelp 656 Monitoring the IMG Forcing a Log File to Roll-over Topic Location: Monitoring the IMG > EventView To force an EventView log file to roll-over do the following: 1. In the Event Viewer, go to the menu File Force Log File Roll-Over. 2. In the folder where you have installed EventView, by default, cantata\IMGUserInterface\EventView, you will see that your Alarms file has been saved at the time you forced the log file rollover. A new log file is then automatically created. Cantata Technology - IMG 1010 Printable WebHelp 657 IMG WebHelp Restarting a Socket Connection Topic Location: Monitoring the IMG > EventView If you lose your socket connection to DataManager, do the following. 1. Go to the File > Start Client Socket. 2. Verify the host name or IP address of the DataManager is correct. If not, make appropriate changes. 3. Click OK in the Client Socket dialog box. Cantata Technology - IMG 1010 Printable WebHelp 658 Monitoring the IMG Span/Channel to VoIP Module Mapping Module 0 Module 1 Span Channel 4096 1 4096 4096 4096 4096 4096 4096 4096 4096 4096 4096 4096 4096 4096 4096 4096 4096 4096 4096 4096 4096 4128 1 8008 3 4 5 6 7 8 9 12 4096 8004 2 4096 4096 Channel 8000 10 4096 Span 0 4096 4096 Port 11 13 14 15 16 17 18 19 20 21 22 23 24 25 26 8012 8016 8020 8024 8028 8032 8036 8040 8044 8048 8052 8056 8060 8064 8068 8072 8076 8080 8084 8088 8092 8096 8100 8104 4128 4128 4128 4128 4128 4128 4128 4128 4128 0 11072 2 11080 3 4 5 6 7 8 9 4128 10 4128 12 4128 4128 4128 4128 4128 4128 4128 4128 4128 4128 4128 4128 4128 4128 4128 Port 11 13 14 15 16 17 18 19 20 21 22 23 24 25 26 11076 11084 11088 11092 11096 11100 11104 11108 11112 11116 11120 11124 11128 11132 11136 11140 11144 11148 11152 11156 11160 11164 11168 11172 11176 659 IMG WebHelp 4096 27 8108 4128 27 11180 4096 29 8116 4128 29 11188 4096 4096 4096 4097 4097 4097 4097 4097 4097 4097 4097 4097 4097 28 30 31 0 1 2 3 4 5 6 7 8 9 4097 10 4097 12 4097 4097 4097 4097 4097 4097 4097 4097 4097 4097 4097 4097 4097 4097 4097 660 11 13 14 15 16 17 18 19 20 21 22 23 24 25 26 8112 8120 8124 8128 8132 8136 8140 8144 8148 8152 8156 8160 8164 8168 8172 8176 8180 8184 8188 8192 8196 8200 8204 8208 8212 8216 8220 8224 8228 8232 4128 4128 4128 4129 4129 4129 4129 4129 4129 4129 4129 4129 4129 28 30 31 0 1 2 3 4 5 6 7 8 9 4129 10 4129 12 4129 4129 4129 4129 4129 4129 4129 4129 4129 4129 4129 4129 4129 4129 4129 11 13 14 15 16 17 18 19 20 21 22 23 24 25 26 11184 11192 11196 11200 11204 11208 11212 11216 11220 11224 11228 11232 11236 11240 11244 11248 11252 11256 11260 11264 11268 11272 11276 11280 11284 11288 11292 11296 11300 11304 Monitoring the IMG 4097 27 8236 4129 27 11308 4097 29 8244 4129 29 11316 4097 4097 4097 4098 4098 4098 4098 4098 4098 4098 4098 4098 4098 28 30 31 0 1 2 3 4 5 6 7 8 9 4098 10 4098 12 4098 4098 4098 4098 4098 4098 4098 4098 4098 4098 4098 4098 4098 4098 4098 11 13 14 15 16 17 18 19 20 21 22 23 24 25 26 8240 8248 8252 8256 8260 8264 8268 8272 8276 8280 8284 8288 8292 8296 8300 8304 8308 8312 8316 8320 8324 8328 8332 8336 8340 8344 8348 8352 8356 8360 4129 4129 4129 4130 4130 4130 4130 4130 4130 4130 4130 4130 4130 28 30 31 0 1 2 3 4 5 6 7 8 9 4130 10 4130 12 4130 4130 4130 4130 4130 4130 4130 4130 4130 4130 4130 4130 4130 4130 4130 11 13 14 15 16 17 18 19 20 21 22 23 24 25 26 11312 11320 11324 11328 11332 11336 11340 11344 11348 11352 11356 11360 11364 11368 11372 11376 11380 11384 11388 11392 11396 11400 11404 11408 11412 11416 11420 11424 11428 11432 661 IMG WebHelp 4098 27 8364 4130 27 11436 4098 29 8372 4130 29 11444 4098 4098 4098 4099 4099 4099 4099 4099 4099 4099 4099 4099 4099 28 30 31 0 1 2 3 4 5 6 7 8 9 4099 10 4099 12 4099 4099 4099 4099 4099 4099 4099 4099 4099 4099 4099 4099 4099 4099 4099 662 11 13 14 15 16 17 18 19 20 21 22 23 24 25 26 8368 8376 8380 8384 8388 8392 8396 8400 8404 8408 8412 8416 8420 8424 8428 8432 8436 8440 8444 8448 8452 8456 8460 8464 8468 8472 8476 8480 8484 8488 4130 4130 4130 4131 4131 4131 4131 4131 4131 4131 4131 4131 4131 28 30 31 0 1 2 3 4 5 6 7 8 9 4131 10 4131 12 4131 4131 4131 4131 4131 4131 4131 4131 4131 4131 4131 4131 4131 4131 4131 11 13 14 15 16 17 18 19 20 21 22 23 24 25 26 11440 11448 11452 11456 11460 11464 11468 11472 11476 11480 11484 11488 11492 11496 11500 11504 11508 11512 11516 11520 11524 11528 11532 11536 11540 11544 11548 11552 11556 11560 Monitoring the IMG 4099 27 8492 4131 27 11564 4099 29 8500 4131 29 11572 4099 4099 4099 4100 4100 4100 4100 4100 4100 4100 4100 4100 4100 28 30 31 0 1 2 3 4 5 6 7 8 9 4100 10 4100 12 4100 4100 4100 4100 4100 4100 4100 4100 4100 4100 4100 4100 4100 4100 4100 11 13 14 15 16 17 18 19 20 21 22 23 24 25 26 8496 8504 8508 8512 8516 8520 8524 8528 8532 8536 8540 8544 8548 8552 8556 8560 8564 8568 8572 8576 8580 8584 8588 8592 8596 8600 8604 8608 8612 8616 4131 4131 4131 4132 4132 4132 4132 4132 4132 4132 4132 4132 4132 28 30 31 0 1 2 3 4 5 6 7 8 9 4132 10 4132 12 4132 4132 4132 4132 4132 4132 4132 4132 4132 4132 4132 4132 4132 4132 4132 11 13 14 15 16 17 18 19 20 21 22 23 24 25 26 11568 11576 11580 11584 11588 11592 11596 11600 11604 11608 11612 11616 11620 11624 11628 11632 11636 11640 11644 11648 11652 11656 11660 11664 11668 11672 11676 11680 11684 11688 663 IMG WebHelp 4100 27 8620 4132 27 11692 4100 29 8628 4132 29 11700 4100 4100 4100 4101 4101 4101 4101 4101 4101 4101 4101 4101 4101 28 30 31 0 1 2 3 4 5 6 7 8 9 4101 10 4101 12 4101 4101 4101 4101 4101 4101 4101 4101 4101 4101 4101 4101 4101 4101 4101 664 11 13 14 15 16 17 18 19 20 21 22 23 24 25 26 8624 8632 8636 8640 8644 8648 8652 8656 8660 8664 8668 8672 8676 8680 8684 8688 8692 8696 8700 8704 8708 8712 8716 8720 8724 8728 8732 8736 8740 8744 4132 4132 4132 4133 4133 4133 4133 4133 4133 4133 4133 4133 4133 28 30 31 0 1 2 3 4 5 6 7 8 9 4133 10 4133 12 4133 4133 4133 4133 4133 4133 4133 4133 4133 4133 4133 4133 4133 4133 4133 11 13 14 15 16 17 18 19 20 21 22 23 24 25 26 11696 11704 11708 11712 11716 11720 11724 11728 11732 11736 11740 11744 11748 11752 11756 11760 11764 11768 11772 11776 11780 11784 11788 11792 11796 11800 11804 11808 11812 11816 Monitoring the IMG 4101 27 8748 4133 27 11820 4101 29 8756 4133 29 11828 4101 4101 4101 4102 4102 4102 4102 4102 4102 4102 4102 4102 4102 28 30 31 0 1 2 3 4 5 6 7 8 9 4102 10 4102 12 4102 4102 4102 4102 4102 4102 4102 4102 4102 4102 4102 4102 4102 4102 4102 11 13 14 15 16 17 18 19 20 21 22 23 24 25 26 8752 8760 8764 8768 8772 8776 8780 8784 8788 8792 8796 8800 8804 8808 8812 8816 8820 8824 8828 8832 8836 8840 8844 8848 8852 8856 8860 8864 8868 8872 4133 4133 4133 4134 4134 4134 4134 4134 4134 4134 4134 4134 4134 28 30 31 0 1 2 3 4 5 6 7 8 9 4134 10 4134 12 4134 4134 4134 4134 4134 4134 4134 4134 4134 4134 4134 4134 4134 4134 4134 11 13 14 15 16 17 18 19 20 21 22 23 24 25 26 11824 11832 11836 11840 11844 11848 11852 11856 11860 11864 11868 11872 11876 11880 11884 11888 11892 11896 11900 11904 11908 11912 11916 11920 11924 11928 11932 11936 11940 11944 665 IMG WebHelp 4102 27 8876 4134 27 11948 4102 29 8884 4134 29 11956 4102 4102 4102 4102 4103 4103 4103 4103 4103 4103 4103 4103 4103 28 30 31 0 1 2 3 4 5 6 7 8 9 4103 10 4103 12 4103 4103 4103 4103 4103 4103 4103 4103 4103 4103 4103 4103 4103 4103 4103 666 11 13 14 15 16 17 18 19 20 21 22 23 24 25 26 8880 8888 8892 8896 8900 8904 8908 8912 8916 8920 8924 8928 8932 8936 8940 8944 8948 8952 8956 8960 8964 8968 8972 8976 8980 8984 8988 8992 8996 9000 4134 4134 4134 4134 4135 4135 4135 4135 4135 4135 4135 4135 4135 28 30 31 0 1 2 3 4 5 6 7 8 9 4135 10 4135 12 4135 4135 4135 4135 4135 4135 4135 4135 4135 4135 4135 4135 4135 4135 4135 11 13 14 15 16 17 18 19 20 21 22 23 24 25 26 11952 11960 11964 11968 11972 11976 11980 11984 11988 11992 11996 12000 12004 12008 12012 12016 12020 12024 12028 12032 12036 12040 12044 12048 12052 12056 12060 12064 12068 12072 Monitoring the IMG 4103 27 9004 4135 27 12076 4103 29 9012 4135 29 12084 4103 4103 4103 4104 4104 4104 4104 4104 4104 4104 4104 4104 4104 28 30 31 0 1 2 3 4 5 6 7 8 9 4104 10 4104 12 4104 4104 4104 4104 4104 4104 4104 4104 4104 4104 4104 4104 4104 4104 4104 11 13 14 15 16 17 18 19 20 21 22 23 24 25 26 9008 9016 9020 9024 9028 9032 9036 9040 9044 9048 9052 9056 9060 9064 9068 9072 9076 9080 9084 9088 9092 9096 9100 9104 9108 9112 9116 9120 9124 9128 4135 4135 4135 4136 4136 4136 4136 4136 4136 4136 4136 4136 4136 28 30 31 0 1 2 3 4 5 6 7 8 9 4136 10 4136 12 4136 4136 4136 4136 4136 4136 4136 4136 4136 4136 4136 4136 4136 4136 4136 11 13 14 15 16 17 18 19 20 21 22 23 24 25 26 12080 12088 12092 12096 12100 12104 12108 12112 12116 12120 12124 12128 12132 12136 12140 12144 12148 12152 12156 12160 12164 12168 12172 12176 12180 12184 12188 12192 12196 12200 667 IMG WebHelp 4104 27 9132 4136 27 12204 4104 29 9140 4136 29 12212 4104 4104 4104 4105 4105 4105 4105 4105 4105 4105 4105 4105 4105 28 30 31 0 1 2 3 4 5 6 7 8 9 4105 10 4105 12 4105 4105 4105 4105 4105 4105 4105 4105 4105 4105 4105 4105 4105 4105 4105 668 11 13 14 15 16 17 18 19 20 21 22 23 24 25 26 9136 9144 9148 9152 9156 9160 9164 9168 9172 9176 9180 9184 9188 9192 9196 9200 9204 9208 9212 9216 9220 9224 9228 9232 9236 9240 9244 9248 9252 9256 4136 4136 4136 4137 4137 4137 4137 4137 4137 4137 4137 4137 4137 28 30 31 0 1 2 3 4 5 6 7 8 9 4137 10 4137 12 4137 4137 4137 4137 4137 4137 4137 4137 4137 4137 4137 4137 4137 4137 4137 11 13 14 15 16 17 18 19 20 21 22 23 24 25 26 12208 12216 12220 12224 12228 12232 12236 12240 12244 12248 12252 12256 12260 12264 12268 12272 12276 12280 12284 12288 12292 12296 12300 12304 12308 12312 12316 12320 12324 12328 Monitoring the IMG 4105 27 9260 4137 27 12332 4105 29 9268 4137 29 12340 4105 4105 4105 4106 4106 4106 4106 4106 4106 4106 4106 4106 4106 28 30 31 0 1 2 3 4 5 6 7 8 9 4106 10 4106 12 4106 4106 4106 4106 4106 4106 4106 4106 4106 4106 4106 4106 4106 4106 4106 11 13 14 15 16 17 18 19 20 21 22 23 24 25 26 9264 9272 9276 9280 9284 9288 9292 9296 9300 9304 9308 9312 9316 9320 9324 9328 9332 9336 9340 9344 9348 9352 9356 9360 9364 9368 9372 9376 9380 9384 4137 4137 4137 4138 4138 4138 4138 4138 4138 4138 4138 4138 4138 28 30 31 0 1 2 3 4 5 6 7 8 9 4138 10 4138 12 4138 4138 4138 4138 4138 4138 4138 4138 4138 4138 4138 4138 4138 4138 4138 11 13 14 15 16 17 18 19 20 21 22 23 24 25 26 12336 12344 12348 12352 12356 12360 12364 12368 12372 12376 12380 12384 12388 12392 12396 12400 12404 12408 12412 12416 12420 12424 12428 12432 12436 12440 12444 12448 12452 12456 669 IMG WebHelp 4106 27 9388 4138 27 12460 4106 29 9396 4138 29 12468 4106 4106 4106 4107 4107 4107 4107 4107 4107 4107 4107 4107 4107 28 30 31 0 1 2 3 4 5 6 7 8 9 4107 10 4107 12 4107 4107 4107 4107 4107 4107 4107 4107 4107 4107 4107 4107 4107 4107 4107 670 11 13 14 15 16 17 18 19 20 21 22 23 24 25 26 9392 9400 9404 9408 9412 9416 9420 9424 9428 9432 9436 9440 9444 9448 9452 9456 9460 9464 9468 9472 9476 9480 9484 9488 9492 9496 9500 9504 9508 9512 4138 4138 4138 4139 4139 4139 4139 4139 4139 4139 4139 4139 4139 28 30 31 0 1 2 3 4 5 6 7 8 9 4139 10 4139 12 4139 4139 4139 4139 4139 4139 4139 4139 4139 4139 4139 4139 4139 4139 4139 11 13 14 15 16 17 18 19 20 21 22 23 24 25 26 12464 12472 12476 12480 12484 12488 12492 12496 12500 12504 12508 12512 12516 12520 12524 12528 12532 12536 12540 12544 12548 12552 12556 12560 12564 12568 12572 12576 12580 12584 Monitoring the IMG 4107 27 9516 4139 27 12588 4107 29 9524 4139 29 12596 4107 4107 4107 28 30 31 9520 9528 9532 4139 4139 4139 28 30 31 12592 12600 12604 671 Troubleshooting An Overview of Troubleshooting Topic Location: Troubleshooting Using Telnet Telnet access can be used for additional diagnostics such as layer 3 and layer 4 call tracing. The username for telnet access is excel and the password is excel2004. You use the Telnet Client pane to enable/disable access or to verify the telnet status. Logs The GC EMS automatically creates the following logs, located at cantata/common/logs/ EventLog_<process ID>.log Contains the events recorded by EventView. BackupFileManager.log Logs when files are backed-up. alarm.log Logs all actions taken while configuring the IMG, and the text of any alarm conditions that occur. If an IMG software fault occurs, it is written to the alarm.log. AdminMgr.log Records information on who has logged into the GC EMS. File management will be provided via BackupFileManager (IMG). All statistic object files are logged at fixed 15 minute intervals. File rollover from day to day is automatic. The name of the rolled log file will be appended with the calendar date code. File names are not user-adjustable. IMPORTANT NOTE: The log files are created upon IMG startup. Under no circumstances shall these files be deleted from the statistics directory while the IMG system software is running. Logging will stop for the statistics object of the deleted file. It is recommended that the log files be copied to another directory before viewing. Call Tracing Call Tracing allows you to view various information on a per call basis. A Call Trace log includes information such as Call Duration, RTCP Stats, and Codecs See Call Tracing for more information. Call Statistics 672 Troubleshooting Call Statistics logs are automatically enabled on the IMG to provide support personnel with key information used to identify the operational status of the system. A separate log file is generated for each protocol on each node. Logs are generated every 15 minutes and backed up using the Backup File Manager. See Call Statistics for more information. Remote Desktop To allow remote access to your GateControl EMS Server for Technical Support, see Configuring Remote Desktop. Cantata Technology - IMG 1010 Printable WebHelp 673 IMG WebHelp Recommendations for Supportability Topic Location: Troubleshooting The following are key elements we have identified across our customer base that have made them successful in their development and deployment of solutions incorporating Cantata products. We are passing these onto you as suggestions to consider when designing and building out solutions. Not all are appropriate for all customers, but we do hope you give them careful consideration. All of us at Cantata want you, our valued customers, to be successful. Contact us via our support website at http://support.cantata.com or a sales representative at [email protected] for additional information regarding our support services and how we can work more closely together for our mutual success. If your solution requires High Availability: Order redundant configurations when performing SS7 Follow the limitations for power, and configurations as noted in the Cantata Product Documentation Purchase on-site spares Make sure your technicians are trained on the Cantata platform Provide technicians with Lab equipment to perform testing Make sure you have test scripts, environments and systems in order to best simulate the environment of intended use for each release and each fix you deliver to your customers Make sure you have backup systems for power Purchase a support agreement from Cantata In addition to the above suggestions, also: 674 Review your network design with Cantata Support to identify opportunities to optimize your solution with respect to our product capabilities Design your network to allow for alternative routes and logical assignments to more quickly address any service affecting issues Make sure you control your system environment and configuration changes Plan your network management and monitoring strategy Ensure that your technicians are trained in all network elements and interfaces Monitor your network 24x7 Have the ability to get someone to every site without delay Have a complete list of contact information for the support arm of each network element you deploy Troubleshooting Provide for supplier remote access if required to diagnose and resolve an issue. Cantata recommends the use of VNC in conjunction with a firewall and network access control lists. The resulting benefit is that a Cantata Support engineer can work with your technicians in a real-time shared access mode. This allows your team the ability to learn while system issues are being examined. Have the ability to capture Ethernet traces via network equipment port mirroring. Because the Ethernet ports on the IMG contain the IP signaling and RTP streams (rather than the GCEMS), this will greatly enhance Cantata’s efforts to quickly resolve issues involving call failures and voice path. For more important information see An Overview of Troubleshooting. Cantata Technology - IMG 1010 Printable WebHelp 675 IMG WebHelp Log Files Topic Location: Troubleshooting Alarm Log File name: alarm.log SwitchManager generates this file. It logs all actions taken by the SwitchManager in configuring the switch, and the text of any alarm conditions that occur on the switch. If a switch software fault occurs, it is written to the alarm.log. Maintenance Log File name: maintenance.xxx.log This type of log is generated by the LLC, the SwitchManager, and all applications linked with the SwitchKit API library. The actual file names are: maintenance_lc.PID.log maintenance_switchmgr.PID.log maintenance_DataManager.PID.log maintenance_appName.PID.log maintenance_app.PID.log where PID is the process ID of that application. SocketLog Logs all the messages going between the IMG and the host. It logs everything that goes across the socket, prior to processing, including the length of the message. The socket log file includes the following abbreviations: Abbreviation Description X IMG 1 Logical Node ID [10.10.156.24] Socket IP address H Host Example Socket.log The following example socket log shows an inbound and outbound message: Jan 11 2002 12:59:57 X1[10.10.156.24]->H : 00 ab 00 38 01 00 10 01 00 05 00 01 01 01 00 00 676 Troubleshooting Jan 11 2002 12:59:57 H->X1[10.10.156.24] : 00 ab 00 38 01 EventLog File name: EventLog_xxx.csv This file is generated by DataManager to record all events that are worthy of reporting to an EventView client. Events that would be logged to an EventView client will be logged in this file independent of whether an EventView client is running or not. The file name is (where PID is the process ID of the DataManager): EventLog_PID.log Cantata Technology - IMG 1010 Printable WebHelp 677 IMG WebHelp Call Statistics Topic Location: Troubleshooting There are certain statistics available that the host queries and reports to specific log files. These system statistic log files are designed to provide support personnel with key information used to identify the operational status of the system. The statistics are kept on a per object basis and are stored in a separate directory. The statistics files are stored in a Microsoft Excel spread sheet format so that they can be easily viewed and manipulated. The available statistics objects are: ISDN SS7 H323 SIP Layer 4 Layer 4 Channel Group Gateway Control Layer Location All statistics for configured objects will be logged to “.csv” (comma separated value) files and stored in the following directory opt/cantata/common/log/callstats Naming The naming convention for the statistics file is as follows: <NodeName>_<StatsObject>_<DB-ID>.csv Channel Group Statistics in ClientView In the Object Table in the Status Panel of the Channel Groups pane you can view the following call statistics for all configured channel groups. Incoming Calls (last 15 minutes) Outgoing Calls (last 15 minutes) 678 Incoming Calls Answered (last 15 minutes) Outgoing Calls Answered (last 15 minutes) Average Hold Time for Answered Calls (last 15 minutes) NOTE: The Average Hold Time is calculated after the call ends. If there is no call released within one query period, the average holding time reported for that period will be 0, even if there are active calls in the period. Troubleshooting See View Channel Group Call Statistics. Cantata Technology - IMG 1010 Printable WebHelp 679 IMG WebHelp Troubleshooting: SS7 Signaling Links Topic Location: Troubleshooting This section describes common causes that prevent SS7 signaling links from coming into service or alignment. Point code mismatch The OPC (Originating Point Code) as defined in the place holder must match the value that the distant end signaling point expects. Also, the distant end's point code must match the APC (Adjacent Point Code) and DPC (Destination Point Code) values. Signaling link code mismatch The Signaling Link Code (SLC) is a number (0-15) which is assigned by both ends to identify a specific link within a link set. The SLC must match the SLC value assigned to the link by the distant end. Network indicator mismatch The Network Indicator (NI) value is defined by two bits (therefore values 0-3 are possible). The default value of the Network Indicator is set to National (0x02) for both ANSI and ITU. Some networks may require the Network Indicator to be set to International (0x00) or one of the spare values (0x01 or 0x03). To change the NI value, see the SS7 Stack pane. Following is an example SS7 trace showing a Network Indicator mismatch (NI is in bold). The local stack is configured to a value of 2, and the remote switch is set to 3. 16:11:14.408 MTP3(U) 1160020102030405 XMT 2/02: SNT 0 2 00000a 000080 00 16:11:14.428 MTP3(U) 118015678e0baaff5500 RCV 2/02: SNT 0 3 000080 00000a 00 The network indicator codes are allocated as follows: bits D C 0 0 (1) International network 0 1 (2) Spare (for international use only) 1 0 (3) National network 1 1 (4) Reserved for national use Link status signaling unit size mismatch 680 Troubleshooting By default, the IMGs transmit a Link Status Signaling Unit (LSSU) with a 2-octet status field. Some signaling points may require a LSSU size of 1-octet. Path and rate problem A span carrying the signaling link must be configured for clear channel operation, in service, and not experiencing slips. Both parties must agree upon the timeslots used to carry the signaling link. Additionally, the data rate of the signaling link must be the same on both sides. No route defined A valid SS7 route must be defined to the destination to enable the IMG to send messages. This is typically indicated by received Signaling Link Testing Message (SLTM) with no SLTMs being sent by the IMG. Cantata Technology - IMG 1010 Printable WebHelp 681 IMG WebHelp Call Tracing An Overview of Call Tracing Topic Location: Troubleshooting > Call Tracing Call Tracing allows you to view various information on a per call basis. A Call Trace log includes information such as Call Duration, RTCP Stats, and Codecs. The Call Trace is saved to a log file in the following directory: opt/cantata/common/calltracing Call Trace log files have the following naming convention: syslog_<chassis serial number>_<timestamp>.log Call tracing uses NFS to write the files to the host. If call tracing is not writing to the file verify that the NFS server is running and verify the NFS mount status. Call Trace Format The following is an example of a call trace segment. 18:56:20.045 CALL(SS7) (01:0003:00) RCVD IAM (0x382b:0x813:7) The following is a description of the information segments in a Call Trace entry. Segment 1 - Time stamp 18:56:20.045 CALL(SS7) (01:0003:00) RCVD IAM (0x382b:0x813:7) Segment 2 - IMG call component: 18:56:20.045 CALL(SS7) (01:0003:00) RCVD IAM (0x382b:0x813:7) Internal components: GCL - Routing / Translation L4 - Routing MEDIA - DSP resources FACPFC - VoIP resources External signaling components SS7 H323 ISDN SIP H225 H245 682 Troubleshooting RAS Segment 3 - (IMG Node ID:Call ID:Call leg) 18:56:20.045 CALL(SS7) (01:0003:00) RCVD IAM (0x382b:0x813:7) IMG Node ID - Logical Node ID assigned in ClientView Call ID - Sequential number from 0 - 9999, unique per call Call leg - 0 for events on the inbound channel, 1 for events on the outbound channel Segment 4 - Description of event 18:56:20.045 CALL(SS7) (01:0003:00) RCVD IAM (0x382b:0x813:7) Related Topics Starting a Call Trace Call Trace Example: Successful Call Call Trace Example: No Match Found in Route Table Call Trace Example: No Match Found in Translation Table Cantata Technology - IMG 1010 Printable WebHelp 683 IMG WebHelp Setting Up Call Tracing Topic Location: Troubleshooting > Call Tracing To enable call tracing, you must perform the following: 1. Configure NFS Mount 2. Configure an NFS Server for Call Tracing Configuring NFS Mount You must configure an NFS mount for the call tracing directory: /opt/cantata/common/calltracing. Configuring the NFS server for Call Tracing When configuring an NFS call server, after adding the Client IP and setting the read/write access in the Basic tab, select the "User Access" tab and check the following options: * Treat all client users as anonymous users * Specify local user ID for anonymous users * User ID: 500 * Specify local group ID for anonymous users * Group ID: 500 684 Troubleshooting Note: Setting the User ID to 500 and Group ID to 500, will create the sysLog call trace files with User and Group ID of ‘excelsw’ account. Verify the user ID & Group ID’s for the excelsw account before setting this. Example syslog file: -rw-rw-rw- 1 excelsw excelsw 32199 Aug 16 10:15 sysLog_00902650_20060816_131518.log Cantata Technology - IMG 1010 Printable WebHelp 685 IMG WebHelp Starting a Call Trace Topic Location: Troubleshooting > Call Tracing To enable Call Tracing: 1. Right-click a Physical IMG entry and select New Call Tracing. The Call Tracing pane appears. 2. In the Call Tracing Period field, enter the amount of time you want the trace to occur (1-7200 s) 3. Click the Start/Reset Call Tracing button to begin the trace. 4. When the trace is complete, go to opt/cantata/common/calltracing to view the trace log. To update the Call Tracing Status and Call Tracing Time Remaining fields while a trace is in progress click the Update Status button. To stop the trace before the Trace Period expires, click the Stop Call Tracing button. Related Topic Call Tracing Call Trace Example: Successful Call Call Trace Example: No Match Found in Route Table Call Trace Example: No Match Found in Translation Table Cantata Technology - IMG 1010 Printable WebHelp 686 Troubleshooting Call Trace Example: Successful Call Topic Location: Troubleshooting > Call Tracing SS7 to SIP 18:56:20.045 CALL(SS7) (01:0003:00) RCVD IAM (0x382b:0x813:7) 18:56:20.045 CALL(SS7) (01:0003:00) SENT Setup Ind w/info to L4 (0x382b:0x813:7) 18:56:20.045 CALL(L4) (01:0003:00) RCVD Setup Ind from SS7 18:56:20.045 CALL(L4) (01:0003:00) SENT RFS to GCL 18:56:20.055 CALL(GCL) (01:0003:00) RCVD RFS DN=[6175551212] ANI=[5088623000] from L4 18:56:20.055 CALL(GCL) (01:0003:00) ANI APRI=[0],SI=[1],Category=[10] 18:56:20.055 CALL(GCL) (01:0003:00) Incoming Channel Group=8 18:56:20.055 CALL(L4) (01:0003:00) RCVD RFS response from GCL 18:56:20.055 CALL(GCL) (01:0003:01) SENT Route Control to L4 18:56:20.055 CALL(L4) (01:0003:00) RCVD Route Control from GCL 18:56:20.055 CALL(L4) (01:0003:00) Accessing Route Table 7 18:56:20.055 CALL(GCL) (01:0003:01) RCVD Mid Stream Router Response 18:56:20.055 CALL(GCL) (01:0003:01) Outgoing Channel Group=18 18:56:20.055 CALL(GCL) (01:0003:01) SENT Route Control to L4 18:56:20.055 CALL(L4) (01:0003:01) RCVD Route Control from GCL 18:56:20.055 CALL(L4) (01:0003:01) Accessing Resource Table 149 18:56:20.055 CALL(L4) (01:0003:01) Resource Group ID is 1 18:56:20.055 CALL(L4) (01:0003:01) SENT Outseize Ctrl to SIP 18:56:20.055 CALL(GCL) (01:0003:01) RCVD CPE of ADDRESS INFO from L4 18:56:20.055 CALL(GCL) (01:0003:01) Leg 1 associated with LTS(1792) 18:56:20.055 CALL(SIP) (01:0003:01) RCVD Outseize Ctrl from L4 18:56:20.055 CALL(SIP) (01:0003:01) SENT Route Ctrl to L4 18:56:20.055 CALL(L4) (01:0003:01) RCVD Route Control from SIP 18:56:20.055 CALL(L4) (01:0003:01) Accessing GatewayId to IP Tables 18:56:20.055 CALL(L4) (01:0003:01) Gateway ID is 1040 18:56:20.055 CALL(L4) (01:0003:01) SENT Route Control Ack to SIP 18:56:20.055 CALL(SIP) (01:0003:01) RCVD Route Ctrl Ack from L4 18:56:20.055 CALL(SIP) (01:0003:01) SENT Route Ctrl to L4 18:56:20.055 CALL(L4) (01:0003:01) RCVD Route Control from SIP 687 IMG WebHelp 18:56:20.055 CALL(L4) (01:0003:01) Accessing IP Bearer Profiles 18:56:20.055 CALL(L4) (01:0003:01) Profile Id 1 (RG 769) 18:56:20.055 CALL(L4) (01:0003:01) SENT Route Control Ack to SIP 18:56:20.065 CALL(SIP) (01:0003:01) RCVD Route Ctrl Ack from L4 18:56:20.065 CALL(SIP) (01:0003:01) SENT INVITE to 10.129.51.137:5060 18:56:20.115 CALL(SIP) (01:0003:01) RCVD 100 Trying 18:56:20.375 CALL(SIP) (01:0003:01) RCVD 180 Ringing 18:56:20.375 CALL(SIP) (01:0003:01) SENT Outseize Ack to L4 18:56:20.375 CALL(SIP) (01:0003:01) SENT Alerting to L4 18:56:20.375 CALL(L4) (01:0003:01) RCVD Outseize ACK from SIP 18:56:20.375 CALL(L4) (01:0003:01) RVCD Alerting from SIP 18:56:20.375 CALL(GCL) (01:0003:00) SENT Connect Response to L4 18:56:20.375 CALL(L4) (01:0003:00) RCVD Connect A/B from GCL 18:56:20.375 CALL(L4) (01:0003:00) SENT Alerting to SS7 18:56:20.375 CALL(SIP) (01:0003:01) RCVD Host Connect from L4 18:56:20.375 CALL(SS7) (01:0003:00) RCVD Alerting from L4 (0x813:0x382b:7) 18:56:20.375 CALL(SS7) (01:0003:00) SENT ACM (0x813:0x382b:7) 18:56:24.395 CALL(SIP) (01:0003:01) RCVD 200 OK 18:56:24.395 CALL(SIP) (01:0003:01) SENT ACK to 10.129.51.137:5060 18:56:24.395 CALL(SIP) (01:0003:01) m line codec list: 8 101 18:56:24.395 CALL(SIP) (01:0003:01) RTMAP type: 8, name: PCMA, clk: 8000 18:56:24.395 CALL(SIP) (01:0003:01) RTMAP type: 101, name: telephone-event, clk: 8000 18:56:24.395 CALL(SIP) (01:0003:01) SENT L3-L3 Outseize Ctrl to VPPL 18:56:24.395 CALL(IP) (01:0003:01) RCVD Outseize from L3, [vts 768] [m1.0.0] 18:56:24.395 CALL(IP) (01:0003:01) RTP: (Src) 10.129.51.134:11072 18:56:24.395 CALL(IP) (01:0003:01) RTP: (Dst) 10.129.51.137:49158 18:56:24.405 CALL(IP) (01:0003:01) VoIP Codec is G711Alaw_64; Payload Size is 20 ms 18:56:24.405 CALL(IP) (01:0003:01) RFC2833 DTMF Relay in use, Dynamic Payload Type is 101 18:56:24.415 CALL(IP) (01:0003:01) SENT Outseize ACK to L3P, toPvid: x66 18:56:24.415 CALL(SIP) (01:0003:01) RCVD Outseize Ack from VPPL 18:56:24.415 CALL(SIP) (01:0003:01) SENT Connect to L4 18:56:24.415 CALL(SIP) (01:0003:01) RCVD Cut Thru from VPPL 18:56:24.415 CALL(SIP) (01:0003:01) RCVD Connect from VPPL 18:56:24.415 CALL(L4) (01:0003:01) RCVD Connect from SIP 688 Troubleshooting 18:56:24.415 CALL(L4) (01:0003:01) SENT CPE of ANSWER to GCL 18:56:24.415 CALL(GCL) (01:0003:01) RCVD CPE of ANSWER from L4 18:56:24.415 CALL(GCL) (01:0003:00) SENT CPE of ANSWER to L4 18:56:24.415 CALL(L4) (01:0003:00) RCVD CPE of ANSWER from GCL 18:56:24.415 CALL(L4) (01:0003:00) SENT Connect to SS7 18:56:24.415 CALL(L4) (01:0003:01) SENT Connect to SIP 18:56:24.415 CALL(SS7) (01:0003:00) RCVD Connect from L4 (0x813:0x382b:7) 18:56:24.415 CALL(SS7) (01:0003:00) SENT ANM (0x813:0x382b:7) 18:56:24.415 CALL(SIP) (01:0003:01) RCVD Connect from L4 18:56:41.075 CALL(SS7) (01:0003:00) RCVD REL (0x382b:0x813:7) cause 31 18:56:41.075 CALL(SS7) (01:0003:00) SENT Disconnect to L4 (0x382b:0x813:7) 18:56:41.075 CALL(L4) (01:0003:00) RCVD Disconnect from SS7 18:56:41.075 CALL(L4) (01:0003:00) SENT Clear Request to SS7 18:56:41.075 CALL(SS7) (01:0003:00) RCVD Clear Request from L4 (0x813:0x382b:7) 18:56:41.075 CALL(SS7) (01:0003:00) SENT Clear Request to L4 (0x382b:0x813:7) 18:56:41.075 CALL(SS7) (01:0003:00) SENT RLC (0x813:0x382b:7) 18:56:41.085 CALL(L4) (01:0003:00) RCVD Clear request from SS7 18:56:41.085 CALL(L4) (01:0003:00) SENT Channel Release w/data to GCL 18:56:41.085 CALL(GCL) (01:0003:00) RCVD Channel Released w/data from L4 18:56:41.085 CALL(GCL) (01:0003:00) Call Duration(sec): 17 18:56:41.085 CALL(GCL) (01:0003:01) SENT Clear Response to L4 18:56:41.085 CALL(GCL) (01:0003:00) Radius Call Duration(sec): 17 18:56:41.085 CALL(L4) (01:0003:01) RCVD Clear from GCL 18:56:41.085 CALL(L4) (01:0003:01) SENT Clear Request to SIP 18:56:41.085 CALL(SIP) (01:0003:01) RCVD Clear Request from L4 18:56:41.085 CALL(SIP) (01:0003:01) SENT BYE to 10.129.51.137:5060 18:56:41.095 CALL(SIP) (01:0003:01) RCVD 200 OK 18:56:41.095 CALL(SIP) (01:0003:01) SENT L3-L3 Clear Req to VPPL 18:56:41.095 CALL(IP) (01:0003:01) RCVD Clear Request from L3 18:56:41.095 CALL(IP) (01:0003:01) RTCP STATS: TxPackets=832; RxPackets=834; lostPackets=0 18:56:41.095 CALL(SIP) (01:0003:01) RCVD Clear Req from VPPL 18:56:41.095 CALL(SIP) (01:0003:01) SENT Clear Request to L4 18:56:41.095 CALL(L4) (01:0003:01) RCVD Clear request from SIP 18:56:41.095 CALL(L4) (01:0003:01) SENT Channel Release w/data to GCL 689 IMG WebHelp 18:56:41.095 CALL(GCL) (01:0003:01) RCVD Channel Released w/data from L4 18:56:41.095 CALL(GCL) (01:0003:01) Call Duration(sec): 17 18:56:41.095 CALL(GCL) (01:0003:01) Radius Call Duration(sec): 17 Cantata Technology - IMG 1010 Printable WebHelp 690 Troubleshooting Call Trace Example: No Match found in the translation table Topic Location: Troubleshooting > Call Tracing # Returns a cause code of Unallocated (unassigned) number 19:53:13.806 CALL(SS7) (01:0007:00) RCVD IAM (0x382b:0x813:11) 19:53:13.806 CALL(SS7) (01:0007:00) SENT Setup Ind w/info to L4 (0x382b:0x813:11) 19:53:13.806 CALL(L4) (01:0007:00) RCVD Setup Ind from SS7 19:53:13.806 CALL(L4) (01:0007:00) SENT RFS to GCL 19:53:13.806 CALL(GCL) (01:0007:00) RCVD RFS DN=[7563214589] ANI=[5088623000] from L4 19:53:13.806 CALL(GCL) (01:0007:00) ANI APRI=[0],SI=[1],Category=[10] 19:53:13.806 CALL(GCL) (01:0007:00) Incoming Channel Group=8 19:53:13.806 CALL(GCL) (01:0007:00) DPE Input :DN=[7563214589] ANI=[5088623000] 19:53:13.806 CALL(GCL) (01:0007:00) Invoke Incoming DPE 1; Channel Group 8 19:53:13.806 CALL(GCL) (01:0007:00) DPE response: No Match 19:53:13.806 CALL(GCL) (01:0007:00) DPE Output:DN=[7563214589] ANI=[5088623000] 19:53:13.806 CALL(GCL) (01:0007:00) SENT Clear Response to L4 19:53:13.806 CALL(L4) (01:0007:00) RCVD RFS response from GCL 19:53:13.806 CALL(L4) (01:0007:00) RCVD Clear from GCL 19:53:13.806 CALL(L4) (01:0007:00) SENT Clear Request to SS7 19:53:13.806 CALL(SS7) (01:0007:00) RCVD Clear Request from L4 (0x813:0x382b:11) 19:53:13.806 CALL(SS7) (01:0007:00) SENT REL (0x813:0x382b:11) cause 1 19:53:13.866 CALL(SS7) (01:0007:00) RCVD RLC (0x382b:0x813:11) 19:53:13.866 CALL(SS7) (01:0007:00) SENT Clear Request to L4 (0x382b:0x813:11) 19:53:13.876 CALL(L4) (01:0007:00) RCVD Clear request from SS7 19:53:13.876 CALL(L4) (01:0007:00) SENT Channel Release w/data to GCL 19:53:13.876 CALL(GCL) (01:0007:00) RCVD Channel Released w/data from L4 19:53:13.876 CALL(GCL) (01:0007:00) Call Duration(sec): 0 19:53:13.876 CALL(GCL) (01:0007:00) Radius Call Duration(sec): 0 Cantata Technology - IMG 1010 Printable WebHelp 691 IMG WebHelp Call Trace Example: No Match Found in Route Table Topic Location: Troubleshooting > Call Tracing # Returns a cause code of No route to destination 19:49:44.096 CALL(SS7) (01:0006:00) RCVD IAM (0x382b:0x813:10) 19:49:44.096 CALL(SS7) (01:0006:00) SENT Setup Ind w/info to L4 (0x382b:0x813:10) 19:49:44.096 CALL(L4) (01:0006:00) RCVD Setup Ind from SS7 19:49:44.096 CALL(L4) (01:0006:00) SENT RFS to GCL 19:49:44.096 CALL(GCL) (01:0006:00) RCVD RFS DN=[7563214589] ANI=[5088623000] from L4 19:49:44.096 CALL(GCL) (01:0006:00) ANI APRI=[0],SI=[1],Category=[10] 19:49:44.096 CALL(GCL) (01:0006:00) Incoming Channel Group=8 19:49:44.096 CALL(L4) (01:0006:00) RCVD RFS response from GCL 19:49:44.096 CALL(GCL) (01:0006:01) SENT Route Control to L4 19:49:44.096 CALL(L4) (01:0006:00) RCVD Route Control from GCL 19:49:44.096 CALL(L4) (01:0006:00) Accessing Route Table 7(m) 19:49:44.096 CALL(L4) (01:0006:00) No routing table, or match in routing table found 19:49:44.096 CALL(L4) (01:0006:00) No Match Found in Router Table !!!! 19:49:44.096 CALL(L4) (01:0006:00) SENT Route Control NACK(81) to GCL 19:49:44.096 CALL(GCL) (01:0006:01) RCVD Mid Stream Router Response 19:49:44.096 CALL(GCL) (01:0006:00) SENT Clear Response to L4 19:49:44.096 CALL(L4) (01:0006:00) RCVD Clear from GCL 19:49:44.096 CALL(L4) (01:0006:00) SENT Clear Request to SS7 19:49:44.096 CALL(SS7) (01:0006:00) RCVD Clear Request from L4 (0x813:0x382b:10) 19:49:44.096 CALL(SS7) (01:0006:00) SENT REL (0x813:0x382b:10) cause 3 19:49:44.166 CALL(SS7) (01:0006:00) RCVD RLC (0x382b:0x813:10) 19:49:44.166 CALL(SS7) (01:0006:00) SENT Clear Request to L4 (0x382b:0x813:10) 19:49:44.166 CALL(L4) (01:0006:00) RCVD Clear request from SS7 19:49:44.166 CALL(L4) (01:0006:00) SENT Channel Release w/data to GCL 19:49:44.166 CALL(GCL) (01:0006:00) RCVD Channel Released w/data from L4 19:49:44.166 CALL(GCL) (01:0006:00) Call Duration(sec): 0 19:49:44.166 CALL(GCL) (01:0006:00) Radius Call Duration(sec): 0 692 Troubleshooting Cantata Technology - IMG 1010 Printable WebHelp 693 IMG WebHelp Payload Types in Call Trace Topic Location: Troubleshooting > Call Tracing Use this table to interpret the payload type (PT) in the m line of a call trace. See Sample Call Trace - Codecs. 694 Troubleshooting Cantata Technology - IMG 1010 Printable WebHelp 695 IMG WebHelp Sample Call Traces Sample Call Trace - Fax Fallback Topic Location: Troubleshooting > Sample Call Traces 18:00:36.615 CALL(SIP) (00:0001:00) RCVD x006e from VPPL 18:00:36.615 CALL(SIP) (00:0001:00) SENT INVITE to 10.129.39.65:5060 18:00:36.615 SIP (W) <--- [10.129.39.65, 5060 <- 10.129.39.37, 5060] INVITE sip:[email protected] SIP/2.0 Via: SIP/2.0/UDP 10.129.39.37:5060;rport;branch=z9hG4bK35c7-1147197636-19999-302 Call-ID: [email protected] CSeq: 1 INVITE Max-Forwards: 70 To: <sip:[email protected]>;tag=64c6310ffd460e7e From: <sip:[email protected]>;tag=a94c095b773be1dd6e8d66 8a785a9c84e0d2 User-Agent: Cantata-SIP/10.3.1.405 Bernard 0 Timestamp: 05092006180036 Contact: <sip:10.129.39.37:5060> Allow: INVITE, BYE, REGISTER, ACK, OPTIONS, CANCEL, INFO Supported: path Expires: 300 Organization: Cantata Technology Inc Content-Type: application/sdp Content-Length: 351 v=0 o=Cantata_SDP 0 0 IN IP4 10.129.39.37 s=Cantata-SIP c=IN IP4 10.129.39.40 t=0 0 m=image 8002 udptl t38 a=T38FaxVersion:0 a=T38MaxBitRate:9600 a=T38FaxFillBitRemoval:0 696 Troubleshooting a=T38FaxTranscodingMMR:0 a=T38FaxTranscodingJBIG:0 a=T38FaxRateManagement:transferredTCF a=T38FaxMaxBuffer:200 a=T38FaxMaxDatagram:72 a=T38FaxUdpEC:t38UDPRedundancy 18:00:36.625 CALL(SIP) (00:0001:01) RCVD x006e from VPPL 18:00:36.645 SIP (W) ---> [10.129.39.65, 5060] SIP/2.0 488 Not Acceptable Here Via: SIP/2.0/UDP 10.129.39.37:5060;rport;branch=z9hG4bK35c7-1147197636-19999-302 From: <sip:[email protected]>;tag=a94c095b773be1dd6e8d66 8a785a9c84e0d2 To: <sip:[email protected]>;tag=64c6310ffd460e7e Call-ID: [email protected] CSeq: 1 INVITE User-Agent: Grandstream HT487 1.0.6.7 Warning: 304 GS "Media type not available" Content-Length: 0 18:00:36.645 CALL(SIP) (00:0001:00) RCVD 488 Not Acceptable Here 18:00:36.645 CALL(SIP) (00:0001:00) SENT ACK to 10.129.39.65:5060 18:00:36.645 SIP (W) <--- [10.129.39.65, 5060 <- 10.129.39.37, 5060] ACK sip:[email protected] SIP/2.0 Via: SIP/2.0/UDP 10.129.39.37:5060;rport;branch=z9hG4bK35c7-1147197636-19999-302 Call-ID: [email protected] CSeq: 1 ACK Max-Forwards: 70 To: <sip:[email protected]>;tag=64c6310ffd460e7e From: <sip:[email protected]>;tag=a94c095b773be1dd6e8d66 8a785a9c84e0d2 User-Agent: Cantata-SIP/10.3.1.405 Bernard 0 Content-Length: 0 18:00:36.645 CALL(SIP) (00:0001:00) SENT INVITE to 10.129.39.65:5060 697 IMG WebHelp 18:00:36.645 SIP (W) <--- [10.129.39.65, 5060 <- 10.129.39.37, 5060] INVITE sip:[email protected] SIP/2.0 Via: SIP/2.0/UDP 10.129.39.37:5060;rport;branch=z9hG4bK6a3a-1147197636-19999-302 Call-ID: [email protected] CSeq: 2 INVITE Max-Forwards: 70 To: <sip:[email protected]>;tag=64c6310ffd460e7e From: <sip:[email protected]>;tag=a94c095b773be1dd6e8d66 8a785a9c84e0d2 User-Agent: Cantata-SIP/10.3.1.405 Bernard 0 Timestamp: 05092006180036 Contact: <sip:10.129.39.37:5060> Allow: INVITE, BYE, REGISTER, ACK, OPTIONS, CANCEL, INFO Supported: path Expires: 300 Organization: Cantata Technology Inc Content-Type: application/sdp Content-Length: 113 v=0 o=Cantata_SDP 0 0 IN IP4 10.129.39.37 s=Cantata-SIP c=IN IP4 10.129.39.40 t=0 0 m=audio 8000 RTP/AVP 0 18:00:36.665 SIP (W) ---> [10.129.39.65, 5060] SIP/2.0 200 OK Via: SIP/2.0/UDP 10.129.39.37:5060;rport;branch=z9hG4bK6a3a-1147197636-19999-302 From: <sip:[email protected]>;tag=a94c095b773be1dd6e8d66 8a785a9c84e0d2 To: <sip:[email protected]>;tag=64c6310ffd460e7e Call-ID: [email protected] CSeq: 2 INVITE 698 Troubleshooting User-Agent: Grandstream HT487 1.0.6.7 Contact: <sip:[email protected]> Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,S UBSCRIBE Content-Type: application/sdp Supported: replaces Content-Length: 155 v=0 o=2222 8000 8001 IN IP4 10.129.39.65 s=SIP Call c=IN IP4 10.129.39.65 t=0 0 m=audio 5004 RTP/AVP 0 a=sendrecv a=rtpmap:0 PCMU/8000 a=ptime:20 18:00:36.665 CALL(SIP) (00:0001:00) RCVD 200 OK 18:00:36.665 CALL(SIP) (00:0001:00) SENT Notify Ack to L4 18:00:36.665 CALL(SIP) (00:0001:00) SENT ACK to 10.129.39.65:5060 18:00:36.665 SIP (W) <--- [10.129.39.65, 5060 <- 10.129.39.37, 5060] ACK sip:[email protected] SIP/2.0 Via: SIP/2.0/UDP 10.129.39.37:5060;rport;branch=z9hG4bK1db7-1147197636-19999-302 Call-ID: [email protected] CSeq: 2 ACK Max-Forwards: 70 To: <sip:[email protected]>;tag=64c6310ffd460e7e From: <sip:[email protected]>;tag=a94c095b773be1dd6e8d66 8a785a9c84e0d2 User-Agent: Cantata-SIP/10.3.1.405 Bernard 0 Content-Length: 0 18:00:36.665 CALL(SIP) (00:0001:00) m line codec list: 0 18:00:36.665 CALL(SIP) (00:0001:00) RTMAP type: 0, name: PCMU, clk: 8000 Cantata Technology - IMG 1010 Printable WebHelp 699 IMG WebHelp Sample Call Trace - Codecs Topic Location: Troubleshooting > Sample Call Traces The media list (m line) in a call trace (shown in blue) indicates the codecs negotiated. To interpret the codec values, see Payload Type Values in Call Trace. > 01:23:53.070 CALL(SIP) (00:0013:00) RCVD INVITE from 192.168.2.14:5060 UDP 01:23:53.070 CALL(SIP) (00:0013:00) with Via sent-by: 192.168.2.14 01:23:53.070 CALL(SIP) (00:0013:00) SENT 100 Trying [] to 192.168.2.14:5060 01:23:53.070 CALL(SIP) (00:0013:00) SENT Route Ctrl to L4 01:23:53.070 CALL(L4) (00:0013:00) RCVD Route Control from SIP 01:23:53.070 CALL(L4) (00:0013:00) Accessing Route Table 2 01:23:53.070 CALL(L4) (00:0013:00) Accessing Resource Table 1 01:23:53.070 CALL(L4) (00:0013:00) SENT Route Control Ack to SIP 01:23:53.070 CALL(SIP) (00:0013:00) RCVD Route Ctrl Ack from L4 01:23:53.070 CALL(SIP) (00:0013:00) Session Group Profile ID is 0 01:23:53.070 CALL(SIP) (00:0013:00) SENT Route Ctrl to L4 01:23:53.070 CALL(L4) (00:0013:00) RCVD Route Control from SIP 01:23:53.070 CALL(L4) (00:0013:00) Accessing IP Bearer Profiles 01:23:53.070 CALL(L4) (00:0013:00) Profile Id 1 (RG 769) 01:23:53.070 CALL(L4) (00:0013:00) SENT Route Control Ack to SIP 01:23:53.070 CALL(SIP) (00:0013:00) RCVD Route Ctrl Ack from L4 01:23:53.070 CALL(SIP) (00:0013:00) m line codec list: 0 8 18 98 101 01:23:53.070 CALL(SIP) (00:0013:00) RTP Type: 0, name: PCMU, clk: 8000 01:23:53.070 CALL(SIP) (00:0013:00) RTP Type: 8, name: PCMA, clk: 8000 01:23:53.070 CALL(SIP) (00:0013:00) RTP Type: 18, name: G729, clk: 8000 01:23:53.070 CALL(SIP) (00:0013:00) RTP Type: 98, name: iLBC, clk: 8000 01:23:53.070 CALL(SIP) (00:0013:00) RTP Type: 101, name: telephone-event, clk: 8000 01:23:53.070 CALL(SIP) (00:0013:00) Leg 0 associated with hndl(19983), LTS(1808) 01:23:53.070 CALL(SIP) (00:0013:00) SENT Setup to L4 01:23:53.070 CALL(L4) (00:0013:00) RCVD Setup Ind from SIP 01:23:53.070 CALL(L4) (00:0013:00) SENT RFS to GCL 01:23:53.070 CALL(GCL) (00:0013:00) RCVD RFS DN=[8623001] ANI=[8623000] from L4 01:23:53.070 CALL(GCL) (00:0013:00) ANI APRI=[0],SI=[0],Category=[10] 700 Troubleshooting 01:23:53.070 CALL(GCL) (00:0013:00) Incoming Channel Group = 1 [dellsoftclients] 01:23:53.070 CALL(GCL) (00:0013:01) SENT Route Control to L4 01:23:53.070 CALL(L4) (00:0013:00) RCVD RFS response from GCL 01:23:53.070 CALL(L4) (00:0013:00) RCVD Route Control from GCL 01:23:53.070 CALL(L4) (00:0013:00) Accessing Route Table 5 01:23:53.070 CALL(GCL) (00:0013:01) RCVD Mid Stream Router Response 01:23:53.070 CALL(GCL) (00:0013:01) Outgoing Channel Group = 0 [ibmsoftclients] 01:23:53.070 CALL(GCL) (00:0013:01) SENT Route Control to L4 01:23:53.070 CALL(L4) (00:0013:01) RCVD Route Control from GCL 01:23:53.070 CALL(L4) (00:0013:01) Accessing Resource Table 1 01:23:53.070 CALL(L4) (00:0013:01) Resource Group ID is 1 01:23:53.080 CALL(L4) (00:0013:01) SENT Outseize Ctrl to SIP 01:23:53.080 CALL(GCL) (00:0013:01) RCVD CPE of ADDRESS INFO from L4 01:23:53.080 CALL(GCL) (00:0013:01) Leg 1 associated with LTS(1809) 01:23:53.080 CALL(SIP) (00:0013:01) RCVD Outseize Ctrl from L4 01:23:53.080 CALL(SIP) (00:0013:01) SENT Route Ctrl to L4 01:23:53.080 CALL(L4) (00:0013:01) RCVD Route Control from SIP 01:23:53.080 CALL(L4) (00:0013:01) Accessing GatewayId to IP Tables 01:23:53.080 CALL(L4) (00:0013:01) Gateway ID is 1025 01:23:53.080 CALL(L4) (00:0013:01) SENT Route Control Ack to SIP 01:23:53.080 CALL(SIP) (00:0013:01) RCVD Route Ctrl Ack from L4 01:23:53.080 CALL(SIP) (00:0013:01) Session Group Profile ID is 0 01:23:53.080 CALL(SIP) (00:0013:01) SENT Route Ctrl to L4 01:23:53.080 CALL(L4) (00:0013:01) RCVD Route Control from SIP 01:23:53.080 CALL(L4) (00:0013:01) Accessing IP Bearer Profiles 01:23:53.080 CALL(L4) (00:0013:01) Profile Id 1 (RG 769) 01:23:53.080 CALL(L4) (00:0013:01) SENT Route Control Ack to SIP 01:23:53.080 CALL(SIP) (00:0013:01) RCVD Route Ctrl Ack from L4 01:23:53.080 CALL(SIP) (00:0013:01) SENT INVITE to 192.168.2.11:5060 UDP 01:23:53.080 CALL(SIP) (00:0013:01) with R-URI: 192.168.2.11:5060 UDP 01:23:53.150 CALL(SIP) (00:0013:01) RCVD 180 Ringing from 192.168.2.11:5060 UDP 01:23:53.150 CALL(SIP) (00:0013:01) SENT Outseize Ack to L4 01:23:53.150 CALL(SIP) (00:0013:01) SENT Alerting to L4 01:23:53.150 CALL(L4) (00:0013:01) RCVD Outseize ACK from SIP 01:23:53.150 CALL(L4) (00:0013:01) RVCD Alerting from SIP 701 IMG WebHelp 01:23:53.150 CALL(GCL) (00:0013:00) SENT Connect Tone to L4 01:23:53.150 CALL(L4) (00:0013:00) RCVD Connect Tone from GCL 01:23:53.150 CALL(L4) (00:0013:00) SENT Request DSP Service to SYSRM 01:23:53.150 CALL(MED) (00:0013:00) Transmitting tone 0x2 on (0x0,0x1,0x1) 01:23:53.150 CALL(MED) (00:0013:00) RCVD OUTPULSE CP 01:23:53.150 CALL(GCL) (00:0013:00) SENT Connect w/Pad Response to L4 01:23:53.150 CALL(L4) (00:0013:00) SENT Progress to SIP 01:23:53.150 CALL(SIP) (00:0013:01) RCVD Host Connect from L4 01:23:53.150 CALL(SIP) (00:0013:00) RCVD Progress from L4 01:23:53.150 CALL(SIP) (00:0013:00) Set Fax Type to Bypass 01:23:53.150 CALL(SIP) (00:0013:00) SENT L3-L3 Outseize Ctrl to VPPL 01:23:53.150 CALL(IP) (00:0013:00) RCVD Outseize from L3, [vts 784] [m1.0.4] 01:23:53.150 CALL(IP) (00:0013:00) RTP: (Src) 192.168.2.72:11136 01:23:53.150 CALL(IP) (00:0013:00) RTP: (Dst) 192.168.2.14:10268 01:23:53.160 CALL(IP) (00:0013:00) VoIP Codec is G711Mulaw; Payload Size is 20 ms 01:23:53.160 CALL(IP) (00:0013:00) RFC2833 DTMF Relay in use, Dynamic Payload Type is 101 01:23:53.170 CALL(IP) (00:0013:00) SENT Outseize ACK to L3P, toPvid: x66 01:23:53.170 CALL(SIP) (00:0013:00) RCVD Outseize Ack from VPPL 01:23:53.170 CALL(SIP) (00:0013:00) SENT 183 Session Progress to 192.168.2.14:5060 UDP 01:23:53.170 CALL(SIP) (00:0013:00) RCVD Cut Thru from VPPL 01:23:53.170 CALL(SIP) (00:0013:00) RCVD Connect from VPPL 01:23:56.350 CALL(SIP) (00:0013:01) RCVD 200 OK from 192.168.2.11:5060 UDP 01:23:56.350 CALL(SIP) (00:0013:01) SENT ACK to 192.168.2.11:5060 UDP 01:23:56.350 CALL(SIP) (00:0013:01) with R-URI: 192.168.2.11:5060 UDP 01:23:56.350 CALL(SIP) (00:0013:01) m line codec list: 0 98 8 18 01:23:56.350 CALL(SIP) (00:0013:01) RTP Type: 0, name: PCMU, clk: 8000 01:23:56.350 CALL(SIP) (00:0013:01) RTP Type: 98, name: iLBC, clk: 8000 01:23:56.350 CALL(SIP) (00:0013:01) RTP Type: 8, name: PCMA, clk: 8000 01:23:56.350 CALL(SIP) (00:0013:01) RTP Type: 18, name: G729, clk: 8000 01:23:56.350 CALL(SIP) (00:0013:01) Set Fax Type to Bypass 01:23:56.350 CALL(SIP) (00:0013:01) SENT L3-L3 Outseize Ctrl to VPPL 01:23:56.350 CALL(IP) (00:0013:01) RCVD Outseize from L3, [vts 785] [m1.1.4] 01:23:56.350 CALL(IP) (00:0013:01) RTP: (Src) 192.168.2.72:11140 01:23:56.350 CALL(IP) (00:0013:01) RTP: (Dst) 192.168.2.11:6110 702 Troubleshooting 01:23:56.460 CALL(IP) (00:0013:01) VoIP Codec is G711Mulaw; Payload Size is 20 ms 01:23:56.470 CALL(IP) (00:0013:01) SENT Outseize ACK to L3P, toPvid: x66 01:23:56.470 CALL(SIP) (00:0013:01) RCVD Outseize Ack from VPPL 01:23:56.470 CALL(SIP) (00:0013:01) SENT Connect to L4 01:23:56.470 CALL(SIP) (00:0013:01) RCVD Cut Thru from VPPL 01:23:56.470 CALL(SIP) (00:0013:01) RCVD Connect from VPPL 01:23:56.470 CALL(L4) (00:0013:01) RCVD Connect from SIP 01:23:56.470 CALL(L4) (00:0013:01) SENT CPE of ANSWER to GCL 01:23:56.470 CALL(GCL) (00:0013:01) RCVD CPE of ANSWER from L4 01:23:56.470 CALL(GCL) (00:0013:00) SENT Disconnect Tone to L4 01:23:56.470 CALL(L4) (00:0013:00) RCVD Disconnect Tone from GCL 01:23:56.470 CALL(L4) (00:0013:00) SENT Cancel DSP Service to SYSRM 01:23:56.470 CALL(MED) (00:0013:00) RCVD CANCEL OUTPULSE CP 01:23:56.470 CALL(MED) (00:0013:00) RCVD CANCEL OUTPULSE DIGITS 01:23:56.470 CALL(GCL) (00:0013:00) SENT CPE of ANSWER to L4 01:23:56.470 CALL(L4) (00:0013:00) RCVD CPE of ANSWER from GCL 01:23:56.470 CALL(L4) (00:0013:00) SENT Connect to SIP 01:23:56.470 CALL(L4) (00:0013:01) SENT Connect to SIP 01:23:56.470 CALL(SIP) (00:0013:00) RCVD Connect from L4 01:23:56.470 CALL(SIP) (00:0013:00) SENT 200 OK to 192.168.2.14:5060 UDP 01:23:56.470 CALL(SIP) (00:0013:01) RCVD Connect from L4 01:23:56.490 CALL(SIP) (00:0013:00) RCVD ACK from 192.168.2.14 UDP 01:23:56.490 CALL(SIP) (00:0013:00) with Via sent-by: 192.168.2.14 01:24:20.870 CALL(SIP) (00:0013:00) with Via sent-by: 192.168.2.14 UDP 01:24:20.870 CALL(SIP) (00:0013:00) RCVD BYE from 192.168.2.14:5060 UDP 01:24:20.870 CALL(SIP) (00:0013:00) SENT L3-L3 Clear Req to VPPL 01:24:20.870 CALL(IP) (00:0013:00) RCVD Clear Request from L3 01:24:20.870 CALL(IP) (00:0013:00) RTCP STATS: TxPackets=1384; RxPackets=5; lostPackets=0 01:24:20.870 CALL(IP) (00:0013:00) RTCP/T38 Packet STATS: TxPackets=1384; RxPackets=5; lostPackets=0 01:24:20.870 CALL(SIP) (00:0013:00) RCVD Clear Req from VPPL 01:24:20.870 CALL(SIP) (00:0013:00) SENT Clear Request to L4 01:24:20.870 CALL(SIP) (00:0013:00) SENT 200 OK to 192.168.2.14:5060 UDP 01:24:20.870 CALL(L4) (00:0013:00) RCVD Clear request from SIP 01:24:20.870 CALL(L4) (00:0013:00) SENT Channel Release w/data to GCL 703 IMG WebHelp 01:24:20.870 CALL(GCL) (00:0013:00) RCVD Channel Released w/data from L4 01:24:20.870 CALL(GCL) (00:0013:00) Call Duration(sec): 24 01:24:20.870 CALL(GCL) (00:0013:01) SENT Clear Response to L4 01:24:20.870 CALL(L4) (00:0013:01) RCVD Clear from GCL 01:24:20.870 CALL(L4) (00:0013:01) SENT Clear Request to SIP 01:24:20.870 CALL(SIP) (00:0013:01) RCVD Clear Request from L4 01:24:20.870 CALL(SIP) (00:0013:01) SENT BYE to 192.168.2.11:5060 UDP 01:24:20.870 CALL(SIP) (00:0013:01) with R-URI: 192.168.2.11:5060 UDP 01:24:20.930 CALL(SIP) (00:0013:01) RCVD 200 OK from 192.168.2.11:5060 UDP 01:24:20.930 CALL(SIP) (00:0013:01) SENT L3-L3 Clear Req to VPPL 01:24:20.930 CALL(IP) (00:0013:01) RCVD Clear Request from L3 01:24:20.930 CALL(IP) (00:0013:01) RTCP STATS: TxPackets=1222; RxPackets=63; lostPackets=0 01:24:20.930 CALL(IP) (00:0013:01) RTCP/T38 Packet STATS: TxPackets=1222; RxPackets=63; lostPackets=0 01:24:20.930 CALL(SIP) (00:0013:01) RCVD Clear Req from VPPL 01:24:20.930 CALL(SIP) (00:0013:01) SENT Clear Request to L4 01:24:20.930 CALL(L4) (00:0013:01) RCVD Clear request from SIP 01:24:20.930 CALL(L4) (00:0013:01) SENT Channel Release w/data to GCL 01:24:20.930 CALL(GCL) (00:0013:01) RCVD Channel Released w/data from L4 01:24:20.930 CALL(GCL) (00:0013:01) Call Duration(sec): 24 Cantata Technology - IMG 1010 Printable WebHelp 704 Troubleshooting Call Trace Example - SIP to SS7 Topic Location: Troubleshooting > Sample Call Traces The following is an example showing the enabling of Call Tracing for SIP and SS7 and the resultant call trace log. Comments are in Bold. To see the associated RADIUS CDR, click here. Trying 192.168.19.52... Connected to img (192.168.19.52). Escape character is 'ˆ]'. username: excel Password: *** NOT Clearing GEL Print Buffer *** > # Entering the SS7 menu >3 L3> s # Enabling SS7 ISUP trace ss7> a0 ISUP/TUP SU Diagnostics Enabled for stack 0 # Exiting to main menu ss7> q L3> q # Entering the SIP menu >S # Enabling the SIP trace SIP> 1 SIP PDU Printing Enabled # Exiting to main menu SIP> q # Entering the call trace menu >W GEL> 29 # Enabling call tracing CALL> P 705 IMG WebHelp -- Logging & Printing All Events -15:47:39.959 SIP (W) ---> [10.129.51.140, 1053] INVITE sip:[email protected]:5060 SIP/2.0 Via: SIP/2.0/UDP 10.129.51.140 To: 5088625347<sip:[email protected]:5060> From: 6175551212<sip:[email protected]:5060>;tag=117938002f7f75 Call-ID: [email protected] Contact: 6175551212<sip:[email protected]:5060> User-Agent: Excel_CSP/82.30.189 Supported: timer Session-Expires: 1800 Min-SE: 300 CSeq: 1 INVITE Content-Type: application/sdp Content-Length: 105 v=0 o=sip 0 0 IN IP4 10.129.51.140 s=SIP_Call c=IN IP4 10.129.51.144 t=0 0 m=audio 12716 RTP/AVP 0 15:47:39.959 SIP (W) <--- [10.129.51.140, 5060 <- 10.129.51.152, 5060] SIP/2.0 100 Trying Via: SIP/2.0/UDP 10.129.51.140;received=10.129.51.140 Call-ID: [email protected] From: 6175551212<sip:[email protected]:5060>;tag= 117938002f7f75 To: 5088625347<sip:[email protected]:5060> CSeq: 1 INVITE Server: Cantata-SIP/10.3.2.105 E1_System 1 Content-Length: 0 706 Troubleshooting 15:47:39.959 CALL(SIP) (01:0001:00) RCVD INVITE from 10.129.51.140:0 UDP 15:47:39.959 CALL(SIP) (01:0001:00) with Via sent-by: 10.129.51.140 15:47:39.959 CALL(SIP) (01:0001:00) SENT 100 Trying to 10.129.51.140:0 15:47:39.959 CALL(SIP) (01:0001:00) SENT Route Ctrl to L4 15:47:39.959 CALL(L4) (01:0001:00) RCVD Route Control from SIP 15:47:39.959 CALL(L4) (01:0001:00) Accessing Route Table 2 15:47:39.959 CALL(L4) (01:0001:00) Accessing Resource Table 1 15:47:39.959 CALL(L4) (01:0001:00) IP Traffic Management: Resource Group ID: 2 568 Busy Count: 1 Channels Allowed: 1024 15:47:39.959 CALL(L4) (01:0001:00) SENT Route Control Ack to SIP 15:47:39.959 CALL(SIP) (01:0001:00) RCVD Route Ctrl Ack from L4 15:47:39.959 CALL(SIP) (01:0001:00) Session Group Profile ID is 0 15:47:39.959 CALL(SIP) (01:0001:00) SENT Route Ctrl to L4 15:47:39.959 CALL(L4) (01:0001:00) RCVD Route Control from SIP 15:47:39.959 CALL(L4) (01:0001:00) Accessing IP Bearer Profiles 15:47:39.959 CALL(L4) (01:0001:00) Profile Id 1 (RG 769) 15:47:39.959 CALL(L4) (01:0001:00) SENT Route Control Ack to SIP 15:47:39.959 CALL(SIP) (01:0001:00) RCVD Route Ctrl Ack from L4 15:47:39.959 CALL(SIP) (01:0001:00) m line codec list: 0 15:47:39.959 CALL(SIP) (01:0001:00) Leg 0 associated with hndl(19999), LTS(1792) 15:47:39.959 CALL(SIP) (01:0001:00) SENT Setup to L4 15:47:39.959 CALL(L4) (01:0001:00) RCVD Setup Ind from SIP 15:47:39.959 CALL(L4) (01:0001:00) SENT RFS to GCL 15:47:39.969 CALL(GCL) (01:0001:00) RCVD RFS DN=[5088625347] ANI=[6175551212] from L4 15:47:39.969 CALL(GCL) (01:0001:00) ANI APRI=[0],SI=[0],Category=[10] 15:47:39.969 CALL(GCL) (01:0001:00) Incoming Channel Group = 4 [SIP_CSP] 15:47:39.969 CALL(GCL) (01:0001:00) DPE Input :DN=[5088625347] ANI=[6175551212] 15:47:39.969 CALL(GCL) (01:0001:00) Invoke Incoming DPE 1; Channel Group 4 15:47:39.969 CALL(GCL) (01:0001:00) DPE response: Proc Complete 15:47:39.969 CALL(GCL) (01:0001:00) DPE Output:DN=[5088625347] ANI=[6175551212] 15:47:39.969 CALL(GCL) (01:0001:00) SENT RADIUS ACCT START 15:47:39.969 CALL(L4) (01:0001:00) RCVD RFS response from GCL 707 IMG WebHelp 15:47:39.969 CALL(GCL) (01:0001:00) RCVD RADIUS ACCT START ACK 15:47:39.969 CALL(GCL) (01:0001:01) SENT Route Control to L4 15:47:39.969 CALL(L4) (01:0001:00) RCVD Route Control from GCL 15:47:39.969 CALL(L4) (01:0001:00) Accessing Route Table 5 15:47:39.969 CALL(L4) (01:0001:00) Accessing Route Table 5 15:47:39.969 CALL(GCL) (01:0001:01) RCVD Mid Stream Router Response 15:47:39.969 CALL(GCL) (01:0001:01) Outgoing Channel Group = 8 [SS7_E1_CSP] 15:47:39.969 CALL(GCL) (01:0001:01) SENT Route Control to L4 15:47:39.969 CALL(L4) (01:0001:01) RCVD Route Control from GCL 15:47:39.969 CALL(L4) (01:0001:01) Accessing Resource Table 1 15:47:39.969 CALL(L4) (01:0001:01) Resource Group ID is 40 15:47:39.969 CALL(L4) (01:0001:01) SENT Outseize Ctrl to SS7 15:47:39.969 CALL(GCL) (01:0001:01) RCVD CPE of ADDRESS INFO from L4 15:47:39.969 CALL(GCL) (01:0001:01) Leg 1 associated with LTS(386) 15:47:39.969 CALL(SS7) (01:0001:01) RCVD Outseize Ctrl from L4 (0x813:0x382b:0) 15:47:39.969 SS7 (U) [0020000a0002 XMT 1: sls:00 pri:00 (0000382b,0000) IAM 0907031005882635740a070310165755212100] 15:47:39.969 CALL(SS7) (01:0001:01) SENT IAM (0x813:0x382b:0) 15:47:40.229 SS7 (U) RCV 1: sls:00 pri:00 (0000382b,0000) ACM 15:47:40.229 CALL(SS7) (01:0001:01) RCVD ACM (0x382b:0x813:0) [000400] 15:47:40.229 CALL(SS7) (01:0001:01) SENT Cut Thru to L4 (0x382b:0x813:0) 15:47:40.229 CALL(SS7) (01:0001:01) SENT Outseize ACK to L4 (0x382b:0x813:0) 15:47:40.229 CALL(L4) (01:0001:01) RCVD Cut Thru from SS7 15:47:40.239 CALL(L4) (01:0001:01) RCVD Outseize ACK from SS7 15:47:40.239 CALL(GCL) (01:0001:00) SENT Connect Tone to L4 15:47:40.239 CALL(L4) (01:0001:00) RCVD Connect Tone from GCL 15:47:40.239 CALL(L4) (01:0001:00) SENT Request DSP Service to SYSRM 15:47:40.239 CALL(MED) (01:0001:00) Transmitting tone 0x2 on (0x1,0x1,0x0) 15:47:40.239 CALL(MED) (01:0001:00) RCVD OUTPULSE CP 15:47:40.239 CALL(GCL) (01:0001:00) SENT Connect w/Pad Response to L4 15:47:40.239 CALL(L4) (01:0001:00) SENT Progress to SIP 15:47:40.239 CALL(SIP) (01:0001:00) RCVD Progress from L4 15:47:40.239 CALL(SIP) (01:0001:00) Set Fax Type to Relay T.38 15:47:40.239 CALL(SIP) (01:0001:00) SENT L3-L3 Outseize Ctrl to VPPL 708 Troubleshooting 15:47:40.239 CALL(IP) (01:0001:00) RCVD Outseize from L3, [vts 768] [m1.0.0] 15:47:40.239 CALL(IP) (01:0001:00) RTP: (Src) 10.129.51.134:8000 15:47:40.239 CALL(IP) (01:0001:00) RTP: (Dst) 10.129.51.144:12716 15:47:40.249 CALL(IP) (01:0001:00) VoIP Codec is G711Mulaw; Payload Size is 20ms 15:47:40.259 CALL(IP) (01:0001:00) SENT Outseize ACK to L3P, toPvid: x66 15:47:40.259 CALL(SIP) (01:0001:00) RCVD Outseize Ack from VPPL 15:47:40.259 CALL(SIP) (01:0001:00) SENT 183 Session Progress to 10.129.51.140:5060 UDP 15:47:40.259 SIP (W) <--- [10.129.51.140, 5060 <- 10.129.51.152, 5060] SIP/2.0 183 Session Progress Via: SIP/2.0/UDP 10.129.51.140;received=10.129.51.140 Contact: <sip:10.129.51.152:5060> Call-ID: [email protected] From: 6175551212<sip:[email protected]:5060>;tag= 117938002f7f75 To: 5088625347<sip:[email protected]:5060>;tag=a9 4c095b773be1dd6e8d668a785a9c843102 CSeq: 1 INVITE Server: Cantata-SIP/10.3.2.105 E1_System 1 Content-Type: application/sdp Content-Length: 176 v=0 o=Cantata_SDP 0 0 IN IP4 10.129.51.152 s=Cantata-SIP c=IN IP4 10.129.51.134 t=0 0 m=audio 8000 RTP/AVP 0 a=rtpmap:0 PCMU/8000 a=silenceSupp:off - - - a=ptime:20 15:47:40.259 CALL(SIP) (01:0001:00) RCVD Cut Thru from VPPL 709 IMG WebHelp 15:47:40.259 CALL(SIP) (01:0001:00) RCVD Connect from VPPL 15:47:43.869 SS7 (U) RCV 1: sls:00 pri:00 (0000382b,0000) ANM 15:47:43.869 CALL(SS7) (01:0001:01) RCVD ANM (0x382b:0x813:0) [00] 15:47:43.869 CALL(SS7) (01:0001:01) SENT Connect to L4 (0x382b:0x813:0) 15:47:43.869 CALL(L4) (01:0001:01) RCVD Connect from SS7 15:47:43.869 CALL(L4) (01:0001:01) SENT CPE of ANSWER to GCL 15:47:43.869 CALL(GCL) (01:0001:01) RCVD CPE of ANSWER from L4 15:47:43.869 CALL(GCL) (01:0001:01) SENT RADIUS ACCT START 15:47:43.869 CALL(GCL) (01:0001:01) RCVD RADIUS ACCT START ACK 15:47:43.869 CALL(GCL) (01:0001:00) SENT Disconnect Tone to L4 15:47:43.869 CALL(L4) (01:0001:00) RCVD Disconnect Tone from GCL 15:47:43.869 CALL(L4) (01:0001:00) SENT Cancel DSP Service to SYSRM 15:47:43.869 CALL(MED) (01:0001:00) RCVD CANCEL OUTPULSE CP 15:47:43.869 CALL(MED) (01:0001:00) RCVD CANCEL OUTPULSE DIGITS 15:47:43.869 CALL(GCL) (01:0001:00) SENT CPE of ANSWER to L4 15:47:43.869 CALL(L4) (01:0001:00) RCVD CPE of ANSWER from GCL 15:47:43.869 CALL(L4) (01:0001:00) SENT Connect to SIP 15:47:43.869 CALL(SIP) (01:0001:00) RCVD Connect from L4 15:47:43.869 CALL(SIP) (01:0001:00) SENT 200 OK to 10.129.51.140:5060 UDP 15:47:43.869 SIP (W) <--- [10.129.51.140, 5060 <- 10.129.51.152, 5060] SIP/2.0 200 OK Via: SIP/2.0/UDP 10.129.51.140;received=10.129.51.140 Contact: <sip:10.129.51.152:5060> Call-ID: [email protected] From: 6175551212<sip:[email protected]:5060>;tag= 117938002f7f75 To: 5088625347<sip:[email protected]:5060>;tag=a9 4c095b773be1dd6e8d668a785a9c843102 CSeq: 1 INVITE Server: Cantata-SIP/10.3.2.105 E1_System 1 Allow: INVITE, BYE, REGISTER, ACK, OPTIONS, CANCEL, INFO Supported: path Accept: application/sdp Content-Type: application/sdp 710 Troubleshooting Content-Length: 176 v=0 o=Cantata_SDP 0 1 IN IP4 10.129.51.152 s=Cantata-SIP c=IN IP4 10.129.51.134 t=0 0 m=audio 8000 RTP/AVP 0 a=rtpmap:0 PCMU/8000 a=silenceSupp:off - - - a=ptime:20 15:47:43.899 SIP (W) ---> [10.129.51.140, 1053] ACK sip:10.129.51.152:5060 SIP/2.0 Via: SIP/2.0/UDP 10.129.51.140 To: 5088625347<sip:[email protected]:5060>;tag=a9 4c095b773be1dd6e8d668a785a9c843102 From: 6175551212<sip:[email protected]:5060>;tag= 117938002f7f75 Call-ID: [email protected] CSeq: 1 ACK Content-Length: 0 15:47:43.899 CALL(SIP) (01:0001:00) RCVD ACK from 10.129.51.140 UDP 15:47:43.899 CALL(SIP) (01:0001:00) 15:48:05.019 SIP (W) with Via sent-by: 10.129.51.140 ---> [10.129.51.140, 1053] BYE sip:10.129.51.152:5060 SIP/2.0 Via: SIP/2.0/UDP 10.129.51.140 To: 5088625347<sip:[email protected]:5060>;tag=a9 4c095b773be1dd6e8d668a785a9c843102 From: 6175551212<sip:[email protected]:5060>;tag= 117938002f7f75 Call-ID: [email protected] CSeq: 2 BYE User-Agent: Excel_CSP/82.30.189 711 IMG WebHelp Content-Length: 0 15:48:05.019 CALL(SIP) (01:0001:00) RCVD BYE from 10.129.51.140:0 UDP 15:48:05.019 CALL(SIP) (01:0001:00) with Via sent-by: 10.129.51.140 UDP 15:48:05.019 CALL(SIP) (01:0001:00) SENT L3-L3 Clear Req to VPPL 15:48:05.019 CALL(IP) (01:0001:00) RCVD Clear Request from L3 15:48:05.019 CALL(IP) (01:0001:00) RTCP STATS: TxPackets=1237; RxPackets=1236; lostPackets=0 15:48:05.019 CALL(IP) (01:0001:00) RTCP/T38 Packet STATS: TxPackets=1237; RxPa ckets=1236; lostPackets=0 15:48:05.019 CALL(SIP) (01:0001:00) RCVD Clear Req from VPPL 15:48:05.019 CALL(SIP) (01:0001:00) SENT Clear Request to L4 15:48:05.019 CALL(SIP) (01:0001:00) SENT 200 OK to 10.129.51.140:5060 UDP 15:48:05.019 SIP (W) <--- [10.129.51.140, 5060 <- 10.129.51.152, 5060] SIP/2.0 200 OK Via: SIP/2.0/UDP 10.129.51.140;received=10.129.51.140 Contact: <sip:10.129.51.152:5060> Call-ID: [email protected] From: 6175551212<sip:[email protected]:5060>;tag= 117938002f7f75 To: 5088625347<sip:[email protected]:5060>;tag=a9 4c095b773be1dd6e8d668a785a9c843102 CSeq: 2 BYE Server: Cantata-SIP/10.3.2.105 E1_System 1 Content-Length: 0 15:48:05.019 CALL(L4) (01:0001:00) RCVD Clear request from SIP 15:48:05.019 CALL(L4) (01:0001:00) SENT Channel Release w/data to GCL 15:48:05.019 CALL(GCL) (01:0001:00) RCVD Channel Released w/data from L4 15:48:05.019 CALL(GCL) (01:0001:00) Call Duration(sec): 22 15:48:05.019 CALL(GCL) (01:0001:01) SENT Clear Response to L4 15:48:05.019 CALL(GCL) (01:0001:00) Radius Call Duration(sec): 22 15:48:05.019 CALL(GCL) (01:0001:00) SENT RADIUS ACCT STOP 712 Troubleshooting 15:48:05.019 CALL(L4) (01:0001:01) RCVD Clear from GCL 15:48:05.019 CALL(L4) (01:0001:01) SENT Clear Request to SS7 15:48:05.019 CALL(SS7) (01:0001:01) RCVD Clear Request from L4 (0x813:0x382b:0) 15:48:05.019 SS7 (U) XMT 1: sls:00 pri:00 (0000382b,0000) REL [0200028090] 15:48:05.089 SS7 (U) RCV 1: sls:00 pri:00 (0000382b,0000) RLC [00] 15:48:05.019 CALL(SS7) (01:0001:01) SENT REL (0x813:0x382b:0) cause 16 15:48:05.089 CALL(SS7) (01:0001:01) RCVD RLC (0x382b:0x813:0) 15:48:05.089 CALL(SS7) (01:0001:01) SENT Clear Request to L4 (0x382b:0x813:0) 15:48:05.089 CALL(L4) (01:0001:01) RCVD Clear request from SS7 15:48:05.089 CALL(L4) (01:0001:01) SENT Channel Release w/data to GCL 15:48:05.089 CALL(GCL) (01:0001:01) RCVD Channel Released w/data from L4 15:48:05.089 CALL(GCL) (01:0001:01) Call Duration(sec): 22 15:48:05.089 CALL(GCL) (01:0001:01) Radius Call Duration(sec): 22 15:48:05.089 CALL(GCL) (01:0001:01) SENT RADIUS ACCT STOP Cantata Technology - IMG 1010 Printable WebHelp 713 Administration Downloading a License Topic Location: Administration When you receive upgrades for your IMG (for example, additional SS7 link or VoIP ports) you must download the new license to the appropriate IMG. Steps 1. Ensure that the license file is in the correct folder on the server: /opt/cantata/common/license/ 2. Right-click the Physical IMG and select IMG Licensing Info. 3. Right-click IMG License Info and select Commit. 4. The License Info pane appears. Click the Download Node License button. The license is downloaded to the IMG based on the serial number of the IMG. IMPORTANT NOTE: If you rename or alter the license file in any way, it becomes unusable. Cantata Technology - IMG 1010 Printable WebHelp 714 Administration Downloading a Raw File to the IMG Topic Location: Administration Dynamic To download API messages for a one-time execution: 1. Create the file with the raw API messages and save it as rawapi.cfg to the following location: /opt/cantata/common/config/ 2. Click the Physical IMG to which you want to download the file. 3. Click the Download Raw File button. If the messages in the file have a different logical node ID other than the physical IMG from which the button is pressed, the logical node ID will be overwritten. This allows sending the same file for multiple nodes without needing to modify its contents. If a message in the file is NACKed by the IMG, all the subsequent messages will be not be sent. Static To download API messages and have them become part of the config file: 1. Create a raw hex file or files and save as "*.hex" to the following folder. /opt/cantata/common/config/ 2. Right-click the Physical IMG entry and select New Raw API Cmds. 3. Right-click Raw API Cmds and select New Raw API Cmd. The Raw API Cmd pane appears. The Configure File field is automatically populated with all *.hex files. 715 IMG WebHelp 4. To send the file to the IMG, right-click Raw API Cmds and select Send Raw API. See the Raw API Command pane reference for details. Cantata Technology - IMG 1010 Printable WebHelp 716 Administration Resetting an IMG Topic Location: Administration You can perform a soft reset of the physical IMG without losing the configuration. Steps 1. Click the Physical IMG that you want to reset. 2. From the Physical IMG pane, click the Clear Software button from the ClientView pane. Cantata Technology - IMG 1010 Printable WebHelp 717 IMG WebHelp User Management An Overview of AdminView Topic Location: Administration > User Management The AdminView utility provides for the administration of user privileges (roles) and authentication. There are two domains in AdminView: User Management Domain Controls the assignment of user access and privileges. Equipment Management Domain Includes three levels of access to ClientView actions performed on the IMG. User Management Domain The user management domain controls user authentication and roles. There are two levels: Administrator A user assigned this role is allowed to perform all User Management functions of the following operations: add users assign roles Basic remove users change passwords self reset password list one or all users display current user information A user assigned this role is only allowed to view his own role and change his own password. Every user is assigned with this role by default. Equipment Management Domain The roles assigned in the Equipment Manager Domain determine the actions a user is allowed to make on the IMG using ClientView. Monitor Provision 718 Allowed to view configuration attributes and system events (alarms, and traps). Every user is assigned with this role by default. See Monitoring the IMG. Allowed to bring components in and out of service. See Provisioning the IMG. Administration Configuration Allowed to modify configuration on the IMG. See Configuration Summary. Default Administrator Information By default there is one user, admin, with the following roles assigned: User Management Domain Equipment Management Domain Administrator - Monitor - Provisioning - Configuration The default password is admin Linux Users After installing the IMG and IMG EMS software, you must edit your /etc/hosts file (one time only). 1. There is an existing entry for localhost mapped to 127.0.0.1. You need to add an entry before the existing 127.0.0.1 entry with the specific IP address, hostname, and alias for the Linux server. Example: 135.119.36.142 <hostname> 127.0.0.1 localhost localhost.localdomain localhost 2. Edit the /etc/sysconfig/network file and enter the same hostname that was added in the /etc/hosts file. For the procedure to do this using the linux GUI, see Setting Up GateControl EMS. ClientView Log In When a user launches ClientView, they are prompted for a Username and Password. The default is admin/admin. 719 IMG WebHelp Re-installation of Software User account information remains through a re-installation of the IMG System Software. Cantata Technology - IMG 1010 Printable WebHelp 720 Administration Administering User Privileges Topic Location: Administration > User Management Before You Begin To run AdminView, the AdminManager process must be running. See Starting GateControl EMS. To verify that Admin Manager is running, type l ps -ef l grep Admin The response should look like this (the highlighted lines indicate that AdminManager is running: [excelsw@dakb-gecems excelsw]$ ps -ef | grep Admin excelsw 11541 1 0 Jan24 ? 00:00:43 /opt/excel/IMG/GateControlEMS/bin/../../jre/bin/java com.zerog.lax.LAX /opt/excel/IMG/GateControlEMS/bin/AdminManager.lax /tmp/env.properties.11541 excelsw 6492 6451 0 12:23 pts/2 00:00:00 grep Admin If there is no response, or if the highlighted line is not included, you must start AdminManager using the following command. ./AdminManager Login to AdminView Before you can perform any administrative functions, login to AdminView as Administrator. 1. Run AdminView Linux: Windows: C:\Program Files\Cantata\IMG\GateControlEMS\bin\AdminView 2. Login as Administrator User ID: admin Password: admin Admin Tasks Changing the Admin Password Adding a User Changing a Password 721 IMG WebHelp Changing a User's Roles Resetting Your Own Password Removing a User Changing the Admin Password To limit access to the Admin functions, change the admin user password: 1. Type chpwd and press ENTER. 2. Enter the Admin user ID, admin, and press ENTER. 3. Enter a new password and press ENTER. 4. Re-enter the new password and press ENTER. Adding a User To add a user: 1. Type adusr and press ENTER. 3. Enter a user ID and press ENTER. 4. Enter a password for the user and press ENTER. 5. Confirm the password and press ENTER. 6. Enter values for the roles to assign to the user. Changing a Password To change a password: 1. Type chpwd and press ENTER. 2. Enter a user ID and press ENTER. 3. Enter a new password and press ENTER. 4. Re-enter the new password and press ENTER. Changing a User's Roles To change a user's roles: 1. Type asnrole and press ENTER. 2. Enter the user ID and press ENTER. 3. Enter the values for the roles to assign to the user and press Enter. You must enter values for all of the roles you want the user to have, even if they are already assigned. Resetting Your Own Password To reset your own password: 722 Administration 1. Type rstpwd and press ENTER. 2. Enter your user ID and press ENTER. 3. Enter a new password and press ENTER. 4. Re-enter the new password and press ENTER. Removing a User To remove a user: 1. Type rmusr and press ENTER. 2. Enter the user ID and press ENTER. Also see Viewing User Information Cantata Technology - IMG 1010 Printable WebHelp 723 IMG WebHelp Admin Commands Topic Location: Administration > User Management Command Description lusrs Display all users' information (IDs, passwords, and roles). lusr Display a specific user's ID, password, and roles. The user's ID must be provided. adusr Add a single user. The user's ID, password, and roles must be provided. Roles 1. Administrator 2. Basic 3. Configuration 4. Provision 5. Monitor rmusr Remove a single user. The user's ID must be provided. chpwd Reset a user's password. The user's ID and new password must be provided. asnrole Assign new roles to an existing user. The user's ID and new roles must be provided. The old roles of the user will be replaced by the new roles. Roles 1. Administrator 2. Basic 3. Configuration 4. Provision 5. Monitor id Display current user information (ID, password, and roles). rstpwd Reset current user's password. quit Exit the program. help Display help information. lcmd List all available commands. 724 Administration Cantata Technology - IMG 1010 Printable WebHelp 725 IMG WebHelp Assigning ClientView Users Topic Location: Administration > User Management Unless you specifically assign user privileges, anyone can access the GCEMS with full Administrative Privileges using: UserName: admin Password: admin Procedure If you want to assign passwords and roles to individual users who may have access to the EMS, follow this procedure. 1. Login to AdminView a. Run AdminView <./AdminView> (located at opt/cantata/IMG/GateControlEMS/bin/ b. Login as Administrator User ID: admin Password: admin 2. Change the Admin Password To limit access to the Admin functions, perform the following steps. a. Type chpwd and press ENTER. b. Enter the Admin user ID, admin, and press ENTER. c. Enter a new password and press ENTER. d. Re-enter the new password and press ENTER. 3. Add a User and assign roles a. Type adusr and click ENTER. b. Enter a user ID and click ENTER. c. Enter a password for the user and press ENTER. d. Confirm the password and press ENTER. e. Enter values for the roles to assign to the user. 1 - Administrator 2 - Basic 3 - Configuration 4 - Provisioning 726 Administration 5 - Monitoring f. Repeat steps a-e for each user. g. Quit Help For a list of commands, type help More Information For more detailed information on Administering User Privileges, see Administering User Privileges in the IMG 1010 On-line Help. Cantata Technology - IMG 1010 Printable WebHelp 727 IMG WebHelp Viewing User Information Topic Location: Administration > User Management If you are logged into AdminView as the Administrator, you can perform the following tasks: Displaying all User Information 1. Type lusrs and hit Enter. A list of all users and their assigned roles are displayed, as shown below: Display a Specific User's Information 1. Type lusr and hit Enter. 2. Enter the user ID and hit Enter. The user ID and their assigned roles are displayed, as shown below: 728 Administration Displaying Your Own Information 1. Type id and hit Enter. Your user ID and your assigned roles are displayed, as shown below: List All Commands To display a list of all commands: 1. Type lcmd and hit Enter. A list of all available commands is displayed, as shown below: Displaying Help To display all available commands with descriptions: 1. Type help and hit Enter. 729 IMG WebHelp Cantata Technology - IMG 1010 Printable WebHelp 730 Administration Starting AdminManager on an Alternate RMI port Topic Location: Administration > User Management AdminManager listens for ClientView connections on port 1099, which is the default port for Java RMI applications. If this port is already in use by another application, you can configure AdminManager to listen on an alternate port. To do so, Admin Manager must be launched manually from the command line. For Windows, open a command window and change directory to where the GCEMS servers have been installed and type: java -jar AdminManager.jar -p [port number] For Linux, open a command window and change directory to where the GCEMS servers have been installed. - type: ../../jre/bin/java -jar AdminManager.jar -p [port number] When running AdminManager on a port other than 1099, ClientView must also specify this alternate port. To do so, open the client.properties file (located at Program Files/Cantata/IMGUserInterface/ClientView/) and change the "rmi port" entry (highlighted below) to the desired port: <?xml version="1.0" encoding="UTF-8"?> <properties version="1" reserved=""> <property key="help.0" value="IMG Help:..\WebHelp\IMG.htm" /> <property key="host.0" value="localhost" /> <property key="host.max" value="5" /> <property key="launch_eventviewer" value="false" /> <property key="logfiles" value="C:\Program Files\Cantata/common/log" /> <property key="product" value="IMG" /> <property key="rmi_port" value="1099" /> <property key="username.0" value="admin" /> <property key="username.max" value="5" /> </properties> Cantata Technology - IMG 1010 Printable WebHelp 731 Software Reference Cantata Technology - IMG 1010 Printable WebHelp 732 Hardware Maintenance Installing a VoIP or Media Module Topic Location: Hardware Maintenance Follow this procedure to add a VoIP or Media module on the IMG. Caution: Electrostatic Discharge Protection (EDP) must always be used. Electrostatic Discharge (ESD) protective straps, shoes, or mats must be used when working with electronic components. Electrostatic discharge from your body can damage integrated circuits during installation. Required Tools and Parts VoIP module or Media module (Cantata supplied). #1 Phillips head screwdriver (customer supplied). 4 Phillips pan head screws (Cantata supplied). Steps 1. Set power to OFF (O) at rear of docking station. 2. Remove Motherboard Tray. See Diagram 1 - Removing Motherboard Tray. a. Loosen the two ejector captive fasteners located on each side of the front panel. b. Lift the ejectors upward and pull to unseat the tray from the docking station. c. Slide the tray out. 3. Locate Module Position. See Diagram 2 - Module Positions. 4. Install module on motherboard a. Position the module over the four standoffs. b. Align the connectors on the module with the connectors on the motherboard and press together. Cautions: 1. The connectors must be properly aligned and fully seated, to ensure a trouble-free installation. 2. When pressing the module onto the motherboard do not press on the components installed on the module, but rather press on an open area on the edge of the Printed Circuit Board itself. 733 IMG WebHelp c. Attach the module with the four (4) Phillips pan head screws. Caution: Do not over tighten the screws. Recommended torque: 3-5 in-lbs (.34-.56 N-M). 5. Re-insert Motherboard Tray a. Align the rail on each side of the tray with the guides on the inside of the docking station. b. Ensure the ejectors are in the up position. c. Slide the tray in until the power connectors and signal connectors initially mate (the ejectors will start to move down). Important Notes Do not force the tray if any resistance occurs when mating with the docking station. Using undue force could damage the unit. The guides only provide gross alignment to the power and signal connectors. The guide pins on the main board and I/O card are self-aligning and provide exact alignment for the connectors. The tray guides also act as the conduit for any Electrostatic Discharge (ESD) as the tray initially mates with the docking station. d. When the tray is seated and the connectors are mated, push the ejectors down and tighten captive fasteners. 6. Set power to ON (1) at rear of docking station. 7. Configure Module. See the procedures for configuring modules: Configuring a Second VoIP Module Configuring Media Diagram 1 - Removing Motherboard Tray 734 Hardware Maintenance Diagram 2 - Module Positions Important: If only one VoIP module is to be installed, it must be at Position 0. Cantata Technology - IMG 1010 Printable WebHelp 735 IMG WebHelp Replacing a Motherboard Tray Topic Location: Hardware Maintenance The Motherboard Tray is the only field replaceable unit of the IMG 1010. The power supply is part of the tray, therefore, you do not have to remove the docking station from the rack and un-cable everything. Procedure 1. Update MAC address (DHCP only) NOTE: If you are using an SD card, simply remove the card from the old motherboard and place it in the new one and proceed to step 2. If you are using DHCP, you must update the MAC address in dhcpd.conf file. a. Note the two MAC addresses of the old motherboard (CTRL0 and CTRL1). b. Note the MAC address of new motherboard, located on the underside near the front panel. The address printed on the label is for CTRL0. The MAC address for CTRL1 is one hex digit higher. See Sample dhcpd.conf File in the IMG WebHelp. c. Edit the dhcpd.conf file located in the etc\ directory on the GCEMS server. A sample MAC address entry in a dhcpd.conf file is shown in bold below: Sample dhcpd MAC address entry: host IMG_CPU1_0 { hardware ethernet xx:xx:xx:xx:xx:xx; d. Locate both MAC address entries for the old motherboard. Change each MAC address to the corresponding address for the new motherboard. e. Save dhcpd.conf file. 2. Remove existing tray AC a. Set power to OFF (O) at rear of docking station. b. Loosen the two ejector captive fasteners located on each side of the front panel. c. Lift the ejectors upward and pull to unseat tray from docking station. d. Slide tray completely out. If returning the tray to Cantata, contact Cantata Technical Support. 736 Hardware Maintenance DC The DC tray is hot-swappable, so there is no on/off switch on the rear panel. a. Loosen the two ejector captive fasteners located on each side of the front panel. b. Lift the ejectors upward and pull to unseat tray from docking station. c. Slide tray completely out. If returning the tray to Cantata, contact Cantata Technical Support. 3. Install New Tray a. Align rail on each side of the tray with the guides on the inside of the docking station. b. Ensure the ejectors are in the up position. c. Slide the tray in until the power connectors and signal connectors initially mate. The ejectors will start to move down. Important! The guides only provide gross alignment to the power and signal connectors. The guide pins on the main board and I/O card are self aligning and provide exact alignment for the connectors. Important! The tray guides also acts as the conduit for any Electrostatic Discharge (ESD) as the tray initially mates with the docking station. Do not force the tray if any resistance occurs when mating with the docking station. Using undue force could damage the unit. d. When the tray is seated and the connectors are mated, push the ejectors down and tighten captive fasteners. e. For the AC tray, set power to ON (1) at rear of docking station.. 4. If you are using DHCP, observe the front panel to ensure that the IMG gets its IP address from DHCP as well as its configuration. 5. If you are returning the old tray, contact your supplier. Cantata Technology - IMG 1010 Printable WebHelp 737 IMG WebHelp Replacing a Fuse Topic Location: Hardware Maintenance Complete the following steps to remove and replace the fuse. Important Notes Replace the fuse with only a Cantata-supplied fuse or equivalent: 3 Amp Slo-Blo fuse, type 3AG. For safety, the integrated fuse can only be replaced when the power cord is removed. Procedure 1. Ensure the power switch on the AC power module is set to O (Off). 2. Unplug AC power cord. 3. Using a small flat bladed screwdriver, open the hinged fuse cover. 4. Remove the fuse holder using the screwdriver and replace fuse in holder. The fuse only mounts on one side of the cartridge. 5. Install the fuse holder into the AC power module with the fuse facing down. Cantata Technology - IMG 1010 Printable WebHelp 738 Hardware Maintenance Troubleshooting Hardware Topic Location: Hardware Maintenance Overview This section contains a troubleshooting table to help you diagnose and resolve hardware issues that could occur during the IMG installation and operation. The table is organized into three sections: Power Alarm LED Indicators Cooling The information in each section is organized as follows: Problem or Symptom Corrective Action Cause or Description This section addresses only the most common issues. If you are unable to solve a problem, record all the information pertaining to your system configuration, including: A description of the symptoms and any corrective action already taken The grounding method Whether you are using a single power source or redundant power sources LAN topology The version of System Software used with the IMG A trace of messaging between the host and the IMG After you record this information, please contact your supplier. Power Problem or Symptom The IMG (with DC power) does not power up. Cause or Description Corrective Action The circuit breaker(s) at the rear of the chassis are switched to OFF (O). Switch the circuit breaker(s) to ON (1). The -48 V DC power source is not plugged in or is not operating. Check the power source for proper output. Replace it if necessary. The –48 V DC power source is not connected properly to the DC power module at the rear of the chassis. Refer to Connecting DC Power and make sure that the power source is connected properly. If necessary, rewire the connections. 739 IMG WebHelp The IMG (with AC power) does not power up. The IMG (with DC power) powers up, but then shuts down. The IMG (with AC power) powers up, but then shuts down. 740 Tray not properly seated in docking station. Remove tray and reinstall to ensure the tray is properly seated. Refer to Replacing a Tray. One of the voltages is outof-tolerance on the low side. Main board shuts down. Restart IMG. If 120/240 V AC power is used the switch at the rear of the chassis is switched to O (Off). Set the switch to 1 (On). The 120/240 V AC power source (outlet) is not plugged in or is not operating. Check the power source (outlet) for power or proper output. Check for tripped circuit breaker. Reset circuit breaker or repair as necessary. The AC power cable is faulty. Replace cable. Refer to Connecting AC Power. Tray not properly seated in docking station. Remove tray and reinstall to ensure the tray is properly seated. Refer to Tray Removal and Replacement. One of the voltages is outof-tolerance on the low side. Main board shuts down. Restart the IMG. A circuit breaker has tripped. Reset circuit breaker. The power source failed or does not provide the required level of voltage and current (–48 V DC/7A). Ensure external power source is functioning at the required levels. If the power source is faulty, repair or replace it. An external circuit breaker has tripped. Reset circuit breaker. The fuse in the AC power module has blown. Remove tray and reinstall to ensure the tray is properly seated. Refer to Replacing a Tray. Remove tray and reinstall to ensure the tray is properly seated. Refer to Replacing a Tray. Check the wiring. Refer to Connecting DC Power. Replace fuse. Refer to Connecting AC Power Hardware Maintenance Cooling Problem or Symptom Cause or Description Corrective Action The IMG is operating, but the tray overheats. ALARM LED on front panel lights red (major) or orange (minor). Refer to the Hardware Alarm Module to access Fan and Temperature Sensor alarm descriptions. Refer to Hardware Alarm Module to access Fan and Temperature Sensor corrective action information. Refer to the LCD display, Hardware Info Menu to access Fan and Temperature Sensor information. If ALARM LED remains on, call Cantata Technical Support. To remove tray and replace, see Replacing a Tray. Front Panel LED Indicators Problem or Symptom Cause or Description Corrective Action The IMG powers up, but the ALARM LED lights red (major) or orange (minor). An alarm condition exists. The LCD display will indicate source of alarm condition. Refer to Front Panel Status LEDs. If ALARM LED is still red, call Cantata Technical Support. The SIG/TIMING 0, 1, 2, or 3 LED lights red (timing error) or orange (reference clock present but not timing system). The E1/T1 SIGNAL/TIMING port 0, 1, 2, or 3 at the rear I/O panel is not connected to an external reference clock. Configure reference timing. The TIMING LED lights orange (hold over). Lost lock on external timing source, but still synchronized to it. Re-configure external timing. The ENET CTRL, ENET DATA, or ENET SIG LED lights red (no link established, error). The Ethernet link has not been established or has been lost. Establish or re-establish link. The SIGNAL SPAN LEDs, for licensed E1/T1 spans, light red (major alarm) or orange (minor alarm). The span has not been established or has been lost. Establish or re-establish span. Cantata Technology - IMG 1010 Printable WebHelp 741 Hardware Reference Hardware Reference Overview Topic Location: Hardware Reference The Hardware Reference includes the following topics: Physical Description Hardware Specifications I/O Cable Specifications RJ 48 Connector Pinouts Hardware Alarm Module Rear Panel Description Front Panel Overview AC Power Information DC Power Information Power and Fan Control Compliance Overview Cantata Technology - IMG 1010 Printable WebHelp 742 Hardware Reference Physical Description Topic Location: Hardware Reference The IMG consists of two mated assemblies: a docking station and field-replaceable tray. It has the following dimensions and weight. Parameter Specification Width 43.89 cm (17.28 in.) Height 4.36 cm (1.72 in.) (1U) Depth 48.26 cm (19.0 in.) Weight 9 kg (20 lbs.) Cantata Technology - IMG 1010 Printable WebHelp 743 IMG WebHelp Hardware Specifications Topic Location: Hardware Reference Physical Description The IMG is a low-profile unit that consists of two assemblies: a docking station and field-replaceable tray which mates to the docking station to form a single unit. It has the following dimensions and weight. Parameter Specification Width 43.89 cm (17.28 in.) Height 4.36 cm (1.72 in.) (1U) Depth 48.26 cm (19.0 in.) Weight 9 kg (20 lbs.) Processor IBM 750GX RISC Processor running at 1GHz 1MB L2 Cache @1GHz 512MBx64 DDRAM @ 200MHz/400MHz (default), up to 1GB 32MB Flash SDCard Environmental Specifications The temperature, humidity, and altitude of the site must fall within the specifications listed below. In general, a typical office environment satisfies these conditions. A temperature-controlled environment is preferable. Parameter Specification Temperature, Operating 0°C to 50°C Temperature, Operating (Short Term) -5°C to 50°C Temperature, Storage -40°C to 70°C Shock, Operational 30°C/hr Shock, Storage -40°C to 23°C @ 10°C/min 744 70°C to 23°C @ 13°C/min Hardware Reference 23°C to -40°C @ 30°C/hr 23°C to 70°C @ 30°C/hr Humidity, Operational 5% to 85% Humidity, Operating (Short Term) 5% to 90% but not to exceed 0.24kg water/kg of dry air Humidity, Packaging 90% to 95% relative humidity @ 40° C Altitude 3952M / 13000 Ft Cantata Technology - IMG 1010 Printable WebHelp 745 IMG WebHelp I/O Cable Specifications Topic Location: Hardware Reference CAUTION: Cantata recommends that you configure any routers or switches connected to the IMG for 100Mbit and Auto-negotiation. Disabling autonegotiation may result in packet loss. Also, broadcast propagation between ports must be enabled to allow BootP. Overview The IMG can be interconnected in a single platform configuration or in a redundant platform configuration. 10/100/1000BaseT Ethernet Cable Specifications The IMG communicates with the host and other units in the network through Ethernet connections over 10BaseT, 100BaseT or 1000BaseT (shielded) cables. The table below lists the cable specifications. Characteristics 10/100Base-T (Shielded) Category 5 Designator Twisted pair Segment Length - Recommended maximum 100 m Cable Type 24 gauge 100-Ohm shielded twisted pair Connector 8-pin RJ-45 T1/E1 Span/Timing Cable Specifications The table below lists the cable specifications. Characteristics T1 (Shielded) Category 8 Designator Twisted pair Segment Length - Recommended maximum 100 meters Cable Type 24 gauge, 100-Ohm shielded twisted pair Connector 8-pin RJ-48 DS3 Cable Specifications DS3 requires 2 cables: 1 for transmit and 1 for receive. 746 Hardware Reference Characteristics 2 Conductor (Shielded Ring) Designator Co-ax Segment Length - Recommended maximum 450 ft. Cable Type 75 ohm BNC Y Connector BNC Cantata Technology - IMG 1010 Printable WebHelp 747 IMG WebHelp RJ-48 Connector Pinouts Topic Location: Hardware Reference Straight Pinout RJ-48 Pin (T1/E1) RJ-48 Pin Signal 1 1 RX, Ring, - 2 2 RX, Tip, + 3 3 Shield/Return/Ground 4 4 TX, Ring, - 5 5 TX, Tip, + 6 6 Shield/Return/Ground 7 No connect No connect 8 No connect No connect Crossover Pinout RJ-48 Pin (T1/E1) RJ-48 Pin 1 4 RX/Ring/- <->TX/Ring/- 2 5 RX/Tip/+ <->TX/Tip/+ 3 3 Shield/Return/Ground 4 1 TX/Ring/- <->RX/Ring/- 5 2 TX/Tip/+ <->RX/Tip/+ 6 6 Shield/Return/Ground 7 No connect No connect 8 No connect No connect Reference Timing RJ-48 Pin (T1/E1) 748 Signal Signal Hardware Reference 1 RX/Ring/- 2 RX/Tip/+ 3 Not Used 4 Not Used 5 Not Used 6 Not Used 7 Not Used 8 Not Used Cantata Technology - IMG 1010 Printable WebHelp 749 IMG WebHelp Hardware Alarm Module Topic Location: Hardware Reference Overview The hardware alarm module supports the IMG platform by configuring the fans and temperature sensors for optimal cooling and temperature control. It also monitors for fan and temperature sensor alarm conditions. The four fans are located on the front panel and the six temperature sensors are located on the main board. The hardware alarm module monitors the following fan and temperature sensor parameters: Fan status: Revolutions per minute (RPM) Temperature sensor status: degrees Celsius (°C) Alarm Status Levels The hardware alarm module supports three levels of alarm reporting: Status of a single fan or temperature sensor Status of all fans and temperature sensors Status of all fans or all temperature sensors Fan Alarms Single Fan Minor - speed is 10% or -5% than the normal speed (8400 RPM). Major - speed is less then the lower threshold (1200 RPM). Multiple Fans Minor - if two or more of the fans are set to the minor alarm state. Normal- if a fans exits an alarm state (returns to normal). Major - if one or more fans are set to the major alarm state. It is possible to get a Normal Alarm without a corresponding Minor Alarm. For example, a single minor alarm followed by a return to normal will generate only a Normal Alarm. Temperature Sensor Alarms Single Temperature Sensor 750 Minor - temperature reading is more than 50°C (alarm clears at 55°C). Major - temperature reading is more than 70°C (alarm goes back to Minor at 65°C). Hardware Reference Critical - temperature reading is more than 80°C (alarm goes back to Major at 75°C). Multiple Temperature Sensors Indicates the highest alarm on all temperature sensors. Fan and Temperature Sensor Alarms Minor - if either the sum of the fans or sum of the temperature sensors is in a minor alarm state. Major - if the sum of the temperature sensors is in major alarm state or the sum of the fans is in a major alarm state. Critical - only if the sum of the temperature sensors is in a critical alarm state. The consequential actions for the above alarm conditions are as follows: Major - fans increase speed to full on. Critical - system resets. Cantata Technology - IMG 1010 Printable WebHelp 751 IMG WebHelp Rear Panel Description Topic Location: Hardware Reference Illustration Overview The IMG rear panel I/O connectors provide the required interfacing to support the Element Management System (EMS). CTRL 0, CTRL 1 - 10/100 (Communication to EMS) These two redundant 10/100BaseT Ethernet connectors provide communication with an external EMS or any other device that needs to be secure from the public network. The connectors do not interface with the internal Ethernet switch and are physically isolated from any network internal to the IMG . These auto-negotiating, full duplex connectors support MDIX (cable cross-over) which eliminates the need for crossover cables for point-to-point connections. DATA 0, DATA 1 - 10/100/1000 (Data and Signaling over IP) These two redundant 10/100/1000BaseT Ethernet connectors interface to the internal Ethernet switch. These connectors are used to communicate to all devices in the IMG that need to communicate over the public network. All internal connections are 10/100BaseT and are aggregated to 1000BaseT, if required. These autonegotiating, full duplex connectors support MDIX (cable cross-over) which eliminates the need for crossover cables for point-to-point connections. 752 Hardware Reference SIG 0, SIG 1 - 10/100 (Signaling over IP) These two redundant 10/100BaseT Ethernet connectors interface to the internal Ethernet switch. These connectors can be logically isolated from the data network or can be used as connections to the data network via software configuration. The connectors bring in signaling over IP. These auto-negotiating, full duplex connectors support MDIX (cable cross-over) which eliminates the need for crossover cables for point-to-point connections. SIGNALING/TIMING - 0, 1, 2, 3 (T1/E1 Signaling and Timing Span Connectors) These four RJ-45 connectors are dedicated for timing and signaling and support T1/E1 interfaces. Any of the four spans can be used to provide signaling, or bearer traffic. 0 and 1 can be used for Reference Timing. 2 and 3 can be used for Loop Timing. REDUNDANCY (1+1 Bearer Redundancy Connector) A dual stacked SCSI connector provides the interface for 1+1 bearer redundancy between IMGs. Redundant 1010s are connected by using two cables. BEARER 0 - 27 (T1/E1 Bearer Span Connectors) The 28 T1 and 21 E1 bearer spans are accessed through the RJ-45 Ethernet connectors. The connectors provide T1 with 100 ohm impedance and E1 with 120 ohm impedance and signaling. See also Network Interface Scenarios. Ethernet Control, Signaling and Data Connector LEDs These Ethernet RJ-45 connectors contain two LEDs that provide the user with Ethernet status. LED Color Description Activity Green/Off Blinks on either transmit (TX) or receive (RX) activity Speed 10/100 Yellow/Off On when 100 Mpbs link established Off when 10 Mpbs link established Speed 10/100/1000 Yellow/Off On when 1000 Mpbs link established Off when 10 or 100 Mpbs link established The figure below shows the RJ-45 Ethernet connector LEDs. 753 IMG WebHelp Cantata Technology - IMG 1010 Printable WebHelp 754 Hardware Reference Determining VoIP Module Type Topic Location: Hardware Reference You can determine whether you have a SLM-IPM-1001 module or a SLM-IPM-0001 module by looking at the Module Configuration Profile field in the VoIP Module pane. If you have an SLM-IPM-1001 VoIP module installed, the following will appear after the vocoder name in the Module Configuration Profile: Any Vocoder (4 Picasso), as shown below. SLM-IPM-1001 If you have an SLM-IPM-0001 Module, the name is Any Vocoder. SLM-IPM-0001 Cantata Technology - IMG 1010 Printable WebHelp 755 IMG WebHelp Dell Server Configuration Details Topic Location: Hardware Reference Dell 1850 Dell 1950 Dell 860 756 Hardware Reference Cantata Technology - IMG 1010 Printable WebHelp 757 IMG WebHelp Front Panel Front Panel Overview Topic Location: Hardware Reference > Front Panel The IMG 1010 front panel consists of a PCB that houses 43 bi-color LEDs, a LCD display and five LCD pushbutton switches used to control the display. A cable interfaces the front panel components with the main board. The figure below shows the front panel controls and indicators. Cantata Technology - IMG 1010 Printable WebHelp 758 Hardware Reference Front Panel LEDs Topic Location: Hardware Reference > Front Panel Each LED consists of two separate LEDs (red and green). The bi-colored LEDs can be selected to be red, green, orange (both red and green on) or blinking of any of the colors. All LEDs are under software control. POWER LED This LED that indicates power status. The green LED is hardwired to 3.3V while the orange LED is under software control. LED Color Description Off No 3.3V power Green 3.3V power available Orange Power warning ALARM LED This LED indicates alarm conditions. LED Color Description Off Not applicable Green No alarms Orange Minor alarm Red Major alarm SIG/TIMING LED These four LEDs indicate T1/E1 spans statuses for the SIGNAL/TIMING 0, 1, 2, 3 connectors. LED Color Description Off Span is out of service. Green Span is in service and is receiving valid data. Orange Receiving an orange alarm RAI Red Span is in service and is receiving a red alarm or no span is connected. TIMING LED 759 IMG WebHelp This LED indicates whether the system timing is free running, locked on an external timing source or in hold over (lost lock on external timing source, but still synched to it). LED Color Description Off Free running Green Locked on external timing source Orange Hold over (lost lock on external timing source, but still synched to it) ENET CTRL LED These two LEDs indicate link and master control of the Ethernet control plane via the CTRL 0 and CTRL 1 connectors. The mastership is controlled via software while the link is under hardware control. ENET DATA LED These two LEDs indicate link and master control of the Ethernet data plane via the DATA 0 and DATA 1 connectors. The mastership is controlled via software while the link is under hardware control. ENET SIG LED These two LEDs indicate link and master control of the Ethernet signaling plane via the SIG 0 and SIG 1 connectors. The mastership is controlled via software while the link is under hardware control. LED Color Description Off No link established Green Link established and active port Orange Link established and standby port Red No link established, error AUX LED These LEDs are reserved for future use. SPAN STATUS LED These 28 LEDs indicate the bearer span (0 - 27) statuses. For DS3, each span has it's own LED. LED Color 760 Description Hardware Reference Off Span is out of service. Green Span is in service and is receiving valid data. Orange Receiving an orange alarm RAI Red Span is in service and is receiving a red alarm or no span is connected. Cantata Technology - IMG 1010 Printable WebHelp 761 IMG WebHelp LCD Display Topic Location: Hardware Reference > Front Panel The LCD display unit consists of a hierarchical LCD display menu system controlled by the five push button switches and default menu items. The display allows the user the capability to retrieve and monitor information. The LCD display is a standard two line times 24 (2x24) character display with a backlight. The default display is initially set to show the Product name and unique chassis ID. The user may optionally set any displayed item as the default by viewing the item and depressing and holding the Select push button then the Right push button. If the host configures a Node Name and ID, the Product Name, Node Name and ID will become the new default item to be displayed. The default display is displayed after all the push buttons are in the released state for a period for approximately one minute. The LCD is typically updated when interrupted by a push button input from the user. Any item displayed by the front panel can be queried by the Host controlling the IMG 1010. LCD Push Button Switches The five push button switches allow the user to select and display information on the LCD display that are specific to an active IMG 1010 configuration. Each switch is interfaced to the main board for control and monitoring. Depressing and holding any of the switches for 500ms (0.5 seconds) will cause that keystroke to be reprocessed, in a typeomatic fashion. The push buttons are as follows: Up Down Used to scroll up to a different line of text. When pressed simultaneously with the Down push button, a hard reset of the IMG 1010 occurs. Used to scroll down to a different line of text. When pressed simultaneously with the Up push button, a hard reset of the IMG 1010 occurs. Left Right 762 Used to display contents of a menu item if no additional menu items exist to the bottom of this item. Used to scroll left to a different line of text. When pressed simultaneously with the Right push button, a soft reset of the IMG 1010 occurs. Hardware Reference Used to scroll right to a different line of text. When pressed simultaneously with the Left push button, a soft reset of the IMG 1010 occurs. Select Used to display contents of a menu item if no additional menu items exist to the right of this item. Used to display the contents of a menu item. Used to enter and exit the scroll mode, when an item contains scroll-able text. This will allow a menu item to display multiple lines of text by scrolling up and down and read the entire line by scrolling right and left. Hard and Soft Resets The push button switches also allow the user to initiate hard and soft unit resets as described below. Hard Reset Pressing the Up and Down switches simultaneously for 2.5 seconds causes a hard reset of the CPU. A hard reset reloads the processor configuration registers and the FPGA configuration data. Soft Reset Pressing the Left and Right switches simultaneously for 2.5 seconds causes a soft reset of the CPU. A soft reset will not reload the processor configuration registers and the FPGA configuration data. Cantata Technology - IMG 1010 Printable WebHelp 763 IMG WebHelp LCD Menus Topic Location: Hardware Reference > Front Panel The following LCD main menus provide the user with means to access, verify, and monitor information: System Info Timing Info Physical Span Info IP Info Hardware Info Menu Display/Control To enter a main menu, the user can either use the Select or Right push button to select the desired menu. The items in the selected main menu will be displayed on the first line (item name line). The second line will be blank. When the item is selected, its text will be displayed in one of three ways: If the text data to be displayed is within 24 characters, the first line will remain and the data will be displayed on the second line. If the data is greater than 24 characters, the data will over right the first line and continue on the second line. In either of these two styles of presentation the text will be updated every second. In the third method, the text data may be scrolled left/right and up/down to a different line of text. When an item contains scroll-able text the user must enable scroll mode by depressing the Select push button. To end scrolling mode, depress the Select push button again. Important: While in the scroll mode the text data will not be updated. Cantata Technology - IMG 1010 Printable WebHelp 764 Hardware Reference System Info Menu Topic Location: Hardware Reference > Front Panel 765 IMG WebHelp Cantata Technology - IMG 1010 Printable WebHelp 766 Hardware Reference Physical Span Info Menu Topic Location: Hardware Reference > Front Panel 767 IMG WebHelp Cantata Technology - IMG 1010 Printable WebHelp 768 Hardware Reference Timing Info Menu Topic Location: Hardware Reference > Front Panel Cantata Technology - IMG 1010 Printable WebHelp 769 IMG WebHelp IP Info Menu Topic Location: Hardware Reference > Front Panel 770 Hardware Reference Cantata Technology - IMG 1010 Printable WebHelp 771 IMG WebHelp Hardware Info Menu Topic Location: Hardware Reference > Front Panel 772 Hardware Reference Cantata Technology - IMG 1010 Printable WebHelp 773 IMG WebHelp Power AC Power Specifications Topic Location: Hardware Reference > Power The AC input power must conform to the following specifications: AC Power 120-240 V AC, 60-50 Hz, 3A-1.5A Range 90 to 240 V AC Cantata Technology - IMG 1010 Printable WebHelp 774 Hardware Reference DC Power Information Topic Location: Hardware Reference > Power DC Power Specifications The DC input power must conform to the following specifications: DC Power -48 V DC (nominal), 7A Range -40 to -60 V DC Cantata Technology - IMG 1010 Printable WebHelp 775 IMG WebHelp Power and Fan Control Topic Location: Hardware Reference > Power Power Control The IMG power ramp-up is initiated only when the tray (main board) is fully seated into the docking station. This is done when the main board receives a fully seated signal from the docking station I/O board. This ensures that power on the main board does not come on until the system is properly seated. All board voltages are then monitored and if any voltage falls out of tolerance on the low-side, a power down of all voltages will occur. In the case where a fault is detected by the CPU and main board shutdown is necessary, a forced shutdown will be initiated. A restart will not be initiated until all voltages are within tolerance. Fan Control The IMG uses four fans for cooling. The fans, located on the front panel, draw air into the unit to cool the main board and I/O board. The air exhausts out vent holes at the rear sides of the docking station. The fans connect directly to the main board and are individually fused and controlled by a fan controller on the main board. The main board also provides six temperature sensors that monitor ambient temperature at strategic locations on the board. When the fan controller detects an over temperature, the fans will increase speed to full on. For example: If one of the fans fail, the remaining fans will increase speed to full on to supply the required cooling. If any of the six temperature sensors detect an over temperature condition, the fans will increase speed to full on to supply the required cooling. Cantata Technology - IMG 1010 Printable WebHelp 776 Hardware Reference Compliance Compliance Overview Topic Location: Hardware Reference > Compliance The IMG meets the following national and international standards. Standard USA/Canada European Union EMC/EMI FCC Part 15 ICES-003 EN55022: 1998/AI:2000/A2:2003 EN55024: 1998/AI:2000/A2:2003 EN300 386: Version 1.3.3 AS/NZS CISPR 22:2002 VCCI Safety CSA-C22.2 No. 60950-1 EN60950-1 AS/NZS 60950.1:2003 CB AS/ACIF S-016 and S-038/TNZ Telepermit JATE Green Book CB Scheme Telecom Australia/New Zealand Japan IEC 60950-1 FCC Part 68/IC CS03 TBR 4, 12, 13 Related Topics Cantata Declaration of Conformity FCC Regulatory Compliance Notices EMI Statement European Union Restriction of the Use of Certain Hazardous Substances in Electrical and Electronic Equipment, Directive 2002/95/EC (RoHS) China Restriction of Hazardous Substances (RoHS) Table Compliance to China Restriction of Hazardous Substances (RoHS) Requirements Cantata Technology - IMG 1010 Printable WebHelp 777 IMG WebHelp FCC Regulatory Compliance Notices Topic Location: Hardware Reference > Compliance Overview This section identifies the United States Federal Communications Commission compliance notices. Federal Communications Commission Part 68 Requirements This equipment complies with FCC rules, Part 68. On the back of this equipment is a label that contains, among other things, the FCC Registration Number. When you are ready to install this unit, contact your local telephone company and supply them with the following information: Standard Jack(s) for connection to the network: RJ48 Service Order Code(s): NA Facility Interface Code(s) (FIC): NA FCC ID#: US: 1RHXDNAN XL1010 Should this equipment cause harm to the telephone network, the telephone company shall, where practicable, notify the customer that temporary discontinuance of service may be required; however, where prior or written notice is not practicable, the telephone company may discontinue service forthwith, if such action is reasonable in the circumstances. You will be informed of your right to file a complaint with the FCC. The telephone company may make changes in its communications facilities, equipment, operation procedures, where such action is reasonable, required in the operation of its business, and is not inconsistent with the rules and regulations of the Federal Communications Commission. If they do, you will be notified in advance to give you an opportunity to maintain uninterrupted telephone service. Do not attempt to repair or modify this equipment. If defective, return it to the person from whom it was purchased who will in turn arrange to return it or to have it repaired by the manufacturer of his authorized agent. The telephone company may ask that you disconnect this equipment from the network until the problem has been corrected or until you are sure that the equipment is not malfunctioning. If trouble is experienced, disconnect this equipment from the telephone line to determine if it is causing the malfunction. If equipment is determined to be malfunctioning, its use shall be discontinued until the problem has been corrected. Affidavit Requirements for Connection to Digital Services An affidavit is required to be given the telephone company whenever digital terminal equipment without encoded analog content and billing protection is used to transmit digital signals containing encoded analog content which are intended for eventual conversion into voice band analog signals and re-transmitted on the network. The affidavit shall affirm that either no encoded analog content or billing information is being transmitted or that the output of the device meets Part 68 encoded analog content or billing protection specifications. 778 Hardware Reference End user/customer will be responsible to file an affidavit with the CPE to a 1.544 Mbps or subrate digital services. Until such time as subrate digital terminal equipment is registered for voice applications, the affidavit requirement for subrate services is waived. Affidavit for Connection of Customer Premises Equipment to 1.544 MBPS and/or Subrate Digital Services For the work to be performed in the certified territory of _______________________________ (Telco Name) State of _________________________ County of _______________________ I, ______________________________ (name) ________________________________ (business address) ___________________ (telephone number) being duly sworn, state: I have responsibility for the operation and maintenance of the terminal equipment to be connected to 1.544 Mbps and/or ____________ subrate digital services. The terminal equipment to be connected complies with Part 68 of the FCC rules except for the encoded analog content and billing protection specifications. With respect to encoded analog content and billing protection: ( ) I attest that all operations associated with the establishment, maintenance, and adjustment of the digital CPE with respect to analog content and encoded billing protection information continuously complies with Part 68 of the FCC Rules and Regulations. ( ) The digital CPE does not transmit digital signals containing encoded analog content or billing information which is intended to be decoded within the telecommunications network. ( ) The encoded analog content and billing protection is factory set and is not under the control of the customer. I attest that the operator(s)/maintainer(s) of the digital CPE responsible for the establishment, maintenance, and adjustment of the encoded analog content and billing information has (have) been trained to perform these functions by successfully having completed one of the following: (Check appropriate blocks) ( ) A. A training course provided by the manufacturer/grantee of the equipment used to encode analog signals; or ( ) B. A training course provided by the customer or authorized representative, using training materials and instructions provided by the manufacturer/grantee of the equipment used to encode analog singles; or ( ) C. An independent training course (e.g., trade school or technical institution) recognized by the manufacturer/grantee of the equipment used to encode analog signals; or ( ) D. In lieu of the preceding training requirements, the operator(s)/maintainer(s) is (are) under the control of a supervisor trained in accordance with ___________________ (circle one) above. 779 IMG WebHelp I agree to provide _________________________________ (Telco’s name) with proper documentation to demonstrate compliance with the information as provided in the preceding paragraph, is so requested. ______________________________________________ Signature ______________________________________________ Title ______________________________________________ Date Subscribed and sworn to before me This day of _________________, 20___ ________________________________ Notary Public My commission expires: ____________________________ Cantata Technology - IMG 1010 Printable WebHelp 780 Hardware Reference EMI Statement Topic Location: Hardware Reference > Compliance FCC Part 15, Class A: This equipment has been tested and found to comply with the limits for a Class A digital device pursuant to Part 15 of FCC Rules. These limits are designed to provide reasonable protection against harmful interference when this equipment is operated in a commercial environment. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his/her own expense. CDC Class A This digital apparatus does not exceed the Class A limits for radio noise emissions from digital apparatus set out in the Radio Interference Regulations of the Canadian Department of Communications. Le present appareil numerique n’emet pas de bruits radioelectriques depassant les limites applicables aux appareils numeriques de la Class A prescrites dans le Reglement sur le brouillage radioelectrique edicte par le Ministere des Communications du Canada. Notice: The Industry Canada label identifies certified equipment. This certification means that the equipment meets certain telecommunications network protective, operational, and safety requirements. The Department does not guarantee the equipment will operate to the user’s satisfaction. Before installing this equipment, users should ensure that it is permissible to be connected to the facilities of the local telecommunications company. The equipment must also be installed using an acceptable method of connection. In some cases, the company’s inside wiring associated with a single line individual service may be extended by means of a certified connector assembly (telephone extension cord). The customer should be aware that compliance with the above conditions may not prevent degradation of service in some situations. Repairs to certified equipment should be made by an authorized Canadian maintenance facility designated by the supplier. Any repairs or alterations made by the user to this equipment, or equipment malfunctions, may give the telecommunications company cause to request the user to disconnect the equipment. Users should ensure for their own protection that the electrical ground connections of the power utility, telephone lines, and internal metallic water pipe system, if present, are connected together. This precaution may be particularly important in rural areas. Caution: Users should not attempt to make such connections themselves, but should contact the appropriate electric inspection authority, or electrician, as appropriate. Cantata Technology - IMG 1010 Printable WebHelp 781 ClientView Pane Reference Advanced Billing Number Translation Topic Location: ClientView Pane Reference Overview Description The settings selected will be included in the charge # parameter if Billing Number translation is configured for the translation table. Related Topics Configuring Digit Matching and Translation Previous Pane Translation Entry Accessing this Pane Cantata IMG EMS -> New Routing Configuration -> New Incoming Translation Tables -> New Incoming Translation Table -> New Translation Entry -> New Advanced Billing Number Translation Maximum Objects: 1 per Translation Entry Pane Field Descriptions Nature of Address Indicates Nature of Address (NOA) to be included in the charge # parameter in case of an outgoing SS7 call (IAM message) using this translation table. Numbering Plan Indicates Numbering Plan (NP) to be included in the charge # parameter in case of an outgoing SS7 call (IAM message) using this translation table. INN Indicator Indicates the International Number Indicator (INN) to be included in the charge # parameter in case of an outgoing SS7 call (IAM message) using this translation table. Cantata Technology - IMG 1010 Printable WebHelp 782 ClientView Pane Reference 783 IMG WebHelp Advanced Carrier Number Translation Topic Location: ClientView Pane Reference Overview Description The LATA setting selected in this pane will be included in the Transient Network Selection (TNS) parameter if Carrier Number Translation is configured for the Translation Table. Related Topics Configuring Digit Matching and Translation Previous Pane Translation Entry Accessing this Pane Cantata IMG EMS -> New Routing Configuration -> New Incoming Translation Tables -> New Incoming Translation Table -> New Translation Entry -> New Advanced Carrier Number Translation Maximum Objects: 1 per Translation Entry Pane Field Descriptions Lata Setting The Lata Setting to be included in the Transient Network Selection (TNS) parameter. interLata - National format (The carrier number is 3 characters) intraLata - ITU-T format (The carrier number is 4 characters) Cantata Technology - IMG 1010 Printable WebHelp 784 ClientView Pane Reference Advanced Dialed Number Parameters Topic Location: ClientView Pane Reference Overview Description With Advanced Dialed Number Parameter matching, the IMG matches on the values of various parameters set in this pane, including: Nature of Address Internal Network Number Indicator (INN) Numbering Plan This type of matching is available only for incoming digit tables. One or more of these parameters are available for matching when the following values are set in the Incoming Translation Table: Type of Operation = Translation String to Match = Dialed Number Related Topics Configuring Advanced Number Matching Parameters for Incoming Calls Previous Pane Translation Entry Accessing this Pane Cantata IMG EMS -> New Routing Configuration -> New Incoming Translation Tables -> New Incoming Translation Table -> New Translation Entry -> New Advanced Dialed Number Translation Maximum Objects: 1 per Translation Entry Pane Field Descriptions Nature of Address Specifies the way in which a number is characterized to an SS7 network for call setup. This field indicates the Nature of Address to match, if any. 000: 001 - Subscriber Number - represents a subscriber’s location. 785 IMG WebHelp 002 - Unknown No Translation Numbering Plan Specifies the numbering plan to which a number conforms. This field indicates the Numbering Plan to match, if any. 000: 001 - ISDN/Telephony The number conforms to an ISDN numbering plan. 002 - Unknown No Translation INN Indicator (Internal Network Number Indicator) Indicates the INN Indicator to match, if any. 786 000 - Routing to International # Allowed The IMG can route the call to an internal network number. 001 - Routing to International # Not Allowed The IMG cannot route the call to an internal network number No Translation Cantata Technology - IMG 1010 Printable WebHelp ClientView Pane Reference Advanced Originating Number Parameters Topic Location: ClientView Pane Reference Overview Description With Originating Number Parameter matching, the IMG matches on the values of various parameters set in this pane: Nature of Address Internal Network Number Indicator (INN) Numbering Plan Calling Party Category Number Incomplete Indicator Screening Indicator Presentation Indicator This type of matching is available only for incoming translation tables. One or more of these parameters are available for matching when the following values are set in the Incoming Translation Table: Type of Operation = Translation String to Match = Originating Number Related Topics Configuring Advanced Number Matching Parameters for Incoming Calls Previous Pane Translation Entry Accessing this Pane Cantata IMG EMS -> New Routing Configuration -> New Incoming Translation Tables -> New Incoming Translation Table -> New Translation Entry -> New Advanced Originating Number Translation. Maximum Objects: 1 per Translation Entry Pane 787 IMG WebHelp Field Descriptions Nature of Address Specifies the way in which a number is characterized to an SS7 network for call setup. This field indicates the Nature of Address to match, if any. 000: 002 - Unknown 001 - Subscriber Number - represents a subscriber’s location No Translation Numbering Plan Specifies the numbering plan to which a number conforms. 000: 002 - Unknown 001 - ISDN/Telephony: The number conforms to an ISDN numbering plan. No Translation Calling Party Category Identifies the category with which a call is associated. 000 - Unknown 001 - Operator - French Language The call is an operator assisted call through a French language operator 002 - Operator - English Language The call is an operator assisted call through an English language operator No Translation Number Incomplete Indicator Specifies whether the digits dialed by the calling party constitute a complete number. 000 - Number is complete No Translation 001 - Number is Incomplete Screening Indicator Specifies whether the location information was provided by the user or by the network, as well as the quality of the information. 788 ClientView Pane Reference 000 - User Provided - Not Screened The user provides the location, but no screening is performed. 001 - User Provided - Verified and Passed The user provides valid location information. 002 - User Provided - Verified and Failed The user provides the location, but it is not valid. 003 - Network Provided The network provides the location information. No Translation Presentation Indicator Specifies whether the IMG can display the calling party number on the called party Caller ID screen. 000 - Presentation Allowed: The IMG can display the calling party number. 002 - Address Not Available: The calling party number is not available to display. 001 - Presentation Restricted: The IMG cannot display the calling party number. 003 - Spare No Translation Cantata Technology - IMG 1010 Printable WebHelp 789 IMG WebHelp Alternate Gatekeepers Topic Location: ClientView Pane Reference Overview Description This pane specifies a backup to the External H.323 Gatekeeper with which the IMGs configured for H.323 will communicate. Related Topics Adding an External Gatekeeper Accessing this Pane Cantata IMG EMS-> External Network Elements-> External Gatekeepers-> External Gatekeeper-> Alternate Gatekeepers Maximum Objects: 6 for each External Gatekeeper Technical Notes Pane Field Descriptions Alternate Gatekeeper Id This field provides an Id (1-6) for the object entry. Name This field provides a name for the object entry. Gatekeeper IP Address This field specifies the IP Address of the Alternate Gatekeeper. Display Table The table presents the information of all the Alternate Gatekeepers configured for the External Gatekeeper (parent). Cantata Technology - IMG 1010 Printable WebHelp 790 ClientView Pane Reference BCI Override Topic Location: ClientView Pane Reference Overview Use this pane to configure Backward Call Indicator override settings. Accessing this Pane Cantata IMG EMS -> Routing Configuration -> Channel Groups -> Channel Group (SS7) -> ISUP Group -> BCI Override Pane Field Descriptions Backward Call Indicator Ignore (default) Override Charge Indicator no indication 791 IMG WebHelp no charge charge Called party status Indicator no indication connect when free subscriber free excessive delay (ANSI only) Called party category Indicator no indication payphone ordinary subscriber End to end method indicator no end-to-end method available SCCP method available pass along method available pass along and SCCP methods available Interworking Indicator no interworking encountered interworking encountered IAM segmentation Indicator no indication additional information has been received and incorporated into call setup ISUP Indicator ISUP not used all the way ISUP used all the way Holding Indicator 792 holding not required holding required ClientView Pane Reference ISDN access indicator terminating access non-ISDN terminating access ISDN Echo control device indicator incoming half echo control device not included incoming half echo control device included SCCP Method indicator no indication connection oriented method available connectionless method available connectionless and connection oriented methods available Cantata Technology - IMG 1010 Printable WebHelp 793 IMG WebHelp Bearer Capabilities Override Topic Location: ClientView Pane Reference Overview Description This pane sets various Bearer Capability parameters. Related Topics Configuring Bearer Capabilities Override Accessing this Pane Cantata IMG EMS -> Routing Configuration -> Channel Groups-> Channel Group (ISDN) -> ISDN Group -> Bearer Capabilities Override Maximum Objects: 1 per ISDN Group Pane Field Descriptions Coding Standard CCITT National standard ISO/IEC Standard Standard for Network side of interface Ignore (default) Information Transfer Capability NOTE: To set the Information Transfer Capability you must also set the Coding Standard to a value other than Ignore. Speech Restricted Digital Info 794 Unrestricted Digital Info ClientView Pane Reference 3.1 kHz audio Video 7 khz Ignore (default) Transfer Mode Circuit Mode Ignore (default) Packet Mode User Information layer 1 protocol G.711 u-law G.721 G.711 A-law H.221 or 242 H.223 or 245 Ignore (default) Cantata Technology - IMG 1010 Printable WebHelp 795 IMG WebHelp BERT Topic Location: ClientView Pane Reference Overview Description Use this pane to initiate a BERT on a DS3 or a DS1 that is in a DS3. Related Topics DS3 Diagnostics Accessing this Pane Cantata IMG EMS -> Logical IMG -> Physical IMG -> Facility -> TDM DS3 -> BERT Tests DS1 Tests Maximum Objects: 1 per Physical IMG Pane Field Descriptions Test Mode 796 Disable (Default) DS1 Test Note: Only one DS1 can be BERT tested at any given time. DS3 Test Note: DS1’s need not be configured when testing the entire DS3 circuit. ClientView Pane Reference DS1 Offset If the Test Mode is DS1 Test, this field is used to select which DS1 that the BERT will be run on. Monitor/Generate Monitor Only (Default) Monitor and Generate Generate Only Pattern All Ones (Default) PRBS15 Alternating 01 PRBS20 PRBS23 QRSS User Defined User Defined If the Pattern is User Defined, this field defines the pattern. Test Pattern Framing Framed DS1 test Pattern (Default) Unframed DS1 Test Pattern Monitoring Fields Monitor Status This is the status of the object that is being monitored, since this is a BIT map these fields could be concatenated together. Out of Sync Detecting AIS Out of Frame Bit Error Detected Framing Error Detected BPV Violation 797 IMG WebHelp Bits Received This is the amount of Bits received in Megabits. Errors Received This is the amount of bit errors received. Elapsed Time This is the length of the time the test has been enabled. Buttons Toggle Error Mode Clicking this button enables the sending of errors on the span. Clicking it again disables it. You can see if this is enabled or disabled in the Error Mode information field. RESTART Click this button to re-start the test. This resets the Bits Received, Errors Received and Elapsed Time values to 0. Cantata Technology - IMG 1010 Printable WebHelp 798 ClientView Pane Reference Call Tracing Topic Location: ClientView Pane Reference Overview Description Use this pane to initiate Call Tracing. A log will be generated showing events that occur on a per-call basis. See Related Topics Call Tracing Sample Call Trace Accessing this Pane Cantata IMG EMS -> Logical IMG -> Physical IMG -> Call Tracing Maximum Objects: 1 per Physical IMG Pane Field Descriptions Call Tracing Period The amount of time in seconds the trace will be logged. Range: 1-7200 Call Tracing Directory The location of the trace log. The default is opt/cantata/common/calltracing. Monitoring Fields Call Tracing Status This field indicates Call Tracing is enabled or disabled, as well as error conditions. To view the current status, click the Update Status button. 799 IMG WebHelp Call Tracing Time Remaining The amount of time remaining in the current trace period. To view the current value, click the Update Status button. Buttons Start/Reset Call Tracing Stop Call Tracing Update Status 800 Cantata Technology - IMG 1010 Printable WebHelp ClientView Pane Reference Cantata IMG EMS Topic Location: ClientView Pane Reference Overview Description This pane is informational only. You do not enter any values. You create a connection between the Element Management System (EMS) and the IMG when you enter the IP address or name of the host when you log in to ClientView. Right-click Cantata IMG EMS to create any of the following: Logical IMG Signaling Variants IP Bearer Traffic Profiles External Network Elements Routing Configuration Accessing this Pane Configuration -> Cantata IMG EMS Pane Monitoring Fields IP Address 1 Port Number 1 Connection State 1 IP Address 2 Port Number 2 Connection State 2 Number of App Count 801 IMG WebHelp Buttons MRTG Scripts The Multi Router Traffic Grapher (MRTG) is a tool to monitor various areas on network links. MRTG generates HTML pages containing PNG images which provide a live visual representation of this traffic. To generate MRTG logs, press the MRTG Scripts button. You can also update MRTG in the Channel Groups pane. See An Overview of MRTG. Cantata Technology - IMG 1010 Printable WebHelp 802 ClientView Pane Reference CAS Circuits Topic Location: ClientView Pane Reference Overview Description Use this pane to configure CAS Circuits. Only TDM spans configured for CAS signaling in the Facilities pane will be available to use in CAS Channel Groups. Previous Configuration Required Signaling Variant Related Topics Configuring CAS Accessing this Pane Cantata IMG EMS -> Routing Configuration -> Channel Groups -> Channel Group (Type CAS) -> Channel Associated Signaling -> CAS Circuits Maximum Objects: Pane Field Descriptions IMG Name 803 IMG WebHelp The name of the IMG on which the group resides. IMG Interface Signaling Bearer Start Interface Offset/Start Channel/End Interface Offset/End Channel Select from spans/channels configured for CAS signaling as required. Only TDM spans configured for CAS signaling in the Facilities pane will appear in this drop-down list. Monitoring Fields Trunk Type T1 E1 CAS Channel Count Number of CAS Channels Channel Count The number of CAS Channels in the group. Busy Out Flag This field indicates if Busy Out is enabled or disabled in the Signaling Variant pane. To Busy Out channels Busy Out must be enabled. Busy Out Disabled (default) Busy Out Enabled To Busy Out a channel or range of channels, select them in the bottom frame, rightclick, and select Busy Out. 804 ClientView Pane Reference Buttons Update Status Updates the status of CICs shown in the Status Pane Cantata Technology - IMG 1010 Printable WebHelp 805 IMG WebHelp Cause Code Tables Topic Location: ClientView Pane Reference Overview Description From here you can create a new Cause Code table by selecting New Cause Code Table. Related Topics Configuring a Cause Code Mapping Table Configure a Channel to Release with Cause Configuring a Channel to Play Treatment Accessing this Pane Cantata IMG EMS -> New Routing Configuration -> New Cause Code Tables Cantata Technology - IMG 1010 Printable WebHelp 806 ClientView Pane Reference Channel Associated Signaling Topic Location: ClientView Pane Reference Overview Description Use this pane to assign a CAS variant to a Channel Group. Previous Configuration Required Signaling Variant Next Configuration Task CAS Circuits Related Topics Configuring CAS Accessing this Pane Cantata IMG EMS -> Routing Configuration -> Channel Groups -> Channel Group (Type CAS) -> Channel Associated Signaling Maximum Objects: Pane Field Descriptions CAS Variant Select the desired variant from those that have been previously configured with the Signaling Variant pane. Cantata Technology - IMG 1010 Printable WebHelp 807 IMG WebHelp Channel Group Topic Location: ClientView Pane Reference Overview Description This pane defines incoming and outgoing attributes for a channel. It identifies the tables to be used for routing and translating calls. It also identifies the IP bearer profiles for H.323 channel groups. NOTE: Many of the parameters that you specify for a channel group are defined as routing-related tables. Therefore, you must define the applicable tables at the routing level before you can assign them to a channel group. Related Topics Creating a Channel Group Creating_an_H_323_Channel_Group Creating a SIP Channel Group Creating_an_SS7_Channel_Group Creating an ISDN Channel Group Accessing this Pane Cantata IMG EMS -> Routing Configuration -> Channel Groups-> Channel Group Maximum Objects: 672 per EMS Technical Notes Pane 808 ClientView Pane Reference Field Descriptions Name This field identifies the name of the Channel group. ID A unique ID for this Channel Group. Channel Group Function This field identifies the direction of calls on this Channel Group. Incoming/Outgoing Trunks: Two way traffic Outgoing Trunks: One way traffic, Outgoing only Incoming Trunks: One way traffic, Incoming only Signaling Type The signaling to be performed on this Channel Group. SS7 H323 CAS 809 IMG WebHelp ISDN SIP Incoming Translation Table Identifies the Incoming translation table that the IMG uses for digit translation and error detection for incoming calls received on this Channel Group. Route Table Identifies the route table to be used for routing calls received on this Channel Group. Incoming Treatment Indicates the way in which the IMG releases a failed incoming call. Play Treatment Release w/Cause Cause Code Mapping Table Specifies an override treatment for a cause code, enabling you to customize the cause codes with alternate treatments. None Incoming IP Profile Indicates the IP characteristics for incoming Voice over IP calls on this Channel Group, including voice encoding compression, payload size, echo suppression, and other parameters. This applies to H.323 and SIP channel groups only. Outgoing Translation Table Indicates the outgoing translation table that the IMG uses for digit translation for outgoing calls on this channel Group. Hunting Options This field specifies the hunting algorithm used for selecting a channel to route an outgoing call. Alternate Even LRU (Lease Recently Used) 810 Alternate Odd Most Idle Round Robin Clockwise Round Robin Counter Clockwise ClientView Pane Reference Sequential Bottom Up Sequential Top Down Outgoing Treatment Specifies the way in which the IMG releases a failed outgoing call. Play Treatment Release w/Cause Ingress Side will Play Call Progress Tones This field specifies if the incoming side will play call progress tones or not. True False Outgoing IP Profile Identifies the IP characteristics for outgoing Voice Over IP calls on this Channel Group, including voice encoding compression, payload size, echo suppression, and other parameters. This applies to H.323 and SIP channel groups only. Treatment Table Identifies the treatment table that the IMG uses if a call fails and the outgoing treatment is set to Release w/cause. TreatmentTable ID: 1: Primary TreatmentTable ID: 2: Secondary Reattempt Cause Code The IMG will automatically attempt to re-route calls in response to the following cause codes: 42,41,34. Use this field to select up to 4 additional Cause Codes for which the IMG will re-attempt a new call, per trunk group. Receive Gain/Transmit Gain Configures 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. 811 IMG WebHelp Gain Control is not supported for pre-call announcements, treatments, or ringback. ___________________________________________________________________ _____________________________ The following fields relate to Overlap Signaling. See Overlap Signaling for more information. Overlap Enable Enable Disable (default) Enable overlap signaling on inbound Channel Groups when the outbound channel group does not support Overlap Signaling (SIP, H.323). The IMG will collect address digits until a Termination Condition is met and then continue call processing. See below for protocol-specific information. Overlap is only applied to the inbound channel, even on an Incoming/Outgoing Trunk. By default, the IMG passes digits to the outbound side as they are received. Termination Digits Digit to indicate end of overlap sending. Default for SS7 Channel Group = # Not used for ISDN Minimum # of Digits The minimum number of digits that the IMG will wait for (collect) in the incoming side before attempting an outseize on the outgoing side. 1-24 (default = 24) NOTE: This field is different from the Max # CdPN digits (IAM) field in the ISUP Group pane, which applies to the outgoing ss7 calls. Inter SAM Timeout Time to wait for another SAM digit before continuing with call processing. Default = 1500 Not used for ISDN Total Overlap Timeout Amount of time to wait for either Minimum # of Digits or Inter SAM timeout to occur before continuing with call processing. 812 ClientView Pane Reference Default = 18000 ___________________________________________________________________ _____________________________ LNP Based Routing Enable Disable (default) See Local Number Portability (LNP). Informational Fields Cantata Technology - IMG 1010 Printable WebHelp 813 IMG WebHelp Channel Group (Route List Entry) Topic Location: ClientView Pane Reference Overview Description Use this pane to add a Channel Group to a Route List. A Route List can include up to 20 channel groups. Related Topics Configuring Route Lists Accessing this Pane Cantata IMG EMS-> Routing Configuration-> Route Lists-> Route List -> Route List Entry -> Channel Group Maximum Objects: 64 Pane Field Descriptions Group Name The name of the Channel Group to add to the Route List. Display Table This pane displays all of the Channel Groups in the route list. Cantata Technology - IMG 1010 Printable WebHelp 814 ClientView Pane Reference Channel Groups Topic Location: ClientView Pane Reference Overview Description From here you create a new channel group by right-clicking on Channel Groups and selecting New Channel Group. Related Topics Creating a Channel Group Accessing this Pane Cantata IMG EMS -> New Routing Configuration -> New Channel Groups Status Pane By clicking the Object Table button in the Status Pane you can view the following call statistics for all configured channel groups. Incoming Calls (last 15 minutes) Outgoing Calls (last 15 minutes) Incoming Calls Answered (last 15 minutes) Outgoing Calls Answered (last 15 minutes) Average Hold Time for Answered Calls (last 15 minutes) Buttons MRTG Scripts To update MRTG after adding a Channel Group, press the MRTG Scripts button. See An Overview of MRTG Cantata Technology - IMG 1010 Printable WebHelp 815 IMG WebHelp Circuit Group Topic Location: ClientView Pane Reference Overview Description This pane configures an SS7 CIC Group. Related Topics Assigning_SS7_CICs_to_an_ISUP_Group Accessing this Pane Cantata IMG EMS -> Routing Configuration -> Channel Groups -> Channel Group (of type SS7) -> ISUP Group -> Circuits Maximum Objects: 768 per SS7 Channel Group Pane Field Descriptions IMG Name The name of the IMG on which the group resides. 816 ClientView Pane Reference IMG Interface Signaling Bearer Start Interface Offset End Interface Offset End Channel Start CIC Skip Channel 16 (E1 Only) True (Skip Channel 16) False (Do Not Skip Channel 16) Enabling this field (True) will result in Channel 16 not being used when CIC are assigned. The CIC numbering will be sequential whether this is enabled or not (see below). Skip Channel 16 Not Enabled (False): Channel CIC Number 15 16 17 Skip Channel 16 Enabled (True): Channel 15 16 CIC Number Not Used 17 16 Monitoring Fields Trunk Type T1 E1 CIC Count 817 IMG WebHelp The number of CICs in the group. Channel Count Buttons Update Status Updates the status of CICs shown in the Status Pane Display Table COT Test To initiate a Continuity Check on a CIC or a group of CICs, right-click on the CIC(s) entry and select Continuity Check Request. The results will appear in the Manual COT Result column (Start, Start NACK, Success, Failure). NOTE: COT cannot be performed on JT-ISUP CICs. Circuit Query Message 818 ClientView Pane Reference To initiate a Circuit Query Message on a CIC or a group of CICs, right-click on the CIC(s) entry and select Circuit Query Message. The CIC State and Block State values will be updated accordingly if there is any change. Cantata Technology - IMG 1010 Printable WebHelp 819 IMG WebHelp Configuration Topic Location: ClientView Pane Reference Overview Description This represents the default configuration file. You can change the name in the UserSpecified field. Accessing this Pane Click Configuration default. Pane Cantata Technology - IMG 1010 Printable WebHelp 820 ClientView Pane Reference Digit Mapping Topic Location: ClientView Pane Reference Overview Description Digit mapping object in CAS is used to configure which stage and string of data within an incoming CAS call contains the information required to correctly route that call. These parameters include the Dialed Number (DNIS or DN), Calling Party Number (ANI), and for R2 CAS, Category (CAT) Tests and conditional statements can also be configured to increase flexibility when the required data can be received in several ways. A digit mapping object must be created for each parameter required (DNIS, ANI, CAT). Within each digit mapping object, enter in which stage and string number of the incoming CAS call contains that data. Previous Configuration Required Signaling Variant Related Topics Configuring CAS Accessing this Pane Cantata IMG EMS -> Signaling -> <Variant Name> -> Digit Mapping Maximum Objects: Pane Field Descriptions String Type Indicates the type of routing information is to be configured. Called Part Number Calling Party Number 821 IMG WebHelp Calling Party Category Calling Party Overlap (Applies to String Type of Calling Party Number only) ANI CAT + ANI NOTE: If no digit map is setup for CAT = Stage 4, and CAT+ANI is selected, in Stage 2, then Stage 2 CAT will be passed along. Instruction 1 Always use this string or test for presence. Use Unconditionally If Stage-String Present Instruction 2 Indicates which stage and string in the incoming CAS call contains the routing information. Stage 1 - String 1 Stage 2 - String 1 Stage 1 - String 2 Stage 2 - String 2 Stage 3 - String 1 Stage 3 - String 2 Stage 4 - String 1 Stage 4 - String 2 Instruction 3 If there no conditional statement, instructions are complete. Instructions Complete Stage 1 - String 2 822 Stage 1 - String 1 Stage 2 - String 1 Stage 2 - String 2 Stage 3 - String 1 Stage 3 - String 2 Stage 4 - String 1 ClientView Pane Reference Stage 4 - String 2 Example For example, if the IMG will be receiving Feature Group D CAS with ANI (Stage1:String1), DN (Stage1:String2), you must configure 2 digit mapping objects. Object 1 String Type = Calling Party Number Instruction 1 = Use Unconditionally Instruction 2 = Stage 1 String 1 Instruction 3 = Instructions Complete Object 2 String Type = Called Party Number Instruction 1 = Use Unconditionally Instruction 2 = Stage 1 String 2 Instruction 3 = Instructions Complete Example The following illustrates the digit mapping you would configure for DN, CAT+ANI, CAT for E1R2 calls. Field Descriptions String Type – Which type of routing information is to be configured. Instruction 1 – Testing if Stage-String is present. Instruction 2 – The stage-string being tested to see if it exists. Instruction 3 – Configure the case when it is TRUE (PRESENT). Instruction 4 & 5 – Which stages-Strings contain that information. 823 IMG WebHelp Instruction 6 – Configure the case when it is FALSE (NOT PRESENT). Instruction 7 – Which stage-string contains the information. Instruction 8 – END of instruction list. Cantata Technology - IMG 1010 Printable WebHelp 824 ClientView Pane Reference DNS Client Topic Location: ClientView Pane Reference Overview Description Use this pane to assign DNS Servers to a physical IMG. Related Topics Configuring DNS for SIP Accessing this Dialog Box Cantata IMG EMS-> Physical IMG-> New DNS Client Maximum Objects: 1 per Physical IMG Pane Field Descriptions DNS Client Network Interface This is automatically populated with the IP Address of the IMG CPU/Network Interface. Primary DNS Server The Primary DNS Server. 825 IMG WebHelp Secondary DNS Server The Secondary DNS Server. Tertiary DNS Server The Tertiary DNS Server. Cantata Technology - IMG 1010 Printable WebHelp 826 ClientView Pane Reference DNS Server Topic Location: ClientView Pane Reference Overview Description Use this pane to configure a DNS Server for Domain Name lookups. Related Topics Configuring DNS for SIP Accessing this Pane Cantata IMG EMS-> External Network Elements-> DNS Servers-> DNS Server Maximum Objects: 8 per EMS Pane Field Descriptions DNS Server Id This field is automatically populated with the next number in sequence. DNS Server Name A unique name you enter to identify the server. DNS Server IP Address The IP Address of this DNS Server. Display Table Shows the information for all DNS servers configured. Cantata Technology - IMG 1010 Printable WebHelp 827 IMG WebHelp DNS Servers Topic Location: ClientView Pane Reference Overview Description You must create this container object before you configure individual DNS Servers. To configure a DNS Server, after you create this object, right-click DNS Servers and select New DNS Server. Related Topics Configuring DNS for SIP Accessing this Pane Cantata IMG EMS-> External Network Elements-> DNS Servers Maximum Objects: 1 Pane Field Descriptions Domain Name The Domain Name of your network. This is appended to the Host Name for DNS lookups. Cantata Technology - IMG 1010 Printable WebHelp 828 ClientView Pane Reference DS3 Physical Span Topic Location: ClientView Pane Reference Overview Description Use this pane to configure a DS3 span. Related Topics Configuring a Single DS3 Span Configuring a Range of DS3 Spans Accessing this Pane Cantata IMG EMS -> Logical IMG -> Physical IMG -> Facility -> TDM DS3 -> DS3 Physical Span Maximum Objects: 28 per Physical IMG Pane Field Descriptions Offset The physical span being configured. 829 IMG WebHelp Loop Timing Type Specifies whether that specific span is used for primary loop timing, secondary loop timing or not. Primary Not Timing Source Secondary Framing Specifies whether the framing of the span is ESF or D4. ESF D4 Signaling Clear Channel Line Length Specifies the length of the DS3 line. 0-225 (default) 226-450 Line Coding Specifies the line coding of T1 span. Bit 7 zero suppressing B8ZS zero suppressing Cantata Technology - IMG 1010 Printable WebHelp 830 ClientView Pane Reference E1 Physical Span Topic Location: ClientView Pane Reference Overview Description This object specifies the physical format of an E1 logical span. The user will be allowed to configure an E1 span, if the IMG 1010 is configured for E1 via the host flags. Related Topics Configuring a T1 or E1 Bearer Span Accessing this Pane Cantata IMG EMS-> Logical IMG-> Physical IMG-> facility -> TDM DS1 (of type E1) > E1 Physical Span Maximum Objects: 1 per TDM DS1 object Technical Notes Pane Field Descriptions Loop Timing Type Specifies whether that specific span is used for primary loop timing, secondary loop timing or not. Primary Not Timing Source Secondary 831 IMG WebHelp Coding Method Specifies the line coding of that specific span: AMI HDB3 Enable CRC4 Specifies whether CRC4 error checking is enabled or disabled: True False Enable FEBE Specifies whether FEBE is enabled or disabled: True False Line Length Specifies whether the E1 interface is 75 ohm or 120 ohm. G.703 ITU-T (75 ohm) G.703 ITU-T (120 ohm) Signaling Method Clear Channel Set this for SS7 and ISDN spans. CAS Set this for CAS spans. Layer 1 Management E1 Layer 1 Mgmt Austel-ISDM E1 Layer 1 Mgmt Euro-ISDN E1 Layer 1 Mgmt Transmit All Zeros Specifies whether transmit all zeros is enabled or disabled. 832 True False ClientView Pane Reference Loopback Mode Bearer or Signaling DS1’s can be configured for local or remote loopback. Each span offset must be individually configured. No Loopback Remote Loopback Local Loopback NOTE: When you place a span in loopback mode the Span Status will indicate Out Of Service. Following the test you must manually put the span back in service by selecting the In Service button. See Loopback Testing for more information. Informational Fields Span Status This monitoring field indicates the current status of the E1 span. Buttons In Service This button brings the E1 span in service. NOTE: You must manually bring a span back in service following a loopback test. Out Of Service This spans takes the E1 span out of service. Default E1 Format The table below shows the default format for E1 spans. You must enable Clear Channel signaling to use timeslot 16 as a voice channel or for out-of-band signaling (for example, an ISDN application). NOTE: Clear Channel signaling must be enabled to use timeslot 16 as a D channel in ISDN applications. NOTE: For CAS, channel 16 will appear as Out of Service. Timeslot Channel on IMG Channel on CSP * 0 0 31 1 1 0 2 2 1 Description Alarms and Framing 833 IMG WebHelp 3 3 2 4 4 3 5 5 4 6 6 5 7 7 6 8 8 7 9 9 8 10 10 9 11 11 10 12 12 11 13 13 12 14 14 13 15 15 14 16 16 30 17 17 15 18 18 16 19 19 17 20 20 18 21 21 19 22 22 20 23 23 21 24 24 22 25 25 23 26 26 24 27 27 25 28 28 26 29 29 27 30 30 28 31 31 29 Voice Channels In-band line signaling (CAS) Voice Channels * This information is provided for customers who are also using a Cantata Converged Services Platform (CSP). See the Cantata web site for information about the CSP. 834 ClientView Pane Reference Cantata Technology - IMG 1010 Printable WebHelp 835 IMG WebHelp ENUM Server Topic Location: ClientView Pane Reference Overview Description Use this pane to configure an ENUM Server. You assign an ENUM Server to a Channel Group in the IP Network Element pane. Pre-requisite Configuration ENUM Server Set Related Topics SIP ENUM Accessing this Pane Cantata IMG EMS-> External Network Elements-> ENUM Server Set-> ENUM Server Maximum Objects: 3 per ENUM Server Set Pane Field Descriptions ENUM Server Id This field is automatically populated with the next number in sequence. ENUM Server Name A unique name you enter to identify the server. ENUM Server IP Address The IP Address of this ENUM Server. Cantata Technology - IMG 1010 Printable WebHelp 836 ClientView Pane Reference ENUM Server Set Topic Location: ClientView Pane Reference Overview Description Use this pane to configure an ENUM Server Set. Related Topics SIP ENUM ENUM Server Accessing this Pane Cantata IMG EMS -> New External Network Elements -> New ENUM Server Set Maximum Objects: 4 per EMS Pane Field Descriptions Name A unique name for this server set. Domain Name The domain name of this server set. SIP Profile The SIP Profile associated with this server set. Select form drop-down list of previously configured SIP Profiles. 837 IMG WebHelp ENUM Server Set ID A unique ID assigned to his server set. Cantata Technology - IMG 1010 Printable WebHelp 838 ClientView Pane Reference External Gatekeeper Topic Location: ClientView Pane Reference Overview Description This object specifies primary Gatekeepers with which the H.323 configured IMGs will communicate. Related Topics Adding an External Gatekeeper Accessing this Pane Cantata IMG EMS-> External Network Elements-> External Gatekeepers-> External Gatekeeper Maximum Objects: 1 per EMS Technical Notes Pane Field Descriptions Name This field provides a name for the object entry. Gatekeeper Auto Discovery This setting determines if the IMG automatically sends gatekeeper discovery messages (GRQ) and are automatically sent to this External Gatekeeper. This applies to both initial discovery, registration, and following a failure. Enable The IMG automatically sends GRQ - Gatekeeper Request and RRQ Registration Request to the external gatekeeper. Disable You must manually discover and register with the gatekeeper using the 839 IMG WebHelp buttons in the H.323 Signaling pane. You must also do this manually following a failure. Gatekeeper IP Address This field specifies the IP Address of the External Gatekeeper. If you don't know the IP Address you can enter 224.0.1.41 to broadcast for an available gatekeeper. Time to Live (sec) The Time to Live value in seconds. The maximum is 655 sec. Monitoring Fields Gatekeeper TTL Value The Time to Live value returned by the Gatekeeper upon registration. Display Table A table displaying the information from the Alternate Gatekeepers is displayed if any Alternate Gatekeepers are defined. Cantata Technology - IMG 1010 Printable WebHelp 840 ClientView Pane Reference External Gatekeepers Topic Location: ClientView Pane Reference Overview Description To create an external gatekeeper, right-click External Gatekeepers and select New External Gatekeepers. Related Topics Adding an External Gatekeeper Accessing this Pane Cantata IMG EMS -> New External Network Elements -> New External Gatekeeper Cantata Technology - IMG 1010 Printable WebHelp 841 IMG WebHelp External Gateway Topic Location: ClientView Pane Reference Overview Description Use this pane to specify external SIP or H.323 gateways from which the IMG may receive an incoming call. To configure a group of gateways, use the Gateway Mask field to validate a range of IP addresses. Related Topics Adding an External Gateway Accessing this Pane Cantata IMG EMS-> External Network Elements-> External Gateways-> External Gateway Maximum External Gateway Objects: 1024 per EMS Technical Notes Pane Field Descriptions Name A unique name identifying the external gateway. 842 ClientView Pane Reference Gateway Signaling Protocol H.323 (default) SIP Gateway Address Type Gateway IP Address (default) Host Name (SIP only) Gateway IP Address If the Gateway Address Type is Gateway IP Address, this field specifies the IP Address of the External Gateway. Gateway Mask Use this field to configure the IMG to accept calls from multiple gateways with one entry. The Gateway Mask in conjunction with the Gateway IP Address field determines the range of IP Addresses from which the IMG will accept calls. If the Incoming IP Address ANDed with the Gateway Mask equals the Gateway IP Address ANDed with the Gateway Mask then the call will be processed. Note that for outbound calls, only the specific IP address in the Gateway IP Address field is used. Examples 1. Only the IP address specified in the Gateway IP Address field is accepted. This is the default. Gateway IP Address: 10.11.12.1 (default) Gateway Mask: 255.255.255.255 2. IP address ranging from 10.11.12.1 to 10.11.12.128 will be processed Gateway IP Address: 10.11.12.1 Gateway Mask: 255.255.255.128 3. IP address ranging from 10.11.12.1 to 10.11.12.31 will be processed Gateway IP Address: 10.11.12.1 Gateway Mask: 255.255.255.224 4. To accept calls from any gateway: 843 IMG WebHelp Gateway IP Address: ANY Gateway Mask: 0.0.0.0 Gateway Host Name (SIP Only) If the Gateway Address Type is Host Name, this field specifies the Host Name of the External Gateway. To look up a gateway based on Host Name you must have a DNS Server configured. Gateway Transport Type This can vary for different gateways and does not need to match the default IMG Transport Type. TCP (default) UDP (SIP Only) Gateway Remote Port The port used for communication with the remote gateway. ___________________________________________________________________ ______________________________ Gateway Registration Required (SIP Only) This field indicates if the IMG must register with the gateway. Applies to SIP Gateways only. Registration Expiration Interval (sec) (SIP Only) Use this field to control the registration refresh interval. Applies to SIP Gateways only. 10-7200 Default = 3600 ___________________________________________________________________ ______________________________ SIP Profile Select a SIP Profile that defines various SIP features for this gateway. OPTIONS Keep Alive Use his field to enable the SIP Busy Out feature on a gateway. You configure SIP Busy Out parameters with the SIP Options KeepAlive pane. 844 Enable Disable (default) ClientView Pane Reference ___________________________________________________________________ ____________________________ The following fields relate to SIP Privacy. See Configuring SIP Privacy. Trusted This field applies to SIP Signaling only. Yes (default) No Privacy This field applies to SIP Signaling only. On Off (default) ___________________________________________________________________ ____________________________ Display Table This table shows all the currently configured External Gateways. Cantata Technology - IMG 1010 Printable WebHelp 845 IMG WebHelp External Gateways Topic Location: ClientView Pane Reference Overview Description To create an external gateway, right-click External Gateways and select New External Gateways. Related Topics Adding an External Gateway Accessing this pane Cantata IMG EMS -> New External Network Elements -> New External Gateways Cantata Technology - IMG 1010 Printable WebHelp 846 ClientView Pane Reference External Network Elements Topic Location: ClientView Pane Reference Overview Description To create a new external network element, right-click External Network Elements and choose one of the following: New External Gatekeepers New Radius Servers New External Gateways New NFS Servers Accessing this Pane Cantata IMG EMS -> New External Network Elements Cantata Technology - IMG 1010 Printable WebHelp 847 IMG WebHelp Facility Topic Location: ClientView Pane Reference Overview Description This is a container object from where you configure individual TDM or IP spans. After you create the Facility object you must commit the configuration before proceeding. Right-click Facility and select one of the following: New TDM DS1 New Bearer IP New TDM DS3 NOTE: To configure a range of TDM spans, use the Facility Wizard. Related Topics Creating a Facility Object Pane Monitoring Fields Synchronization Mode Cantata Technology - IMG 1010 Printable WebHelp 848 ClientView Pane Reference Facility Wizard Topic Location: ClientView Pane Reference Overview Description Use the Facility Wizard to configure a range of TDM spans. Related Topics Creating a Facility Object Steps 1. Right-click Facility 2. Click the Facility Wizard button 3. The first pane that appears is the TDM DS1 Wizard pane, shown below. Complete the fields as required and click OK. The next pane that appears depends on whether the span is E1 or T1. See the T1 Physical Span pane reference or E1 Physical Span pane reference. Field Descriptions Trunk Type This field is automatically set to T1 or E1 depending on the type of IMG you have. Component ID This field specifies whether the TDM DS1 objects to be configured through the wizard are part of the Signaling spans or the Bearer spans. Signaling Bearer 849 IMG WebHelp Start Interface This field specifies the starting interface to configure. Allowable values will be 0 to 3, if the Component ID is set to ‘Signaling’ and will be 0 –27, if the Component ID is set to ‘Bearer’. 0–3 (If Component ID is set to Signaling) 0 – 27 (If Component ID is set to Bearer) Span count This field specifies how many offsets to be configured including the Start Interface. Cantata Technology - IMG 1010 Printable WebHelp 850 ClientView Pane Reference FCI Override Topic Location: ClientView Pane Reference Overview Description Use this pane to configure the IMG to override various Forward Call Indicators parameters with specified values. 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. You enable FCI Override by selecting Override in the FCI Override field, and then select values for each parameter. Related Topics Configuring FCI Override Accessing this Pane Cantata IMG EMS -> Routing Configuration -> Channel Groups -> Channel Group (SS7) -> ISUP Group -> FCI Override Maximum Objects: 1 per ISUP Group Pane Field Descriptions 851 IMG WebHelp * Default if FCI Override is enabled Forward Call indicator Ignore - FCI Override is disabled and the IMG sends whatever value it receives (or the default if no value received) (Default) Override - Values in FCI parameters will be overridden by values selected in corresponding field below. National/International call indicator National * International End-to-end Method Indicator No end-to-end method available * SCCP method available pass along method available pass-along and SCCP methods available Interworking Indicator No interworking encountered * interworking encountered Information Indicator No end-to-end information available * end-to-end information available ISUP Indicator ISUP not used all the way * ISUP used all the way ISUP preference Indicator ISUP preferred all the way * ISUP required all the way ISUP not required all the way ISDN Access Indicator 852 ClientView Pane Reference originating access non-ISDN * originating access ISDN SCCP Method Indicator No indication * connection oriented method available connectionless method available connectionless and connection oriented method available. Cantata Technology - IMG 1010 Printable WebHelp 853 IMG WebHelp Filter/Timer Configure Topic Location: ClientView Pane Reference Overview Description Use this pane to adjust CAS trunk and line signaling filters and timers. Typically, this is only required when the trunk or line that the IMG is connected to is not operating to line interface specifications. All timers and filters are set to default values based on industry specifications when the channel trunk type is configured. Previous Configuration Required Signaling Variant Related Topics Configuring CAS Accessing this Pane Cantata IMG EMS -> Signaling -> <Variant Name> -> Filter/Timer Configure Maximum Objects: Pane Field Descriptions PPL Filter/Timer Type Generic Protocol Timer DTMF Signaling Timer (E1 Only) R2 Signaling Timer (E1 Only) MFR1 Signaling Timer (E1 Only) PPL Filter/Timer Selection R2 Signaling Timers 854 0x01 Pulse Duration (15) The length of time to transmit a pulsed R2 signal. ClientView Pane Reference 0x02 Pulse Delay (15) The minimum delay between the end of transmission of the last R2 signal of the compelled cycle and the start of transmission of a pulsed signal. 0x03 Minimum Valid Duration (7) The minimum length of time a signal must be received before it is declared a valid signal. 0x04 Maximum Tone State Change (2000) ñ the length of time to scan a receive R2 signal state change. DTMF Signaling Timers 0x01 DTMF Transmit Duration (6) 0x03 DTMF Maximum Receive 1st Digit Detect (2000) 0x02 DTMF Transmit Inter-digit Duration (6) 0x04 DTMF Maximum Receive Inter-digit Timeout (2000) 0x05 DTMF Minimum Receive Digit Duration (4) 0x06 DTMF Minimum Receive Inter-digit Timeout (4) MFR1 Signaling Timers 0x01 MFR1 Transmit KP Duration (10) 0x03 MFR1 Transmit Inter-digit Duration (6) 0x02 MFR1 Transmit Digit Duration (6) 0x04 MFR1 Minimum Receive KP Duration (5) 0x05 MFR1 Minimum Receive Digit Duration (3) 0x06 MFR1 Maximum Receive KP Detect (1000) 0x07 MFR1 Minimum Receive Inter-digit Timeout (3) 0x08 MFR1 Maximum Receive Inter-digit Timeout (1000) PPL Filter/Timer Value (ms) Use the slider or enter a value in the Value: box. 855 IMG WebHelp Cantata Technology - IMG 1010 Printable WebHelp 856 ClientView Pane Reference H323 Signaling Pane Topic Location: ClientView Pane Reference Overview Description Use this pane to assign a Network Interface for H.323 Signaling and various H.323 configuration. Related Topics H323 Overview Configuring H.323 Signaling Accessing this Pane Cantata IMG EMS -> Logical IMG -> Physical IMG -> Signaling -> H323 Maximum Objects: 1 per Physical IMG Technical Notes Pane 857 IMG WebHelp Field Descriptions NOTE: Fields with an asterisk (*) are only required if you are connecting to an H.323 gatekeeper. Once you have registered with a gatekeeper, these fields cannot be changed until you unregister. H.323 Id This field defines the H.323 Id to be used by the concerned Network Interface. This must be unique per IMG registering to the same Gatekeeper. You cannot make subsequent changes to this field if Gatekeeper Support is enabled and you are registered with a gatekeeper. H.323 Signaling IP Address This field specifies the IP Address of the Network Interface being provisioned for H.323 Signaling. H.245 Tunneling This field enables inbound tunneling. You can enable outbound tunneling in the IP Bearer Profile used for outbound calls. See H245 Tunneling. Enable Disable Gatekeeper Support Enabled Allows the IMG to communicate with an external H.323 gatekeeper, which must be configured with the External Gatekeeper pane. Once the IMG has registered with a Gatekeeper, changes to the gatekeeper related fields (indicated with an asterisk) will not be allowed. Disabled Upon changing this field to Disabled, the IMG will automatically send a URQ (unregistration request) message to the Gatekeeper. E.164 Number * This field specifies an alias for the H.323 gateway as an ITU E.164 number. You cannot make subsequent changes to this field if Gatekeeper Support is enabled. Gateway URL * This field specifies an alias for the H.323 gateway as a Uniform Resource Locator (URL). You cannot make subsequent changes to this field if Gatekeeper Support is enabled. Gateway EMail * 858 ClientView Pane Reference This field specifies an alias for the H.323 gateway as an e-mail address. You cannot make subsequent changes to this field if Gatekeeper Support is enabled. H323 Variant This drop-down selection specifies the H.323 variant being used. ITU: International Telecommunications Union H323 Version This drop-down selection specifies the H.323 version being used. H.323 V2: Version 2 H323 terminal Type This drop-down selection specifies the H.323 terminal type being used. This value is used in H.245 MSD procedure. GW with no MC: Gateway with no Media Controller Gateway Technology Prefix * If your gatekeeper requires a prefix, enter it here. The default is 1#. Note that you must also add and strip the prefix when routing to the gatekeeper. See Configuring Digit Matching and Translation. Initiate TCS on all Incoming Calls If enabled, the IMG will not start the H.245 timers on an Incoming fastStart call. The H245 ppl will remain in state 41 until H225 notifies H245 that the call is released, an H245 EndSession Message or a TCS is received. If the TCS message is received all the timers are started and the IMG expects to get all the mandatory messages or the call will get released Enable (default) Disable Monitoring Fields Gatekeeper Connection Status Once the IMG discovers a gatekeeper or registers the name, the gatekeeper name displays here. Buttons You can Discover and Register with a gatekeeper manually using these buttons. To automatically Discover and Register with a gatekeeper, enable Gatekeeper Auto Discovery in the External Gatekeeper pane. 859 IMG WebHelp To make changes to a gatekeeper that is currently registered, you must Unregister, make changes, then Discover and Register again. Discover GK Unregister with GK 860 Register with GK Cantata Technology - IMG 1010 Printable WebHelp ClientView Pane Reference H323 Timers Pane Topic Location: ClientView Pane Reference Overview Description You can configure various H.225 and H.245 timers used in H.323 Signaling. NOTE: If you make changes to the default timer values and then later delete the H.323 Timer object and then create a new one, the timer values will not be reset to the default values but will retain the values you entered. If you wish to revert to the default values you must do so manually. Related Topics Configuring H.323 Signaling Accessing this Pane Cantata IMG EMS -> Logical IMG -> Physical IMG -> Signaling -> H323 Signaling -> H323 Timers Maximum Objects: 1 per H.323 Signaling object Technical Notes Pane Field Descriptions H225 T301 (10 ms) Timer T301 defines how long the calling element shall wait for the called element to respond. This timer starts when Alerting is received and normally terminates on Connect or when the caller terminates the call attempt and sends Release Complete. The valid range of values is 18000-65000 (10 ms). H225 T303 (10 ms) 861 IMG WebHelp Timer T303 defines how long the calling element shall wait for an Alerting, Call Proceeding, Connect, Release Complete or other message from the called element after it has sent a Setup message. The valid range of values is 400-30000 (10 ms). H225 T310 (10 ms) Timer T310 defines how long the calling element shall wait for an Alerting, Connect, Release Complete or other message from the called element after it has received a Call Proceeding message. The valid range of values is 1000-60000 (10 ms). H245 T101 (10 ms) Timer T101 is used in the Capability Exchange procedure. It specifies the maximum time during which no TerminalCapabilitySetAck or TerminalCapabilitySetReject message may be received. The valid range of values is 300-30000 (10 ms). H245 T103 (10 ms) Timer T103 is used in Unidirectional and Bidirectional Logical Channel Signaling procedure. It specifies the maximum time during which no OpenLogicalChannelAck or OpenLogicalChannelReject or CloseLogicalChannelAck message may be received. The valid range of values is 300-30000 (10 ms). H245 T105 (10 ms) Timer T105 is used for Round-Trip Delay procedure. It specifies the maximum time during which no RoundTripDelayResponse message may be received. The valid range of values is 300-5000 (10 ms). H245 T106 (10 ms) Timer T106 is used in the Master-Slave Determination procedure. It specifies the maximum time during which no acknowledgement message may be received. The valid range of values is 300-30000 (10 ms). H245 T108 (10 ms) Timer T108 is used in the Close Logical Channel procedure. It specifies the maximum time during which no RequestChannelCloseAck or RequestChannelCloseReject message may be received. The valid range of values is 300-30000 (10 ms). H245 T109 (10 ms) Timer is used in Mode Request procedure. It specifies the maximum time during which no RequestModeAck or RequestModeReject message may be received. The valid range of values is 300-30000 (ms). Cantata Technology - IMG 1010 Printable WebHelp 862 ClientView Pane Reference Incoming Translation Tables Pane Topic Location: ClientView Pane Reference Overview Description From here you create an incoming translation table by right clicking on Incoming Translation Table and selecting New Translation Table. Related Topics Digit Translation Incoming Translation Process Configuring Digit Matching and Translation Accessing this Pane Cantata IMG EMS -> New Routing Configuration -> New Incoming Translation Tables Cantata Technology - IMG 1010 Printable WebHelp 863 IMG WebHelp Inpulsing Parameters Topic Location: ClientView Pane Reference Overview Description Use this pane to configure inpulse data collection parameters on specified channels. Use inpulse parameters when data is collected by means of an Inseize Instruction. Call setup inpulsing parameters define the address signaling type, number of digit strings, and collection method used during call setup. The IMG supports four different inpulsing stages, and each stage is defined as either one or two digit strings. When instructing the IMG to collect address signaling information that is typically presented with inband dual frequency tones, you must specify a preprogrammed inpulsing stage that describes how to perform the digit collection. Each channel has four inpulsing stages that can be preprogrammed. The inpulsing stage configuration options include: the address signaling type (DTMF, MFR1, MFR2) the string collection method (fixed number digits, KP/ST framed, compelled) the number of strings (1 or 2) Previous Configuration Required Signaling Variant The Address Signaling Type selected in the Signaling Variant pane will be automatically configured for the Inpulsing Parameters pane. Related Topics Configuring CAS Accessing this Pane Cantata IMG EMS -> Signaling Variants -> <Variant Name> -> Inpulsing Parameters Maximum Objects: 4 Pane 864 ClientView Pane Reference Field Descriptions Stage Number 1-4 # of Digit String 1 2 Address Signaling Type This field is automatically populated from the Address Signaling Type set in the Signaling Variant pane. The address signaling type must be the same for both strings within a stage, but may differ between stages. DTMF MFR2 MFR1 Time Out (in ms) The maximum amount of time from the detection of the first digit until all digits have been collected for the stage. The first digit must be detected or the receive first digit timer must expire before this timer is active. Collection Method 1 See Collection Methods. Data See Collection Data. Collection Method 2 See Collection Methods. 865 IMG WebHelp Data See Collection Data. Collection Methods Options for DTMF Fixed Number of Digits Fixed or Indefinite Number of Digits Use Termination Digit If the first digit detected is zero, the Indefinite Number of Digits method is used and the Completion Timer or Interdigit Timer is used (whichever expires first) to terminate digit collection. If the first digit collected is not zero, the Fixed Number of Digits method is used. This method is used to help facilitate collecting digit strings on channels that process national and international calls. Options for MFR1 Fixed Number of Digits Use KP/ST Signals Use Termination Digit Fixed or Indefinite Number of Digits Options for MFR2 Fixed Number of Digits Compelled Use Termination Digit Collection Data Data for Fixed Number of Digits Digit Count (1-24, FF) (default = 10) Set this value to 0xFF if you want the IMG to continue requesting Forward R2 signals until no more are received. Data for Use Termination Digit Digit Value (0-9, #, *) (default = "#") Data for Compelled 866 ClientView Pane Reference Digit Count (1-24) Set this value to 0xFF if you want the IMG to continue requesting Forward R2 signals until no more are received. Forward R2 There is no data for the following Collection Types: Use KP/ST Signals Fixed or Indefinite Number of Digits Cantata Technology - IMG 1010 Printable WebHelp 867 IMG WebHelp Inseize Instruction Topic Location: ClientView Pane Reference Overview Description Use this pane to form a list of configuration instruction for inseize control. You create a separate Inseize Instruction entry for each instruction that you add to the list. You assign Instruction Lists to channels in the Channel Group pane. The IMG executes the list upon detecting an inseizure on the channel. Important Note: that the order in which the instructions appear in the ClientView tree is the order in which they will be sent. Previous Configuration Required Signaling Variant Related Topics Configuring CAS Accessing this Pane Cantata IMG EMS -> Signaling -> <Variant Name> -> Inseize Instruction Maximum Objects: 19 Pane Field Descriptions Instruction Type Report Call Processing Event Receive Stage N Address 868 Generate Call Processing Event Report Incoming Call with Address Data Generate Inseize Acknowledgment Send Host Acknowledgment Delay n Milliseconds ClientView Pane Reference Inseize Data Varies depending on Instruction Type Report Call Processing Event Off-hook Dial Tone Digits Wink 1-8 Dialtone Generate Call Processing Event Backward Pulsed R2 Signal Backward Pulsed R2 Signal with Completion Event Backward Compelled R2 Signal Backward Compelled or Pulsed R2 Signal Receive Stage N Address Stage 1 Stage 3 Stage 2 Stage 4 Backward Signal ID (E1 Only) Applies to Generate Call Processing Event only 1-15 Stages to Report 1-4 Applies to Report Call Processing Event of Digits. Delay Time (ms) Applies to Instruction Type of Delay n Milliseconds. Use the slider or enter a value in the Value: box. 869 IMG WebHelp Cantata Technology - IMG 1010 Printable WebHelp 870 ClientView Pane Reference IP Bearer Profile Pane Topic Location: ClientView Pane Reference Overview Description Use this pane to define a set of VOIP parameter values such as Silence Suppression, Echo Cancellation and RTP Redundancy. You assign the profile to a SIP or H.323 Channel Group to define inbound or outbound behavior. To commit the profile, go back to the IP Bearer Traffic Profiles pane and click the Save Profiles button, or simply select another object in the Configuration Tree. After you create the profile, you use the Supported Vocoders pane to assign a list of supported codecs to the profile. NOTE: The IMG has an adaptive Jitter Buffer which adjusts its size dynamically. The minimum is 75ms and the maximum is 150ms. The Jitter Buffer is not configurable. Related Topics Configuring IP Bearer Profiles Next Configuration Vocoder Entry Channel Group Accessing this Pane Cantata IMG EMS -> IP Bearer Profiles-> IP Bearer Profile Maximum Objects: 16 per EMS Technical Notes Pane 871 IMG WebHelp Field Descriptions IP Bearer Profile Id This value identifies the Id being defined. This value is subsequently used in the Channel Group object to specify the IP Bearer Profile instance. IP Bearer Profile Name This value provides a name to the profile being defined. This value is subsequently used in the Channel Group object to specify the IP Bearer Profile instance. Silence Suppression This field does not apply for the AMR or EVRC codecs as they use their own internal Silence Suppression scheme. Enable Disable See Silence Suppression for more information. Echo Cancellation In compliance with ITU G.168-2000, this feature eliminates echo introduced by impedance mismatched hybrids on TDM channels. The maximum tail length is 128 milliseconds for VoIP Module SLM-IPM-0001 and 64 milliseconds for the VoIP Module SLM-IPM-0001. You may want to implement Echo Cancellation for tandem calls on trunks with echo or to clean an incoming signal before connecting to a media resource, such as a Voice Response Unit or Answering Machine Detection. 872 Enable Disable ClientView Pane Reference RTP Redundancy This feature provides RTP packet redundancy to guard against network packet loss (RFC 2198) for RTP traffic in voice or fax/modem bypass calls. This is not supported for iLBC, AMR, and EVRC. EVRC and AMR have internal schemes that are not configurable. Note that Open Phone does not support RTP Redundancy. No Redundancy Redundancy Level 1 RTP Payload Type for Redundancy This numeric value (96-101, 104, 106-127) defines the packet type used for RTP Redundancy. For an incoming call, if the sending gateway is using a codec that is configured on the IMG but with a different dynamic payload type, the IMG will accommodate that by sending the dynamic payload type sent by the sending gateway in the Invite message. For example, if the IMG has iLBC profile configured with a value of 100, an incoming call to the IMG has iLBC set to 98, the IMG will send the 98 back in the 200 OK to accept iLBC. Fax Mode This field defines the mode of operation for Fax Calls. Disable The fax is sent as a voice call. Depending upon the codec used, faxes may not be possible. Enable Relay (T.38) The fax is delivered using T.38 packets. Enable Bypass The codec configured in the Fax Bypass Codec field below is used to send the fax. This functionality is not supported for the AMR and EVRC codecs. Relay Fallback to Bypass: 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. 873 IMG WebHelp In the event neither a T.38 fax nor a Bypass fax can be established in a fax fallback scenario, the IMG allows the voice call to proceed as if no negotiation had happened. Fax Bypass Codec The codec to use when the Fax Mode is set to Enable Bypass. This field does not apply for the AMR or EVRC codecs. G711 ulaw: 64 kbps North American G711 alaw: 64 kbps ITU Fax Packet Redundancy This feature provides Fax packet redundancy to guard against network packet loss. This is only applicable to Relay Fax Mode. This field does not apply for the AMR or EVRC codecs. No Redundancy Redundancy Level 1 Original payload is duplicated one time. Redundancy Level 2 Original payload is duplicated two times. Redundancy Level 3 Original payload is duplicated three times. Digit Relay This setting specifies the method to use to propagate DTMF digits. This field does not apply for the AMR or EVRC codecs. DTMF In-band Digits are sent in the same packets as the voice. DTMF Packetized Digits are sent in separate packet type (RTP Events as defined by RFC 2833) using payload type specified by the Digit Relay Packet Type. DTMF via H.245 UII (out-of-band, IP suppressed) Digits are propagated using H.245 signaling. This option is not applicable for SIP signaling. NOTE: If the far end does not support what is configured for Digit Relay the IMG will send DTMF In-band. If this occurs, the call trace will indicate the following: 20:41:07.240 CALL(225) (00:0001:01) Falling Back to In-Band Digit Tx 874 ClientView Pane Reference DTMF Digit Mapping The following is the mapping of received digits. Event Decimal 0-9 0-9 * 10 # 11 A-D 12-15 Flash 16 Digit Relay Packet Type This numeric value (96-101, 104, 106-127) defines the packet type used for Digit Relay. DTMF digit relay packet type is configurable to any value type in the range (96 - 127). Most endpoints default to 101. However, since this setting is not negotiated during call setup, it is important that the IMG is configured to match the remote endpoint setting. Modem Behavior Bypass Switches to another codec when you are in a modem call. The codec that you switch to is specified in the Fax Bypass Codec field. For example, if you are using a low bit rate codec, such as G.729, a modem or fax call will probably not be successful. So in this case the IMG changes the codec to what is configured in the Fax Bypass Codec field. This functionality is not supported for the AMR and EVRC codecs. H.245 Outbound Tunneling This field enables/disables the H.245 tunneling feature for outbound calls. To enable outbound tunneling, you must also enable tunneling globally from the H.323 Signaling object. By enabling tunneling globally you enable tunneling for inbound calls. This field is ignored when SIP signaling is used. Initial Inactivity Timer (10ms) Not currently supported. Media Inactivity Timer (10ms) Not currently supported. Comedia Mode 875 IMG WebHelp See Symmetric NAT Traversal for more information Disable Active This applies to SIP only. It used when the IMG is behind a NAT and you want the IMG to send or accept SIP INVITEs. The IMG will convey that it is behind a NAT to the distant endpoint in the SDP. The IMG advertises to other gateways to change their RTP port and IP address to map with the NAT by sending the direction attribute a=direction<active> in the SIP SDP. Passive Used when the IMG is on a public network and you want the IMG to allow calls to a distant endpoint that is behind a NAT. The IMG uses the Source IP and Ports of the incoming RTP, RTCP, and T38 packets as the Destination IP and Port of the outgoing RTP, RTCP, and T38 packets. Display Table This table lists the Supported Vocoders to be used by SIP or H.323 for codec negotiation during call. The entries are listed in descending priority. Cantata Technology - IMG 1010 Printable WebHelp 876 ClientView Pane Reference IP Bearer Traffic Profiles Pane Topic Location: ClientView Pane Reference Overview Description To create an IP bearer traffic profile, right-click IP Bearer Traffic Profiles and select New IP Bearer Profiles. Related Topics Configuring IP Bearer Profiles Accessing this Pane Cantata IMG EMS -> IP Bearer Traffic Profiles -> New IP Bearer Profiles. Buttons Save Profiles Use this button to commit IP Bearer Profiles. Cantata Technology - IMG 1010 Printable WebHelp 877 IMG WebHelp IP Network Element Pane Topic Location: ClientView Pane Reference Overview Description Use this pane to configure endpoints from which or to which IP calls can be routed. An IP Network element can be: Any of the configured IMG’s Any of the configured External Gatekeepers Any of the configured External Gateways Related Topics Assigning a Channel Group to an H323 Endpoint Pre-requisite Configuration Channel Group Accessing this Pane Cantata IMG EMS -> Routing Configuration -> Channel Groups-> Channel Group -> IP Network Element Maximum Objects: 1 per Channel Group Technical Notes Pane Field Descriptions IP Network Element This field is a drop-down list of the configured IMG’s, external gateways, and external gatekeepers. Cantata Technology - IMG 1010 Printable WebHelp 878 ClientView Pane Reference IP Traffic Management Entry Topic Location: ClientView Pane Reference Overview Description IP Traffic Management, also called Call Admission Control, allows you to configure the number of simultaneous calls that can be active between a network element (any configured IMG, external gateway, or external gatekeeper) and an IMG. IP traffic limits are applied to the combined total of incoming and outgoing calls. Example Call Trace The following is an example of what would appear in the call trace for every call to or from a gateway under IP restrictions. CALL> 16:16:48.480 CALL(L4) Resource Group ID: 2 (00:7040:01) IP Traffic Management: 583 Busy Count: 55 Channels Allowed: 300 Accessing this Pane Cantata IMG EMS -> Routing Configuration -> IP Traffic Management Entry Maximum Objects: 1,024 Error Responses SIP If a SIP call is rejected because the maximum number of calls is reached, the IMG will send a 503 response. H.323 If an H.323 call is rejected because the maximum number of calls is reached, the IMG will send a cause code of 34 - No Circuits Available. Pane 879 IMG WebHelp Field Descriptions IMG The IMG upon which the traffic restrictions will be applied. When set to ‘All IMGs’ the restricted Network Element will be allowed the Maximum number of sessions to each IMG node. Network Element The External Gateway upon which the traffic restrictions will be applied. This field is a drop-down list of all the configured External Gateways. Max Number of Simultaneous sessions This is the maximum number of calls that can be active at any one time between the designated network element and the IMG, in either direction. Buttons Save IP Traffic Table Updates the ingress and egress route tables with the configured traffic restrictions. Cantata Technology - IMG 1010 Printable WebHelp 880 ClientView Pane Reference ISDN Circuits Pane Topic Location: ClientView Pane Reference Overview Description Use this pane to assign B-Channels to a D-Channel. Related Topics Assigning B-Channels (Circuits) to be controlled by the D-Channel Accessing this Pane Cantata IMG EMS-> -> Routing Configuration -> Channel Group -> ISDN Group -> ISDN Circuits Maximum Objects: 480 per ISDN Group Pane Field Descriptions IMG Interface Type of Circuits Bearer Signaling Start Interface Offset Beginning span in this Circuit Group. 881 IMG WebHelp Start Channel Beginning channel in this Circuit Group. End Interface Offset Last span in this Circuit Group. End Channel Last channel in this Circuit Group. Start Facility Number The number of the first Facility in the group. Monitoring Fields Trunk Type Informational Field - The trunk type of this Circuit Group. B Channel Count Informational Field - The number of B Channels in this Circuit Group. Channel Count Informational Field – This is the total number of channels, including D- Channels, on the span. Cantata Technology - IMG 1010 Printable WebHelp 882 ClientView Pane Reference ISDN D Channel Pane Topic Location: ClientView Pane Reference Overview Description Use this pane to configure an ISDN D Channel. Related Topics Overview of ISDN Configuration Configuring a D-Channel Accessing this Pane Cantata IMG EMS -> Logical IMG -> Physical IMG -> Signaling -> ISDN -> ISDN D Channels -> New ISDN D Channel Maximum Objects: T1 – 32/ E1 - 24 per Physical IMG Pane Field Descriptions Primary Interface - Offset The span on which the primary D Channel is located. Primary Channel The channel on which the primary D Channel is located. 883 IMG WebHelp NFAS Supported Indicates if NFAS is supported on the D Channel. Yes (default) No Secondary Interface - Offset If NFAS is enabled, the span on which the secondary D Channel is located. Secondary Channel If NFAS is enabled, the channel on which the secondary D Channel is located. Base Variant The base ISDN variant used. The default is National-ISDN 2 Network Side. T1 Network Side Variants National-ISDN 2 ATT 5ESS Q.931 PRI (Custom PPL Required) ATT 4ESS Q.931 PRI (Custom PPL Required) Northern Telecom DMS-100 Q.931 PRI Northern Telecom DMS-250 Q.931 PRI JATE Net5 Q.931 (10.3.3 ER2) T1 User Side Variants National-ISDN 2 ATT 5ESS Q.931 PRI (Custom PPL Required) ATT 4ESS Q.931 PRI (Custom PPL Required) Northern Telecom DMS-100 Q.931 PRI Northern Telecom DMS-250 Q.931 PRI JATE Net5 Q.931 (10.3.3 ER2) E1 Network Side Variants 884 Euro-ISDN JATE ClientView Pane Reference E1 User Side Variants Euro-ISDN JATE B Channel Selection Determines the hunt method for selecting B Channels. Linear Clockwise (default) Circular Clockwise Linear Counter Clockwise Circular Counter Clockwise HDLC Bit Polarity Normal (default) Inverted Network Side Layer 2 Override Options vary depending on variant. Location The value populated in the Location parameter in the Cause IE when a call is released. User (0 - Message Generated by User) (default) Local public network (2 - Message generated by public network serving the local user) Private Network (1 - Message generated by private network serving the local user) Transit network (3 - Message generated by transit network) Remote public network (4 - Message generated by public network serving the remote user) Remote private network (5 - Message generated by private network serving the remote user) International network (7 - Message generated by international network) Network Beyond Interworking Point (0A - Message generated by network beyond inter-working point) Monitoring Fields 885 IMG WebHelp D Channel Status In Service Active Out of Service Standby Not Aligned Secondary D Channel Status In Service Active Out of Service Standby Display Table This table shows all of the D Channels configured. Cantata Technology - IMG 1010 Printable WebHelp 886 ClientView Pane Reference ISDN Group Pane Topic Location: ClientView Pane Reference Overview Description Use this pane to configure an ISDN Group. Related Topics Defining an ISDN Channel Group Accessing this Pane Cantata IMG EMS-> -> Routing Configuration -> Channel Group -> ISDN Group Maximum Objects: T1 - 32/ E1 - 24 per Channel Group Pane Field Descriptions ISDN D channel The D Channel that provides signaling for this group. Network Type Do Not Include Network-Specific Facilities (NSF) IE ATT Megacom 800 Service ATT Software Defined Network ATT Megacom ATT Accunet ATT Long Distance Service ATT International 800 ATT Multiquest 887 IMG WebHelp Northern Telecom Private Net Northern Telecom OutWats Northern Telecom InWats Northern Telecom Foreign Exchange Northern Telecom Tie Trunk Northern Telecom TRO Call Bearer Capabilities Allowed Voice (default) Unrestricted 56K 3.1 KHz audio Unrestricted 64K Restricted 64K 384K Unrestricted digital information with tones and announcements Discard Privacy Info Option selected is removed from the outgoing SETUP message. See Configuring SIP Privacy. Off (default except for ISDN B Channels) Generic Number Only Display Only (default for ISDN B Channels) Display and Generic Number Calling Party Only Display and Calling Number Calling, Display and Generic Cantata Technology - IMG 1010 Printable WebHelp 888 ClientView Pane Reference ISDN Signaling Pane Topic Location: ClientView Pane Reference Overview Description This a container object for configuring ISDN D Channels. After creating this object, right-click on ISDN D Channels and select New ISDN D Channel. Related Topics An Introduction to ISDN Overview of ISDN Configuration Configuring ISDN Signaling Accessing this Pane Cantata IMG EMS -> Logical IMG -> Physical IMG -> Signaling -> ISDN Maximum Objects: 1 per Physical IMG Cantata Technology - IMG 1010 Printable WebHelp 889 IMG WebHelp ISDN Timers Topic Location: ClientView Pane Reference Overview Description Use this pane to change default ISDN Timers, if required. Related Topics Configuring ISDN Timers Accessing this Pane Cantata IMG EMS -> Logical IMG -> Physical IMG -> Signaling -> ISDN D Channels > ISDN D Channel -> ISDN Timers Maximum Objects: 1 per ISDN Signaling object Pane Field Descriptions Q931 T303 (10 ms) The value for ISDN Timer T303, in 10 ms increments. Q931 T305 (10 ms) The value for ISDN Timer T305, in 10 ms increments. Q931 T308 (10 ms) The value for ISDN Timer T308, in 10 ms increments. Q931 T310 (10 ms) The value for ISDN Timer T310, in 10 ms increments. Cantata Technology - IMG 1010 Printable WebHelp 890 ClientView Pane Reference ISUP Group Topic Location: ClientView Pane Reference Overview Description This pane defines the configuration for a group of ISUP channels. The contents of the pane will vary depending on whether the associated SS7 Stack is ANSI or ITU. Related Topics Configuring an ISUP Group Accessing this Pane Cantata IMG EMS -> Routing Configuration -> Channel Groups-> Channel Group (SS7) -> ISUP Group Maximum Objects: 512 per SS7 Channel Group Panes ISUP Group Pane - ITU, CCITT and ETSI Versions Also see ANSI Version. 891 IMG WebHelp Field Descriptions OPC - DPC This field has a drop-down list populated with OPC-DPC combinations from previously configured SS7 Stack (OPC) and SS7 Route (DPC) configuration. Glare Rule This field indicates how simultaneous incoming and outgoing seizures of the same SS7 channel are resolved. Drop Outgoing Call The incoming seizure is denied. Drop Incoming Call The outgoing seizure is denied Odd/Even The incoming seizure is denied if either the OPC value is less than the DPC value and the CIC number is odd, or the OPC value is greater than the DPC value and the CIC number is even (ITU-T Recommendation Q.767). Incoming Continuity Check Configures the behavior in case of receiving an IAM with 'Continuity Check required on this circuit'. 892 ClientView Pane Reference Wait for COT (default) Wait for the COT before sending the INVITE or Setup (in case of outgoing IP channel groups) Do not wait for COT Propagate the IAM with 'Continuity check required on previous circuit' (in case of outgoing SS7 channel groups) Out Continuity Check This field indicates how frequently outgoing calls on this SS7 channel undergo an automatic continuity check None: 1:xx: One out of every X calls undergoes a Continuity Check. Satellite Circuit This field indicates if this SS7 channel makes use of a satellite facility. No Yes CIC Service Rule This list indicates what SS7 message, if any, the responsible SS7 stack sends when IMG takes this SS7 channel is out-of-service. Block The SS7 stack sends an SS7 Blocking (BLO) message. Note—This stack will send an SS7 Unblocking (UBL) message when the IMG puts this SS7 channel back in service No Bloc The SS7 stack does not send SS7 message. Note—This stack will send an SS7 Reset Circuit (RSC) message when the IMG puts this SS7 channel back in service No Action The SS7 stack does not send an SS7 message Hop Counter This list indicates the number of switches that can have processed a call before the responsible switch rejects the call. Off 01-31 893 IMG WebHelp State transitions Group Operations Individual Operations(R/B/U) Individual Operations(B/U) Echo Suppression Echo Suppressor Not Present Echo Suppressor Present Max # of CdPN Digits (IAM) For outgoing SS7 calls, when the number of digits reaches this value the IMG sends an IAM and the remaining digits are sent in a SAM. Range = 0-16 Alert/Answer Determines if the alerting/answering of the call will be setup using ACM/ANM combination or using CON. ANM/ACM or CON (default) Parameter Compatibility Checking Determines if the IMG will check for incompatible parameters in an ISUP message. Off On Parameter Compatibility Pass On Determines the behavior of IMG when receiving an incompatible parameter in an ISUP message, whether to pass it to the far end or not. Off (Do Not Pass) On (Pass) Overload Handling This configures how the IMG responds upon getting busy (low idle time). The IMG can indicate to the far end that it is overloaded either by releasing (REL) the call or by sending an OLM (Overload Message). 894 Send REL Send OLM ClientView Pane Reference UPT upon UPU This configures how the IMG responds upon receiving a UPU (User Part Unavailable) from the far end of the CIC. If enabled, the IMG will send a UPT (User Part Test) message continuously until any ISUP message is received from the far end of the CIC. Yes (enable) No (disable) Transmission Medium Determines the value of the transmission medium parameter in any IAM message referring to that CIC. Speech 3.1 KHz Audio 64 Kbit Unrestricted Propagation Delay If enabled, when the IMG receives an IAM message with no Propagation delay specified, the propagated IAM message to the far end will contain the ‘Propagation Delay counter’ parameter with the value set in the Propagation Delay Time field (below). If the IAM message coming to the IMG already contains a propagation delay value, the propagated IAM message to the far end will contain the ‘Propagation Delay counter’ parameter with the value set to the sum of the incoming Propagation Delay Time field (below). Off (disable) On (enable) Propagation Delay Time (MS) See Propagation Delay field above. History Passage Off On Discard Privacy INFO The selected option will be removed from the ISUP message. See Configuring SIP Privacy. Off (default) Display Only 895 IMG WebHelp Generic Number Only Calling Party Only Display & Generic Number Display and Calling Number Calling, Display and Generic TMR Allowed On Off (default) TMR Screening Cause Value Speech 3.1 KHz audio 64 Kbits/s unrestricted 64 kbits/s preferred 2x64 Kbits/s unrestricted 384 Kbits/s unrestricted LNP Routing Enable Use this field to enable or disable Local Number Portability routing. See Local Number Portability (LNP). ISUP Group Pane - ANSI Version 896 ClientView Pane Reference Field Descriptions OPC - DPC This field has a drop-down list populated with OPC-DPC combinations from previously configured SS7 Stack (OPC) and SS7 Route (DPC) configuration. Local CLLI This field indicates the local CLLI (Common Language Location Identification) code for the group of SS7 channels to which this channel belongs. Remote CLLI This field indicates the remote CLLI (Common Language Location Identification) code for the group of SS7 channels to which this channel belongs. Glare Rule This field indicates how simultaneous incoming and outgoing seizures of the same SS7 channel are resolved. Drop Outgoing Call The incoming seizure is denied. Drop Incoming Call The outgoing seizure is denied Odd/Even 897 IMG WebHelp The incoming seizure is denied if either the OPC value is less than the DPC value and the CIC number is odd, or the OPC value is greater than the DPC value and the CIC number is even (ITU-T Recommendation Q.767). Incoming Continuity Check Configures the behavior in case of receiving an IAM with 'Continuity Check required on this circuit'. Wait for COT (default) Wait for the COT before sending the INVITE or Setup (in case of outgoing IP channel groups) Do not wait for COT Propagate the IAM with 'Continuity check required on previous circuit' (in case of outgoing SS7 channel groups) Out Continuity Check This field indicates how frequently outgoing calls on this SS7 channel undergo an automatic continuity check None: 1:02: One of every 2 calls undergoes a Continuity Check. 1:xx: One out of every X calls undergoes a Continuity Check. 1:03: One of every 3 calls undergoes a Continuity Check. 1:04: One of every 4 calls undergoes a Continuity Check. 1:05: One of every 5 calls undergoes a Continuity Check. 1:06: One of every 6 calls undergoes a Continuity Check. 1:07: One of every 7 calls undergoes a Continuity Check. 1:08: One of every 8 calls undergoes a Continuity Check. 1:09: One of every 9 calls undergoes a Continuity Check. 1:10: One of every 10 calls undergoes a Continuity Check. 1:11: One of every 11 calls undergoes a Continuity Check. 1:12: One of every 12 calls undergoes a Continuity Check. 1:13: One of every 13 calls undergoes a Continuity Check. 1:14: One of every 14 calls undergoes a Continuity Check. 1:15: One of every 15 calls undergoes a Continuity Check. 1:16: One of every 16 calls undergoes a Continuity Check. Satellite Circuit This field indicates if this SS7 channel makes use of a satellite facility. 898 No ClientView Pane Reference Yes CIC Service Rule This list indicates what SS7 message, if any, the responsible SS7 stack sends when IMG takes this SS7 channel is out-of-service. Block The SS7 stack sends an SS7 Blocking (BLO) message. Note—This stack will send an SS7 Unblocking (UBL) message when the IMG puts this SS7 channel back in service No Bloc The SS7 stack does not send SS7 message. Note—This stack will send an SS7 Reset Circuit (RSC) message when the IMG puts this SS7 channel back in service No Action The SS7 stack does not send an SS7 message Hop Counter This list indicates the number of switches that can have processed a call before the responsible switch rejects the call. Off 01-31 State transitions Group Operations Individual Operations(R/B/U) Individual Operations(B/U) Echo Suppression Echo Suppressor Not Present Echo Suppressor Present Max # of CdPN Digits (IAM) For outgoing SS7 calls, when the number of digits reaches this value the IMG sends an IAM and the remaining digits are sent in a SAM. Range = 0-16 Originating Line Info 899 IMG WebHelp Don't Pass OLI Circuit Group Carrier Indicator This field indicates the nature of signaling on this SS7 channel’s physical medium. Your input, permitted only if this SS7 channel is associated with an SS7 stack whose ISUP is ANSI-compliant. Unknown Digital Analog Analog and Digital Alarm Carrier Indicator Unknown HW Cxr SW Cxr CVT Upon UPU This field indicates if the controlling SS7 stack will automatically send an SS7 Circuit Validation Test (CVT) message when it receives a User Part Unavailable (UPU) indication for a call’s destination (DPC). No Yes GRS/GRA Behaviour Pre ANSI 1995 (default if SS7 Stack is configured for ANSI 93) Post ANSI 1995 (default if SS7 Stack is configured for ANSI 95 or 97) Sending GRS/GRA The post 1995 GRA message, which would be sent in response to an incoming post 1995 GRS, will have the optional circuit assignment map parameter included if it was included in the incoming GRS. The pre 1995 GRA message, which would be sent in response to an incoming pre 1995 GRS, will not have a pointer to optional circuit assignment map parameter. Receiving GRS/GRA The received GRS/GRA messages are validated against the pre 1995 or post 1995 format depending upon the configuration for the base CIC. A confusion (CFN) message will be sent if the incoming message does not have the expected format. Originating Line INFO Checking 900 ClientView Pane Reference Disable (default) The IMG will not validate that there is a Charge Number parameter included in the IAM with the Originating Line Info parameter Enable The IMG will validate that there is a Charge Number parameter included in the IAM with the Originating Line Info parameter as per ANSI standards. Discard Privacy INFO Discard Privacy info omits CLI in the ISUP message (default = NO) Off Generic Number Only Display Only Display & Generic Number Calling Party Only Display and Calling Number Calling, Display and Generic TMR Values Allowed Speech 3.1 KHz audio 64kbit/s unrestricted Alternate Speech Alternate 64kbit/s unrestricted 64kbit/s preferred 2x64kbit/s unrestricted 384kbit/s unrestricted USI Transfer Capability Allowed Speech Restricted Digital Info Unrestricted Digital Info 3.1 KHz Audio Unrestricted Digital with tones/announcements USI Transfer Rate Allowed 64 Kbits/s 901 IMG WebHelp 384 Kbits/s USI Screening Cause Value 65 (Bearer Not Implemented) 38 (Incompatible Destination) LNP Routing Enable Use this field to enable or disable Local Number Portability routing. See Local Number Portability (LNP). Cantata Technology - IMG 1010 Printable WebHelp 902 ClientView Pane Reference License Information Topic Location: ClientView Pane Reference Overview Description This ClientView pane displays your current IMG license information. If you have acquired a new license for additional functionality, click the Download Node License button to download the license to the IMG 1010 from the IMG server. Related Topics Downloading a New License Accessing this Pane Cantata IMG EMS -> Logical IMG -> Physical IMG -> New Licensing Info Maximum Objects: 1 per Physical IMG Technical Notes Pane Timed License Evaluation License Evaluation licenses expire after a specified number of days. If you are using an Evaluation License, the License Expiration Info field indicates the date/time that the license will expire, as shown below. If you are not using an Evaluation License, the field will say "Does not expire". When there is 72 hours remaining on the license and again when it expires you will get an EventView alarm and, if the IMG is processing calls, a warning pop-up in ClientView 903 IMG WebHelp Buttons Download License File Cantata Technology - IMG 1010 Printable WebHelp 904 ClientView Pane Reference Location Override Topic Location: ClientView Pane Reference Overview Description The location override can be used to override the location value sent by the IMG in the Cause Indication parameter in the Release (REL) message within an SS7 call. Related Topics Configuring Location Override Accessing this Pane Cantata IMG EMS -> Routing Configuration -> Channel Groups -> Channel Group (SS7) -> ISUP Group -> Location Override Maximum Objects: 1 per Physical IMG Technical Notes Pane Field Descriptions Location Override Ignore (default) Override Location If Override is enabled, the following options appear. User (Message Generated by User) (default) 905 IMG WebHelp Private Network (Message generated by private network serving the local user) Local public network (Message generated by public network serving the local user) Transit network (Message generated by transit network) Remote public network (Message generated by public network serving the remote user) Remote private network (Message generated by private network serving the remote user) International network (Message generated by international network) Network Beyond Interworking Point (Message generated by network beyond inter-working point) Coding Standard CCITT (default) National International Standard defined for the network interface Cantata Technology - IMG 1010 Printable WebHelp 906 ClientView Pane Reference Logical IMG Topic Location: ClientView Pane Reference Overview Description This object identifies a Point Of Presence (POP) that can include up to 16 Physical IMG’s. SS7 Once an SS7 stack is configured on an IMG that is the only IMG in the logical group that an SS7 stack can be configured on. See Configuring Multiple IMGs for SS7. Related Topics Creating a Logical IMG Accessing this Pane Cantata IMG EMS-> Logical IMG Maximum Objects: 16 Technical Notes Pane Field Descriptions Logical IMG ID 907 IMG WebHelp Automatically assigned number to identify this IMG. IMG Name A unique name you enter to identify the IMG. IP Address The IP Address of this IMG. IMG Type Automatically populated field. Informational Fields Subnet Serial Number Software Version TDM Group 0 Type TDM Group 1 Type VoIP Module 0 Status VoIP Module 1 Status Connection State Cantata Technology - IMG 1010 Printable WebHelp 908 ClientView Pane Reference Media Topic Location: ClientView Pane Reference Overview Description This pane identifies the NFS servers in your system for downloading files to the DSPs on the IMG. Related Topics Configuring Media Accessing this Pane Cantata IMG EMS -> Logical IMG -> IMG Name -> New Media Maximum Objects: 1 per Physical IMG Technical Notes Pane Field Descriptions Media Name (Used in NFS) A label used to identify the NFS server. User ID User ID for UNIX permissions. Group ID Group ID for UNIX permissions. Network Interface The IP address assigned to the NFS server. Primary Vocabulary Index File Name 909 IMG WebHelp This field is automatically populated with the default file name. Primary Server ID Indicates the ID of the NFS server to be the primary. Secondary Vocabulary Index File Name This field indicates the secondary Vocabulary Index File Note: filename must start with “/” or “\\”. Secondary Server ID Indicates the ID of the NFS server to be the secondary. Monitoring Fields Primary NFS Server Status Not Configured Failed Available Primary NFS Server Status Not Configured Failed 910 Available Cantata Technology - IMG 1010 Printable WebHelp ClientView Pane Reference Media DSP Topic Location: ClientView Pane Reference Overview Description This pane configures functions on a DSP. NOTE ON CAS: For DTMF reception configure an a-law or u-law Universal Receiver. For MFR1 or MFR2 reception you must configure the specific MFR1 or MFR2 receiver accordingly. If you try to perform MFR1 or MFR2 using a Universal Receiver, you will get a Call Trace indication of "No DSP of this type configured". Related Topics Configuring Media Accessing this Pane Cantata IMG EMS -> Logical IMG -> IMG Name -> New Media -> New Media Module -> New Media DSP Maximum Objects: 2 per Physical IMG Pane Field Descriptions DSP Id Indicates the DSP. Receive 0 Configuration Indicates the function configured for the Receive 0 DSP. ulaw DTMF Rcv ulaw MFR1 Rcv alaw DTMF Rcv alaw MFR1 Rcv ulaw MFR2 Rcv 911 IMG WebHelp alaw MFR2 Rcv alaw CPA Rcv ulaw CPA Rcv Playback/Record Transmit 0 Configuration Indicates the function configured for the Transmit 0 DSP. ulaw Universal Generator: A description of the choice alaw Universal Generator Receive 1 Configuration Indicates the function configured for the Receive 1 DSP. ulaw DTMF Rcv ulaw MFR1 Rcv alaw DTMF Rcv alaw MFR1 Rcv ulaw MFR2 Rcv alaw MFR2 Rcv ulaw CPA Rcv alaw CPA Rcv Playback/Record Transmit 1 Configuration Indicates the function configured for the Transmit 1 DSP. ulaw Universal Generator alaw Universal Generator Receive 2 Configuration Indicates the function configured for the Receive 2 DSP. ulaw DTMF Rcv ulaw MFR1 Rcv 912 alaw DTMF Rcv alaw MFR1 Rcv ulaw MFR2 Rcv alaw MFR2 Rcv ulaw CPA Rcv ClientView Pane Reference alaw CPA Rcv Playback/Record Transmit 2 Configuration Indicates the function configured for the Transmit 2 DSP. ulaw Universal Generator alaw Universal Generator Cantata Technology - IMG 1010 Printable WebHelp 913 IMG WebHelp Media Module Topic Location: ClientView Pane Reference Overview Description This pane configures a DSP module on the IMG. Related Topics Configuring Media Accessing this Pane Cantata IMG EMS -> Logical IMG -> IMG Name -> New Media -> New Media Module Maximum Objects: 1 per Physical IMG Pane Field Descriptions Module Interface Id 0 On-Board Module Name Cantata Technology - IMG 1010 Printable WebHelp 914 ClientView Pane Reference Network Interface Topic Location: ClientView Pane Reference Overview Description Use this pane to configure control, data, and signaling interfaces. They can be on the same or separate subnets. Related Topics Configuring Network Interfaces Accessing this Pane Cantata IMG EMS ->Logical IMG -> Physical IMG -> Network Interfaces -> Network Interface Maximum Objects: 6 per Physical IMG Pane Field Descriptions Physical Interface CPU VoIP Module 1 VoIP Module 0 Logical Interface 915 IMG WebHelp Redundant Control: (Not available for VoIP Modules.) Redundant Signaling Redundant Data Address Type IP V4 IP Address Notes: The IP address for each network interface must be unique. You cannot reuse an IP address for another network interface including the IMG’s own IP address. The two VoIP modules are allowed only on data ports so be sure their IP addresses are on the same subnet. For the VoIP modules, since they are only allowed on the Data ports, the IP addresses for both should be on the same subnet. If the CPU profile is configured to go through the Control port, the IP address of that profile should be on the same subnet as the IMG's IP address (CTRL 0/1 IP addresses). If the CPU is configured to go through the Data ports, the IP address of that profile should be on a different subnet from the IMG's CTRL 0/1 subnet. This IP can be on the same subnet as the VoIP modules or a different one. You should not delete the VoIP module 0/1 if that profile is used to configure the VoIP modules 0/1 under Facility. Also, if a CPU network interface is configured and used for NFS traffic, do not delete it. IP Address/Subnet If the CPU profile’s IP address is on the same subnet as an existing profile, it must use the same logical interface. The IP address assigned using BootP is automatically bound to the Redundant Control interface. If the CPU profile’s IP address in on its own subnet, any of the logical interfaces can be used. Default Gateway Gratuitous ARP and ARP Responses This field is used for the SIP-Based Load Balancing feature when you are creating a SIP Virtual Address. When you create a Virtual SIP Address, you set this field to disable. When the Gratuitous ARP and ARP Responses is set to Disable, this Virtual IP Address will 916 ClientView Pane Reference not be allowed to issue a Gratuitous ARP. In addition, whenever an external node attempts to send an ARP to this Virtual IP Address, the ARP Reply will be suppressed. Any node that knows the MAC address associated with this Virtual IP Address (through static configuration as used in Load Balancers) will be able to send packets to it. The Virtual IP Address will be able to send packets to any desired node since ARP Requests from the Virtual IP Address for an unknown IP’s MAC address will be allowed. For all outbound SIP requests, the real SIP Signaling IP Address is used to send SIP messages, even if the outbound transaction is within a dialog which had previously used the Virtual IP Address. Any Network Interface that is configured with Gratuitous ARP and ARP Responses Disabled will appear in the SIP Virtual IP Address field drop-down in the SIP Virtual Address pane. Cantata Technology - IMG 1010 Printable WebHelp 917 IMG WebHelp Network Interfaces Topic Location: ClientView Pane Reference Overview Description To create a network interface, right-click Network Interfaces and select New Network Interfaces. Related Topics Configuring Network Interfaces Accessing this Pane Cantata IMG EMS -> Logical IMG -> Physical IMG -> Network Interfaces Cantata Technology - IMG 1010 Printable WebHelp 918 ClientView Pane Reference NFS Server Topic Location: ClientView Pane Reference Overview Description This pane configures an NFS Server from which the IMGs will retrieve media files. Related Topics Configuring an NFS Server Accessing this Pane Cantata IMG EMS -> External Network Elements -> NFS Servers -> NFS Server Maximum Objects: 8 per EMS Pane Field Descriptions NFS Server Id This is a logical number (1-8) that identifies each NFS server configured. It is automatically populated with the next available number, but can be changed. NFS Server Enabled This field indicates if the server is enabled or disabled Disabled Enabled NFS Server Name A label used to identify the NFS server. NFS Server IP Address IP Address of the NFS server. NFS Mount Directory 919 IMG WebHelp This is the location of the directory that is to be mounted. The directory must start with “/” or “\\”. Display Table This pane displays all of the NFS Servers configured. Cantata Technology - IMG 1010 Printable WebHelp 920 ClientView Pane Reference NFS Servers Topic Location: ClientView Pane Reference Overview Description This is a container pane from which you configure individual NFS Servers. Related Topics Configuring an NFS Server Accessing this Pane Cantata IMG EMS -> External Network Elements -> NFS Servers Maximum Objects: 1 Cantata Technology - IMG 1010 Printable WebHelp 921 IMG WebHelp SIP Options KeepAlive Topic Location: ClientView Pane Reference Overview Description Use this pane to configure parameters for the SIP Busy Out feature. The IMG can monitor the status of external SIP gateways by sending periodic SIP OPTIONS messages. If the gateway does not respond in a configured amount of time the IMG will mark the gateway as down and attempt to re-route the call to a different gateway. You enable the SIP Busy Out feature on a specific gateway in the External Gateway pane. Preceding Configuration SIP Profile Related Topics SIP Busy Out External Gateway Accessing this Pane Cantata IMG EMS -> Profiles -> SIP Profile -> Options KeepAlive Maximum Objects: 1 per SGP Pane 922 ClientView Pane Reference Field Descriptions Number of Responses The number of positive responses received before marking a gateway as "up" (in a reachable state). 1-10 default = 3 Up Timer Timer to define the interval between OPTIONS messages when the gateway is responsive. If the gateway does not respond within the timer, the gateway will be marked as down and calls will not be routed to the gateway. 30-600 seconds default = 120 Down Timer Timer to define the interval between OPTIONS messages when the gateway is down (non responsive). If the gateway responds within the timer, and the number of times indicated in the , it will be marked as up and routing calls to the gateway will resume. 1-20 seconds default = 30 Cantata Technology - IMG 1010 Printable WebHelp 923 IMG WebHelp Outgoing Translation Tables Topic Location: ClientView Pane Reference Overview Description From here you create an outgoing translation table by right clicking on Outgoing Translation Tables and selecting New Translation Table. Related Topics Digit Translation Configuring Digit Matching and Translation Accessing this Pane Cantata IMG EMS -> New Routing Configuration -> New Outgoing Translation Tables Cantata Technology - IMG 1010 Printable WebHelp 924 ClientView Pane Reference Outseize Instruction Topic Location: ClientView Pane Reference Overview Description Use this pane to form a list of configuration instruction for outseize control. You create a separate Outseize Instruction entry for each instruction that you add to the list. You assign Instruction Lists to channels in the Channel Group pane. The IMG uses the list to perform an outseizure on the channel. Important Note: that the order in which the instructions appear in the ClientView tree is the order in which they will be sent. Previous Configuration Required Signaling Variant Related Topics Configuring CAS Accessing this Pane Cantata IMG EMS -> Signaling -> <Variant Name> -> Outseize Instruction Maximum Objects: 19 Pane Field Descriptions Instruction Type Scan for Wink N Outpulse Stage N Address Info Report Call Processing Event Send Host Acknowledgement Cancel R2 Receiver (E1 Only) Scan for Backward R2 Signal (E1 Only) 925 IMG WebHelp ___________________________________________________________________ _______ The second field depends on the Instruction Type: NOTE: For the following Instruction Types there are no more fields: Send Host Acknowledgement Scan for Backward R2 Signal (E1 Only) Cancel R2 Receiver (E1 Only) Scan for Wink N Wink Number 1-8 Report Call Processing Event Event Off-hook Backward R2 Signal Dialtone Detected First Digit Detected Wink 1-8 (T1 Only) Outpulse Stage N Address Info Stage Number Stage 1, 2, 3, 4 ___________________________________________________________________ _______ Delay Time (ms) (T1 Only) Applies to Instruction Type of Delay n Milliseconds. Use the slider or enter a value in the Value: box. 926 ClientView Pane Reference Cantata Technology - IMG 1010 Printable WebHelp 927 IMG WebHelp Physical IMG Topic Location: ClientView Pane Reference Overview Description Use this pane to add an IMG to a Logical IMG. Before you can add and configure Physical IMGs, you must create a Logical IMG to which you then add Physical IMGs. Physical IMGs in the same Logical IMG do not have to be co-located. Physical IMGs do not have to be in the same Logical IMG unless you are doing SS7 signaling and they are controlled by the same SS7 stack. Previous Configuration Required Logical IMG Related Topics Adding a Physical IMG Accessing this Pane Cantata IMG EMS-> Logical IMG-> Physical IMG Maximum Objects: 16 per Logical IMG Technical Notes Pane Field Descriptions 928 ClientView Pane Reference Logical IMG ID This field specifies the logical node ID of the physical IMG. The values are in the range from 0 to 63. This value will be disabled once it is configured and cannot be modified. IMG Name This field specifies the name of the physical IMG. Its length is up to 12 characters. The following are valid characters: a-z, A-Z, 0-9, - . ! % * _ ` ' ( ) [ ] { } < > IP Address (nn.nn.nn.nn) This field specifies the IP address of the physical IMG. IMG Type This field specifies the hardware type of the IMG. 1010 Monitoring Fields Subnet Serial Number Motherboard Revision Motherboard I/O Revision Software Version TDM Group 0 Type TDM Group 1 Type VoIP Module 0 Status VoIP Module 1 Status Connection State This monitoring field specifies the connection state between the physical IMG and the Communication Manager. NFS for Configuration Status Buttons Clear Software This button clears the software from the IMG and forces a hard reset – equivalent to cycling the power. Download Raw File This button is used to download API messages that configure specific custom PPL’s. The API messages have to be included in a file named 'rawapi.cfg' that exists in the location /opt/cantata/common/config on the GateControl EMS Server. If the messages in the file have a different logical node ID other than the physical IMG from which the button is pressed, the logical node ID will be overwritten. This allows 929 IMG WebHelp sending the same file for multiple nodes without needing to modify its contents. If a message in the file is NACKed by the IMG, all the following messages will be not be sent. SS7 Remote Node Info Mount Status Indicates if the NFS Server is available. Display Table This table shows a list of the configured physical IMG’s configured within the logical IMG. Cantata Technology - IMG 1010 Printable WebHelp 930 ClientView Pane Reference Physical Port Configuration Topic Location: ClientView Pane Reference Overview Description Use this pane to configure the Interface Mode for a port on the IMG. The IMG defaults to 10.100 with Auto-negotiation. You can change the setting to Full Duplex, in which case it will be negotiated to half-duplex. Select the desired mode of reach port. NOTE: Full Duplex is not supported for CTRL 0/1. Related Topics Configuring IP Interface Mode Accessing this Pane Cantata IMG EMS-> Network Interfaces -> Physical Port Configuration Maximum Objects: 1 per Physical IMG Pane Options Auto 100 Full (not supported for CTRL 0/1) Cantata Technology - IMG 1010 Printable WebHelp 931 IMG WebHelp Radius Client Topic Location: ClientView Pane Reference Overview Description This pane configures a Radius Client for a single Physical IMG. Before configuring a client, at least one Radius Server must be configured. Related Topics An Overview of RADIUS Configuring a RADIUS Client Accessing this Pane Cantata IMG EMS-> Logical IMG-> Physical IMG-> Radius Client Maximum Objects: 1 per Physical IMG Technical Notes Pane Field Descriptions Radius Client Network Interface 932 ClientView Pane Reference This drop-down list is populated with all of the Network Interfaces configured on this particular IMG. It is the responsibility of the user to make sure the interface may reach the particular server. If you are Authentication Port The port on the physical IMG that will be used to talk to the Authentication server. Accounting Port The port on the physical IMG that will be used to talk to the Accounting server. RADIUS Server Debug Mode Off (Default) If Radius is configured and the RADIUS server becomes unavailable, the IMG will not process incoming calls. This is most typically found when the IMG is used to create CDRs. Since the absence of a RADIUS server results in unbillable calls, the IMG has been designed to not process calls when RADIUS is enabled. If this occurs the IMG will reject calls to the network with the following cause values: ISDN - Cause 41 - Temporary failure SS7 - Cause 41 - Temporary failure H.323 - Cause 41 - Temporary failure SIP - 503 - Service Unavailable On When Debug Mode is On, calls will be completed whether the RADIUS server is active or not. The IMG will not require authentication from the RADIUS server to complete a call and no billing information will be logged. This is most typically used when using RADIUS for debugging purposes (tracking call failures, cause codes, etc). You can also choose this mode if you wish the IMG to continue to process calls in an un-billed fashion if you prefer to provide free service rather than no service. Prepaid Support Enable The IMG will act on 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. Disable (default) NOTE: Radius Prepaid Support Mode will be disabled if Radius Debug Mode is enabled. The two modes cannot be enabled at the same time. 933 IMG WebHelp RADIUS Time Format This setting determines the format that will be used in CDR in attributes that include time. Legacy Format This is the format used before the availability of the Time Zone feature (10.3.2 ER6). Use this for backward compatibility if you are not using local time. Example: Cantata-setup-time = "TUE FEB 20 22:24:45:270 2007" Legacy Format with timezone Use this format to represent local time in CDRs. Example: Cantata-setup-time = "WED FEB 14 12:05:54:740 2007 -0500" RFC-2822 with optional day of week Use this format to represent local time with optional day of week in CDRs. Example: Cantata-setup-time = "Tue, 20 Feb 2007 23:31:36.553 +0000" Primary Authentication Radius Server The Server ID that is used as the primary Authentication Server. Drop-down list populated with all Radius Authentication Servers that have been configured. Automatically populated with the first Authentication Server configured. Secondary Authentication Radius Server The Server ID that is used as the secondary Authentication Server. Drop-down list populated with all Radius Authentication Servers that have been configured. Primary Accounting Radius Server The Server ID that is used as the primary Accounting Server. Drop-down list populated with all Radius Accounting Servers that have been configured. Automatically populated with the first Accounting Server configured. Secondary Accounting Radius Server The Server ID that is used as the secondary Authentication Server. Drop-down list populated with all Radius Accounting Servers that have been configured. Cantata Technology - IMG 1010 Printable WebHelp 934 ClientView Pane Reference Radius Server Topic Location: ClientView Pane Reference Overview Description Use this pane to configure information about the Radius Servers that are in the network. There are two types of Radius Servers, accounting and authorization; each type may have a primary and secondary server. The same server may also do both accounting and authorization. The Servers are configured at the network level. Radius Client must be configured for every Physical IMG. Related Topics An Overview of RADIUS Configuring a RADIUS Accounting Server Configuring a RADIUS Authentication Server RADIUS Client Accessing this Pane Cantata IMG EMS->External Network Elements->Radius Servers->Radius Server Maximum Objects: 256 per EMS Technical Notes Pane Field Descriptions Radius Server Id 935 IMG WebHelp Allows a unique reference to address this particular server. 1-255 Radius Server Type This describes the type of server, whether it is used for authentication or for accounting. Authentication This server is used to give permission for the call to continue. Accounting This server is used for tracking billing information for the call. Radius Server Data Format Cantata Format Radius Server IP Address The IP Address of the Radius Server. Radius Server Port The port on the server which will accept the Radius connection. Radius Server UserName A Username to access this server. Radius Server Password The password to access this server. Radius Server Authentication Type This is the type of authentication the client server will use. PAP: Password Authentication Protocol CHAP: Challenge Handshake Authentication Protocol Radius Server Server Secret This must match the shared secret configured on the RADIUS server, otherwise authentication will fail. Display Table 936 ClientView Pane Reference The table will show all the Radius Clients that have been configured. Cantata Technology - IMG 1010 Printable WebHelp 937 IMG WebHelp Radius Servers Topic Location: ClientView Pane Reference Overview Description To create a Radius Server, right-click Radius Server and select New Radius Servers. Related Topics An Overview of RADIUS Configuring a RADIUS Accounting Server Configuring a RADIUS Authentication Server Accessing this Pane Cantata IMG EMS -> New External Network Elements -> New Radius Servers Maximum Objects: 1 Pane This pane shows the number of each type of Radius Server that have been configured. Cantata Technology - IMG 1010 Printable WebHelp 938 ClientView Pane Reference Raw API Command Topic Location: ClientView Pane Reference Overview Description Use this pane to download a raw API file to the IMG and have it become part of the Config file. Related Topics Downloading a Raw File Accessing this Pane Cantata IMG EMS-> Logical IMG -> Physical IMG -> New Raw API Cmds -> New Raw API Cmd Maximum Objects: 1 per Physical IMG Pane Field Descriptions Configure File Automatically populated. Cantata Technology - IMG 1010 Printable WebHelp 939 IMG WebHelp Raw API Commands Topic Location: ClientView Pane Reference Overview Description Related Topics Downloading a Raw File Accessing this Pane Cantata IMG EMS-> Logical IMG -> Physical IMG -> New Raw API Cmds Cantata Technology - IMG 1010 Printable WebHelp 940 ClientView Pane Reference Route List Topic Location: ClientView Pane Reference Overview Description This pane creates a Route List with Hunting Options specified. You then add entries to the list with the Route Entry pane. Route lists are sets of up to 20 channel groups from which the router can select an outgoing channel for a call. The goal of the route lists is to route calls in the most efficient and cost-effective manner possible. The channel groups that you assign to a route list provide alternate routes to a call destination. If the channels in one channel group are unavailable due to one of the cause codes listed below, the router attempts to select a channel from the remaining channel groups within the route list. The router searches the channel groups based on the hunting option that you specify for the route list. It selects an individual channel based on the hunting option that you specify within a channel group definition. Re-routing Cause Codes: NO CIRCUIT AVAILABLE - Cause Code 34 TEMPORARY FAILURE - Cause Code 41 EXCHANGE CONGESTION - Cause Code 42 Related Topics Configuring Route Lists Before you begin You must create your channel groups before you create your route lists. Accessing this Pane Cantata IMG EMS -> Routing Configuration -> Route Lists -> Route List Maximum Objects: 254 per EMS Pane Field Descriptions Name 941 IMG WebHelp A descriptive name for the route list table Route List ID This field is automatically populated with the next available number. Hunting Options Select the hunting algorithm that the router uses to select a channel group within the route list. The following hunting options are available LRU The router selects the least recently used channel group; that is, the group that has been idle for the longest period of time. Round Robin The router selects the first free channel group that follows the channel group that it selected for the previous call. With this option, the router maintains a pointer to the last used channel group and begins each new search at the next channel group within the route list. Sequential For each call, the router searches for a channel group based on the sequence of the channel groups in the route list. With this option the router always begins its search with the first channel group in the route list. Display Table This pane displays all of the Channel Groups assigned to the route list. Cantata Technology - IMG 1010 Printable WebHelp 942 ClientView Pane Reference Route Lists Topic Location: ClientView Pane Reference Overview Description From here you create a new Route List by right-clicking on Route Lists and selecting New Route List. Related Topics Configuring Route Lists Accessing this Pane Cantata IMG EMS -> New Routing Configuration -> New Route Lists Cantata Technology - IMG 1010 Printable WebHelp 943 IMG WebHelp Route Table Topic Location: ClientView Pane Reference Overview Description This pane is used to define rules for routing a call. This pane appears when you are creating the following: Route Table Service Routing Table Cause Code Table Related Topics Creating a Route Table Sort Order in Translation Tables and Routing Tables Previous Configuration Required Routing Tables Next Configuration Route Entry Accessing this Pane Cantata IMG EMS -> Routing Configuration -> New Routing Tables -> New Route Table Cantata IMG EMS -> Routing Configuration -> New Cause Code Tables -> New Cause Code Table Cantata IMG EMS -> Routing Configuration -> New Service Routing Tables -> New Service Routing Table Maximum Objects: 66 Total Route/Cause Code/Service Routing Tables per EMS Technical Notes Pane Field Descriptions Name 944 ClientView Pane Reference This is a descriptive name to define the table. This name appears for selection from other screens. ID This is a unique number to identify the table for addressing purposes and for logging. Routing Criteria Order This pop-up includes all of the different criteria supported for routing calls. The criteria are evaluated in the order in which they appear in this window. Move criteria up or down as desired and click OK. If this is a Cause Code table, the only criteria option is Cause Code. Buttons Save Route Table This button sends the Route Table to all the IMGs that are controlled by this GC EMS. Delete All Route Entries Deletes all entries in the route table, as long as the table is not currently assigned to any Channel Groups. When you click the button, a confirmation box will appear. Click Yes to proceed. If the table is assigned to a channel group, an error message will appear. Otherwise, the entries will be deleted. The entries will remain showing in the pane until you select another object. Display Table The pane will display all of the entries that have been configured for this particular route table. Cantata Technology - IMG 1010 Printable WebHelp 945 IMG WebHelp Routing Configuration Topic Location: ClientView Pane Reference Overview Description The Routing Configuration pane is a container that holds all the routing-related objects. From this pane, you can select the following routing configuration options by right clicking Routing Configuration and then selecting the desired option. Related Topics An Overview of Routing on the IMG A Summary of Routing Configuration Tasks Accessing this Pane Cantata IMG EMS -> New Routing Configuration Maximum Objects: 1 Technical Notes Buttons Download Translations This button downloads the Digit Translation tables to each Logical IMG Resource Table Incoming GW Table GW ID Table Cantata Technology - IMG 1010 Printable WebHelp 946 ClientView Pane Reference Routing Tables Topic Location: ClientView Pane Reference Overview Description From here you create a new Routing Table by right-clicking on Routing Tables and selecting New Route Table. Related Topics Creating a Route Table Accessing this Dialog Box Cantata IMG EMS -> New Routing Configuration -> New Routing Tables Maximum Objects: 85 Total Routing and Cause Code Tables Cantata Technology - IMG 1010 Printable WebHelp 947 IMG WebHelp Signaling Topic Location: ClientView Pane Reference Overview Description To configure SS7 or H.323 signaling parameters for a Physical IMG, first right click on the IMG Name and select New Signaling. The Signaling Tab appears in the left pane. From here you can configure SS7 or H.323 signaling, or view existing configurations. Related Topics Configuring ISDN Signaling Configuring H.323 Signaling Configuring SIP Signaling Configuring SS7 Signaling Accessing this Pane Cantata IMG EMS -> Logical IMG -> IMG Name -> New Signaling Cantata Technology - IMG 1010 Printable WebHelp 948 ClientView Pane Reference Signaling Variants Topic Location: ClientView Pane Reference Overview Description This is a container for creating custom SS7 or SIP-T variants. Related Topics Creating Custom SS7 Variants Accessing this Pane Cantata IMG EMS -> New Signaling Variants Display Table This table shows the components included in the variant entry selected. Cantata Technology - IMG 1010 Printable WebHelp 949 IMG WebHelp Signaling Variant Topic Location: ClientView Pane Reference Overview Description This pane is used to create a signaling variant. SS7 Variants are based on one of the base ISUP variants. It is also used to import a prepackaged SS7 variant file provided by Cantata. SS7 Signaling variants are used to modify the base variants based on country-specific or regulatory needs. CAS Variants are used to modify base variant (CCITT for E1, Trunk Type specific defaults for T1) based on country-specific or regulatory requirements. SIP-T You can also use this pane to modify a base variant name to be used by the IMG in outgoing ISUP MIME messages for SIP-T. NOTE: Once a custom variant is assigned to a stack, you cannot modify or delete an existing entry in the variant. You can add new entries, however. Related Topics Creating Custom SS7 Variants Configuring SIP-T Accessing this Pane Cantata IMG EMS -> New Signaling Variants -> Signaling Variant Maximum Objects: 10 per EMS (variants must have unique ID and variant name) Technical Notes Pane SS7 and SIP-T E1 CAS 950 ClientView Pane Reference T1 CAS Field Descriptions Variant Name This field specifies the name of the variant to be created (up to 25 characters). Variant Type This field specifies the type of protocol for this variant. SS7 CAS SIP-T Base Variant This field specifies the variant that this new variant is based on. SS7 ANSI 97 ANSI 92 ANSI 95 951 IMG WebHelp ITU 97 CCITT 88 CAS ITU 93 ETSI V1 ETSI V2 ETSI V3 T1 Signaling E1 Signaling Variant Id 1-10 Trunk Type (T1 CAS Only) E+M FXS Loop In Start Dial (T1 CAS Only) Wink Start (default for E+M) Dial Tone (default for FXS Loop) Immediate None Out Start Dial (T1 CAS Only) Wink Start (default for E+M) Dial Tone Fixed Pause None (default for FXS Loop) CAS Idle Bits (E1 CAS Only) CAS out Of Service Bits (E1 CAS Only) Address Signaling Type (CAS Only) 952 MFR1 (Default for T1) (for E1 also requires PPL Configuration) ClientView Pane Reference DTMF (for E1 also requires PPL Configuration) MFR2 (Default for E1) Outbound Multi-string (T1 CAS Only) Disabled (default) Stage1 (DN+ANI) Stage1 (ANI+DN) Stage2 (ANI+DN) Stage2 (DN+ANI) Busy Out Flag (CAS Only) Disabled (default) Enabled Use this field to enable the busy out feature on a channel or range of channels. Only channels configured with a trunk type of E&M. You Busy Out channels in the CAS Circuits pane. You cannot "busy out" a channel if this flag is disabled. Display Table This table shows a list of the configured Variant entries. Cantata Technology - IMG 1010 Printable WebHelp 953 IMG WebHelp SIP DTMF Support Topic Location: ClientView Pane Reference Overview Description Use this pane to enable and configure SIP DTMF support to send a DTMF digit to another gateway. There are two methods supported: SIP INFO Method SIP Subscribe/Notify Related Topics SIP INFO Method for DTMF Accessing this Pane Cantata IMG EMS -> Profiles -> SIP Profile -> SIP DTMF Support Maximum Objects: 1 per SGP Pane Field Descriptions Method Disable (default) Subscribe 954 Info with Pattern (this option previously named "INFO") Info DTMF digit relay (10.3.3 ER 2) ClientView Pane Reference DTMF String Enter the desired string. Options # ## ### #### Default = ### DTMF Duration Time (ms) This is the allowed amount of time for the entire DTMF string to be received. If the timer expires, it resets to zero and starts over. Default = 500 Default Subscriber Duration (s) (Subscribe/Notify Method Only) The amount of time that a subscriber session will be kept up. This value is also the maximum allowed duration. Minimum Subscriber Duration (s) (Subscribe/Notify Method Only) The minimum amount of time that a subscriber session must be established for. Cantata Technology - IMG 1010 Printable WebHelp 955 IMG WebHelp SIP From Header Tags Topic Location: ClientView Pane Reference Overview Description Use this pane to configure how the IMG handles certain tags in the SIP From header. Accessing this Pane Cantata IMG EMS -> Profiles -> SIP Profile -> SIP From Header Tags Preceding Pane SIP Profile Maximum Objects: 1 per SGP Pane Field Descriptions ISUP OLI When this option is selected, the IMG will include the INFO digits received in the Originating Line Info parameter (OLI) in the IAM message from the SS7 ANSI side into the ISUP_OLI tag in the From Header on the SIP side, and vice versa. Disable Enable ISUP CPC 956 Disable CPC Placed at User Part Support Example ClientView Pane Reference From:unavailable<sip:unavailable;[email protected]>;ta g=95ffcd055e0f78f7d5d397020e89288d78a1 CPC Placed at URI Parameter Support Example From:unavailable<sip:[email protected];cpc=operator>;ta g=95ffcd055e0f78f7d5d397020e89288d78a1 Unmapped Values Ignore Pass Value Cantata Technology - IMG 1010 Printable WebHelp 957 IMG WebHelp SIP Headers Topic Location: ClientView Pane Reference Overview Description Use this pane to enable support for the following: Diversion Header Support P Charge Info Time Stamp Support P Asserted Info Remote Party ID Accessing this Pane Cantata IMG EMS -> Profiles -> SIP Profile -> SIP Headers Preceding Pane SIP Profile Maximum Objects: 1 per SGP Pane Field Descriptions Diversion Header Support 958 ClientView Pane Reference If you enable this feature, SS7 Redirection information will be sent in the SIP Diversion Header in the outgoing SIP INVITE. See SIP Diversion Header for more information. Disable (default) CC-Diversion Diversion Time Stamp Support Enable: The IMG will insert the Timestamp Header in the format of: Timestamp: MMDDYYYYHHMMSS This value is derived from the system time of the IMG. (After bootup the IMG uses Jan 1,1970 as its internal date or receives a proper value for the time through SNTP) Disable The IMG will not insert the Timestamp. However, actions based on the Timestamp are in accordance with sec 8.2.6.1 of RFC 3261 P Charge Info P Asserted Info The P-Asserted-Identity header field is used among trusted SIP entities (typically intermediaries) to carry the identity of the user sending a SIP message as it was verified by authentication. A proxy server which handles a message can, after authenticating the originating user in some way (for example: Digest authentication), insert such a P-Asserted-Identity header field into the message and forward it to other trusted proxies. A proxy that is about to forward a message to a proxy server or UA that it does not trust MUST remove all the PAsserted-Identity header field values if the user requested that this information be kept private. Copyright (C) The Internet Society (2002). All Rights Reserved. Remote Party ID The SIP Remote-Party-ID header identifies the calling party and includes user, party, screen and privacy headers that specify how a call is presented and screened. See SIP Privacy. Cantata Technology - IMG 1010 Printable WebHelp 959 IMG WebHelp SIP Network Element Topic Location: ClientView Pane Reference Overview Description Use this pane to enable a physical IMG to send out a SIP Registration for Authentication. Pre-requisite You must have configured an External Gateway where you have Outbound Registration enabled . Related Topics Accessing this Pane Cantata IMG EMS -> Logical IMG -> Physical IMG -> Signaling -> SIP Signaling -> SIP Network Element Maximum Objects: 15 per SIP Gateway Pane Field Descriptions SIP Network Element The external SIP Gateway. 960 ClientView Pane Reference SIP UserName (AOR) (Address of Record) A SIP Identifier, or Address of Record (AOR) allows SIP users to communicate with each other without knowing network addresses. AORs are in the same format as an E-mail address: username@domainName. SIP Authentication UserName The UserName the IMG will use for authentication with this gateway. SIP Authentication Password The Password the IMG will use for authentication with this gateway. Monitoring Fields SIP Network Element Connection Status The status of this SIP Gateway. Cantata Technology - IMG 1010 Printable WebHelp 961 IMG WebHelp SIP Options KeepAlive Topic Location: ClientView Pane Reference Overview Description Use this pane to configure parameters for the SIP Busy Out feature. The IMG can monitor the status of external SIP gateways by sending periodic SIP OPTIONS messages. If the gateway does not respond in a configured amount of time the IMG will mark the gateway as down and attempt to re-route the call to a different gateway. You enable the SIP Busy Out feature on a specific gateway in the External Gateway pane. Preceding Configuration SIP Profile Related Topics SIP Busy Out External Gateway Accessing this Pane Cantata IMG EMS -> Profiles -> SIP Profile -> Options KeepAlive Maximum Objects: 1 per SGP Pane 962 ClientView Pane Reference Field Descriptions Number of Responses The number of positive responses received before marking a gateway as "up" (in a reachable state). 1-10 default = 3 Up Timer Timer to define the interval between OPTIONS messages when the gateway is responsive. If the gateway does not respond within the timer, the gateway will be marked as down and calls will not be routed to the gateway. 30-600 seconds default = 120 Down Timer Timer to define the interval between OPTIONS messages when the gateway is down (non responsive). If the gateway responds within the timer, and the number of times indicated in the , it will be marked as up and routing calls to the gateway will resume. 1-20 seconds default = 30 Cantata Technology - IMG 1010 Printable WebHelp 963 IMG WebHelp SIP Profile Topic Location: ClientView Pane Reference Overview Description Use this pane to configure various SIP features in the IMG. CHANGES TO THIS PANE: The following features are no longer configured with this pane but with the pane noted. SIP Proxy - SIP Proxy pane SIP DTMF - SIP DTMF Support SIP Headers - SIP Headers WARNING: Making changes to a SIP Profile that is assigned to active calls may result in call failure or other adverse effects. Stop all traffic to gateways or channel groups that use a SIP Profile before you make changes. Related Topics SIP Features Accessing this Pane Cantata IMG EMS -> Profiles -> SIP Profile Maximum Objects: 16 per EMS Pane 964 ClientView Pane Reference Field Descriptions SIP Profile ID 1-15 SIP Profile Name A unique name to identify the profile. ___________________________________________________________________ __________________ These fields relate to the SIP PRACK feature. PRACK Support Disable (default) Required Supported PRACK Timer (sec) This timer is used to request an “extension” of the transaction at proxies in case if the INVITE transaction will take some time to generate a final response (RFC 3262 page 3). When this PRACK Refresh timer expires, the IMG will send out 1XX reliable response. 60 (s) 150 (s) (default) ___________________________________________________________________ __________________ CODEC Priority This feature allows you to configure whether the IMG or the remote gateway takes priority when selecting a codec. Local Remote Example: If the IMG has a CODEC list of: g711u g711a g729 965 IMG WebHelp and a remote gateway offers: g729 g711u If the Codec Negotiation Priority is set to Local, the IMG will answer with g711u. If the Codec Negotiation Priority is set to Remote, the IMG will answer with g729. Outbound Modem Triggers Re-INVITE (10.3.3 ER2) Disable (default) Enable R-URI Header Tags If selected, the tag will be added into the R-URI of the outgoing INVITE in the “sip_uri_enc” method. RN This tag is used to convey the location routing number. See LNP Routing for more information. NPDI This tag is used to indicate whether an LNP query has been performed. See LNP Routing for more information. CIC The CIC parameter is a three- or four- digit code used in routing tables to identify the network that serves the remote user when a call is routed over many different networks. See SIP Carrier Identification Code for more information. 3XX Redirect Support When this feature is enabled, the IMG will send a new INVITE to the contact returned in a 3XX response from a redirect server. When this feature is disabled, the IMG will release the call when it receives a 3XX response from a redirect server and map 3XX code to 4XX code. See SIP Redirection for more information. Enable (default) Disable SIP Loop Detection If a SIP request is received and falls in the loop detection path, you may want to ignore the loop. For example if the request has a different To header and also includes a diversion header. 966 Enable ClientView Pane Reference Disable Disable with no Header Check SIP Re-Origination Attempts This feature allows you to limit the number of INVITE re-transmission attempts (1-5 attempts). The number configured supersedes the standard # of re-transmissions specified in RFC3261 (which is based on timers T1 and T2 ). Retransmit All (default) 2 1 3 4 5 ___________________________________________________________________ ____________________________________________ These fields relate to the SIP Trunk Group Selection feature. Apply the OTG to the outbound SIP Invite On an outgoing invite, the OTG that was received from the incoming call will take precedence over the internal IMG incoming Channel group name if it was a SIP call (for any other inbound protocol, the OTG would be the incoming Trunk Group Name). This OTG is then appended in the “From” header of the outbound invite. Enable Disable (default) Use the incoming OTG for incoming Channel Group Selection When the OTG field is included in the “From” header the IMG will use this trunk group as the incoming trunk group to determine which incoming DPE table and route table to use. The OTG will also be able to be added to the “From” header in an outbound SIP invite, the OTG will have the A side trunk group name. The IMG extracts the OTG from the SIP "From" header and passes in the Initial Setup. If an OTG is found, the IMG will use that channel group instead of the one that came from the lookup table in the SIP process. Enable Disable (default) Use the DTG for outgoing channel group selection When the DTG is received in the request-URI the IMG will skip the mid-call router and use the DTG that was received as the outbound channel group. 967 IMG WebHelp When the IMG is about to perform routing for the outbound side, it will look for the DTG from the same location as the Calling Party Number. If the DTG is valid, the call will then use the channel group that corresponds to that DTG instead of performing a routing lookup Enable Disable (default) ___________________________________________________________________ _______________________ These fields apply to the Pass through ‘+’ sign in the user part of URI feature. Append (+) for Headers Use this field to prefix ‘+’ to the user if the incoming INVITE does not have ‘+’. Select one or more headers to apply the "+" to. Remove (+) for Headers Use this field to remove a "+" from an incoming INVITE if you do not want it included in the outgoing INVITE. This can also be used in the case that the incoming side is not SIP. INFO for Spirou/ITX (10.3.3 ER1) 968 ClientView Pane Reference Enable Disable Use this field to enable the sending of the SS7 ITX message based on a SIP INFO message received from a SIP Application. This allows a SIP application to interwork with the SPIROU standard (Signalisation Pour l'Interconnexion des Réseaux Ouverts/Signaling for the Interconnection of Open Networks). See Support for SPIROU/ITX in SIP INFO. Outgoing Fully Qualified Domain Name (FQDN) (10.3.3 ER2) If this option is enabled and the Domain Name fields in the SIP signaling and VoIP Module (Facility pane) objects are filled with FQDNs, then all the outgoing request and response SIP messages will include FQDNs instead of IP addresses (Local IMG Signaling and VoIP Module IP addresses) Disable Signaling Only Only the FQDN of the local IMG signaling IP address is inserted in the outgoing SIP messages. See Call Trace. SDP c=line Only Only the FQDN of the local IMG VoIP IP address is inserted in the outgoing SIP messages. See Call Trace. Both The FQDNs of the local IMG signaling IP address and the local IMG VoIP address are inserted in the outgoing SIP messages. See Call Trace. See Fully Qualified Domain Name Support for more information. Cantata Technology - IMG 1010 Printable WebHelp 969 IMG WebHelp SIP Profile Timers Topic Location: ClientView Pane Reference Overview Description Use this pane to configure SIP timers that apply to a specific SIP Profile. Related Topics SIP Profiles Accessing this Pane Cantata IMG EMS -> SIP Profile -> SIP Profile Timers Preceding Pane SIP Profile Maximum Objects: 1 per SGP Pane Cantata Technology - IMG 1010 Printable WebHelp 970 ClientView Pane Reference SIP Proxy Topic Location: ClientView Pane Reference Overview Description Use this pane to configure various settings for connection to a SIP Proxy. Related Topics SIP Proxy Handling Preceding Pane SIP Profile Accessing this Pane Cantata IMG EMS -> Profiles -> SIP Profile -> SIP Proxy Maximum Objects: 1 per SGP Pane Field Descriptions Outbound Proxy Enable Disable (default) Send Re-Invite to Proxy 971 IMG WebHelp Enable Disable (default) Send Outbound Register Enable Disable (default) Proxy Transport UDP (default) TCP Proxy Address Type Host Name IP Address Proxy Name If Address Type = Host Name , enter Proxy Name Proxy IP Address Proxy Port Default = 5060 Cantata Technology - IMG 1010 Printable WebHelp 972 ClientView Pane Reference SIP Session Timer Topic Location: ClientView Pane Reference Overview Description Use this pane to configure SIP Session Timer values. Related Topics SIP Session Timer SIP Session Timer Call Flows SIP UPDATE Preceding Pane SIP Profile Accessing this Pane Cantata IMG EMS -> Profiles -> SIP Profile -> SIP Session Timer Maximum Objects: 1 per SGP Pane Field Descriptions Session Timer 973 IMG WebHelp Enable (default) Disable Enforce Feature Enable If enabled, the IMG will perform the session refresh request even if the remote gateway does not support session timer. The session timer cannot be turned off in mid dialog. Disable (default) Refresh Method Re-Invite The IMG will use re-INVITE even if the remote gateway supports UPDATE. Update The IMG will use UPDATE only if the remote gateway supports it, otherwise reINVITE will be used instead. Refresher Only applicable for initial refresh response when IMG acts as UAS and the request does not specify refresher. Local The IMG will perform a refresh. Remote The IMG will wait for refresh request. Minimum Session Expires Establishes the lower bound session refresh interval. It can be raised but cannot be lowered. It is mandatory on 422 response and optional on INVITE and UPDATE request. It must not be less than 90 seconds. Default = 900 Session Expire Establishes the upper bound session refresh interval. It can be lowered but cannot be below the value specified in Min-SE. It is optional on INVITE or UPDATE request and 2xx response to INVITE or UPDATE. The recommended value is 30 minutes. Default = 1800 974 Cantata Technology - IMG 1010 Printable WebHelp ClientView Pane Reference SIP Signaling Topic Location: ClientView Pane Reference Overview Description Use this pane to configure SIP signaling. Related Topics An Introduction to SIP Configuring SIP Signaling Accessing this Pane Cantata IMG EMS-> Logical IMG-> Physical IMG -> Signaling -> SIP Maximum Objects: 1 per Physical IMG Pane Field Descriptions SIP Signaling IP Address The IP Address of the Network Interface used for SIP Signaling. Local SIP Port 975 IMG WebHelp The port used for SIP signaling. SIP Compact Header Enable Disable Default Transport Type UDP (default) TCP Default SIP UserName (AOR) Default UserName for Authentication Default SIP Authentication UserName Default SIP Authentication Password Enable SIP-T Yes No SIP-T Behavior Optional Required Privacy Support To enable Privacy for the entire GC EMS, set the Privacy Support field for the method supported by the proxy. All calls will be handled according to this setting, regardless of other SIP Privacy settings on an External Gateway or ISDN/ISUP Group. See Configuring SIP Privacy. Off (default) Remote-Party only P-Asserted only Both Remote IMGs SIP Profile 976 ClientView Pane Reference Select a SIP Profile to define how another IMG should treat a call going to or coming from this logical IMG. Fully Qualified Domain Name (FQDN) (10.3.3 ER2) The FQDN to be inserted in outgoing SIP messages when FDQN is enabled in the SIP Profile. See Fully Qualified Domain Name Support for more information. Cantata Technology - IMG 1010 Printable WebHelp 977 IMG WebHelp SIP T Entity Topic Location: ClientView Pane Reference Overview Description Use this pane to customize the name of an ISUP variant in an ISUP MIME body sent by the IMG when SIP-T is enabled. NOTE: You must have SIP T Enabled in the SIP Signaling pane to access the SIP T Entity pane. Related Topics Configuring SIP-T Accessing this Pane Cantata IMG EMS -> Logical IMG -> Physical IMG -> Signaling -> SIP Signaling -> SIP T Entity Maximum Objects: 4 per SIP Signaling object Pane Field Descriptions SS7 Stack Select the stack to which you are assigning the variant. SIP Variant Select the custom variant name to send in ISUP MIME body. You must have previously created this custom variant using the Variant Table pane. Cantata Technology - IMG 1010 Printable WebHelp 978 ClientView Pane Reference SIP Timers Topic Location: ClientView Pane Reference Overview Description Use this pane to configure SIP Timers. Related Topics Configuring SIP Timers Accessing this Pane Cantata IMG EMS -> Logical IMG -> Physical IMG -> Signaling -> SIP Signaling -> SIP Timers Maximum Objects: 1 per SIP Signaling object Pane Field Descriptions SIP T1 (10 ms) The value for SIP Timer T1, in 10 ms increments. SIP T2 (10 ms) The value for SIP Timer T2, in 10 ms increments. SIP T4 (10 ms) The value for SIP Timer T4, in 10 ms increments. SIP Timer D (10 ms) The value for SIP Timer D, in 10 ms increments. 979 IMG WebHelp Cantata Technology - IMG 1010 Printable WebHelp 980 ClientView Pane Reference SIP Virtual Address Topic Location: ClientView Pane Reference Overview Description Use this pane to configure a SIP Virtual IP Address for SIP Based Load Balancing. Related Topics SIP-Based Load Balancing Configuring SIP Based Load Balancing SIP Signaling Network Interface Accessing this Pane Cantata IMG EMS -> Logical IMG -> Physical IMG -> Signaling -> SIP Signaling -> SIP Virtual Address Maximum Objects: 2 per SIP Signaling object Pane Field Descriptions SIP Virtual Address ID 1 or 2 SIP Virtual IP Address This drop-down will be populated with any CPU Network Interface entries that have Gratuitous ARP and ARP Responses set to Disable. Select the desired entry. When the Gratuitous ARP and ARP Responses is set to Disable, this Virtual IP Address will not be allowed to issue a Gratuitous ARP. In addition, whenever an external node attempts to send an ARP to this Virtual IP Address, the ARP Reply will be suppressed. 981 IMG WebHelp Any node that knows the MAC address associated with this Virtual IP Address (through static configuration as used in Load Balancers) will be able to send packets to it. The Virtual IP Address will be able to send packets to any desired node since ARP Requests from the Virtual IP Address for an unknown IP’s MAC address will be allowed. For all outbound SIP requests, the real SIP Signaling IP Address is used to send SIP messages, even if the outbound transaction is within a dialog which had previously used the Virtual IP Address. IP Virtual Port Default = 5060. 982 Cantata Technology - IMG 1010 Printable WebHelp ClientView Pane Reference SNMP Agent Topic Location: ClientView Pane Reference Overview Description Use this pane to configure the SNMP Agent on a physical IMG. Related Topics An Overview of SNMP Configuring SNMP SNMP Manager Accessing this Pane Cantata IMG EMS-> Logical IMG-> Physical IMG-> New SNMP Agent Maximum Objects: 1 per Physical IMG Pane Field Description Engine ID Unique ID for the IMG's SNMP manager. SNMP System Name The name of the IMG. The default is IMG<NodeID>. System Location Physical location of IMG. 983 IMG WebHelp System Contact Who to contact regarding problems with this IMG. Radius Client Network Interface The IP Address of the RADIUS Client for this IMG. Cantata Technology - IMG 1010 Printable WebHelp 984 ClientView Pane Reference SNMP Manager Topic Location: ClientView Pane Reference Overview Description Use this pane to configure the IMG SNMP module to match settings on your SNMP Manager. Related Topics An Overview of SNMP Configuring SNMP SNMP Agent Accessing this Pane Cantata IMG EMS -> New External Network Elements -> SNMP Managers -> SNMP Manager Maximum Objects: 3 per GC EMS Pane Field Descriptions Engine ID Unique ID of the external SNMP Manager the IMGs SNMP Agent will communicate with. 985 IMG WebHelp SNMP User Name Human-readable name for the manager. SNMP Community Name Security string to include in communications with manager running SNMPv2c. SNMP Server IP Address IP Address of the External SNMP Manager. SNMP Trap Port Port ID of the External SNMP Manager. Default = 161. SNMP Version Version of the SNMP protocol to use when communicating with the SNMP Manager. SNMP v1 SNMP v2c Authentication Protocol SNMPv3 security to ensure message actually comes from the SNMP manager and that the contents are unaltered. Authentication Key Privacy Protocol SNMPv3 security to ensure no one can eavesdrop on communications. Privacy Key SNMP Timeout (ms) How long to wait for an ACK from a manager before timing out. Trap Retries How many times to resend a trap to the SNMP manager. ___________________________________________________________________ ____________________________ 986 ClientView Pane Reference The following fields relate to filtering traps. See examples below. Trap Notify Type Inclusive Include traps that match the filtering configured. Exclusive Exclude traps that match the filtering configured. Trap Subtree The OID of the MIB. Trap Notify Filter A mask indicating which traps to filter in/out. ___________________________________________________________________ ____________________________ Trap Configuration Examples Examples for using the Trap Filters in the SNMP Manager object screen. Example 1 Goal: Do not report a trap for Object ID 1.3.6.1.6.3.1.1.5.4. All others will be reported. Configuration Trap Notify Type: exclusive Trap Subtree: 1.3.6.1.6.3.1.1.5.4 Trap Notify Filter: 1.1.1.1.1.1.1.1.1.1 Example 2 Goal: Do not report traps for Object ID's 1.3.6.1.6.3.1.1.5.3 and 1.3.6.1.6.3.1.1.5.4. All others will be reported. Note: OID's such as 1.3.6.1.6.3.1.1.5.1 and 1.3.6.1.6.3.1.1.5.5, etc will also not be reported. Configuration Trap Notify Type: exclusive Trap Subtree: 1.3.6.1.6.3.1.1.5 Trap Notify Filter: 1.1.1.1.1.1.1.1.1 Note: OID's such as 1.3.6.1.6.3.1.1.5.1, 1.3.6.1.6.3.1.1.5.2 and 1.3.6.1.6.3.1.1.5.5, etc will also not be reported. Example 3 987 IMG WebHelp Goal: Only report traps with Object ID 1.3.6.1.6.3.1.1.5.3. All others will NOT be reported. Configuration Trap Notify Type: inclusive Trap Subtree: 1.3.6.1.6.3.1.1.5.3 Trap Notify Filter: 1.1.1.1.1.1.1.1.1.1 Example 4 Goal: Only report traps with Object ID's 1.3.6.1.6.3.1.1.5.3 and 1.3.6.1.6.3.1.1.5.4. All others will NOT be reported. Configuration Trap Notify Type: inclusive Trap Subtree: 1.3.6.1.6.3.1.1.5 Trap Notify Filter: 1.1.1.1.1.1.1.1.1 Note: OID's such as 1.3.6.1.6.3.1.1.5.1, 1.3.6.1.6.3.1.1.5.2 and 1.3.6.1.6.3.1.1.5.5, etc will also be reported. Example 5 Goal: Only report traps that begin with Object ID 1.3.6.1. All others will NOT be reported. Configuration Trap Notify Type: inclusive Trap Subtree: 1.3.6.1 Trap Notify Filter: 1.1.1.1 Cantata Technology - IMG 1010 Printable WebHelp 988 ClientView Pane Reference SNMP Managers Topic Location: ClientView Pane Reference Overview Description To configure an SNMP Manager, right-click SNMP Managers in the ClientView tree and select New SNMP Manager. Accessing this Pane Cantata IMG EMS -> New External Network Elements -> SNMP Managers See SNMP Manager pane. Cantata Technology - IMG 1010 Printable WebHelp 989 IMG WebHelp SS7 Signaling Topic Location: ClientView Pane Reference Overview Description This object identifies the SS7 signaling and specifies the SS7 redundancy state. Related Topics Configuring SS7 Signaling Accessing this Pane Cantata IMG EMS-> Logical IMG-> Physical IMG -> Signaling-> SS7 Maximum Objects: 1 per Physical IMG Technical Notes Pane Field Descriptions Redundancy Configuration This field specifies the state of the SS7 state machine 990 StandAlone A single physical IMG with no redundancy Primary Primary physical IMG, which will support SS7 links ID: 0 – 63. It has to be informed about its Secondary node ID. ClientView Pane Reference Secondary Secondary physical IMG, which will support SS7 links ID: 64 – 127. It has to be informed about its primary node ID. Peer Logical Node ID This field specifies the primary or secondary physical IMG nodes in case of a redundant configuration. Monitoring Fields Primary State This monitoring field displays the state of the primary SS7 server node. Secondary State This monitoring field displays the state of the secondary SS7 server node. Buttons Switch Over This button forces an SS7 state machine switchover. Cantata Technology - IMG 1010 Printable WebHelp 991 IMG WebHelp SS7 Link Topic Location: ClientView Pane Reference Overview Description This object identifies an SS7 link within an SS7 link set to an APC. Related Topics Configuring_SS7_Signaling_Links Accessing this Pane Cantata IMG EMS -> Logical IMG -> Physical IMG -> SS7 -> SS7 Stack -> SS Link Set -> SS7 link Maximum Objects: 64 per Logical IMG Technical Notes Pane Field Descriptions Primary/Secondary This field specifies whether the SS7 link is supported by the primary or secondary physical IMG. Primary Secondary Link ID This field specifies the SS7 link ID. Link ID 0 – 63 are allowed for the primary physical IMG, while link ID 64 – 127 are allowed for the secondary physical IMG. Interface - Offset This field specifies the physical offset (span) on which the SS7 link will be configured. 992 ClientView Pane Reference Channel This field specifies the channel from the physical offset (span) chosen in the previous field on which the SS7 link will be configured. Signaling Link Code This field specifies the SLC of the SS7 link. SLC is unique across any SS7 link set with a range of values of 0 – 15. Data Rate This field specifies the data rate of the SS7 signaling link. NOTE: For T1 SS7 links with line coding configured for B7ZS, only the 48 Kbps data rates are valid. 64 Kbps 56 Kbps mask MSB (The Most significant bit is masked resulting in 56 kbps) 56 Kbps mask LSB (The Least significant bit is masked resulting in 56 kbps) 48 Kbps mask LSB and MSB (The Least and Most significant bits are masked resulting in 48 kbps) 48 Kbps mask 2 MSBs (The 2 Most significant bits are masked resulting in 48 kbps) Electrical Interface DS1 Channel DS1 Channel Data Monitoring Fields Link Status This monitoring field displays the status of the SS7 link whether it is in or out of service. Buttons In Service This buttons brings the SS7 link in service. Out Of Service This buttons brings the SS7 link out of service. Inhibit This buttons inhibits the SS7 link. UnInhibit 993 IMG WebHelp This buttons uninhibits the SS7 link. Display Table This table displays a list of the configured SS7 links under a specific SS7 Link set. Cantata Technology - IMG 1010 Printable WebHelp 994 ClientView Pane Reference SS7 Link Set Topic Location: ClientView Pane Reference Overview Description This object identifies a link set that is used to connect an SS7 stack on the physical IMG to an adjacent point code. Related Topics Configuring_SS7_Link_Sets Accessing this Pane Cantata IMG EMS-> Logical IMG-> Physical IMG-> SS7 -> SS7 Stack -> SS7 Link Set Maximum Objects: 128 per physical IMG Technical Notes Pane Field Descriptions Link Set ID This field specifies the ID of the SS7 link set. APC This field specifies the adjacent point code of the node that this link set will be connected to. The format of the APC will follow the same rules in the SS7 stack. For example if the OPC is ITU 97, which follows the format of 3-8-3, the APC should also be running ITU 97 and should follow the format of 3-8-3. Point codes can be expressed in dotted decimal or decimal format. Comments You can enter information about the Link Set such as location and type of SS7 far side (for example, New York STP). Display Table 995 IMG WebHelp This table displays a list of the SS7 link sets configured under a specific stack. Cantata Technology - IMG 1010 Printable WebHelp 996 ClientView Pane Reference SS7 Parameter Filter Topic Location: ClientView Pane Reference Overview Description This pane indicates which SS7 parameters are passed on to the outbound side and which are not. By default, all parameters are passed except for Transit Network Select. Related Topics Configuring SS7 Parameter Filters Accessing this Pane Cantata IMG EMS -> Routing Configuration -> Channel Groups -> Channel Group (of type SS7) -> SS7 Parameter Filter Maximum Objects: 1 per ISUP Group Pane Field Descriptions For each field, the options are: Pass Don't Pass Access Transport Calling Party Number Carrier Identification Carrier Selection Info 997 IMG WebHelp Charge Number Generic Address Generic Name Jurisdiction Info Original Called Number Out Trunk Group Number Originating Line Info Redirecting Number Redirecting Info Service Code Indicator Transit Network Select Cantata Technology - IMG 1010 Printable WebHelp 998 ClientView Pane Reference SS7 Route Topic Location: ClientView Pane Reference Overview Description This pane defines a route to an SS7 destination (DPC). Related Topics Configuring SS7 Signaling Routes Accessing this Pane Cantata IMG EMS -> Logical IMG -> Physical IMG -> Signaling -> SS7 -> SS7 Route Maximum Objects: 512 routes to 128 destinations per Physical IMG Technical Notes Pane Field Descriptions Route ID This field identifies the ID of the SS7 Route. Allowable values are 0 to 511. Route Type This field identifies whether the route to the specified DPC is the first one configured or whether there are already existing routes to that DPC. New Route Existing Route (Combined Link Set Enabled) Existing Route (Combined Link Set Disabled) Linkset ID 999 IMG WebHelp This field will be enabled only if the Route type is set to ‘Existing Route (Combined Link Set Enabled)’. This field is a pull-down menu of the already-configured linksets New DPC This field will be enabled only if the Route type is set to ‘New Route’. This field identifies the Point Code of the Destination. Point codes can be expressed in dotted decimal or decimal format. Existing DPC This field will be enabled only if the Route type is set to ‘Existing Route (Combined Link Set Disabled)’ or ‘Existing Route (Combined Link Set Enabled) This field is a pull-down menu of the already-configured Destinations. Priority This field identifies the priority of the route when there are multiple routes to the same destination. Allowable values are 0 to 35. This field will be disabled when the route type is set to ‘Existing Route (Combined Link Set Enabled)’ because all the routes within the combined link set will have the same priority. Comments A meaningful description of this route, such as the location and type of the SS7 far side (for example Chicago 5ESS.) Display Table This table shows a list of the configured SS7 Routes under a specific Link Set Cantata Technology - IMG 1010 Printable WebHelp 1000 ClientView Pane Reference SS7 Stack Topic Location: ClientView Pane Reference Overview Description This pane configures an SS7 stack. Related Topics Configuring_an_SS7_Signaling_Stack Accessing this Pane Cantata IMG EMS-> Logical IMG-> Physical IMG-> SS7 -> SS7 Stack Maximum Objects: 4 per Physical IMG Technical Notes Pane Field Descriptions Stack ID This field specifies the ID of the stack. The values are in the range 0 – 3. ClientView ensures that the Stack ID is unique across multiple physical IMG’s. SS7 Variant 1001 IMG WebHelp This field specifies the variant used for the stack. Base Only any custom variants that have been created NOTE: Once a custom variant is assigned to a stack, you cannot modify or delete an existing entry in the variant. You can add new entries, however. ISUP This field specifies the ISUP variant. ANSI 97: The point code format is 8-8-8 ANSI 92: The point code format is 8-8-8 ANSI 95: The point code format is 8-8-8 ITU 97: The point code format is 3-8-3 ITU 93: The point code format is 3-8-3 CCITT 88: The point code format is 3-8-3 ETSI V1: The point code format is 3-8-3 ETSI V2: The point code format is 3-8-3 ETSI V3: The point code format is 3-8-3 China JT-ISUP OPC This field specifies the originating point code value of stack. Point codes can be expressed in dotted decimal or decimal format. MTP Pause This field determines whether resuming traffic to a paused DPC will be immediate or delayed. Immediate Delayed Cause Location The value populated in the Location parameter in the Cause IE when a call is released. User (0 - Message Generated by User) (default) Local public network (2 - Message generated by public network serving the local user) 1002 Private Network (1 - Message generated by private network serving the local user) ClientView Pane Reference Transit network (3 - Message generated by transit network) Remote private network (5 - Message generated by private network serving the remote user) Remote public network (4 - Message generated by public network serving the remote user) International network (7 - Message generated by international network) Network Beyond Interworking Point (0A - Message generated by network beyond inter-working point.) Exchange Type Type A The IMG does not send any messages at start-up, but responds to a GRS with a GRA, or an RSC with an RLC. Type B The IMG sends a GRS/RSC at start-up. The IMG waits for a remote GRA/RLC before bringing the CICs in service. Message Compatibility Pass On This field specifies whether or not to pass unrecognized messages when they are received. On Off Network Indicator This field specifies whether the network indicator of ISUP messages sent is set to national or international. National (default for ANSI ISUP Variants) 01 - Spare International (default for non-ANSI ISUP Variants) 03 - Spare Suppress UCICs Enabled (default if the Network Indicator is set to International) Default (when upgrading from a pre-10.3.2 ER5 release, this field will be set to the default for the Network Indicator configured). Disabled (default if the Network Indicator is set to National) CFN Status 1003 IMG WebHelp Enabled (default) IMG will respond to an unknown message with CFN (Confusion Message). Disabled IMG will not respond to an unknown message with CFN (Confusion Message). Japanese MTP Variant When configuring Japan ISUP, this field selects the appropriate configuration for MTP depending on the variant you are using. JT TTC A/B Plane Bit Insertion and Validation Display Table This tables displays a list of the configured stacks on a physical IMG. JT-ISUP The IMG supports JT-ISUP, the SS7 standard for Japan (JT-Q.763). You select this variant in the ISUP field of the SS7 Stack pane. If you select JT-ISUP you also select an MTP variant in the Japanese MTP Variant field. Differences from other ISUP version Point code format is 7-4-5 Unique CIC mapping scheme (see JT ISUP CIC Mapping) Manual COT test not supported Troubleshooting Check for Point Code Mismatch Make sure Distant End Gateway supports JT-ISUP JT ISUP CIC Mapping Timeslot E1 CIC T1 CIC 0 Frame Alignment 0 1 0 6 2 6 12 3 12 18 1004 ClientView Pane Reference 4 18 1 5 24 7 6 1 13 7 7 19 8 13 2 9 19 8 10 25 14 11 2 20 12 8 3 13 14 9 14 20 15 15 26 21 16 Not Used 4 17 3 10 18 9 16 19 15 22 20 21 5 21 27 11 22 4 17 23 10 23 24 16 25 22 26 28 27 5 28 11 29 17 30 23 31 29 N/A Cantata Technology - IMG 1010 Printable WebHelp 1005 IMG WebHelp T1 Physical Span Topic Location: ClientView Pane Reference Overview Description This object specifies the physical format of a T1 logical span. The user will be allowed to configure a T1 span, if the IMG 1010 is configured for T1 via the host flags. Related Topics Configuring a T1 or E1 Bearer Span Accessing this Pane Cantata IMG EMS-> Logical IMG-> Physical IMG-> facility -> TDM DS1 (of type T1) > T1 Physical Span Maximum T1 Physical Span Objects: 1 per TDM DS1 object Technical Notes Pane Field Descriptions Loop Timing Type Specifies whether that specific span is used for primary loop timing, secondary loop timing or not. Primary Not Timing Source Secondary Framing 1006 ClientView Pane Reference Specifies whether the framing of the span is ESF or D4. ESF D4 Signaling Clear Channel Line Length Specifies the length of the T1 line: 0-133 ft 167-299 ft 134-166 ft 300-533 ft 534-655 ft NOTE: In SNMP, the first value in the range is returned, in meters, as shown below: 0-133 ft = 0 134-166 ft = 41 167-299 ft = 51 300-533 ft = 91 534-655 ft = 163 Line Coding Specifies the line coding of T1 span. Bit 7 zero suppressing NOTE: For T1 SS7 links with line coding configured for B7ZS, only the 48 Kbps data rates (configured in the SS7 Link pane) are valid. B8ZS zero suppressing Loopback Mode Bearer or Signaling DS1’s can be configured for local or remote loopback. Each span offset must be individually configured. No Loopback Remote Loopback Local Loopback 1007 IMG WebHelp NOTE: When you place a span in loopback mode the Span Status will indicate Out Of Service. Following the test you must manually put the span back in service by selecting the In Service button. See Loopback Testing for more information. Monitoring Fields Span Status This monitoring field indicates the current status of the E1 span. Button Descriptions In Service This button brings the T1 span in service. NOTE: You must manually bring a span back in service following a loopback test. Out Of Service This spans takes the T1 span out of service. Cantata Technology - IMG 1010 Printable WebHelp 1008 ClientView Pane Reference TDM DS1 Topic Location: ClientView Pane Reference Overview Description Use this pane to configure a T1 or E1 span. Related Topics Configuring a T1 or E1 Bearer Span Accessing this Pane Cantata IMG EMS-> Logical IMG-> Physical IMG-> Facility -> New TDM DS1 Maximum Objects: T1 - 32 / E1 - 24 per Physical IMG Pane Field Descriptions Trunk Type This field is automatically populated with T1 or E1 based on the type of IMG you have. Component ID This field specifies whether the TDM DS1 is a signaling span or bearer span. Signaling Bearer Interface ID This field is automatically populated with the next number in sequence. Comments Add comments as you desire. Cantata Technology - IMG 1010 Printable WebHelp 1009 IMG WebHelp TDM DS3 Topic Location: ClientView Pane Reference Overview Description Use this pane to configure a DS3 Interface. Related Topics Configuring a Single DS3 Span Configuring a Range of DS3 Spans DS3 Diagnostics Accessing this Pane Cantata IMG EMS -> Logical IMG -> Physical IMG -> Facility -> TDM DS3 Maximum Objects: 1 per Physical IMG Pane Field Descriptions DS3 Framing Type MI3 CBIT (default) Component ID Bearer Interface ID Line Length 1010 0-225 ft ClientView Pane Reference 226-450 ft ___________________________________________________________________ _____________________________________________ The following fields relate to DS3 Loopback. See DS3 Diagnostics for more information. DS3 and DS1 FEAC Responses Enabling this option allows loop-back to be configured from the “far-end” equipment connected on the other end of the line. Enable Disable There is a specific FEAC code to request ALL DS1's be put in loopback. There are also specific FEAC codes for each span offset. Therefore, you can request that the far end put all DS1's in loopback (you do not send 27 FEAC codes, just one, the ALL DS1's code). If you want to request that just one DS1 offset (for example offset 14) be put in loopback then you send the code value that corresponds to offset 14. DS3 Loopback Mode No Loopback Remote Loopback (CBIT Only) Local Loopback All DS1s Loopback Mode Following the request to put DS1 offset 14 in loopback, you CANNOT make another request for loopback on another span without first taking span 14 out of loopback. No Loopback Remote Loopback (CBIT Only) Local Loopback ___________________________________________________________________ _____________________________________________ Monitoring Fields DS3 Status FEBE Count Cantata Technology - IMG 1010 Printable WebHelp 1011 IMG WebHelp Telnet Client Topic Location: ClientView Pane Reference Overview Description Use this pane to enable/disable access a Telnet Client or to verify the telnet status. Related Topics Using Telnet Accessing this Pane Cantata IMG EMS-> Logical IMG-> Physical IMG-> Telnet Client Maximum Objects: 1 per Physical IMG Technical Notes Pane Field Descriptions Telnet Client This field sets the Telnet Client to Enable or Disable. Monitoring Fields Telnet Connection Status This field is informational only. Remote IP Address This field is informational only. Cantata Technology - IMG 1010 Printable WebHelp 1012 ClientView Pane Reference Time of Day Entry Topic Location: ClientView Pane Reference Overview Description Use this pane to create an entry in a Time of Day routing table. Related Topics Configuring Time of Day Routing Accessing this Pane Cantata IMG EMS-> Routing Configuration-> Time of Day Tables-> Time of Day Table -> Time of Day Entry Maximum Objects: 5,000 per Time of Day table Pane Field Descriptions Entry ID Automatically populated with next available number. Enable Enable or Disable this table. Route List 1013 IMG WebHelp The route list this table will use. Reoccuring One Time Every Week Day Every Day Weekly Monthly Yearly Start Date The day this table will take effect. Start Time The time this table will take effect. When you click in the filed the 24-Hour Clock pop-up appears. Use the radio buttons to select the desired time. End Date The day this table will no longer be in effect. End Time The time this table will no longer be in effect. When you click in the filed the 24-Hour Clock pop-up appears. Use the radio buttons to select the desired time. Days of the Week Which days this table will take effect. When you click on this field, the Day of the Week pop-up appears. Type of Monthly This field only applies when the Reoccuring field is set to Monthly. day of the month This field only applies when the Reoccuring field is set to Monthly. day type Cantata Technology - IMG 1010 Printable WebHelp 1014 ClientView Pane Reference Time of Day Table Topic Location: ClientView Pane Reference Overview Description Use this pane to create a Time of Day routing table. NOTE: If you set IMGs to local time and a Time of Day table is used across multiple IMGs, each IMG will use its own local time. See Setting Local Time for more information. Related Topics Configuring Time of Day Routing Accessing this Pane Cantata IMG EMS-> Routing Configuration-> Time of Day Tables-> Time of Day Table Maximum Objects: 66 Total Route/Cause Code/Time of Day Tables per EMS Pane Field Descriptions Name A unique name for this table. ID Automatically populated with next available number. Default Route List Indicates the route list to use if there is no time of day match. Display Table Description of why the panel is used. 1015 IMG WebHelp Cantata Technology - IMG 1010 Printable WebHelp 1016 ClientView Pane Reference Time of Day Tables Topic Location: ClientView Pane Reference Overview Description This is a container object for Time of Day tables. You must create this before you can create Time of Day tables. After you create this object, right-click Time of Day Tables and select New Time of Day Table. Related Topics Configuring Time of Day Routing Accessing this Pane Cantata IMG EMS-> Routing Configuration-> Time of Day Tables Cantata Technology - IMG 1010 Printable WebHelp 1017 IMG WebHelp Time Zone Setting Topic Location: ClientView Pane Reference Overview Description Use this pane to set the system time on a physical IMG to the local time. By default the IMG uses Greenwich Mean Time. To configure RADIUS to use local time, use the RADIUS Time Format field in the RADIUS Client pane. Related Topics Setting Local Time Accessing this Pane Cantata IMG EMS -> Logical IMG -> Physical IMG -> New UTC Offset Maximum Objects: 1 per Physical IMG Pane Field Descriptions offset from UTC time Select the local time represented as Universal Time (UTC) plus or minus in 30 second increments. Cantata Technology - IMG 1010 Printable WebHelp 1018 ClientView Pane Reference Timing Synchronization Priority List Topic Location: ClientView Pane Reference Overview Description This object defines the timing sources for a specific physical IMG and the priority of these sources. Related Topics About Synchronization Priority Lists Configuring a Synchronization Priority List Accessing this Pane Cantata IMG EMS-> Logical IMG-> Physical IMG -> Timing Sync Priority List Maximum Objects: 1 per Physical IMG. Technical Notes Pane Field Descriptions For each field, select one of the following: Primary Reference Primary Loop Secondary Reference Secondary Loop Free Running Cantata Technology - IMG 1010 Printable WebHelp 1019 IMG WebHelp TMR-USI Override Topic Location: ClientView Pane Reference Overview Description This pane sets Transmission Medium Requirements (TMR) and User Service Indicator (USI) parameters for an SS7 ISUP Group. Related Topics Configuring TMR-USI Override Accessing this Pane Cantata IMG EMS -> Routing Configuration -> Channel Groups-> Channel Group (SS7) -> ISUP Group -> TMR-USI Override Maximum Objects: 1 per ISUP Group Pane Field Descriptions Transmission Medium Requirement Override Speech 3.1 kHz audio 64 kbit/s unrestricted Alternate Speech Alternate 64kbit/s unrestricted 2x64kbit/s unrestricted 384kbit/s unrestricted Ignore (default) Coding Standard 1020 ITU-T standardized ISO/IEC Standard ClientView Pane Reference National standard Ignore (default) Standard for Network Side of Interface Information Transfer Capability Speech Restricted Digital Info Unrestricted Digital Info 3.1 kHz audio Unrestricted Digital with tones/announcements Video Ignore (default) Transfer Mode Circuit Mode Ignore (default) Packet Mode Transfer Data Type G.711 u-law G.721 G.711 A-law H.221 or 242 H.223 or 245 Ignore (default) Cantata Technology - IMG 1010 Printable WebHelp 1021 IMG WebHelp TOS Configuration Topic Location: ClientView Pane Reference Overview Description Use this pane to configure Type of Service (TOS) parameters for an IP Profile. Related Topics Configuring Type of Service Accessing this Pane Cantata IMG EMS-> IP Bearer Profiles-> IP Bearer Profile-> TOS Configuration Maximum Objects: 1 per IP Bearer Profile Pane Field Descriptions Precedence Routine (default) Immediate 1022 Priority Flash Flash Override CRITIC/ECP Internetwork control Network control ClientView Pane Reference Delay Normal Delay (default) Low Delay Throughput Normal Throughput (default) High Throughput Reliability Cost Normal Reliability (default) High Reliability Normal Cost (default) Low Cost Cantata Technology - IMG 1010 Printable WebHelp 1023 IMG WebHelp Translation Entry Topic Location: ClientView Pane Reference Overview Description This pane adds an entry to an Incoming or Outgoing Translation Table. It defines the digit processing attributes that the IMG uses to process digit strings. Related Topics Digit Translation Configuring Digit Matching and Translation Accessing this Pane Cantata IMG EMS -> New Routing Configuration -> New Outgoing Translation Tables -> New Translation Table -> New Translation Entry Or: Cantata IMG EMS -> New Routing Configuration -> New Incoming Translation Tables -> New Translation Table -> New Translation Entry Maximum Objects: 200 Pane Incoming Translation Entry 1024 ClientView Pane Reference Outgoing Translation Entry Error Detection 1025 IMG WebHelp Field Descriptions Entry ID Automatically populated. Enable Indicates if the table entry is enabled (True) and available for use, or disabled (False). With this option, you can define an entry and then enable it at a later time, or you can enable the entry at different times. The default is Yes. True (Enabled) False (Disabled) Type of Operation The operation that the IMG performs for the current entry. Translation - Translate a matched digit string and/or associated call parameters to a different digit string and parameter values. Error Detection (only available for Incoming Translation) You can specify the cause code that the IMG associates with a dialed number or carrier number that represents an error condition. Translation Fields The following fields apply if the Type of Operation is Translation. 1026 ClientView Pane Reference Also see Error Detection Fields. String to Match The type of digit string that the IMG uses to match against the value in the String field. The options vary based on the type of operation you select in the Type of Operation field. The following values are available: Error Detection - identify a digit string that represents an error condition and to assign the appropriate cause code. Dialed Number Match the dialed number against the value in the String field. The dialed number is the called party number. Available when Operation is Translation and Error Detection. Originating Number Match the originating number against the value in the String field. The originating number is generally the calling party number. Available when Operation is Translation. String The digit string mask that the IMG compares to each incoming or outgoing number to determine whether the number is a match for the current Translation Table attributes entry. You can use the digits and wildcards. The values you enter in this field are processed as strings, not numbers, so enter the values accordingly. NOTE: The pound (#) character is generally used to terminate a digit string and the asterisk (*) character is generally used to trigger a service, such as *70 to disable call waiting. Internally, the IMG maps the asterisk (*) character to a value of hexadecimal E and the pound (#) character to hexadecimal F. This can result in improper digit processing if your digit strings contain hexadecimal E or F. See Digit Translation Wildcards. Match Channel Group as Well Use this option if you add a prefix to an incoming number. This criteria is added to the other criteria configured when matching is performed. Not Used A list of all the Channel Groups configured as Outgoing or Incoming/Outgoing (for Outgoing Translation Table) A list of all the Channel Groups configured as Incoming or Incoming/Outgoing (for Incoming Translation Table) Match Nature of Address as Well (Incoming Only) 000 - Reserved 1027 IMG WebHelp 001 - Subscriber Number 003 - National Number 002 - Unknown - National Use 004 - International Number 005 - Network Specific number 113 - Subscriber Number - Operator Requested 114 - National Number - Operator Requested 115 - International Number - Operator Requested 116 - No Number Present - Operator Requested 117 - No Number Present - Cut Through 118 - 905 Call 119 - Test Call Not Used Match “+” as well (Incoming Only) 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. SIP URI Header (Dialed Number Only) From Header (Originating Number Only) To Header (Dialed Number Only) Matching on Dialed Number If matching on Dialed Number, matching is allowed on either the “SIP URI Header” or the “To Header”. This is an “OR” condition if both are selected. Dialed # Translation The translation mask that describes how the Dialing Plan Engine (DPE) translates a dialed number to a new value. You can use the digits and wildcard. This field is available only when the Operation is Translation. This field can be left empty to translate to a null string. Originating # Translation The translation mask that describes how the Dialing Plan Engine (DPE) translates an originating number to a new value. You can use the digits and wildcard. This field is available only when the Operation is Translation. This field can be left empty to translate to a null string. ___________________________________________________________________ _______________________ 1028 ClientView Pane Reference These fields apply to the Pass through ‘+’ sign in the user part of URI feature. Append (+) for Headers Use this field to prefix ‘+’ to the user if the incoming INVITE does not have ‘+’. Select one or more headers to apply the "+" to. Remove (+) for Headers Use this field to remove a "+" from an incoming INVITE if you do not want it included in the outgoing INVITE. This can also be used in the case that the incoming side is not SIP. ___________________________________________________________________ _______________________ Dialed # Translation The translation mask that describes how the Dialing Plan Engine (DPE) translates a dialed number to a new value. You can use the digits and wildcard. This field is available only when the Operation is Translation. This field can be left empty to translate to a null string. Originating # Translation The translation mask that describes how the Dialing Plan Engine (DPE) translates an originating number to a new value. You can use the digits and wildcard. This field is 1029 IMG WebHelp available only when the Operation is Translation. This field can be left empty to translate to a null string. Billing Number Translation The value present will be included in the Charge Number parameter in case of an outgoing SS7 call (IAM message) using this translation table. To change the default attributes of the parameter, use the Advanced Billing Number Translation pane. Info Digits Translation Info Digits are included in the Originating Line Info Parameter (OLIP) in case of an outgoing SS7 call (IAM Message). See Advanced Translation Features. Carrier Number Translation The value present will be included in the Transient Network Selection (TNS) parameter in case of an outgoing SS7 call (IAM message) using this translation table. To change the default attributes of the parameter, use the Advanced Carrier Number Translation pane. Re-Run Option Valid if Type of Operation is Translation and String to Match is Dialed Number. None Originating Number If a call matches this entry, any defined translation will occur, and processing would jump to the Originating Number portion of the current translation table. Second String for Translation None INFO Digits (ANSI Variants Only) The info digits are included within the Originating Line Info Parameter (OLIP) that is received from the SS7 side. ANSI protocol variants require including the Charge Number parameter whenever the Originating Line Info Parameter is included in the IAM. The IMG can also match on the Info digits received within the ISUP MIME body included in a SIP message when SIP-T is enabled. Second String Enter characters to represent the Info Digits (valid characters J, K). 1030 ClientView Pane Reference The Info Digits may appear anywhere in the translation numbers, however if the same variable is repeated, ‘JJ’ or ‘KK’, the digits must appear together in the translation numbers. To identify and treat the Info Digits separately, they must be defined as ‘JK’ or ‘KJ’. NOTE: The Secondary String information is only for building the translation numbers; the IMG will not search based on them. Error Code Assign a cause code to a digit string for call treatment purposes (applies only if Type of Operation is Error Detection). The IMG performs the appropriate treatment for the call based on the cause code it assigns. Service Routing Select a previously configured Service Route entry to implement Pre-Call Announcements. See Configuring Pre-call Announcements and Route Entry pane. Error Detection Fields The following fields apply if the Type of Operation is Error Detection. String to Match The type of digit string that the IMG uses to match against the value in the String field. The options vary based on the type of operation you select in the Type of Operation field. The following values are available Dialed Number Match the dialed number against the value in the String field. The dialed number is the called party number. Available when Operation is Translation and Error Detection. Originating Number Match the originating number against the value in the String field. The originating number is generally the calling party number. Available when Operation is Translation. String The digit string mask that the IMG compares to each incoming or outgoing number to determine whether the number is a match for the current Translation Table attributes entry. You can use the digits and wildcards. The values you enter in this field are processed as strings, not numbers, so enter the values accordingly. NOTE: The pound (#) character is generally used to terminate a digit string and the asterisk (*) character is generally used to trigger a service, such as *70 to disable call waiting. Internally, the IMG maps the asterisk (*) character to a value of 1031 IMG WebHelp hexadecimal E and the pound (#) character to hexadecimal F. This can result in improper digit processing if your digit strings contain hexadecimal E or F. See Digit Translation Wildcards. Match “+” as well (Incoming Only) 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. SIP URI Header (Dialed Number Only) From Header (Originating Number Only) To Header (Dialed Number Only) Matching on Dialed Number If matching on Dialed Number, matching is allowed on either the “SIP URI Header” or the “To Header”. This is an “OR” condition if both are selected. ___________________________________________________________________ _______________________ These fields apply to the Pass through ‘+’ sign in the user part of URI feature. Append (+) for Headers Use this field to prefix ‘+’ to the user if the incoming INVITE does not have ‘+’. Select one or more headers to apply the "+" to. Remove (+) for Headers Use this field to remove a "+" from an incoming INVITE if you do not want it included in the outgoing INVITE. This can also be used in the case that the incoming side is not SIP. 1032 ClientView Pane Reference ___________________________________________________________________ _______________________ Error Code This field is used to indicate the Error Code if the Type of Operation is Error Detection. Service Routing Select a previously configured Service Route entry to implement Pre-Call Announcements. See Configuring Pre-call Announcements and Route Entry pane. Cantata Technology - IMG 1010 Printable WebHelp 1033 IMG WebHelp Translation Table Topic Location: ClientView Pane Reference Overview Description With this tab you create a new Incoming or Outgoing Translation Table by specifying a number and name that uniquely identify the table. From there you can add Table Entries. Related Topics Digit Translation Sort Order in Translation Tables and Routing Tables Sorting Criteria Entries are sorted by two criteria: 1. Highest to lowest 2. Shortest to longest For example: 888 887 8881111 5* 508 Related Topics Digit Translation Configuring Digit Matching and Translation Accessing this Pane Cantata IMG EMS -> New Routing Configuration -> New Incoming Translation Tables -> New Translation Table Or: Cantata IMG EMS -> New Routing Configuration -> New Outgoing Translation Tables -> New Translation Table Maximum Objects: 20 per EMS - total Incoming and Outgoing 1034 ClientView Pane Reference Pane Field Descriptions Translation Table Id The IMG automatically assigns a unique number to a new table. If necessary, you can override this number by selecting an unused number from 1 to 20. Translation Table Name A descriptive name for the table. Buttons Save Translation Table This button sends the translation table to all the IMGs that are controlled by this GC EMS. Delete All Translation Entries Deletes all entries in the translation table as well as any child objects of the table (Advanced Billing Parameters, Advanced Dialed Number Parameters, Advanced Originating Number Parameters, Advance Carrier Number Parameters), as long as the table is not currently assigned to any Channel Groups. When you click the button, a confirmation box will appear. Click Yes to proceed. If the table is assigned to a channel group, an error message will appear. Otherwise, the entries will be deleted. The entries will remain showing in the pane until you select another object. Cantata Technology - IMG 1010 Printable WebHelp 1035 IMG WebHelp Treatment Entry Topic Location: ClientView Pane Reference Overview Description This pane is used to add an entry to a Treatment Table. Related Topics Adding Entries to a Treatment Table Accessing this Pane Cantata IMG EMS-> Routing Configuration-> New Treatment Tables-> New Treatment Table -> New Treatment Entry Maximum Objects: 256 per Translation Table Pane Field Descriptions Treatment Entry Id This field is automatically populated with the next available number. Treatment Description A name to identify the entry. Cycles to Play Treatment 1-3 1036 Cantata Technology - IMG 1010 Printable WebHelp ClientView Pane Reference Treatment Phrase Topic Location: ClientView Pane Reference Overview Description This pane adds a phrase to a Treatment Table Entry. You can add multiple phrases (which can be announcements, tones, originating/dialed digits) to create a single entry. Related Topics Adding Phrases to a Treatment Table Entry Accessing this Pane Cantata IMG EMS-> Routing Configuration-> New Treatment Tables-> New Treatment Table -> New Treatment Entry -> New Treatment Phrase Maximum Objects: 15 per Treatment Table Pane Field Descriptions Partial Phrase Entry This field is automatically populated with the next number in sequence. Partial Phrase Type Announcement Originating Digits Dialed Digits Tone Partial Phrase Id If Phrase Type is Announcement: 1037 IMG WebHelp Select from the list of announcements, populated from the Vocabulary Index File entries. If Phrase Type is Tone, select from the list of tones: Busy Reorder Warning Intercept Vacant Code Reorder (LEC) No Circuit (LEC) Reorder (Carrier) No Circuit (Carrier) If Phrase Type is Dialed Digits or Originating Digits the field is automatically populated. Cycles to Play Tone This field only applies if the Phrase Type is Tone. Select the desired number of cycles, up to 15. Continuous 1-15 Cantata Technology - IMG 1010 Printable WebHelp 1038 ClientView Pane Reference Treatment Table Topic Location: ClientView Pane Reference Overview Description This pane is used to create a new Treatment Table. Related Topics Creating a Treatment Table Accessing this Pane Cantata IMG EMS-> Routing Configuration-> New Treatment Tables-> New Treatment Table. Maximum Objects: 6 (in addition to the default table) Pane Field Descriptions Treatment Table Id This field is automatically populated with the next number in sequence. Treatment Table Name A descriptive name for the table. Cantata Technology - IMG 1010 Printable WebHelp 1039 IMG WebHelp Treatment Tables Topic Location: ClientView Pane Reference Overview Description This pane is a container for creating new Treatment Tables. Related Topics An Overview of Error Handling Configuring Error Handling Configuring a Channel to Play Treatment Adding Custom Treatments Creating a Treatment Table Accessing this Pane Cantata IMG EMS-> Routing Configuration-> New Treatment Tables Maximum Objects: 1 Cantata Technology - IMG 1010 Printable WebHelp 1040 ClientView Pane Reference Variant Entry Topic Location: ClientView Pane Reference Overview Description This pane is used to customize an SS7 or CAS signaling variant. NOTE: Once a custom variant is assigned to an SS7 stack, you cannot modify or delete an existing entry in the variant. NOTE: If a CAS variant with a custom entry is assigned to a channel group, the variant cannot be deleted. Previous Configuration Required Signaling Variant Next Configuration Tasks (CAS) Digit Mapping Filter/Timer Configure Inpulsing Parameters Inseize Instruction Outseize Instruction Related Topics Configuring CAS Creating Custom SS7 Variants Accessing this Pane Cantata IMG EMS -> Signaling Variants -> Signaling Variant -> Variant Entry Pane Field Descriptions Base Variant 1041 IMG WebHelp This field indicates the base variant to be used. It is automatically populated based on the value in the Signaling Variant this entry is being added to. PPL Component ID The PPL component to be configured. SS7 CAS 0x01 E1 PPL Component 0x03 T1 PPL Component PPL Entity Type The PPL Entity to be configured. PPL Tables PPL Config Bytes PPL Entity ID The PPL Entity ID to be configured. 1-1000 For PPL table, the Entity ID is set by the Variant ID. + PPL Entity Value This field applies to PPL Config Bytes only. The Value for the Config Byte to be configured. PPL Entity File The PPL Entity File field is used to select the .cfg file containing the PPL configuration messages to download for that component. This field is available when the PPL Entity type selected is PPL Tables or when The PPL Component ID is 0xFF – Generic File. All the .cfg files should be in the path: /opt/cantata/IMG/config/Variant/”VariantName” on the Linux host. PPL Table When the Component ID is 0xFF – Generic File, the PPL Entity Type field controls at which point in the configuration the file set by the PPL Entity File field is sent to the node. The choices for the PPL Entity Type field are: 1042 Stack Link ClientView Pane Reference Route Destination Comments Use this field to add comments. Display Table This table shows a list of the configured Variant entries under the Signaling variant. Cantata Technology - IMG 1010 Printable WebHelp 1043 IMG WebHelp Vocabulary Index Entry Topic Location: ClientView Pane Reference Overview Description This pane is used to add announcement entries to a Vocabulary Index File. Related Procedure Configuring an NFS Server Vocab Index File Accessing this Pane Cantata IMG EMS-> Routing Configuration-> New Vocabulary Index Files-> New Vocabulary Index File -> New Vocabulary Index File Entry Maximum Objects: 1,024 per VIF Pane Field Descriptions File Id This field is automatically populated with the next available number. File Description Precise description of the file which will be sued to identify it in other panes. 1044 ClientView Pane Reference Primary Server Id The Primary NFS Server that the announcement is stored on. Secondary Server Id The Secondary NFS Server that the announcement is stored on. File Name The filename of the announcement. File Format Raw Data Format Wav Format File Encoding G711 Alaw G726 32 Kbps ADPCM G711 ulaw 32 Kbps OKI ADPCM 24 Kbps OKI ADPCM 16 bit linear (11025 Khz mono) 8 bit linear (11025 Khz mono) Start Offset for File File Length to be played Cantata Technology - IMG 1010 Printable WebHelp 1045 IMG WebHelp Vocabulary Index File Topic Location: ClientView Pane Reference Overview Description This pane creates a new Vocabulary Index File, which is used to identify announcements stored on the NFS server and used in the playing of treatments. Related Topics Configuring an NFS Server Accessing this Pane Cantata IMG EMS-> Routing Configuration-> New Vocabulary Index Files-> New Vocabulary Index File Maximum Objects: 1 per EMS Pane Field Descriptions Vocabulary Index File Id This field is automatically populated with the next available number. Vocabulary Index Filename This field is automatically populated (img_vocab.dat). Cantata Technology - IMG 1010 Printable WebHelp 1046 ClientView Pane Reference Vocabulary Index Files Topic Location: ClientView Pane Reference Overview Description This pane is a container for individual Vocabulary Index Files you create. Related Procedure Configuring an NFS Server Vocab Index File Accessing this Dialog Box Cantata IMG EMS-> Routing Configuration-> New Vocabulary Index Files Maximum Objects: 1 Cantata Technology - IMG 1010 Printable WebHelp 1047 IMG WebHelp Vocoder Entry Topic Location: ClientView Pane Reference Overview Description This pane specifies a single payload type and size for use by the IP Bearer Profile. Multiple Supported Vocoder objects may be specified for each IP Bearer Profile. The collection of these objects is sent in a prioritized order during IP signaling (SIP/H.323) negotiation. Related Topics VoIP Overview Configuring IP Bearer Profiles Accessing this Pane Cantata IMG EMS-> IP Bearer Profiles-> IP Bearer Profile-> Supported Vocoders Maximum Objects: 7 per IP Bearer Profile Technical Notes Pane Field Descriptions Entry ID This field specifies the ID of the vocoder. Note: This field does not control the priority in the Terminal Capability Exchange. The priority is controlled by the order in the Supported Vocoder Display Table. Payload Type This field specifies the desired codec for the Vocoder entry. 1048 AMR (SIP Only) EVCR (SIP Only) ClientView Pane Reference G.711 alaw G.723 5.3 Kbps G.711 u-law G.723 6.3 Kbps G.729 G.729E/G (SIP Only) (10.3.2 ER 2 or above) iLBC (SIP Only) IMPORTANT NOTE: You must have your Host Flags set correctly to enable certain vocoders. Additionally, you must have a valid license for AMR and iLBC. See Setting Host Flags. Preferred Payload Size (ms) This field specifies the desired payload size for the selected Payload Type. Defaults AMR = 20 EVRC = 20 G.711 alaw = 20 G.723 (5.3/6.3) = 30 G.729 = 20 G.729E/G = iLBC = 20 Minimum Payload Size (ms) This field specifies the minimum payload size for the selected Payload Type. Defaults AMR = 20 EVRC = 20 G.711 alaw = 10 G.723 (5.3/6.3) = 30 G.729 = 10 iLBC = 20 Maximum Payload Size (ms) This field specifies the maximum payload size for the selected Payload Type. Defaults 1049 IMG WebHelp AMR = 20 EVRC = 20 G.711 (alaw/u-law) = 30 G.723 (5.3/6.3) = 60 G.729 = 60 iLBC = 30 Default Payload Type Applies only to AMR, EVRC, and iLBC. Defaults AMR = 97 EVRC = 98 iLBC = 96 Annex B Support Yes The media attribute "Annexb=no" is sent by the IMG in the SIP SDP, when enforcing the use of the G.729a payload type. 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. No (default for G.729 and G.729E codecs) Not Used (default for non- G.729 and G.729E codecs) Display Table This table lists the Supported Vocoders to be used in the H.245 Terminal Capability Exchange for IP Bearer Profile (parent) object. The entries are listed in descending priority. You can change the order using the up and down buttons on the toolbar. Cantata Technology - IMG 1010 Printable WebHelp 1050 ClientView Pane Reference VoIP Module Topic Location: ClientView Pane Reference Overview Description Use this pane to configure the Voice over IP spans that carry RTP traffic. These spans correspond to the IP ports on the VoIP modules. Related Topics Configuring VoIP Determining VoIP Module Type Accessing this Pane Cantata IMG EMS -> Facility -> Bearer-IP Maximum Objects: 2 per Physical IMG Technical Notes Pane Field Descriptions Module ID This field identifies the ID of the VoIP module to be configured, 0 or 1. The user can find out the VoIP modules configured by looking into the physical IMG object. Network Interface The user has no control on this field. It automatically shows the name of the module being configured. VoIP Module 0: Port 0 VoIP Module 1: Port 0 Network IP address 1051 IMG WebHelp This field is automatically populated with the IP address configured for that VoIP module under the Network interfaces. If the user attempts to configure the VoIP module before configuring the Network Interface an error message will be displayed and the user will have to go back and configure the network interface first. Module Configuration Profile This informational field indicates the Codec Profile you have configured (in the BOOTP Host Flags). Any Vocoder Any Vocoder (4 Picasso) G711 Only G711 Only (4 Picasso) iLBC Profile (4 Picasso) Wireless Profile (4 Picasso) Starting RTP Port (10.3.2 ER2 and above) To change the default (8000), click on the field and enter a value in the Range Dialog, shown below. Value must be a multiple of 2. You can enter a value directly in the text box or use the sliding range at the top of the box. To change the value for an existing configuration you must delete the VoIP module object and then re-create it and change the port number. Fully Qualified Domain Name (FQDN) (10.3.3 ER2) The FQDN to be inserted in outgoing SIP messages when FDQN is enabled in the SIP Profile. See Fully Qualified Domain Name Support for more information. Monitoring Fields Number of Channels configured This field shows how many VoIP channels have been successfully configured. It varies depending on the Profile configured. The range of ports for Module 0 is 8000 9534, and on Module 1 is 11072 - 12604. 1052 ClientView Pane Reference Display Table This table displays the status of the IP address /port numbers corresponding to the configured VoIP channels. Cantata Technology - IMG 1010 Printable WebHelp 1053
