Avaya CCSS 1000/2000 Feature Documentation
Release 4.1 NN44100-129 Issue 1 August 2013 Notice protected by copyright and other intellectual property laws including the sui generis rights relating to the protection of databases. You may not While reasonable efforts have been made to ensure that the modify, copy, reproduce, republish, upload, post, transmit or distribute information in this document is complete and accurate at the time of in any way any content, in whole or in part, including any code and printing, Avaya assumes no liability for any errors. Avaya reserves the software unless expressly authorized by Avaya. Unauthorized right to make changes and corrections to the information in this reproduction, transmission, dissemination, storage, and or use without document without the obligation to notify any person or organization of the express written consent of Avaya can be a criminal, as well as a such changes. civil offense under the applicable law.
Documentation disclaimer Third-party components “Documentation” means information published by Avaya in varying Certain software programs or portions thereof included in the Product mediums which may include product information, operating instructions may contain software distributed under third party agreements (“Third and performance specifications that Avaya generally makes available Party Components”), which may contain terms that expand or limit to users of its products. Documentation does not include marketing rights to use certain portions of the Product (“Third Party Terms”). materials. Avaya shall not be responsible for any modifications, Information regarding distributed Linux OS source code (for those additions, or deletions to the original published version of Products that have distributed the Linux OS source code), and documentation unless such modifications, additions, or deletions were identifying the copyright holders of the Third Party Components and the performed by Avaya. End User agrees to indemnify and hold harmless Third Party Terms that apply to them is available on the Avaya Support Avaya, Avaya's agents, servants and employees against all claims, Web site: http://support.avaya.com/Copyright. lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation, Trademarks to the extent made by End User. The trademarks, logos and service marks (“Marks”) displayed in this Link disclaimer site, the Documentation and Product(s) provided by Avaya are the registered or unregistered Marks of Avaya, its affiliates, or other third Avaya is not responsible for the contents or reliability of any linked Web parties. Users are not permitted to use such Marks without prior written sites referenced within this site or documentation provided by Avaya. consent from Avaya or such third party which may own the Mark. Avaya is not responsible for the accuracy of any information, statement Nothing contained in this site, the Documentation and Product(s) or content provided on these sites and does not necessarily endorse should be construed as granting, by implication, estoppel, or otherwise, the products, services, or information described or offered within them. any license or right in and to the Marks without the express written Avaya does not guarantee that these links will work all the time and has permission of Avaya or the applicable third party. no control over the availability of the linked pages. Avaya is a registered trademark of Avaya Inc. Warranty Avaya provides a limited warranty on its Hardware and Software All non-Avaya trademarks are the property of their respective owners, (“Product(s)”). Refer to your sales agreement to establish the terms of and “Linux” is a registered trademark of Linus Torvalds. the limited warranty. In addition, Avaya’s standard warranty language, Downloading Documentation as well as information regarding support for this Product while under warranty is available to Avaya customers and other parties through the For the most current versions of Documentation, see the Avaya Avaya Support Web site: http://support.avaya.com. Please note that if Support Web site: http://support.avaya.com. you acquired the Product(s) from an authorized Avaya reseller outside of the United States and Canada, the warranty is provided to you by Contact Avaya Support said Avaya reseller and not by Avaya. See the Avaya Support Web site: http://support.avaya.com for product Licenses notices and articles, or to report a problem with your Avaya product. For a list of support telephone numbers and contact addresses, go to THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA the Avaya Support Web site: http://support.avaya.com, scroll to the WEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO/ ARE bottom of the page, and select Contact Avaya Support. APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AUTHORIZED AVAYA RESELLER (AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH AVAYA OR AN AUTHORIZED AVAYA RESELLER. UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN AVAYA AUTHORIZED RESELLER; AVAYA RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING OR SELLING THE SOFTWARE WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING, DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER REFERRED TO INTERCHANGEABLY AS “YOU” AND “END USER”), AGREE TO THESE TERMS AND CONDITIONS AND CREATE A BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE APPLICABLE AVAYA AFFILIATE (“AVAYA”).
Copyright Except where expressly stated otherwise, no use should be made of materials on this site, the Documentation, Software, or Hardware provided by Avaya. All content on this site, the documentation and the Product provided by Avaya including the selection, arrangement and design of the content is owned either by Avaya or its licensors and is
2 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Contents
Chapter 1: Introduction...... 13 Key Features...... 14 CCSS 1000...... 14 CCSS 2000...... 15 System Capacity...... 15 Signaling Link Physical Interface...... 15 T1/E1 Connectivity...... 16 Software Components...... 16 Architectural Overview (Simplex Configuration)...... 16 Architectural Overview (Fault Tolerant Configuration)...... 17 Software Architecture...... 18 Standards Compliance...... 20 Chapter 2: Installation...... 23 Hardware Installation and Configuration...... 23 System Cabling Diagrams...... 23 DCCSS7 Datalinks (Fault Tolerant Configuration)...... 23 SS7/C7 Server Software Installation...... 26 Removal of Previous Version...... 27 Installation...... 28 Change Protocol...... 31 CCSSALARM Version...... 31 Setting a netmask for PROXY...... 31 CCSS Monitoring by MPS Manager...... 32 CCSS Server Upgrade Procedures...... 32 Upgrading the Lone Server In A Standalone Configuration...... 32 Upgrading Both Servers In A Fault-Tolerant Configuration...... 33 Upgrading A Single Server In A Fault-Tolerant Configuration...... 34 Chapter 3: Configuration...... 35 Introduction to Configuration...... 35 Sample Configuration Files...... 36 ss7.conf.sample...... 36 ss7.conf.sample.alink...... 37 ss7.conf.sample.tcap...... 38 Configuration Commands...... 39 Data Link Configuration...... 65 DCC3K Data Link Configuration...... 65 DCCSS7 Ethernet connections...... 66 TMS Configuration Through MPS Manager...... 68 SS7/C7 Network Configuration...... 71 MTP3 Layer 3 Configuration...... 71 Own Signaling Point...... 71 Linksets and Links...... 71 Combined Linksets...... 72 Routes...... 72
Avaya CCSS 1000/2000 Feature Documentation August 2013 3 F-Link Configuration Examples...... 73 A-Link Configuration Examples...... 74 Sequential SLS based load sharing across linksets...... 74 Linkset Redundancy between TMSs...... 77 F-link Configuration...... 77 A-link Configuration...... 78 F-Link Configuration...... 80 F-Link Configuration Examples...... 81 A-Link Configuration Examples...... 81 ISUP Configuration...... 84 ISUP Nodes...... 85 ISUP Circuit Groups...... 85 ISUP Circuits...... 85 Mixed Mode System Configuration...... 86 Modify Commands...... 86 ss7.conf Sample File...... 89 Changing the ISUP Variant...... 90 ISUP Call Control Modes of Operation...... 90 Call Control Configuration...... 90 Call Control Modes of Operation...... 90 Configuration Items...... 92 Proxy Mode Configuration Examples...... 92 Package Compatibility...... 92 Call Control Configuration for Proxy Mode...... 93 MPS Configuration For Proxy Mode...... 93 TCAPProxy Configuration...... 94 TMS Configuration...... 94 TMS Integrated Mode Configuration...... 94 Package Compatibility...... 94 CCSS Configuration...... 95 TMS Configuration...... 96 Hybrid Proxy Mode Configuration...... 96 Package Compatibility...... 96 CCSS Configuration...... 97 TMS Configuration...... 99 LineID Mode Configuration...... 99 Package Compatibility...... 99 CCSS Configuration...... 100 MPS Configuration for LineID Mode...... 101 TMS Configuration...... 101 Fault Tolerant Configuration...... 101 SCCP/TCAP Configuration...... 103 SCCP Layer Configuration...... 103 Application Context Group Configuration...... 106 Multiple Application Contexts Configuration...... 107 TCAP Layer...... 107 TCU Timer Configuration...... 109
4 Avaya CCSS 1000/2000 Feature Documentation August 2013 TCU Option Configuration...... 109 Suppress Subsystem Test...... 110 Call Protect...... 111 Integration of MPS N+1 Redundancy and Call Protect...... 111 Call Protect CCSS SS7 Configuration...... 112 CCSS System Limits...... 113 Chapter 4: CCSS Commands...... 115 MGMTUI...... 115 Report Commands...... 117 Control Commands...... 123 Statistics Commands...... 126 Trace Commands...... 127 UI...... 131 TCU User Interface (TCUUI) Commands...... 141 Chapter 5: Operations, Administration, and Maintenance...... 151 System Startup Procedures...... 151 System Shutdown Procedures...... 152 CCSS Shutdown from mgmtui...... 153 Backup and Restore...... 154 Backup Devices and Options...... 154 Backup Methods...... 155 Backing up with the tar Utility...... 155 Displaying the Contents of a tar Backup...... 156 Restoring with the tar Utility...... 156 Backing up to a Secondary Drive...... 156 Restoring Entire Drive Using tar Utility...... 159 Individual Directory Backup Using tar...... 159 Restoring the Directories using tar...... 160 Backing up with cp (Copy)...... 160 Backup Tips...... 161 SS7/C7 Server Backup...... 161 SS7/C7 Server Restore...... 161 System Status and Statistics...... 162 Call Control Statistics...... 162 Reset Call Control Statistics...... 164 Redundancy Status...... 164 MPS Resource Daemon (proxy) Command Summary...... 165 Proxy Debug...... 166 Diagnostics and Troubleshooting...... 169 User Interface to the Call Control Process...... 169 SS7/C7 Process Logging Messages...... 172 Service Affecting Commands...... 174 Chapter 6: ISUP Application Programming...... 177 Application Setup - Resource Allocation...... 177 Condition Mode...... 178 Network Message Exchange...... 179 Sending Messages...... 181
Avaya CCSS 1000/2000 Feature Documentation August 2013 5 Receiving Messages...... 182 Voice Path Connection...... 183 Receiving an Incoming Call (Receive Resource Mode)...... 184 Incoming Call Message Exchange...... 185 Originating an Outbound Call (Receive Resource Mode)...... 187 Receiving an Incoming Call (Condition Mode)...... 190 Handle the ccs7cc and vrto condition...... 191 Incoming Call Message Exchange...... 192 Originating an Outbound Call (Condition Mode)...... 193 Interworking With a non-SS7/C7 Server (Condition Mode)...... 195 During the Call...... 197 Call Progress Detection...... 197 Call Teardown (Application Initiated)...... 197 Call Teardown (Network Initiated)...... 198 Performing a Referral...... 200 Application Procedure...... 200 Application Message Exchange...... 201 Application Referral Hunt Groups...... 203 Using Call Progress Detection With Referral...... 205 Application Message Exchange...... 206 Release Link Trunk (RLT)...... 206 Single Port RLT...... 206 Dual Port RLT...... 207 RLT Applications...... 207 Message Sequence Diagrams...... 208 Single Port RLT - Success...... 208 Single Port RLT - Failure...... 209 Single Port with Pullback...... 210 Single FAR Dual Port RLT...... 211 Multiple FAR Dual Port RLT...... 212 ISDN User Part (ISUP) Message Data Items...... 212 Backward Compatibility...... 213 Data Items...... 214 Initial Address Message...... 214 Nature of Connection Indicators...... 214 Forward Call Indicators...... 215 Calling Party Category...... 217 Transmission Medium Requirement...... 217 Called Party Number...... 218 Calling Party Number...... 219 Redirecting Number...... 221 Redirection Information...... 222 Original Called Number...... 223 End of Optional Parameters...... 225 Extended Address Message...... 225 IAMX Parameters...... 225 Extended Option 4 and 5...... 226
6 Avaya CCSS 1000/2000 Feature Documentation August 2013 Extended Option 6 and 7...... 226 Forward Call Indicators...... 227 Generic Number...... 227 Optional Forward Call Indicators...... 229 User Service Info...... 230 Location Number...... 233 Jurisdiction Info...... 235 Carrier ID...... 235 Charge Number...... 235 Originating Line Info...... 236 SCF ID...... 236 Correlation ID...... 237 Access Transport Parameter...... 237 Call Reference...... 237 Closed User Group Interlock Code...... 237 Additional Parameters...... 238 Address Complete...... 238 Backward Call Indicator...... 238 Optional Backward Call Indicators...... 240 End of Optional Parameters...... 241 Extended Address Complete Message...... 241 Extended Option 2...... 241 ACMX Parameters...... 241 Extended Option 6 and 7...... 242 Call Reference...... 242 Call Diversion Information...... 243 Redirection Number...... 243 Cause Indicator...... 244 Access Delivery Information...... 245 Generic Notification Indicator...... 245 Answer...... 246 Backward Call Indicator...... 246 Optional Backward Call Indicators...... 248 End of Optional Parameters...... 249 Extended Answer...... 249 Extended Option 1...... 249 ANMX Parameters...... 250 Extended Option 2...... 250 Connected Number...... 250 Additional Parameters...... 252 End of Optional Parameters...... 252 Call Progress...... 252 Event Information...... 253 Backward Call Indicator...... 253 Optional Backward Call Indicators...... 256 End of Optional Parameters...... 256 Extended Call Progress...... 256
Avaya CCSS 1000/2000 Feature Documentation August 2013 7 Extended Option 2...... 257 Extended Option 4...... 257 Extended Option 5...... 257 Cause Indicator...... 258 Call Diversion Information...... 258 Redirection Number...... 259 Generic Notification Indicator...... 260 Additional Parameters...... 261 Connect...... 261 Backward Call Indicator...... 261 Optional Backward Call Indicators...... 264 End of Optional Parameters...... 264 Extended Connect...... 265 Extended Option 2...... 265 Additional Parameters...... 265 Information...... 265 Information Indicators...... 266 Calling Party Category...... 267 Calling Party Number...... 267 End of Optional Parameters...... 269 Information Request...... 270 Information Request Indicators...... 270 End of Optional Parameters...... 271 Cause Diagnostics...... 271 Release...... 271 Cause Indicators...... 272 End of Optional Parameters...... 275 Extended Release...... 276 Extended Option 1...... 276 Extended Option 2...... 276 Extended Option 4...... 277 Extended Option 5...... 277 Extended Option 8...... 278 Called Party Number...... 278 Signaling Point Code...... 280 Automatic Congestion Level...... 280 Redirection Number...... 280 Redirection Information...... 281 Release Complete...... 282 Cause Indicators...... 283 User to User Information...... 286 Access Transport Parameter...... 287 Continuity Message...... 287 Continuity Indicators...... 287 Continuity Check Request...... 288 Continuity Processing (Proxy Mode)...... 288 Inbound Continuity Processing...... 289
8 Avaya CCSS 1000/2000 Feature Documentation August 2013 Outbound Continuity Processing...... 289 Facility Request...... 290 Facility Indicator...... 290 Called Party Number...... 290 Subsequent Number...... 291 Call Reference...... 292 Signalling Point Code...... 292 User to User Information...... 292 Facility Accept...... 293 Facility Indicator...... 293 Facility Reject...... 293 Facility Indicator...... 293 Cause Indicators...... 293 Cause Diagnostic...... 295 Additional Parameters...... 295 Decoding/Encoding...... 296 Remove...... 298 Printing a Network Message...... 299 Sample Call Functions...... 300 ISUP Application Programming using the SS7 Toolkit...... 301 Dynamic Provisioning of Extended Mode...... 301 Dynamic Provisioning of Extended Mode in PROXY Mode...... 301 Chapter 7: ISUP Programming in TMS Integrated Mode for MPS...... 303 ISUP Application Programming Using the SS7 Toolkit...... 304 SS7 Toolkit...... 304 SS7 Toolkit Blocks...... 304 SS7 Toolkit Folders...... 305 ISUP Protocol Folders...... 305 ISUP Parameter Value Specification in TMS Integrated Mode...... 306 Message Types...... 307 Starting ISUP Applications...... 307 Application Flow...... 308 Outbound ISUP Call...... 308 Call Origination...... 309 Originate Block...... 312 Sending UUI message...... 312 Releasing a Call...... 313 Inbound ISUP Call...... 314 Call Reception...... 315 Releasing a Call...... 317 Sample TMS Integrated mode applications...... 319 Installation Procedure for SS7 Toolkit...... 319 Performing Referral in TMS mode...... 320 Sample Referral Application for TMS mode...... 324 CCSS Configuration for TMS integrated Mode...... 324 Configurable Default ISUP Parameter Values...... 325 Chapter 8: ISUP Programming in LineID Mode...... 327
Avaya CCSS 1000/2000 Feature Documentation August 2013 9 ISUP Application Programming in LineID Mode (MPS Mode)...... 327 MPSMODE Parameters...... 328 Bind and Unbind...... 328 Acquiring the CCSS Resource in LineID Mode...... 329 Folder Structure...... 329 Send Resource...... 329 Message Types...... 329 Application Flow...... 330 Get CCSS Resource...... 330 Check Call Protect...... 331 Binding the LineID...... 332 Call Protect Outbound...... 332 Call Protect Inbound...... 334 Releasing the Call...... 334 Data Items...... 335 Chapter 9: TCAP Application Programming...... 337 System Overview and Architecture...... 337 SCCP...... 338 Functionality...... 338 Routing and Addressing...... 339 TCAP...... 340 Functionality...... 340 TCAP USER...... 341 Dialog Management...... 341 Resource Operations...... 342 Application Setup - Resource Allocation...... 342 Application Termination- Resource Deallocation...... 343 Sending TCAP Messages...... 343 Receiving TCAP Messages...... 344 Message Flow Diagrams...... 345 ISSUE GET Succeeds...... 345 ISSUE GET Fails...... 346 Dialog Initiated By The Application...... 347 Dialog Initiated By The Network...... 348 Application Free During Dialog...... 349 Proxy/TCAP Resource...... 350 MPS Developer Interface...... 350 Issue Get...... 351 TCAP Folders...... 351 Mode Folder...... 351 Transaction/Component Message Header...... 353 Transaction Type Message Folder...... 355 Component Type Message Folder...... 360 Notice Message folder...... 364 Application State Machine Transition Diagram...... 366 TCU Dialogue State Transition Diagram...... 367 Appendix A: Application Bridging Techniques...... 369
10 Avaya CCSS 1000/2000 Feature Documentation August 2013 Interprocess Communications...... 369 PLM Copy for Continuity Handling...... 370 Appendix B: Configuration Information Worksheets...... 375 Network Information...... 375 Circuit Group Information...... 375 Appendix C: CCSS Configuration Files...... 377 The ss7.conf File (Proxy Mode)...... 377 Sample ss7.conf File for TMS Integrated Mode...... 379 TMS Configuration File...... 380 Appendix D: Alarms...... 381 CCME Alarms...... 381 MGMT Alarms...... 399 ISUP Alarms...... 418 MTP3 Alarms...... 422 MTP2 Alarms...... 426 MTP1 Alarms...... 431 SCCP Alarms...... 433 TCAP Alarms...... 434 TCU Alarms...... 436 PERM Alarms...... 443 Agent Alarms...... 447 Router Alarms...... 448 Manager Alarms...... 448 PSF-MTP3 Alarms...... 450 PSF-ISUP Alarms...... 450 VO (DCC3K) Alarms...... 451 Appendix E: Advanced Installation, Configuration, and Testing...... 453 Hardware Installation and Configuration...... 453 DCCSS7 Cable connections...... 453 DCCSS7 Configuration...... 454 Hostname, Ethernet Addresses, BOOTPTAB Configuration...... 459 Configuring from the ccssinstall script...... 460 SS7/C7 Software Installation...... 460 FFT - Field Factory Test...... 462 FFT for DCCSS7...... 462 DCCSS7 Cable connections...... 463 ss7.conf.fft.a File...... 463 ss7.conf.fft.b File...... 464 tms.cfg Configuration File...... 464 Testing DCC Data Links...... 466 Restoring The FT...... 466 Appendix F: Fault Tolerance Terminology...... 469 Fault Tolerance...... 469 Controlled Switchover...... 469 Forced Switchover...... 469 Active Node...... 470 Standby Node...... 470
Avaya CCSS 1000/2000 Feature Documentation August 2013 11 PSF (Protocol Specific Function)...... 470 PSF Update...... 470 WarmStart...... 471 MGMT State Machine States...... 471 Initializing State...... 471 Configuration State...... 471 Shutdown State...... 471 Shutdown Maintenance State...... 472 Shutdown, Going Active State...... 472 Out-of-Service State...... 472 Out-of-Service Standby State...... 472 Out-of-Service, Going Active...... 473 Out-of-Service, Going Standby...... 473 Out-of-Service, Going Standby_2...... 473 Active, No Standby State...... 473 Active, With Standby State...... 474 Standby State...... 474 STATE_ACTIVE_STBY_GOING_DOWN...... 474 Out-of-Service, Shutting Down...... 474 Going Standby, CCME Warm-start in Progress...... 475 (STATE_GOING_STANDBY_CCME_WARMSTARTING)...... 475 Going Standby, CCME Warm-start Complete...... 475 (STATE_GOING_STANDBY_CCME_WARMSTARTED)...... 475 Active, Warm-start in Progress...... 475 (STATE_ACTIVE_STANDBY_WARMSTARTING)...... 475 Active, Warm-start Complete...... 476 (STATE_ACTIVE_STANDBY_WARMSTARTED)...... 476 Standby, Going Active...... 476 Going Active Controlled...... 476 Going Standby Controlled...... 476 STATE_GOING_OOS_STANDBY...... 477 STATE_GOING_STBY_FLOW_CTL...... 477 STATE_GOING_ACTV_FLOW_CTL...... 477 Server State Transitions...... 477 Tokens...... 478 Appendix G: CCSS Timers...... 481 CCME Timers...... 481 ISUP Timers...... 483 MTP3 Timers...... 485 MTP2 Timers...... 487 Appendix H: DCCSS7 Debugging Utility...... 489 The DCCSS7 Debugging Utility...... 489 Identifying DCCSS7 Cards...... 489 Starting an L2debug Session...... 490 The L2debug Menu...... 490 L2debug Menu Option Details...... 491 Index...... 501
12 Avaya CCSS 1000/2000 Feature Documentation August 2013 Chapter 1: Introduction
SS7 is an out-of-band signaling system used to exchange information between network switching elements. The Avaya MPS CCSS SS7 software provides an application with access to information that is contained within the signaling messages and can be used to implement highly adaptable and flexible application services. ISUP (ISDN User Part) is a common signaling protocol that defines the procedures for call setup, coordination, and tear-down of trunk calls on an SS7 network. ISUP provides information such as calling party number, called party number, trunk management, and coordination between originating and terminating switches. ISUP is a technology for switched network connections between subscriber line exchange terminations and ISUP provides the signaling functions required to support basic service and supplementary services that include calling line identification and call forwarding. Because this information is available to an application, a number of services can be implemented. The services include, but are not restricted to the following: • Applications can use the calling party or called party information to determine how the call should be handled (accepted, rejected, or forwarded). • The applications can be activated from the calling party or called party information. Activating the application in this manner provides access to different applications or different levels of service to the same application. Service Providers may also identify calls from frequent callers, problem callers, and so on. Identified calls can be routed for special handling. • Applications can use a Calling Card platform to access a card database • Televoting applications have a special requirement. The total call time including setup is typically less than five seconds. The application can use the called party number information to determine the nature of the vote. • Line Identification Database (LIDB) applications can use the information in the ISUP messages to access a database that could contain caller specific information. The Avaya Media Processing Server (MPS) can be used to obtain further information, such as a PIN number, before accessing the database and can either release or forward the call. In conjunction with an Avaya CTI server, the call could be forwarded to an agent within a service center and the caller information automatically updated at the agent stations. In a value added services platform like an IVR system, availability of ports to service incoming or outgoing calls is an important factor for success. After a call is serviced, it may be necessary to float the call back to the originating switch for further action and to release the ports. The Release Link Trunk (RLT) feature enables the CCSS to send requests to the switch that the call came from and request that the switch release the call. This feature releases the port and allows the switch to route the call to another destination for treatment.
Avaya CCSS 1000/2000 Feature Documentation August 2013 13 Introduction
Key Features
CCSS 1000
CCSS 1000 has the following standard features: • Application call control for incoming and outgoing calls. • Application programmable ISDN User Part message parameters. • Application programmable Terminal Capabilities Application Part (TCAP) User Part messaging. • MTP-L2/MTP-L3 and ISDN User Part available to ITU/ANSI/ETSI specifications. • Man Machine Language (MML) terminal handler. • Alarms Logging. • Client software compatible with MPS Release MPS 4.1. • Example MPS Developer application software is included. • UNIX Operating System Environment. • Support for up to 64 Destination Points in the network. • Up to 480 lines supported. • Up to 20 T1 and 16 E1 circuits supported. • Runs on Solaris 2.10 • Telcordia and ETSI V3 variant supported. • SS7 RLT software supported. • Integration with MPS redundancy and Call Protect. The following are optional features: • National adaptation. • 48V DC power option. • Active or Standby configuration.
14 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] CCSS 2000
CCSS 2000
CCSS 2000 includes the following features in addition to the Model 1000 feature list: • Standalone server configuration. • Dual LAN connectivity to MPS systems. • Support for up to 384 Circuit Groups (memory and CPU). • Up to 9216 Lines for T1 and 11520 Lines for E1 are supported. • Supports a warm standby fault tolerance solution.
System Capacity
The CCSS supports multiple MPS systems (referred to as clients) using a single or dual Ethernet LAN interface. CCSS 2000 can support up to 384 circuit groups which is equivalent to 9216 Lines for T1 or 11520 Lines for E1 (CCSS 1000 supports up to a maximum of 480 lines which is equivalent to 20 T1 or 16 E1 circuits). The standard CCSS 2000 configuration is sufficient for most application environments. It is scalable for the demanding environments that require additional performance. The CCSS includes the required hardware for connecting to the signaling network over SS7 links. The CCSS is connected to client MPS systems using an Ethernet LAN connection and is used for exchanging SS7 protocol information with the application (optionally, dual rail Ethernets can be configured). All client applications must be able to communicate with the CCSS and the signaling network to perform call processing.
Signaling Link Physical Interface
The standard CCSS configuration utilizes DCC3000 datalink cards to support between one and 16 links. Consider the software limitations when you configure the DCCLINK for more than two data links from a single DCCSS7 card. For additional information, see CCSS System Limits on page 113. The links can be received on any of the eight spans that are received by the DCC/PLI on the same TMS. T1/E1 interfaces are supported using the TMS native span interface to the SS7 network.
Avaya CCSS 1000/2000 Feature Documentation August 2013 15 Introduction
T1/E1 Connectivity
A multiplexer is not required for connectivity using T1 or E1. T1/E1 connectivity is supported using the T1/E1 connections that terminate on the TMS Phone Line Interface (PLI). SS7 signaling is supported on a DCC3K card with an SS7 software load (referred to as the DCCSS7) that is contained within the TMS and terminates the signalling. A TMS with a DCCSS7 card and a DCC/PLI card can support up to eight T1/E1 spans. DCCSS7 has redundant Ethernet links.
Note: The DCCSS7 is reset and reloaded every time the host TMS is rebooted. The DCC3K image is distributed as part of the CCSS package.
Software Components
The following software versions are required on the CCSS 1000/2000 and on the MPS using the CCSS: • Server: SunOs 2.10 (Solaris 10); PERIccss package (ccss7.1.0) • Client: MPS Release 4.x.
Architectural Overview (Simplex Configuration)
The CCSS uses a client/server architectural model where the CCSS is a server accessed by the MPS systems (clients) for SS7 call control and transactional functions. The CCSS interface to the client is a TCP/IP interface over Ethernet. The CCSS is housed within the standard Avaya equipment chassis that is mounted in a standard Avaya cabinet. An optional 48V DC power supply is available for Telco environments. The CCSS 1000 is a call control and signalling server that contains hardware and software to enable SS7 functions. Due to system resources, a maximum of 480 ports, equivalent to 20 T1 or 16 E1 circuits, is supported. There must be sufficient memory in the system for all the programs to be memory resident. CPU utilization must never reach 100%.
16 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Architectural Overview (Fault Tolerant Configuration)
Architectural Overview (Fault Tolerant Configuration)
CCSS provides a fault-tolerant configuration referred to as CCSS-FT. CCSS-FT is a hot standby solution that is achieved by incorporating Trillium Fault-Tolerance Core and Trillium Protocol-Specific Function (PSF) software into the existing Trillium ISUP and MTP3 software layers, while adding a run-time state update capability to the Call-Control and Maintenance Entity (CCME) that performs ISUP call-control functions. The hot standby algorithm uses check pointing of the state of the SS7 stack between the active and standby systems. A CCSS can be configured to manage call volumes in the thousands of calls. In high volume cases, fault-tolerant configuration provides a high-availability CCSS solution. In this dual- server configuration, software routes the SS7 network messages between two identical CCSS 1000/2000 systems. Each server has its own dedicated power supply with replicated protocol layers and both are in a running state. When both servers are running, one is in active state and executes the software to provide the necessary protocol functionality. The other server is in a standby state. The active server processes the protocol messages and updates the new state information to the standby server. The CCSS management process is responsible for configuring and controlling all SS7 stack component processes. When CCSS management detects a failure on the active server, it readies the standby server by activating the protocol layers of the standby server. Management (MGMT) processes on the fault-tolerant pair of servers communicate with one another to complete the switchover between servers and reroute protocol traffic to the server that is becoming active. With CCSS-FT hot-standby redundancy, connected calls at the time of the switchover remain connected after the switchover has occurred. MGMT maintains the state machine of the CCSS servers and controls the servers accordingly.
Note: The following is important information: • CCSS-FT does not have a load sharing configuration (that is, traffic is not shared between the active and standby servers). Both the active and standby servers must have the same configurations. • The algorithms for linksets and routesets redundancy/load balancing are part of MTP3 specifications. The redundancy is improved because the state of link alignment is maintained across the changeover. • There is no enhancement to the existing redundancy support for SCCP/TCAP. On CCSS systems configured for SCCP/TCAP and ISUP, ISUP calls are abandoned in the event of a fault that induces fault-tolerant changeover. TCAP transaction states are not maintained between the CCSS pair when fault-tolerant changeover occurs. • A pair of fault tolerant servers, CCSS A and CCSS B, should have similar configuration files. The only difference should be in the CONFIG REDUNDANT_SERVER command where each server would identify the remote server as its peer.
Avaya CCSS 1000/2000 Feature Documentation August 2013 17 Introduction
Software Architecture
The CCSS 1000/2000 server software consists of multiple processes that communicate with each other, the SS7 protocol stack, and their clients. The client side software is implemented using the VAS Resource paradigm providing a conduit for the application to send messages to the server. The TMS-integrated mode is an alternative to the VAS resource paradigm that processes SS7 protocol data in MPS Developer call-processing blocks without use of an external VAS resource. The responsibilities of the processes that provide the CCSS 1000/2000 functionality are the following: • ccme--This process implements ISUP call control and maintenance and interfaces with the SS7 protocol stack and the client systems. The ccme process provides ISUP message routing for Circuit Identification Code to application line mapping, a call control state machine to protect against application errors and encoding and decoding of messages between the network format and the native application format with parameter validation for the ISUP messages. The process also tracks system statistics including total inbound and outbound call attempts, calls accepted, rejected, failed, and so on. • ccssalarm--This process is responsible for collecting alarms generated on the server. The alarms are logged to one of a set of alarm files on the server. The active file expands to a preconfigured size before it is copied and a new active alarm file is created. The alarm files are each named alarms.x, where x is a number that increases sequentially for each new file. The alarms can be forwarded to a remote host to be displayed through the MPS Manager network management tool. • ui--This is the user interface process that is available for the system operator to control the CCSS 1000/2000. The system status and ISUP circuits are reported and controlled through this interface. (See UI on page 131.) • ccss_stat--This process collects call statistics such as number of inbound call attempts, number of outbound call attempts, and so on. The process collects statistics every 15 minutes and logs them to a file. The statistics for the previous month are backed up by this process. The statistics are backed up at the start of a new month or when the system is rebooted. • mgmt--The management process is the control center for the CCSS. The management process maintains the state machine that determines the active or standby status of the server. At startup, MGMT reads the server configuration from disk and configures call control and the SS7 protocol stack. MGMT then selects the appropriate state, active or standby, for the server. In a standalone configuration, the lone CCSS server is active unless the server is shut down by an operator. In a fault tolerant configuration, MGMT processes on the two servers negotiate to determine which server will be active and which will be standby. The MGMT process on the active server enables the call control and the SS7 protocol layers to make the server active. In a fault-tolerant configuration, the two MGMT
18 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Software Architecture
processes communicate through a peer-to-peer interface to bring the second server to the standby state. In a fault-tolerant configuration, both MGMT processes on dual CCSS servers coordinate with one another for controlled or forced switchover. Forced switchover, for example, occurs if: - MGMT on the standby server loses communication with the active MGMT. - the active MGMT detects a failure in the active server and communicates it to the standby MGMT. When a forced switchover occurs, the standby MGMT takes all actions necessary to reroute call traffic to the standby server and make itself active. The server that was active takes recovery action and becomes the standby server. Controlled switchover is a series of actions that are carefully sequenced by both the active and standby MGMT processes to exchange active and standby states without call loss. • mgmtui – This is the user interface to the CCSS management process. mgmtui provides the operator with a system administration and management interface. The system operator can enter REPORT, CONTROL, STATISTIC or TRACE commands. (See MGMTUI on page 115.) • tcu – The TCAP User process provides the following features: - Managing application resources. - Maintain connection between CCSS and Application Server. - Mapping TCAP messages to/from Applications. - Monitoring subsystem status. - Providing user command interface (tcuui) for monitoring, debugging and managing purpose • tcuui – This is the user interface to the TCAP User process. For tcuui commands, see TCU User Interface (TCUUI) Commands on page 141. • procmon – Process monitor one per CCSS process. It starts and runs the process as a child process. On abnormal exit, it handles the SIGNAL and restarts the process. • mti - mtp3/tcap/isup – Implements the MTP3, ISUP and TCAP layers of the SS7 protocol.
Avaya CCSS 1000/2000 Feature Documentation August 2013 19 Introduction
The client side software provides the following functionality: • Local resource agents (CCSS proxy, TCAP proxy) – These processes interfaces with the applications and with the CCSS 1000/2000 over single or dual rail Ethernets. This resource provides broadcast, message discrimination, and keepalive functionality.
Figure 1: System Block Diagram: Fault Tolerant CCSS
Standards Compliance
The Message Transfer Part (MTP) Level 1 defines the electrical and mechanical characteristics of the signaling links that connect SS7 components. The MTP Level 2, which is analogous to
20 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Standards Compliance
the OSI Data Link Layer, ensures the reliable transfer of messages between two directly connected Signaling Points. The MTP Level 3, which is analogous to the OSI Network Layer, provides message transport routing, traffic management, flow control and multiple signaling point capability. The ISDN User Part (ISUP) provides the capabilities for switched network connections between subscriber line exchange terminations. The Transaction Capabilities Application Part and Signaling Connection Control Part (TCAP/SCCP) user parts provide the protocol support for transaction-based processing between service control points in the SS7 network, for implementation of information services such as 1-800 call routing, text-messaging, and more.
Layer ANSI ITU Other ISUP ANSI T1.113.X '92 Blue Book Q.761-Q.764, '88 ETSI V3 EN 300 356-1 ANSI T1.113.X '96 White Book Q.761-Q.764, ETSI V2 ETS 300 356 '92 Q.767 ETSI V1 ETS 300 121 Telcordia GR-317- CORE Telcordia GR-394- CORE Telcordia GR-905- CORE MTP-L3 ANSI T1.111.4,'92 Blue Book Q.704-Q.707, '88 ANSI T1.111.4,'96 White Book Q.704-Q.707, '92 MTP-L2 ANSI T1.111.3,'92 Blue Book Q.701-Q.703, '88 ANSI T1.111.3,'96 White Book Q.701-Q.703, '92 TCAP ANSI T1.114, '92 Blue Book Q.771-Q.775, '88 ANSI T1.114, '96 White Book Q.771-Q.775, '92 Q.771-Q.775, '96 SCCP ANSI T1.112, '92 Blue Book Q.711-Q.714, '88 ANSI T1.112, '96 White Book Q.711-Q.714, '92
Note: Variant Q767 is same as ETSI V1 variant. GR-394-CORE is supported.
Avaya CCSS 1000/2000 Feature Documentation August 2013 21 Introduction
22 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Chapter 2: Installation
This chapter covers: 1. Hardware Installation 2. Installation of Software Packages
Hardware Installation and Configuration
Hardware installation is covered in the Avaya Media Processing Server 1000 Hardware Installation and Maintenance and Avaya Media Processing Server 500 Hardware Installation and Maintenance" guides. The diagrams that follow supplement the information in those documents to illustrate connections between fault-tolerant CCSS servers and to show the connections to the DCCSS7 cards.
System Cabling Diagrams
DCCSS7 Datalinks (Fault Tolerant Configuration)
Avaya CCSS 1000/2000 Feature Documentation August 2013 23 Installation
CCSS Cable connections using DCCSS7 Datalinks (Fault Tolerant Configuration)
24 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] DCCSS7 Datalinks (Fault Tolerant Configuration)
DCCSS7 data links are distributed across two networks. Distributing across two networks enable the system to continue to function in the event of a failure of one of the LANs.
Avaya CCSS 1000/2000 Feature Documentation August 2013 25 Installation
CCSS Cable Connections using DCCSS7 datalinks (Stand Alone Servers)
Ethernet Connections using DCCSS7 datalinks
SS7/C7 Server Software Installation
Typically the CCSS package is factory-installed for new orders, using procedures from the Installing Avaya MPS Software on the Solaris Platform guide. For upgrades from MPS 3.x to
26 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Removal of Previous Version
MPS 4.1, upgrade procedures in the Migrating Avaya Media Processing Server from 3.x to 4.1 guide apply. The following instructions for installing the system software on the CCSS 2000 server are provided as a reference, for instances where the CCSS package may have to be removed and/or re-installed on site. Complete the information worksheets in Appendix B and use that information during the installation and configuration. For additional information, see Network Information on page 375.
Removal of Previous Version
If there is a previous version of CCSS software installed, it will have to be removed before installing the new software. To remove previous versions of the software, do the following: 1. Switch to super user. peri@V245-251-124 {3} su Password:
csh V245-251-124# 3. Execute pkgrm to remove the pervious versions. pkgrm PERIccss. 4. Respond to all prompts.
Note: The removal of PERIccss package does not affect the files present in $CCSSHOME/etc directory. Below is a session log of the removal of the PERIccss package using 'pkgrm PERIccss'.
pkgrm PERIccss pdv210-251-107# pkgrm PERIccss
The following package is currently installed: PERIccss CCSS Server Distribution (SPARC) ccss7.0.0
Do you want to remove this package? [y,n,?,q] y
## Removing installed package instance
This package contains scripts which will be executed with super-user permission during the process of removing this package.
Do you want to continue with the removal of this package [y,n,?,q] y ## Verifying package
Avaya CCSS 1000/2000 Feature Documentation August 2013 27 Installation
## Removing pathnames in class
Removal of
Installation
The CCSS package can be installed on a Solaris system only , using the following steps. 1. Switch to super user.
peri@pdv210-251-107 {26} su Password:
# csh V245-251-124# 3. Change directory where the PERIccss package resides. 4. Execute pkgadd to install the new version. Respond to all prompts. pkgadd -d root@pdv210-251-107 {22} pkgadd -d .
The following packages are available: 1 PERIccss CCSS Server Distribution (SPARC) ccss7.1.0
Select package(s) you wish to process (or 'all' to process all packages). (default: all) [?,??,q]:
Processing package instance
28 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Installation
Avaya Incorporated 211 Mt. Airy Road Basking Ridge, NJ 07920 USA
This software is furnished under a license and may be used and copied only in accordance with the terms of such license and with the inclusion of the above copyright notice. This software or any other copies thereof, may not be provided or otherwise made available to anyone other than the licensee. Title to and ownership of this software remains with the Avaya.
The information in this document is subject to change without notice and should not be construed as a commitment by Avaya.
Avaya assumes no responsibility for the use or reliability of its software on equipment that is not supplied by Avaya.
Removing old logs...
Three latest logs for PERIccss are available at /var/sadm/install_data
/tmp/install0DaG4C/checkinstall2DaG4C: /var/sadm/install_data/install- mpsPERIccss050113-13:40:51.log: cannot create Check Java version... SUCCESS: "/usr/java/bin/java -version" is "1.6.0" Ready for package installation
Specify the base directory under which the PERIccss Distribution will be installed.
PERIccss base install directory [/opt/vps]: [?,q]
CCSS Protcol Configuration... Please select a protocol from the following: 1. isup-tcap 2. sip 3. ccxml ( Enter protocol as a single number ) Protocol:==> 1
TCAP ASN.1 Encoding Format Configuration... Please select the TCAP ASN.1 length ecoding format: 1. TCAP ASN.1 Indefinite Length Encoding 2. TCAP ASN.1 Definite Length Encoding ( Enter '1' or '2' ) Encoding:==> 1 Using as the package base directory. ## Processing package information. ## Processing system information. 5 package pathnames are already properly installed. ## Verifying disk space requirements. ## Checking for conflicts with packages already installed. ## Checking for setuid/setgid programs.
This package contains scripts which will be executed with super-user permission during the process of installing this package.
Do you want to continue with the installation of
Avaya CCSS 1000/2000 Feature Documentation August 2013 29 Installation
/opt/vps/packages/ccss7.1.0/bin/alm_off /opt/vps/packages/ccss7.1.0/bin/alm_on /opt/vps/packages/ccss7.1.0/bin/cc_ptimer /opt/vps/packages/ccss7.1.0/bin/ccme_isup /opt/vps/packages/ccss7.1.0/bin/ccme_iup
......
/tftpboot/tp1100-60.ini /tftpboot/tp1100-AMR.ini /tftpboot/tp1100.ini /tftpboot/tp200.ini /tftpboot/tp800.ini [ verifying class
Creating /etc/ccsshome
Modifying .cshrc of peri...... done
Creating /etc/rc3.d/S50ccss
Creating /opt/ccss/etc/perirc.csh
CCSS protocol configuration is non-interactive. The systems is currently configured for ISUP validating current setup OK Setting up TCAP Setup of TCAP complete Installing TPM200 image into /tftpboot
Installing TPM200 INI file into /tftpboot
Installing TPM800 software into /tftpboot
Installing TPM800 INI file into /tftpboot
This procedure sets up the mti to the appropriate TCAP ASN.1 encoding format This procedure allows user to switch between TCAP ASN.1 definite length and indefinite length encoding schemes
Non-interactive execution... TCAP ASN.1 Indefinite length encoding set
Version of PERIglobl found is globl4.1.0 Using ccssalarm.is Installation log is at /opt/ccss/etc/ccss.install.log
Installation of
30 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Change Protocol
Note: DCCSS7 is reset and rebooted whenenever the controlling TMS is rebooted. This is a constraint of the TMS implementation. The DCCSS7 can be rebooted independent of the TMS using l2debug. See DCCSS7 Debugging Utility on page 489.
Change Protocol
To change the protocol use the setup_protocol command. For SS7, choose option 1 (isup- tcap). Options 2 and 3 are for SIP, which is not covered in this manual. setup_protocol
root@pdv210-251-107 {3} setup_protocol Please select a protocol from the following: 1. isup-tcap 2. sip 3. ccxml ( Enter protocol as a single number ) Protocol:==> 1 The systems is currently configured for SIP validating current setup OK Setting up TCAP Setup of TCAP complete root@pdv210-251-107 {4}
CCSSALARM Version
The command setup_vpsis checks the version of ccssalarm that is compiled against the version of PERIglobl installed on the system. setup_vpsis root@pdv210-251-107 {16} setup_vpsis Version of PERIglobl found is globl4.1.0 Using ccssalarm.is root@pdv210-251-107 {17}
Setting a netmask for PROXY
The CCSS checks the IP addresses of configured CCME and TCU proxy hosts against the netmasks of its LAN interfaces to assure that the CCSS and proxies are on the same subnet. However, the CCSS server can be configured to allow the CCSS to connect to proxies on any
Avaya CCSS 1000/2000 Feature Documentation August 2013 31 Installation
network. To do so, create an empty file named “.anynet” in the $CCSSHOME/etc directory on the CCSS system.
peri@pdv210-251-107 {8} touch $CCSSHOME/etc/.anynet
CCSS Monitoring by MPS Manager
Create a CCSS component by running the mkccss script. For more information about making CCSS components, see SS7/C7 Software Installation on page 460. The CCSS server can be monitored by MPS Manager. A CCSS icon that depicts the state of the CCSS server appears in the MPS Manager GUI monitoring tool that is running on the MPS server. The CCSS server actively reports the status to the MPS server. The CCSS icon changes color to indicate the state of the CCSS server. When the CCSS server is up and running, the CCSS icon is green. If the CCSS server is shut down or if a failure occurs, the icon changes color to red. If the CCSS server is inaccessible to MPS Manager, the CCSS icon is black. To enable CCSS server monitoring by MPS Manager, the environment variables CCSSSTARTSCRIPT and CCSSSTOPSCRIPT need to be set as shown in the following:
setenv CCSSSTARTSCRIPT/CCSSSTOPSCRIPT
root@tcccss12 {1} setenv CCSSSTARTSCRIPT $CCSSHOME/bin/vos_start : root@tcccss12 {1} setenv CCSSSTOPSCRIPT $CCSSHOME/bin/vos_stop
CCSS Server Upgrade Procedures
Upgrading the Lone Server In A Standalone Configuration
For a standalone CCSS server, network traffic will be interrupted while the server is upgraded. Sequencing of the termination and restart of the CCSS server and the applications to minimize call loss should be considered (periods of low traffic, for example).
1. Enter the command ccss_down to block all circuits.
32 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Upgrading Both Servers In A Fault-Tolerant Configuration
Note: Waiting for incoming calls to complete or soft-terminating applications before proceeding to the next step can minimize call loss during shutdown of a standalone CCSS server. 2. Enter ccss_stop to stop all CCSS processes on the standalone (active) server. 3. Apply any patches or package upgrades. Use the peripatch script for applying patches.
Note: Before continuing to the next step, consider the nature of the applications that will be run. It might be best to assign and start applications in a particular order prior to starting the CCSS server. Otherwise, some incoming network traffic might initially be mishandled after the SS7 network resumes traffic but before applications have time to come into service and handle the network traffic. If applications are running and have not been terminated, they stay running. If applications have been terminated they must be restarted. 4. Enter ccss_start to restart the CCSS server.
Upgrading Both Servers In A Fault-Tolerant Configuration
For a fault-tolerant configuration, the server that is not undergoing the upgrade can be made active before the upgrade is started so there is no interruption in network traffic. The second server to be upgraded is made standby by controlled switchover prior to the upgrade. Upgrading both servers does not involve interruption of service. 1. If the CCSS server to be upgraded first is Active prior to upgrade, run the MGMTUI command to perform a controlled switchover so that the server to be upgraded becomes Standby. Otherwise proceed to step 2. 2. If either server is Active prior to the upgrade, run ccss_stop on the CCSS server that is to be upgraded. 3. Run ccss_stop on the server to be upgaded. 4. Apply any patches or package upgrades to the shutdown server. Use the peripatch script for applying patches. 5. If necessary, make changes to configuration files on the shutdown CCSS server as specified in the patch README file and release notes. 6. Enter ccss_start on the upgraded server.
Avaya CCSS 1000/2000 Feature Documentation August 2013 33 Installation
7. If the restarted CCSS server and its network interconnections have been properly configured, the CCSS server should go to standby state. If it does not, repeat steps 1 and 3 until configuration issues are resolved. 8. After the upgraded server goes to standby, enter the MGMTUI command to perform a controlled switchover. The upgraded server will become active and the server that is not yet upgraded becomes standby. 9. Run ccss_stop on the standby server. 10. Apply any patches or package upgrades to the shut-down server. Use the peripatch script for applying patches. 11. If necessary, make changes to configuration files on the shutdown CCSS server as specified in the patch README file and release notes. 12. Enter ccss_start on the upgraded server. 13. Repeat steps 7 through 10 on the restarted server until it achieves standby state.
Upgrading A Single Server In A Fault-Tolerant Configuration
For a fault-tolerant configuration undergoing an upgrade of a single server, the server not undergoing the upgrade can be made active before the upgrade is started so there is no interruption in service. 1. If the server to be upgraded is in the Active/With Standby state, perform a controlled switchover to make it standby. Otherwise, proceed to step 2. 2. Run ccss_stop on the standby server. 3. Apply any patches or package upgrades to the shut-down server. Use the peripatch script for applying patches. 4. If necessary, make changes to configuration files on the shutdown CCSS server as specified in the patch README file and release notes. 5. Enter ccss_start on the upgraded server. 6. If the restarted CCSS server and its network interconnections have been properly configured, the CCSS server should switch to standby state. If it does not, repeat steps 2 through 5 until the configuration issues are resolved. 7. After the upgraded server becomes standby, the upgrade is complete. The operator may optionally enter the MGMTUI command to perform a controlled switchover. The upgraded server becomes active and the server that is not upgraded becomes standby.
34 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Chapter 3: Configuration
This chapter covers: 1. Introduction to Configuration 2. Sample Configuration Files 3. Configuration Command Syntax 4. Data Link Configuration 5. MTP Layer 3 Configuration 6. ISUP Configuration 7. Call-Control Mode Configuration 8. Fault Tolerant Configuration 9. SCCP/TCAP Configuration
Introduction to Configuration
The CCSS server configuration files exist in the $CCSSHOME/etc directory. For ISUP and TCAP/SCCP, all of the CCSS configuration information is contained in the file ss7.conf in the $CCSSHOME/etc directory. Sample configuration files are distributed with the PERIccss package and are installed in the $CCSSHOME/etc directory. The sample files contain.sample in the filenames and there are samples for configurations such as, A-Link configuration and F-Link configuration. When you configure the SS7 server, a new ss7.conf file is created in the $CCSSHOME/etc directory. Lines from the sample files are copied there and edited as needed to define a site-specific configuration. The sample configuration files are presented in the next section, followed by a listing of all configuration commands. The remainder of the chapter discusses the sections of the configuration files that are devoted to the configuration of distinct aspects and features of the CCSS. Configuration examples provide lines from the sample configuration files, as needed.
Avaya CCSS 1000/2000 Feature Documentation August 2013 35 Configuration
Sample Configuration Files ss7.conf.sample
A sample ss7.conf configuration file is shown as follows.
ss7.conf File
# CCSS node CONFIG NODE=A1, OPC=2068, TYPE=SEP;
# MTP configuration CONFIG DCCHOST=dccl1, HOST=dcclink1; CONFIG DCCLINK=link1, SLC=0, DCCHOST=dccl1, PRIORITY=0, CHASSIS=2, BPS=2, SLOT=4, SPAN=1, CHANNEL=24, SS7SPAN=1, SS7CHAN=1, BR=64000; CONFIG DCCLINK=link2, SLC=1, DCCHOST=dccl1, PRIORITY=0, CHASSIS=2, BPS=2, SLOT=4, SPAN=2, CHANNEL=24, SS7SPAN=1, SS7CHAN=2, BR=64000; CONFIG LINKSET=ls1, DPC=2067, TYPE=FLINK, ACTIVELINK=2, LINKS=link1,link2; CONFIG CMB_LINKSET=cs1, LSETS=ls1; CONFIG ROUTE=rt1, DPC=2067, LSETS=cs1;
# ISUP trunk groups CONFIG TRK_GRP=1, CIR_GRP=0, GRP_TYPE=T1, DPC=2067; CONFIG TRK_GRP=2, CIR_GRP=1, GRP_TYPE=T1, DPC=2067; CONFIG TRK_GRP=3, CIR_GRP=2, GRP_TYPE=T1, DPC=2067; CONFIG TRK_GRP=4, CIR_GRP=3, GRP_TYPE=T1, DPC=2067;
# TMS host for TMS-Integrated Mode # Map TMS-Integrated Mode trunkgroups (1 and 2) to TMS1 spans 1 and 2 CONFIG CCME_TMS_HOST=TMS1, HOSTNAMES=tms1a, tms2a; CONFIG CCME_TMS_GRP=1, CCME_TMS_HOST=TMS1, TMS_SPAN=1; CONFIG CCME_TMS_GRP=2, CCME_TMS_HOST=TMS1, TMS_SPAN=2;
# MPS AP for Proxy Mode. # Map Proxy Mode trungroups (3 and 4) to SCN1, MPS component #3, lines 1-48 CONFIG CCME_PROXY_HOST=SCN1, HOSTNAMES=scn1a, scn2a; CONFIG CCME_PROXY_GRP=3, CCME_PROXY_HOST=SCN1, VPS=3, LINE=1; CONFIG CCME_PROXY_GRP=4, CCME_PROXY_HOST=SCN1, VPS=3, LINE=25;
# Local SCCP point code CONFIG SCCP_LOCAL=A1, OPC=2068;
# Network SCCP point code and SSN CONFIG SCCP_NETWORK=periSCP, DPC=2067, SSN=252;
# MPS AP MCP1 will run TCAP aplications # Map TCAP applications for two T1s to MCP1, MPS component #20, lines 1-48 CONFIG TCUSER_HOST=MCP1, VAS=VAS2; CONFIG TCUSER_CLIENT=VAS2, GROUP=1, TYPE=T1, VPS=20, LINE=1; CONFIG TCUSER_CLIENT=VAS2, GROUP=2, TYPE=T1, VPS=20, LINE=25;
#Override ISUP default parameter values CONFIG CCME_DEFAULT=FOCI_CALL-IND, VALUE=1;
36 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] ss7.conf.sample.alink
#Define call control optional values CONFIG CCME_OPTION=OVERLAP, VALUE=y;
#Change the default timer value for the timer P13 CONFIG CCME_TIMER=P13, VALUE=15;
# Identify the other CCSS host in a redundant pair (for fault-tolerant configuration) CONFIG REDUNDANT_SERVER=ccss_remote, SERVER_ID=A, HOSTNAMES=tcccss12_1, PINGHOSTS=tcccss12_2; ss7.conf.sample.alink
ss7.conf.sample.alink
#configure signaling point CONFIG NODE=CCSSA, OPC=2065, TYPE=SEP;
# DCCSS7 hosts CONFIG DCCHOST=dccl1, HOST=dcclink1; CONFIG DCCHOST=dccl2, HOST=dcclink2;
# SS7 links CONFIG DCCLINK=link1, SLC=0, DCCHOST=dccl1, PRIORITY=0, CHASSIS=2, BPS=1, SLOT=4, SPAN=1, CHANNEL=24, SS7SPAN=1, SS7CHAN=1, BR=64000; CONFIG DCCLINK=link2, SLC=1, DCCHOST=dccl1, PRIORITY=0, CHASSIS=2, BPS=1, SLOT=4, SPAN=2, CHANNEL=24, SS7SPAN=1, SS7CHAN=2, BR=64000; CONFIG DCCLINK=link3, SLC=2, DCCHOST=dccl2, PRIORITY=0, CHASSIS=2, BPS=2, SLOT=4, SPAN=1, CHANNEL=24, SS7SPAN=1, SS7CHAN=1, BR=64000; CONFIG DCCLINK=link4, SLC=3, DCCHOST=dccl2, PRIORITY=0, CHASSIS=2, BPS=2, SLOT=4, SPAN=2, CHANNEL=24, SS7SPAN=1, SS7CHAN=2, BR=64000;
# link sets CONFIG LINKSET=ls1, DPC=2066, TYPE=ALINK, ACTIVELINK=2, LINKS=link1,link2; CONFIG LINKSET=ls2, DPC=2067, TYPE=ALINK, ACTIVELINK=2, LINKS=link3,link4;
# combined linksets for the STP routes CONFIG CMB_LINKSET=stpcls1, LSETS=ls1, ls2; CONFIG CMB_LINKSET=stpcls2, LSETS=ls2, ls1;
# routes for the STP CONFIG ROUTE=stpr1, DPC=2066, LSETS=stpcls1; CONFIG ROUTE=stpr2, DPC=2067, LSETS=stpcls2;
# combined linksets for the ISUP DPCs CONFIG CMB_LINKSET=cs1, LSETS=ls1, ls2; CONFIG CMB_LINKSET=cs2, LSETS=ls2, ls1;
# routes for the ISUP DPCs CONFIG ROUTE=rt1, DPC=2068, LSETS=cs1; CONFIG ROUTE=rt2, DPC=2069, LSETS=cs2;
# trunk groups CONFIG TRK_GRP=1, CIR_GRP=0, GRP_TYPE=T1, DPC=2068; CONFIG TRK_GRP=2, CIR_GRP=1, GRP_TYPE=T1, DPC=2068; CONFIG TRK_GRP=3, CIR_GRP=2, GRP_TYPE=T1, DPC=2069; CONFIG TRK_GRP=4, CIR_GRP=3, GRP_TYPE=T1, DPC=2069;
# proxy mode host and application lines CONFIG CCME_PROXY_HOST=SCN1, HOSTNAMES=localhost; CONFIG CCME_PROXY_GRP=1, CCME_PROXY_HOST=SCN1, VPS=1, LINE=1;
Avaya CCSS 1000/2000 Feature Documentation August 2013 37 Configuration
CONFIG CCME_PROXY_GRP=2, CCME_PROXY_HOST=SCN1, VPS=1, LINE=25; CONFIG CCME_PROXY_GRP=3, CCME_PROXY_HOST=SCN1, VPS=2, LINE=1; CONFIG CCME_PROXY_GRP=4, CCME_PROXY_HOST=SCN1, VPS=2, LINE=25;
# This sets up call control for extended mode 4 application folders # This can be adjusted to match older revisions of the CCSS CONFIG CCME_OPTION=EXTENDED, VALUE=4;
ss7.conf.sample.tcap
ss7.conf.sample.tcap
#configure signaling point CONFIG NODE=CCSSA, OPC=2065, TYPE=SEP;
# DCCSS7 hosts CONFIG DCCHOST=dccl1, HOST=dcclink1; CONFIG DCCHOST=dccl2, HOST=dcclink2;
# SS7 links CONFIG DCCLINK=link1, SLC=0, DCCHOST=dccl1, PRIORITY=0, CHASSIS=2, BPS=1, SLOT=4, SPAN=1, CHANNEL=24, SS7SPAN=1, SS7CHAN=1, BR=64000; CONFIG DCCLINK=link2, SLC=1, DCCHOST=dccl1, PRIORITY=0, CHASSIS=2, BPS=1, SLOT=4, SPAN=2, CHANNEL=24, SS7SPAN=1, SS7CHAN=2, BR=64000; CONFIG DCCLINK=link3, SLC=2, DCCHOST=dccl2, PRIORITY=0, CHASSIS=2, BPS=2, SLOT=4, SPAN=1, CHANNEL=24, SS7SPAN=1, SS7CHAN=1, BR=64000; CONFIG DCCLINK=link4, SLC=3, DCCHOST=dccl2, PRIORITY=0, CHASSIS=2, BPS=2, SLOT=4, SPAN=2, CHANNEL=24, SS7SPAN=1, SS7CHAN=2, BR=64000;
# link sets CONFIG LINKSET=ls1, DPC=2066, TYPE=ALINK, ACTIVELINK=2, LINKS=link1,link2; CONFIG LINKSET=ls2, DPC=2067, TYPE=ALINK, ACTIVELINK=2, LINKS=link3,link4;
# combined linksets for the STP routes CONFIG CMB_LINKSET=stpcls1, LSETS=ls1, ls2; CONFIG CMB_LINKSET=stpcls2, LSETS=ls2, ls1;
# routes for the STP CONFIG ROUTE=stpr1, DPC=2066, LSETS=stpcls1; CONFIG ROUTE=stpr2, DPC=2067, LSETS=stpcls2;
# combined linksets for the ISUP DPCs CONFIG CMB_LINKSET=cs1, LSETS=ls1, ls2; CONFIG CMB_LINKSET=cs2, LSETS=ls2, ls1;
# routes for the ISUP DPCs CONFIG ROUTE=rt1, DPC=2068, LSETS=cs1; CONFIG ROUTE=rt2, DPC=2069, LSETS=cs2;
# trunk groups CONFIG TRK_GRP=1, CIR_GRP=0, GRP_TYPE=E1, DPC=2068; CONFIG TRK_GRP=2, CIR_GRP=1, GRP_TYPE=E1, DPC=2068; CONFIG TRK_GRP=3, CIR_GRP=0, GRP_TYPE=E1, DPC=2069; CONFIG TRK_GRP=4, CIR_GRP=1, GRP_TYPE=E1, DPC=2069;
# ISUP call control proxy mode line assignments # map trunkgroups to application lines on MPS AP host mpsap1 CONFIG CCME_PROXY_HOST=SCN1, HOSTNAMES=mpsap1; CONFIG CCME_PROXY_GRP=1, CCME_PROXY_HOST=SCN1, VPS=1, LINE=1;
38 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Configuration Commands
CONFIG CCME_PROXY_GRP=2, CCME_PROXY_HOST=SCN1, VPS=1, LINE=31; CONFIG CCME_PROXY_GRP=3, CCME_PROXY_HOST=SCN1, VPS=2, LINE=1; CONFIG CCME_PROXY_GRP=4, CCME_PROXY_HOST=SCN1, VPS=2, LINE=31;
# SCCP originating pointcode and local subsystems CONFIG SCCP_LOCAL=A1, OPC=2065; CONFIG SCCP_LOCAL_SS=periIP, NODENAME=A1, SSN=146; CONFIG SCCP_LOCAL_SS=periIP2, NODENAME=A1, SSN=8;
# global title CONFIG SCCP_LOCAL_GT=localGT, LOCAL_SS=periIP, TT=000, NP=1, NAI=004, ES=2, ADDR='393358817136'; CONFIG SCCP_LOCAL_GT=NortGT2, LOCAL_SS=periIP2, TT=000, NP=1, NAI=004, ES=2, ADDR='393358817136'; CONFIG SCCP_GTTNODE=NortSTP8, SPC=60, SSN=8;
# SCCP network CONFIG SCCP_NETWORK=periSCP, DPC=2068, SSN=146; CONFIG SCCP_GTMAP=periGTa, GTTFORMAT=1, GTFORMATPARAM=(NAI=020, OE=001, TT=100, NP=000, ES=000), ADDR='2068', REPLACE=REP_YES, ROUTING=ROUTE_GT, OUTPC=2068, SSN=146, GTACTION=FIX:1:3; CONFIG ACN_GRP=CAMEL, LOCAL_SS=periIP, ACN='0.4.0.0.1.0.50.1', RULE=RULE_DMSIP; CONFIG ACN_ADD=CAMEL3, ACN_GRP=CAMEL, ACN='0.4.0.0.1.21.3.4'; CONFIG ACN_ADD=periACN, ACN_GRP=DEFAULT, ACN='0.4.0.0.1.21.1.1';
# TCAP proxy line assignments # configure tcap user for applications on MPS AP host mpsap1, MPS component #1 CONFIG TCUSER_HOST=mpsap1, VAS=SCN1; CONFIG TCUSER_CLIENT=SCN1, GROUP=1, TYPE=E1, VPS=1, LINE=1; CONFIG TCUSER_CLIENT=SCN1, GROUP=2, TYPE=E1, VPS=1, LINE=31;
# tcuser options CONFIG TCU_OPTION=NO_AGAPP_SORT;
# tcuser timer configuration CONFIG TCUSER_TIMER=T_RULEDMSIP, LEN=10;
Configuration Commands
The following is a list of the CCSS configuration commands supported by management. When the CCSS server is started, the configuration commands are read from the ss7.conf configuration file by the management (MGMT) process. The management process establishes connection with the other components of the CCSS and applies the configuration. CONFIG NODE
This command defines the local point code for the CCSS server. CONFIG NODE=name, OPC=point_code, TYPE=sp_type; NODE Name of the node assigned by the user. OPC One of the following: • Origination Point Code. The value of the OPC is expressed as a decimal number. It is the user's responsibility to convert from a
Avaya CCSS 1000/2000 Feature Documentation August 2013 39 Configuration
Point Code expressed in either ITU, 3-8-3, or ANSI, 8-8-8, format to its decimal equivalent. • ITU Conversion: [1st x 211]+[2nd x 23]+3rd • ANSI Conversion: [1st x 216]+[2nd x 28]+3rd
TYPE This parameter defines the type of node, which can either be a SEP (Signaling End Point) or STP (Signaling Transfer Point). STP is used only for internal testing and not for customer installations.
CONFIG VARIANT
For systems connected to either an ITU or ANSI variant, this command allows the user to configure the system with a yearly variant, such as ITU, ITU92, ANSI, ANSI92, and so on. CONFIG VARIANT=val; VARIANT Variant values are: ITU, ITU88, ITU92, ITU96, ITU99, ANSI, ANSI88, ANSI92, ANSI96,Q767,ETSI, ETSIV2, ETSIV3, TELCORDIA.
The following table shows the variants used to configure each layer:
val MTP2 MTP3 ISUP SCCP TCAP default ITU88 ITU ITU ITU92 ITU92 ITU ITU88 ITU ITU ITU ITU92 ITU88 ITU88 ITU ITU ITU88 ITU92 ITU92 ITU92 ITU ITU ITU92 ITU92 ITU96 ITU96 ITU ITU ITU92 ITU96 ITU99 ITU88 ITU ITU ITU ITU92
Note: For the variant value configured on ITU99, the ISUP layer is still in compliance with the ITU variant except that the ITU99 mandatory C GPN length supports up to 24 address digits. ANSI ITU88 ANSI96 ANSI92 ANSI92 ANSI92 ANSI88 ITU88 ANSI ANSI88 ANSI88 ANSI88 ANSI92 ITU88 ANSI ANSI92 ANSI92 ANSI92 ANSI96 ITU88 ANSI96 ANSI92 ANSI92 ANSI96 ETSI ITU88 ITU Q767 ITU92 ITU92 ETSIV2 ITU88 ITU ETSIV2 ITU92 ITU92 ETSIV3 ITU88 ITU ETSIV3 ITU92 ITU92
40 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Configuration Commands
val MTP2 MTP3 ISUP SCCP TCAP Q767 ITU88 ITU Q767 ITU92 ITU92 TELCORDIA ITU88 ANSI96 TELCORDI ANSI92 ANSI96 A (BELL)
CONFIG DCCHOST
Identifies a DCC host and its hostname CONFIG DCCHOST=alias, HOST=hostname [, hostname2]; DCCHOST Alias name for the DCC host to be used in the CONFIG DCCLINK command. HOST The number of LAN connections to the DCC host, and the hostnames used on each LAN connection. There may be one hostname, or two hostnames (separated by a comma) for a dual- LAN connection. Tokens (those appearing in capital letters in this section) cannot be used as host names.
CONFIG DCCLINK
Defines the configuration for one signaling link. CONFIG DCCLINK=name,SLC=slc,HOST=dcchost,PRIORITY=
Avaya CCSS 1000/2000 Feature Documentation August 2013 41 Configuration
Example The following example illustrates the usage of this command. CONFIG DCCLINK=link1, SLC=1, DCCHOST=dccl1, PRIORITY=0, CHASSIS=1, BPS=1, SLOT=1, SPAN=1, CHANNEL=24, SS7SPAN=1, SS7CHAN=1, BR=64000;
Note: The BPS,SLOT,SPAN and CHANNEL are placeholders Values in ss7.conf should be taken from SS7MAP entries made in the tms.cfg file. See CONFIG DCCLINK command (ss7.conf) on page 66.
CONFIG LINKSET
Defines the linkset for MTP3. CONFIG LINKSET=name, DPC=dpc, TYPE=type, ACTIVELINK=activelink, LINKS=link1, link2,...; LINKSET An arbitrary name to define a linkset for MTP3 to differentiate it among the linksets. DPC Destination Point Code. Defines the address of the node in which the CCSS server will communicate with. (See OPC of NODE command) TYPE Defines the type of linkset as ALINK or FLINK ACTIVELINK Defines the number of active links within a linkset LINKS The list of links already defined using the LINK command.
CONFIG CMB_LINKSET
Defines a combined linkset for the case where one linkset in a combined linkset is down. In this case, the alternate linkset is used to transmit the data. CONFIG CMB_LINKSET=name, LSETS=lset1, lset2,...; CMB_LINKSET Name of the linkset defined by the user. LSETS A linkset which is defined in the LINKSET command.
CONFIG ROUTE
Defines a route for MTP3. The destination point code (dpc) identifies an SS7 point which can be reached using combined linkset. CONFIG ROUTE=name, DPC=dpc, LSETS=Cset1, Cset2,...; ROUTE Name of the route defined by the user. DPC Destination Point Code
42 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Configuration Commands
LSETS Linkset name which is defined in the CMB_LINKSET command. Examples The following example illustrates the usage and the relationship of this command. In this example, the linkset type is F-LINK. CONFIG NODE=A1, OPC=2068, TYPE=SEP; CONFIG DCCHOST=dccl1, HOST=dcclink1; CONFIG DCCLINK=link1, SLC=0, DCCHOST=dccl1, PRIORITY=0, CHASSIS=2, BPS=2, SLOT=4, SPAN=1, CHANNEL=24, SS7SPAN=1, SS7CHAN=1, BR=64000; CONFIG DCCLINK=link2, SLC=1, DCCHOST=dccl1, PRIORITY=0, CHASSIS=2, BPS=2, SLOT=4, SPAN=2, CHANNEL=24, SS7SPAN=1, SS7CHAN=2, BR=64000; CONFIG LINKSET=ls1, DPC=2067, TYPE=FLINK, ACTIVELINK=2, LINKS=link1,link2; CONFIG CMB_LINKSET=cs1, LSETS=ls1; CONFIG ROUTE=rt1, DPC=2067, LSETS=cs1; CONFIG TRK_GRP=1, CIR_GRP=0, GRP_TYPE=T1, DPC=2067; CONFIG TRK_GRP=2, CIR_GRP=1, GRP_TYPE=T1, DPC=2067; CONFIG TRK_GRP=3, CIR_GRP=2, GRP_TYPE=T1, DPC=2067; CONFIG TRK_GRP=4, CIR_GRP=3, GRP_TYPE=T1, DPC=2067;
Note: The DPC value used in this example is the same in LINKSET and ROUTE commands because the DPC is used by MTP3 to find the ultimate destination of a message. Examples In the following example, the linkset type is ALINK , and there are two ALINK linksets for routing to two ISUP DPCs. CONFIG NODE=CCSSA, OPC=2065, TYPE=SEP; # DCCSS7 hosts CONFIG DCCHOST=dccl1, HOST=dcclink1; CONFIG DCCHOST=dccl2, HOST=dcclink2; # SS7 links CONFIG DCCLINK=link1, SLC=0, DCCHOST=dccl1, PRIORITY=0, CHASSIS=2, BPS=1, SLOT=4, SPAN=1, CHANNEL=24, SS7SPAN=1, SS7CHAN=1, BR=64000; CONFIG DCCLINK=link2, SLC=1, DCCHOST=dccl1, PRIORITY=0, CHASSIS=2, BPS=1, SLOT=4, SPAN=2, CHANNEL=24, SS7SPAN=1, SS7CHAN=2, BR=64000; CONFIG DCCLINK=link3, SLC=2, DCCHOST=dccl2, PRIORITY=0, CHASSIS=2, BPS=2, SLOT=4, SPAN=1, CHANNEL=24, SS7SPAN=1, SS7CHAN=1, BR=64000; CONFIG DCCLINK=link4, SLC=3, DCCHOST=dccl2, PRIORITY=0, CHASSIS=2, BPS=2, SLOT=4, SPAN=2, CHANNEL=24, SS7SPAN=1, SS7CHAN=2, BR=64000; # link sets CONFIG LINKSET=ls1, DPC=2066, TYPE=ALINK, ACTIVELINK=2, LINKS=link1,link2; CONFIG LINKSET=ls2, DPC=2067, TYPE=ALINK, ACTIVELINK=2, LINKS=link3,link4; # combined linksets for the STP routes CONFIG CMB_LINKSET=stpcls1, LSETS=ls1, ls2; CONFIG CMB_LINKSET=stpcls2, LSETS=ls2, ls1; # routes for the STP CONFIG ROUTE=stpr1, DPC=2066, LSETS=stpcls1; CONFIG ROUTE=stpr2, DPC=2067, LSETS=stpcls2; # combined linksets for the ISUP DPCs CONFIG CMB_LINKSET=cs1, LSETS=ls1, ls2; CONFIG CMB_LINKSET=cs2, LSETS=ls2, ls1;
Avaya CCSS 1000/2000 Feature Documentation August 2013 43 Configuration
# routes for the ISUP DPCs CONFIG ROUTE=rt1, DPC=2068, LSETS=cs1; CONFIG ROUTE=rt2, DPC=2069, LSETS=cs2; # trunk groups CONFIG TRK_GRP=1, CIR_GRP=0, GRP_TYPE=T1, DPC=2068; CONFIG TRK_GRP=2, CIR_GRP=1, GRP_TYPE=T1, DPC=2068; CONFIG TRK_GRP=3, CIR_GRP=2, GRP_TYPE=T1, DPC=2069; CONFIG TRK_GRP=4, CIR_GRP=3, GRP_TYPE=T1, DPC=2069;
Note: The NODE command must be entered as the first line of the ss7.conf file.
CONFIG TRK_GRP
Defines the trunk group, circuit group, circuit type, and destination point code. These configuration options are for ISUP only. CONFIG TRK_GRP=tid, CIR_GRP=cid, GRP_TYPE=type, DPC=dpc; TRK_GRP Define trunk group id (decimal number) CIR_GRP Define circuit group id (decimal number) GRP_TYPE Define circuit type (T1/E1) DPC Destination Point Code
CONFIG SCCP_LOCAL
Defines the point code and name which is associated with the local SCCP signaling point. CONFIG SCCP_LOCAL=nodename, OPC=point code; SCCP_LOCAL Node name OPC Origination Point Code
CONFIG SCCP_LOCAL_SS
Adds a sub-system on the local node. The SCCP_LOCAL_SS command is optional. If SCCP_LOCAL_SS is not configured, the local subysystem number is equal to the subsystem number specified in the SCCP_NETWORK command. If SCCP_LOCAL_SS is not configured, then the applications can specify the name in the origination field in the mode folder to register itself to this subsystem specified in the SCCP_NETWORK command. CONFIG SCCP_LOCAL_SS=sub-system name, NODENAME=nodename, SSN=sub-system number; SCCP_LOCAL_SS Local sub-system name NODENAME Node name defined in SCCP_LOCAL
44 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Configuration Commands
SSN Sub-system number Examples CONFIG SCCP_LOCAL_SS=periIPa, NODENAME=A1, SSN=20; CONFIG SCCP_LOCAL_SS=periIPb, NODENAME=A1, SSN=21;
CONFIG SCCP_LOCAL_SS
Modified command syntax to configure multiple subsystems with varying allocation of dialogues, invokes, and hashing bins per subsystem. CONFIG SCCP_LOCAL_SS=subsystem name, NODENAME=nodename, SSN=subsystem number, NUMDLG=Num-of-dlgs, NUMINV=Num-of- invs; SCCP_LOCAL_SS Local subsystem name NODENAME Node name defined in SCCP_LOCAL SSN Subsystem number NUMDLG Number of dialogues configured per subsystem NUMINV Number of invokes per subsystem Examples CONFIG SCCP_LOCAL_SS=periIP, NODENAME=CCSS3, SSN=146, NUMDLG=250, NUMINV=1000; CONFIG SCCP_LOCAL_SS=periIP, NODENAME=CCSS3, SSN=146, NUMDLG=13107, NUMINV=13107;
CONFIG SCCP_LOCAL_GT
Associates a global title address with the local node. Applications can specify the name in the origination field in the mode folder to use the global title as part of the calling party address. CONFIG SCCP_LOCAL_GT=name, LOCAL_SS=sub-system_name, TT=trans_type, NP=number_plan, NAI=address_indicator, ES=encoding, ADDR=address; SCCP_LOCAL_GT Symbolic name for local global title address for outgoing calling party address LOCAL_SS Local sub-system name defined in SCCP_LOCAL_SS TT Translation type NP Numbering plan
Avaya CCSS 1000/2000 Feature Documentation August 2013 45 Configuration
NAI Nature of address indicator ES Encoding scheme ADDR Global title address. Address should be single quoted ['xxx']. Examples CONFIG SCCP_LOCAL_GT=periGT1, LOCAL_SS=periIPa, NAI=020, ADDR='1111111'; CONFIG SCCP_LOCAL_GT=periGT2, LOCAL_SS=periIPa, TT=100, ADDR='2222222'; CONFIG SCCP_LOCAL_GT=periGT3, LOCAL_SS=periIPb, TT=300, NP=000, ADDR='3333333'; CONFIG SCCP_LOCAL_GT=periGT4, LOCAL_SS=periIPb, TT=300, NP=000, NAI=001, ES=2, ADDR='4444444';
CONFIG SCCP_NETWORK
Configures the network endpoints (an associated sub-system or signaling point) with which the CCSS communicates. • Identify the far-end signaling point code to be accessed. • Identify the sub-system to which the local node will access. • Identify the far-end signaling point code as a concerned point of the local sub-system SSN=20.
CONFIG SCCP_NETWORK=nodename, DPC=val, SSN=val, [BPC=val]; SCCP_NETWORK Remote network node name DPC Destination Point Code SSN Sub-system number BPC Backup Point Code. If the Primary destination specified in DPC goes Out-Of-Service, the BPC will take its place. (This function is not implemented.) Examples CONFIG SCCP_NETWORK=periSCPa, DPC=2069, SSN=20; CONFIG SCCP_NETWORK=periSCPb, DPC=2070, SSN=20;
CONFIG SCCP_NETWORK
Configures the network endpoints (an associated sub-system or signaling point) with which the CCSS communicates.
46 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Configuration Commands
CONFIG SCCP_NETWORK= nodename, DPC= val, SSN=val, SUPPRESS_SST = boolean, [BPC=val]; SCCP_NETWORK Remote network node name DPC Destination Point Code SSN Sub-system number BPC Backup Point Code. If the Primary destination specified in DPC goes Out-Of-Service, the BPC will take its place. (This function is not implemented.) SUPPRESS_SST If this field is set to TRUE, the SST message for the configured SSN is suppressed. This field is optional and any value other than TRUE indicates that the SST message is sent from the CCSS. Examples CONFIG SCCP_NETWORK=periSCPa, DPC=2069,SSN=20, SUPPRESS_SST = TRUE; CONFIG SCCP_NETWORK=periSCPb, DPC=2070, SSN=20, SUPPRESS_SST = FALSE; CONFIG SCCP_NETWORK=periSCPc, DPC=2071, SSN=20;
CONFIG SCCP_GTTNODE
Configures the default global title translation node for outbound SCCP messages. For an outbound transaction, the application may specify SCCP_GTTNODE in the destination field if the global title address is used to code the SCCP called party address. CONFIG SCCP_GTTNODE=nodename, SPC=point code, SSN=val, [BPC=val]; SCCP_GTTNODE Remote network node name SPC Signaling Point Code SSN Sub-system number. This is optional.
Note: If the network operator requires SSN in Called Party GT then this field must be specified. BPC Backup Point Code. This is optional.
CONFIG SCCP_GTTNODE
Configures the default global title translation node for outbound SCCP messages. For an outbound transaction, the application may specify SCCP_GTTNODE in the destination field if the global title address is used to code the SCCP called party address.
Avaya CCSS 1000/2000 Feature Documentation August 2013 47 Configuration
CONFIG SCCP_GTTNODE= nodename, SPC= point code, SSN=val, [BPC=val], SUPPRESS_SST=boolean; SCCP_GTTNODE Remote network node name SPC Signaling Point Code SSN Sub-system number. This is optional.
Note: If the network operator requires SSN in Called Party GT then this field must be specified. BPC Backup Point Code. This is optional. SUPPRESS_SST If this field is set to TRUE, the SST message for the configured SSN is suppressed. This field is optional and any value other than TRUE indicates that the SST message is sent from the CCSS.
Note: The fields SSN, BPC and SUPPRESS_SST are optional in the SCCP_GTTNODE command. In SCCP_GTTNODE configuration entry, the SUPPRESS_SST option follows SSN or BPC, as shown in the following examples. When all three fields are configured, the order of these fields must be the following: SSN = 140 , BPC = 2067, SUPPRESS_SST = TRUE Examples CONFIG SCCP_GTTNODE= periSTP, SPC= 2079; CONFIG SCCP_GTTNODE= periSTP, SPC= 2079, SSN= 140; CONFIG SCCP_GTTNODE= periSTP, SPC= 2079, SSN= 140, BPC=2067; CONFIG SCCP_GTTNODE= periSTP, SPC= 2079, SSN= 140, SUPPRESS_SST = TRUE ; CONFIG SCCP_GTTNODE= periSTP, SPC= 2079, SSN= 140, BPC=2067, SUPPRESS_SST = TRUE ;
CONFIG SCCP_GTASSO
Configures the SCCP GTT association. CONFIG SCCP_GTASSO=name, GTTFORMAT=#, GTFORMATPARAM=param_list, GTACTIONS=action_list, GTFUNCSET=PERI/ TRILLIUM; SCCP_GTASSO Identifies the name of this association. For example: SCCP_GTASSO=PERIasso,
48 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Configuration Commands
GTTFORMAT Specifies the global title type in this association. There are four types of global titles for ITU and two types for ANSI (corresponding to two of the four ITU types). This value must match the following parameter. type 1: nature of address indicator and odd even indicator type 2: translation type type 3: translation type, numbering plan, and encoding scheme type 4: translation type, numbering plan, encoding scheme, and nature of address indicator For example: GTTFORMAT=1, GTFORMATPARAM This field is a comma-separated list enclosed within parentheses. The available values are as follows: NAI (nature of address): 1 subscriber number 3 national significant number 4 international number OE (odd even number): 0 even number of address signals 1 odd number of address signals TT (translation type): integer number NP (number plan): 0 unknown number plan 1 ISDN Te1 numbering plan 2 Telephone numbering plan 3 Data numbering plan 4 Telex numbering plan 5 Maritime Mobile numbering plan 6 Land Mobile numbering plan 7 ISDN Mobile numbering plan ES (encoding scheme): 0 unknown encoding scheme 1 BCD odd 2 BCD even The valid parameters for the four types of global title addresses are: type 1 OE, NAI type 2 TT type 3 TT, NP, ES type 4 TT, NP, ES, NAI For example: GTFORMATPARAM=( TT=2, NP=3, ES=2), This is a type 3 address parameter. GTACTIONS This list is used to specify the order of actions used to process global title translations. There are five types of actions. Three of them need ranges. • FIX:start:end: fixed range of digits for GTT • VAR_ASC:start:end: variable number of digits GTT in ascending order
Avaya CCSS 1000/2000 Feature Documentation August 2013 49 Configuration
• VAR_DES:start:end: variable number of digits GTT in descending order • GT_TO_PC: digits in incoming GT are used as the point code for route purpose. This type is used in ISNI. • CONST: always translate the incoming GT to a fixed address. For example: GTACTIONS=(FIX:1:3, VAR_ASC:1:3), This action list defines a searching sequence to perform a GTT. GTFUNCSET Specifies which function used for global operations. Valid values are TRILLIUM or PERI. (Only TRILLIUM is currently supported.) For example: GTFUNCSET=TRILLIUM Example CONFIG SCCP_GTASSO=PERIasso, GTTFORMAT=3, GTFORMATPARAM=(TT=2, NP=3, ES=2), GTACTIONS=(FIX:1:3, VAR_ASC:1:3), GTFUNCSET=TRILLIUM;
CONFIG SCCP_GTMAP
Adds an address map for configuring the Global Title Address Translation Database in the local SCCP layer. CONFIG SCCP_GTMAP=name, GTTFORMAT=global title format, GTFORMATPARAM=Gt_Format_Param_List, MY_ADDR=addr, REPLACE=yes/no, ROUTING=GT/SSN, OUTPC=point code, SSN=ssn, GTACTION=action_type; SCCP_GTMAP Symbolic name for global title address. GTTFORMAT Global title translation format. Values for ITU are 1,2,3 and 4. Values for ANSI are 2 and 3. GTFORMATPARAM GT format parameter list. MY_ADDR Signaling Point Code REPLACE Replace global title. The specified value (yes or no) determines whether or not the global title can be replaced. ROUTING Outgoing routing type (GT or SSN) OUTPC Outgoing Point Code SSN Outgoing Sub-system number GTACTION Method used to translate the global title. Valid action type values are: FIX:start:end, VAR_ASC:start:end, VAR_DES:start:end, GT_TO_PC, CONST.
50 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Configuration Commands
To use any value other than FIX, the NEW_GTT upgrade in Trillium's software is required.
CONFIG ACN_GRP
Used by the TCU for selecting a proper application based on dialogue portion in the received TCAP BEGIN. CONFIG ACN_GRP=ACN Group name, LOCAL_SS=Local Sub-System Name, ACN='ACN string', RULE=rule; ACN_GRP Application context group name displayed in the tcuui report. LOCAL_SS Name specified in SCCP_LOCAL_SS in the ss7.conf file. ACN Application context name in 'dot' format. This string should be matched with application context name specified in the MODE folder. Also, the string must be enclosed by apostrophe characters. RULE One of the following: • RULE_DMSIP is for Internal IP Configuration. It will match inbound dialog requests to an application based on the correlation ID in the dialog portion. • RULE_DEFAULT finds any available application that belongs to this ACN group.
CONFIG ACN_ADD
Used by the TCU for supporting multiple application context names for a single Application Context Group (ACG). CONFIG ACN_ADD=ACN Logical name, ACN_GRP=ACN Group Name, ACN='ACN string'; ACN_ADD Application context name to be added to existing ACN Group. ACN_GRP Application context group name specified in ACN_GRP in the ss7.conf file or DEFAULT if to be added to default group. ACN Application context name in 'dot' format. Also, the string must be enclosed by apostrophe characters.
CONFIG TCUSER_HOST
Configures the hostnames of computers able to access to the TCAP interface. CONFIG TCUSER_HOST=hostname, VAS=hostname; TCUSER_HOST Hostname of the system running applications that require access to the TCAP resource. This is the host name of the MPS.
Avaya CCSS 1000/2000 Feature Documentation August 2013 51 Configuration
VAS Name to be associated with this hostname. Example CONFIG TCUSER_HOST=MCP1, VAS=VAS1;
CONFIG TCUSER_CLIENT
Specifies the phone numbers of client applications that will use the TCAP resource. CONFIG TCUSER_CLIENT=hostname, GROUP=#, TYPE=type, VPS=val, LINE=val; TCUSER_CLIENT Logical name assigned to the host running the applications. GROUP The internal number used by the TCU software to track this circuit group. The valid range is 1-128. TYPE Channel configuration span type, specified as either E1 or T1. VPS System ID number of the client CPS where the applications will be running. LINE Starting line number of the group of channels. Examples In these examples, VAS1 is the logical name defined by TCUSER_HOST. CONFIG TCUSER_CLIENT=VAS1, GROUP=1, TYPE=E1, VPS=1, LINE=1; CONFIG TCUSER_CLIENT=VAS1, GROUP=2, TYPE=E1, VPS=1, LINE=31; CONFIG TCUSER_CLIENT=VAS1, GROUP=1, TYPE=T1, VPS=1, LINE=1; CONFIG TCUSER_CLIENT=VAS1, GROUP=2, TYPE=T1, VPS=1, LINE=25;
CONFIG TCU_TIMER
Configures the TCU timers. CONFIG TCU_TIMER=timer_id, LEN=timer length; TCU_TIMER One of the following: • T_RULEDEFAULT is the time that TCU will hold an inbound request before it aborts if no application is ready for application groups using default rule. • T_RULEDMSIP is the time that TCU will hold an inbound request before it aborts if no application is ready for application groups using DMS Internal IP rule. • T_RUOS is the time that TCU will hold before aborting all active applications after a remote subsystem is detected as being temporarily out of service. • T_AUDIT is the timer used for freeing up outstanding dialogs.
52 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Configuration Commands
LEN Time in seconds allowed for tcu to hold inbound BEGIN: • For T_AUDIT timer, set between 30 to 86400 secs (24 hours). • For T_RUOS timer, set between 0 to 60 secs.
Example CONFIG SCCP_LOCAL=A1, OPC=2068; CONFIG SCCP_LOCAL_SS=periIP, NODENAME=A1, SSN=252; CONFIG ACN_GRP=DMS_IP, LOCAL_SS=periIP, ACN='0.4.0.0.1.0.50.1', RULE=RULE_DMSIP; CONFIG ACN_ADD=DMS_IPv2, ACN_GRP=DMS_IP, ACN='0.4.0.0.1.21.3.4'; CONFIG ACN_ADD=MAPv2, ACN_GRP=DEFAULT, ACN='0.4.0.0.1.0.80.1'; CONFIG TCU_TIMER=T_RULEDMSIP, LEN=5;
CONFIG TCU_OPTION
Configures the TCU Options. CONFIG TCU_OPTION=option_name; TCU_OPTION At present, only the following are supported: NO_AGAPP_SORT - By default, applications will be inserted into the waitlist after sorting it based on group number and circuit number for handling incoming events. To disable this, that is, to have applications in the sequence in which "GET" messages received, this option can be used. FT_ISUP - Enabes the ISUP fault tolerant to remain active when TCAP is configured and enables ISUP calls to be maintained on failover. This option provides the option of call recovery when a TCAP dialog is in place. DLG_RSP - Enables the result field to be populated with “ACN not supplied” for a User Abort dialog in Dialogue Response Application protocol data unit. TSTATINFO - It is a delay timer value set between requests for subsystem status information. By default is set to 2 secs However it can be set to any value between the range of 2 - 10 secs by using the following configuration command. Example CONFIG TCU_OPTION=NO_AGAPP_SORT; CONFIG TCU_OPTION=FT_ISUP; CONFIG TCU_OPTION=DLG_RSP; CONFIG TCU_OPTION=TSTATINFO, VALUE=value;
CONFIG MGMT_OPTION
This command specifies management option values
CONFIG MGMT_OPTION=option_name, VALUE=value;
Avaya CCSS 1000/2000 Feature Documentation August 2013 53 Configuration
MGMT_OPTION Specifies option name. It can be PEER_PING_THRESHOLD or SEQUENTIAL_LOADSHARE. VALUE New value for option. For PEER_PING_THRESHOLD, the value ranges from 0 to 20. For SEQUENTIAL_LOADSHARE, the valid values are 0 and 1. Example CONFIG MGMT_OPTION=PEER_PING_THRESHOLD, VALUE=10; CONFIG MGMT_OPTION=SEQUENTIAL_LOADSHARE, VALUE=1;
CONFIG MGMT_TIMER
Changes the default timer value for the specified MGMT timer. CONFIG MGMT_TIMER=PEER_PING, VALUE=value; MGMT_TIMER Defines the timer name VALUE Timer value in seconds Example CONFIG MGMT_TIMER=PEER_PING, VALUE=2;
CONFIG CCME_PROXY_HOST
Identifies a proxy host and its host names. CONFIG CCME_PROXY_HOST=alias, HOSTNAMES=hostname1[,hostname2][,TYPE=MPS]; CCME_PROXY_ Alias name for the proxy host to be used in other CCME configuration HOST commands when referring to this host. Keywords like 'vps', 'vas' and terms with hyphens cannot be used for configuring the hostnames. HOSTNAMES The number of LAN connections to the host, and the hostnames used on each LAN connection. There may be one hostname, or two left-column: TYPE hostnames (separated by a comma) for a dual-LAN connection. right-column: The Tokens (those appearing in capital letters in this section) cannot be only valid value is used as host names. (See Tokens on page 478.) Host names may MPS (TYPE=MPS). not contain hyphens. This indicates the host is in an MPS N +1 cluster and that MPS N+1 configuration must be performed. See the section on LineID Mode ConfigurationLineID Mode Configuration on page 99.
54 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Configuration Commands
Example CONFIG CCME_PROXY_HOST=SCN1, HOSTNAMES=scn1a, scn2a;
CONFIG CCME_TMS_HOST
Identifies a TMS host and its host names. CONFIG CCME_TMS_HOST=alias, HOSTNAMES=hostname1 [, hostname2]; CCME_TMS_ HOST Alias name for the TMS host to be used in other CCME configuration commands when referring to this host. Keywords like 'vps', 'vas' and terms with hyphens cannot be used for configuring the hostnames. HOSTNAMES The number of LAN connections to the host, and the hostnames used on each LAN connection. There may be one hostname, or two hostnames (separated by a comma) for a dual-LAN connection. Tokens (those appearing in capital letters in this section) cannot be used as host names. (See Tokens on page 478.) Host names may not contain hyphens. Example CONFIG CCME_TMS_HOST=TMS1,HOSTNAMES=tms1a, tms2a;
CONFIG CCME_PROXY_GRP
Associates a configured trunk group with a Proxy host, an MPS component number, and application line numbers. CONFIG CCME_PROXY_GRP=TRK_GRP#, CCME_PROXY_HOST=alias, VPS=#, LINE=#; CCME_PROXY_ Call control circuit group number. The value will be one of the trunk GRP group numbers defined in a prior CONFIG TRK_GRP command. CCME_PROXY_ Host alias name defined in a prior CONFIG CCME_PROXY_HOST HOST command. VPS Number of the MPS component with the application lines dedicated to serve this trunk group. LINE Line number for the application (on the specified MPS) that services the first voice circuit in the group. The line numbers for the remaining circuits in the group are assigned sequentially. Example CONFIG CCME_PROXY_GRP=1, CCME_PROXY_HOST=SCN1, VPS=3, LINE=1;
CONFIG CCME_PROXY_GRP
Associates a configured trunk group with a Proxy host, an MPS component, application line numbers, TMS host and TMS span number in Hybrid Proxy Mode or LineID Mode.
Avaya CCSS 1000/2000 Feature Documentation August 2013 55 Configuration
CONFIG CCME_PROXY_GRP= TRK_GRP#, CCME_PROXY_HOST= alias, VPS=#, LINE=#,CCME_TMS_HOST=
CONFIG CCME_OVERLAP_RULE
Allows to configure the system with a list of recognized prefix/length combinations. CONFIG CCME_OVERLAP_RULE=rule_name, NOA=nature_of_address_indicator, PREFIX=prefix, LENGTH=length; CCME_OVERLAP_RULE Unique name for each rule NOA Single character for the Nature of Address Indicator N - National I - International S - Subscriber Number U - Nature of Address Unknown A - Any (match only on prefix and length, accepting any Nature of Address Indicator) PREFIX Sequence of calling party digits (0-9), in single quotes. This is the prefix to be matched LENGTH Minimum number of digits that must be collected to satisfy this rule Example CONFIG CCME_OVERLAP_RULE=Rule1, NOA=N, PREFIX='98862', LENGTH=9;
56 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Configuration Commands
Note: If the prefix for any CCME_OVERLAP_RULE is to exceed the default CDPN_LEN value (18) or the OVERLAP_DEFLEN option value is to exceed the default CDPN_LEN value (18), then the command to change the default for CDPN_LEN must precede the commands to set the OVERLAP_DEFLEN option value and the definition of any overlap-receive rules. CONFIG CCME_OPTION=OVERLAP, VALUE=Y; CONFIG CCME_OPTION=CDPN_LEN, VALUE=24; CONFIG CCME_OVERLAP_RULE=Rule1, NOA=I, PREFIX='61126', LENGTH=22; CONFIG CCME_OPTION=OVERLAP_DEFLEN, VALUE=20;
CONFIG CCME_TMS_GRP
Associates a configured trunk group with a TMS host and TMS span number. CONFIG CCME_TMS_GRP=TRK_GRP#, CCME_TMS_HOST=alias, TMS_SPAN=#; CCME_TMS_GRP Call control circuit group number. The value is one of the trunk group numbers defined in a prior CONFIG TRK_GRP command. CCME_TMS_HOST Host alias name defined in a prior CONFIG CCME_TMS_HOST command. TMS_SPAN TMS span number (1-8) for the span bearing the voice channels of this trunk group. Example CONFIG CCME_TMS_GRP=1, CCME_TMS_HOST=TMS1, TMS_SPAN=1;
CONFIG CCME_DEFAULT
Overwrites the system default value for an ISUP parameter value. CONFIG CCME_DEFAULT=string, VALUE=value; CCME_DEFAULT Token that CCME uses to identify a single default parameter value. VALUE New value that the server will use to overwrite the hard-coded default value for the identified parameter. Example CONFIG CCME_DEFAULT=FOCI_CALL_IND, VALUE=1;
Table 1: Supported ISUP Parameters Precede table with statement: Configurable ISUP parameter default (CCME_DEFAULT) values are in table X.
Avaya CCSS 1000/2000 Feature Documentation August 2013 57 Configuration
ISUP PARAMETER DEFAULT VALUE RANGE ( CCME_DEFAULT) (VALUE) Min Value Max Value NTCI_SATELLITE_IND 0 0 2 NTCI_CONTINUITY_CHECK_IND 0 0 2 NTCI_ECHO_CONTROL_IND 0 0 1 FOCI_CALL_IND 0 0 1 FOCI_EE_METHOD_IND 0 0 3 FOCI_ISUP_IND 1 0 1 FOCI_ISUP_PREFER_IND 0 0 3 FOCI_ISDN_ACCESS_IND 1 0 1 FOCI_SCCP_METHOD_IND 0 0 3 FOCI_SPARE 0 0 31 CGPC_CGPC 10 0 255 XMR_REQUIREMENT 0 0 255 CDPN_NOA_IND 1 0 7 CDPN_INN_IND 1 0 255 CGPN_CGP_NI_IND 0 0 3 CGPN_NUMBER_PLAN 1 0 7 CGPN_ADD_PRESENT_RESTRIC 0 0 4 T_IND CGPN_SCREEN_IND 1 0 4 RDTG_NOA_IND 0 0 255 RDTG_NUMBER_PLAN 0 0 7 RDTG_ADDRESS_PRESENT_RES 0 0 3 TRICT_IND REDI_REDIRECT_IND 3 0 7 REDI_REDIRECT_REASON 0 0 15 REDI_REDIRECTION_COUNTER 4 0 5 REDI_REDIRECTION_REASON 0 0 15 OCDN_NOA_IND 0 0 255 OCDN_NUMBER_PLAN 0 0 7 OCDN_ADDRESS_PRESENT_RES 0 0 3 TRICT_IND GNUM_NUM_QUAL_IND 1 0 9
58 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Configuration Commands
ISUP PARAMETER DEFAULT VALUE RANGE ( CCME_DEFAULT) (VALUE) Min Value Max Value GNUM_NOA_IND 1 0 255 GNUM_NII_IND 0 0 1 GNUM_NUMBER_PLAN 0 0 7 GNUM_PRESENT_RESTRICT_IND 0 0 3 GNUM_SCREEN_IND 0 0 3 OFCI_CUG_IND 0 0 3 OFCI_SEG_IND 0 0 1 OFCI_CLI_REQ_IND 0 0 1 USI_CODE_STD 0 0 3 USI_INFO_TRANS_CAP 0 8 24 USI_TRANS_MODE 0 0 2 USI_INFO_TRANS_RATE 16 0 24 USI_STRUCT -1 0 7 USI_CFG -1 0 3 USI_ESTABLISH -1 0 3 USI_SYMMETRY -1 0 3 USI_INFO_DTO_TRANS_RATE -1 0 24 USI_L1_IDENT 1 0 1 USI_L1_USR_INFO 2 0 63 USI_L2_IDENT -1 0 2 USI_L2_USR_INFO -1 0 63 USI_L3_IDENT -1 0 3 USI_L3_USR_INFO -1 0 63 LNUM_NOA_IND 1 0 255 LNUM_NII_IND 0 0 1 LNUM_NUMBER_PLAN 1 0 7 LNUM_PRESENT_RESTRICT_IND 0 0 3 LNUM_SCREEN_IND 0 0 3 CAID_NETWORK_ID_PLAN 0 0 2 CAID_NETWORK_ID_TYPE 0 0 2
Avaya CCSS 1000/2000 Feature Documentation August 2013 59 Configuration
ISUP PARAMETER DEFAULT VALUE RANGE ( CCME_DEFAULT) (VALUE) Min Value Max Value CAID_CARRIER_ID 0 0 1 CHNM_NOA_IND 0 0 7 CHNM_NUMBER_PLAN 0 0 7 OLI_LINEINFO 0 0 255 END_OF_PARAMETER 0 0 0 BACI_CHARGE_IND 0 0 3 BACI_CDP_STAT_IND 0 0 3 BACI_CDP_CAT_IND 0 0 3 BACI_EE_METHOD_IND 0 0 3 BACI_INTERNETWORK_IND 0 0 1 BACI_EE_INFO_IND 0 0 1 BACI_ISUP_IND 0 0 1 BACI_HOLD_IND 0 0 1 BACI_ISDN_ACCESS_IND 0 0 1 BACI_ECHO_CONTROL_IND 0 0 1 BACI_SCCP_METHOD_IND 0 0 3 OBI_INBAND_IND 0 0 1 OBI_FORWARD_IND 0 0 1 CONN_NOA_IND 0 0 1 CONN_NUMBER_PLAN 0 0 1 CONN_ADD_PRSNT_RESTRICT_I 0 0 1 ND CONN_SCREEN_IND 0 0 1 EVI_EVI_IND 0 0 255 EVI_EVENT_PRESENT_RESTRIC 0 0 7 T_IND CAU_EXT_IND1 0 0 1 CAU_CODING_STANDARD 0 0 3 CAU_LOCATION 0 0 15 CAU_EXT_IND1A 0 0 1 CAU_RECOMMENDATION 0 0 6
60 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Configuration Commands
ISUP PARAMETER DEFAULT VALUE RANGE ( CCME_DEFAULT) (VALUE) Min Value Max Value CAU_EXT_IND2 2 0 7 CAU_CAUSE_VAL 16 0 127 CAU_COND_COND 0 0 2 CAU_COND_EXT_IND3 0 0 1 CAU_COND_ATT_NUM -1 -1 -1 CAU_COND_EXT_IND3A 0 0 1 CAU_COND_REJ_ATTRIB -1 -1 -1 CAU_COND_EXT_IND3B 0 0 1 CAU_COND_AVAIL_ATTRIB -1 -1 -1 CAU_COND_PARM_NAM -1 -1 -1 CAU_EXT_IND1 0 0 1 SPC_SPC 0 0 55555 SUS_RES_SRI 0 0 1
Note: A value of -1 indicates the parameter will not be sent to the network.
CONFIG CCME_STANDBY_MAP
This command is used in LineID mode only when MPS N+1 Call Protect is configured. This command occurs once for each Active PROXY host (defined in a previous CONFIG CCME_PROXY_HOST command) that is capable of supporting LineID mode and Call Protect. When Call Protect is configured on an MPS N+1 platform, two APs (identified by PROXY hostname and VPS or MPS component number) control a single TMS. One AP is referred to as the primary/Active MPS and the other is the secondary/standby MPS. The CCSS must be configured to identify both the primary and secondary MPSs and the component numbers on each MPS that are associated with each cluster. The primary MPS is configured as opposed to secondary MPS by the CONFIG CCME_STANDBY_MAP command. CONFIG CCME_STANDBY_MAP=MAP_GRP, CCME_PROXY_HOST=alias, VPS=#, CCME_PROXY_STANDBY_HOST=alias, STANDBY_MPS=#; CCME_STANDBY_MAP Call control active or primary to secondary or standby mapping. This command is an alphanumeric number. CCME_PROXY_HOST Alias name from a prior CONFIG CCME_PROXY_HOST command.
Avaya CCSS 1000/2000 Feature Documentation August 2013 61 Configuration
CCME_PROXY_STANDBY_HOST Alias name from a prior CONFIG CCME_PROXY_STANDBY_HOST command. VPS / STANDBY_MPS Define the component number that is serving the Primary and Secondary APs on an N+1 cluster. Example: CONFIG CCME_STANDBY_MAP=MAP1, CCME_PROXY_HOST=SCN1, VPS=1, CCME_PROXY_STANDBY_HOST= SCN2, STANDBY_MPS=101;
CONFIG CCME_PROXY_STANDBY_HOST
Identifies a standby proxy host on an MPS N+1 cluster and the host names. CONFIG CCME_PROXY_STANDBY_HOST=alias, HOSTNAMES=hostname1 [, hostname2]; CCME_PROXY_STANDBY_HOST Alias name for the standby proxy host used in CCME configuration commands when referring to this host. HOSTNAMES The number of LAN connections to the host and the hostnames used on each LAN connection. There may be one hostname or two hostnames (separated by a comma) for a dual-LAN connection. Example: CONFIG CCME_PROXY_STANDBY_HOST=SCN2, HOSTNAMES=scn2a, scn2b;
CONFIG CCME_MPSLINE_MAP_GRP
This command creates associations between CICs and LineIDs for a trunk group. The trunk# must have appeared in a previous CCME_PROXY_GRP command and symbolic_name is an alias from a prior CCME_TMS_HOST command. Consecutive LineIDs are mapped to the CICs in the trunk group, beginning with TMS=tms_num, CHASSIS=chassis_num, SLOT=slot_num, LINE = line_num. The TMS connection for the management of TMS channel states is made to the TMS host identified by symbolic_name. The CICs in group trunk# are associated with the TMS channels in the TMS span numbered span#. CONFIG CCME_MPSLINE_MAP_GRP=trunk#, TMS=tms_num, CHASSIS=chassis_num, SLOT=slot_num, LINE = line_num, CCME_TMS_HOST=symbolic_name, TMS_SPAN=span_num#; CCME_MPSLINE_MAP_GRP Call control circuit group number. The value is one of the trunk group numbers defined in a prior CONFIG TRK_GRP command. TMS TMS number.
62 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Configuration Commands
CHASSIS Chassis number. The number range is 1 to 15. SLOT Slot number 1 to 4. LINE Line number for the application (on the specified VPS) that services the first voice circuit group. The line numbers for the remaining circuits in the group are assigned sequentially. CCME_TMS_HOST Host alias name defined in a prior CONFIG CCME_TMS_HOST command. TMS_SPAN The span number of the TMS. The number range is 1 to 8. Example: CONFIG CCME_MPSLINE_MAP_GRP=1, TMS=1, CHASSIS=1, SLOT=1, LINE=1, CCME_TMS_HOST=DCC2K, TMS_SPAN=1;
CONFIG CCME_OPTION
Specifies call control option values. CONFIG CCME_OPTION=string, VALUE=value; CCME_OPTION Specifies the option name. VALUE New value for specified option. Example CONFIG CCME_OPTION=EXTENDED, VALUE=1;
Call Control Mode Options
CCME_OPTION Default Value Possible Values OVERLAP N Y or N SUPPRESS_ALARM N Y or N OVERRIDE_ACM N Y or N
Call Control Parameter Value Options
DEFAULT VALUE RANGE CCME OPTION (VALUE) Min Value Max Value ACM_BACI_M 0 0 1 E1_GROUP_STATUS 0 0 1 NO_DRS 0 0 1 ACM_BACI_BA 0 0 3
Avaya CCSS 1000/2000 Feature Documentation August 2013 63 Configuration
DEFAULT VALUE RANGE CCME OPTION (VALUE) Min Value Max Value ACM_BACI_DC 1 0 3 ACM_BACI_FE 1 0 3 ACM_BACI_HG 0 0 3 ACM_BACI_I 0 0 1 ACM_BACI_J 0 0 1 ACM_BACI_K 1 0 1 ACM_BACI_L 0 0 1 ACM_BACI_N 0 0 1 ACM_BACI_PO 0 0 3 AUTO_ACM 1 0 1 UUINFO_LEN 0 0 128 ACC_TRANS_LEN 0 0 128 EXTENDED 0 0 16 CDPN_LEN 18 18 64 TCAP_MODE 0 0 1 AUTO_BLOCK_CIRCUITS 0 0 1 OLD_ALARM_DATE_FORMAT 0 0 1 ACM_OBI_A 0 0 1 ACM_CDVI_CBA 0 0 7 ACM_CDVI_GFED 0 0 15 ACM_REDN_NOA_IND 0 0 127 ACM_REDN_INN_IND 0 0 1 ACM_REDN_NP_IND 0 0 7 ACM_CAUSE_LOCATION 0 0 15 ACM_CAUSE_CS 0 0 3 ACM_CAUSE_VALUE 0 0 127 ACM_ADI_A 0 0 1 ACM_GNNO 0 0 127 INCLUDE_OBI 0 0 1 INCLUDE_CDVI 0 0 1
64 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Data Link Configuration
DEFAULT VALUE RANGE CCME OPTION (VALUE) Min Value Max Value INCLUDE_CAUSE 0 0 1 INCLUDE_ADI 0 0 1 INCLUDE_GNNO 0 0 1 RELEASE_LOCATION 0 0 10 OVERLAP_DEFLEN -1 1 64 TCAP_GRS 0 0 1
CONFIG CCME_TIMER
Changes the default timer value for the specified CCME protection timer. CONFIG CCME_TIMER=name, VALUE=value; CCME_TIMER Defines the timer name (P0-P13). VALUE Timer value in seconds. Example CONFIG CCME_TIMER=P13,VALUE=15;
For configurable timers and values see CCME Timers on page 481.
Data Link Configuration
The Avaya MPS platform is distributed with DCC3K SS7 data link hardware for the CCSS software package. This section outlines the CCSS SS7 data link hardware and the data link configuration procedures.
DCC3K Data Link Configuration
By adding a DCC3K card to a TMS that has a DCC/PLI card the resulting combination has the ability to support SS7 data links. Each TMS can support up to eight T1/E1 spans. Each DCC3K card with CCSS SS7 software can support two datalinks without resource contention. However, CCSS SS7 software can be configured for one to 16 DCCSS7 links. The additional DCC3K card with a SS7 software load is called a DCCSS7.
Avaya CCSS 1000/2000 Feature Documentation August 2013 65 Configuration
DCCSS7 Ethernet connections
Configuration in the ss7.conf file uses the commands, CONFIG DCCHOST on page 41 and CONFIG DCCLINK on page 41 to configure the DCC3K data link. A separate CONFIG DCCLINK command must be specified for each link. CONFIG DCCLINK command (ss7.conf)
CONFIG DCCHOST=dccl1, HOST=dcclink1; CONFIG DCCHOST=dccl2, HOST=dcclink2; CONFIG DCCLINK=link1, SLC=0, DCCHOST=dccl1, PRIORITY=0, CHASSIS=1, BPS=2,
66 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] DCCSS7 Ethernet connections
SLOT=2, SPAN=1, CHANNEL=24, SS7SPAN=1, SS7CHAN=1, BR=64000; CONFIG DCCLINK=link2, SLC=1, DCCHOST=dccl1, PRIORITY=0, CHASSIS=1, BPS=2, SLOT=2, SPAN=2, CHANNEL=24, SS7SPAN=1,SS7CHAN=2, BR=64000; CONFIG DCCLINK=link3, SLC=3, DCCHOST=dccl2, PRIORITY=0, CHASSIS=2, BPS=4, SLOT=2, SPAN=1, CHANNEL=24, SS7SPAN=1, SS7CHAN=1, BR=64000; CONFIG DCCLINK=link4, SLC=4, DCCHOST=dccl2, PRIORITY=0, CHASSIS=2, BPS=4, SLOT=2, SPAN=2, CHANNEL=24, SS7SPAN=1, SS7CHAN=2, BR=64000;
The CHASSIS, BPS, SLOT, SPAN, CHANNEL, SS7SPAN, and SS7CHAN fields must match up with appropriate entries in the tms.cfg configuration file.The tms.cfg configuration file contains configuration information for the TMS. tms.cfg configuration parameters
Example for E1 configuration ;------; TMS PLI Span SRV Mps Out Pool Protocol Options ; Num Slot Num type Num line Pkg List ;------LOAD 1 4 1 SS7 - - - e1_mf_ss7_proto.cfg B=1-15:17-31 D=16 LOAD 1 4 2 SS7 - - - e1_mf_ss7_proto.cfg B=1-15:17-31 D=16 LOAD 1 4 3 SS7 - - - e1_mf_ss7_proto.cfg B=1-15:17-31 D=16 LOAD 1 4 4 SS7 - - - e1_mf_ss7_proto.cfg B=1-15:17-31 D=16 LOAD 1 4 5 SS7 - - - e1_mf_ss7_proto.cfg B=1-15:17-31 D=16 LOAD 1 4 6 SS7 - - - e1_mf_ss7_proto.cfg B=1-15:17-31 D=16 LOAD 1 4 7 SS7 - - - e1_mf_ss7_proto.cfg B=1-15:17-31 D=16 LOAD 1 4 8 SS7 - - - e1_mf_ss7_proto.cfg D=1:3
[SS7] ;------; TMS PLI Span Chan SS7 Span Chan ; Num Slot Num Num Slot Num Num ;------SS7MAP 1 4 1 16 2 1 1 SS7MAP 1 4 2 16 2 1 2 SS7MAP 1 4 3 16 2 1 3 SS7MAP 1 4 4 16 2 1 4 SS7MAP 1 4 5 16 2 1 5 SS7MAP 1 4 6 16 2 1 6 SS7MAP 1 4 7 16 2 1 7 SS7MAP 1 4 8 1 2 1 8 SS7MAP 1 4 8 3 2 1 9
Note: Contiguous D channels cannot be configured. Table 2: BR values to be specified in ss7.conf based protocol config files
MODE SPAN PROTOCOL BR Values TMS t1_sf_ss7_proto.cfg 56000 TMS t1_esf_ss7_proto.cfg 64000 TMS e1_mf_ss7_proto.cfg 64000
Avaya CCSS 1000/2000 Feature Documentation August 2013 67 Configuration
MODE SPAN PROTOCOL BR Values PROXY t1_sf_ss7_proxy_proto.cfg 56000 PROXY t1_esf_ss7_proxy_proto.cfg 64000 PROXY e1_mf_ss7_proxy_proto.cfg 64000
In the tms.cfg file, SS7MAP lines maps to a LOAD line. The DCC3K SS7 Span Num and Chan Num, map to the TMS Span Num and the D channels as specified in corresponding LOAD lines.
TMS Configuration Through MPS Manager
The following steps demonstrate the procedure for configuring the tms.cfg file through the MPS Manager. 1. Open the MPS Control Center for the MPS component by clicking on Control Center icon in MPS Manager GUI. In the MPS Control Center box, click the MPS Configuration icon as shown in the following diagram. This will open the MPS configurator GUI.
68 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] TMS Configuration Through MPS Manager
2. In the MPS configurator GUI, select the TMS component you want to configure. By selecting the T1/E1 Card you can view the existing Protocol and Line Mapping for the spans as shown in the following diagram. You can add or remove the spans in the window.
3. Select the T1/E1 span for changing the protocols. The drop down as shown in the diagram will display the protocol list to chose from. Select the protocol to use. Click the Change button.
Avaya CCSS 1000/2000 Feature Documentation August 2013 69 Configuration
The following is the mapping of the protocols in the window with the .cfg files present in $MPSHOME/common/etc/tms. • TMS Integrated Mode
t1_esf_ss7_proto.cfg SS7 T1 ESF 64K Signalling t1_sf_ss7_proto.cfg SS7 T1 SF 56K Signalling e1_mf_ss7_proto.cfg SS7 E1 MF 64K Signalling
• Proxy Mode
t1_esf_ss7_proxy_proto.cfg SS7 T1 ESF 64K Signalling t1_sf_ss7_proxy_proto.cfg SS7 T1 SF 56K Signalling e1_mf_ss7_proxy_proto.cfg SS7 E1 MF 64K Signalling
These settings should match the settings in ss7.conf file in $CCSSHOME/etc.
4. Click the CCSS (SS7) button to configure Data Link channel. Set the channel to be used as Data Link Channel as shown in the following diagram and press Apply. The Bearer channels are automatically selected. These settings should match the ss7.conf file settings in $CCSSHOME/etc. You can view the ss7.conf by clicking on the ss7.conf button.
70 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] SS7/C7 Network Configuration
5. Press Save to save the configuration in the $MPSHOME/common/etc/tms/tms.cfg file.
SS7/C7 Network Configuration
MTP3 Layer 3 Configuration
Own Signaling Point
The Signaling Point Code (SPC) and Network Indicator (NI) are set in the server software installation and are determined by the signaling provider. The SPC is used as a unique address for the server node. The NI specifies the type of network that the server communicates with the other nodes.
Linksets and Links
MTP communicates to other SS7 nodes using links. Multiple links to the same SS7 node are linksets.
Avaya CCSS 1000/2000 Feature Documentation August 2013 71 Configuration
In the preceding diagram, a link is the connection between the two SS7 nodes (Link A or Link B). Links A and B combine to make a linkset. In an F-link configuration, one node is the CCSS 1000/2000 and the other node is a switch (an SSP). In an A-link configuration, one node is the CCSS 1000/2000 and the other node is an STP. Linksets are configured by the user in the ss7.conf file.
Combined Linksets
A combined linkset is a group of linksets that can be used for messaging between two SS7 nodes that are not directly connected.
In the preceding diagram, a message going from node A to node D can use either Linkset 1 or Linkset 2. Linksets 1 and 2 form a Combined Linkset. Combined Linksets are configured by the user in the ss7.conf file.
Routes
A route is a path of linksets between the source and destination SS7 nodes.
72 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] F-Link Configuration Examples
In the preceding diagram, a route between nodes A and D can be the A-C, C-D linksets, the A-B, B-D linksets or the A-E, E-D linksets. The routes are assigned a priority and MTP tries to use the route with the highest priority. Routes are assigned a priority by the order in the ss7.conf file. Routes are configured by the user in the ss7.conf file.
F-Link Configuration Examples
Commands in the ss7.conf configuration file are required for an F link configuration. sample F-link configuration (ss7.conf)
# CCSS node CONFIG NODE=A1, OPC=2065, TYPE=SEP;
# MTP configuration CONFIG DCCHOST=dccl1, HOST=dcclink1; CONFIG DCCLINK=link1, SLC=0, DCCHOST=dccl1, PRIORITY=0, CHASSIS=2, BPS=2, SLOT=4, SPAN=1, CHANNEL=24, SS7SPAN=1, SS7CHAN=1, BR=64000; CONFIG DCCLINK=link2, SLC=1, DCCHOST=dccl1, PRIORITY=0, CHASSIS=2, BPS=2, SLOT=4, SPAN=2, CHANNEL=24, SS7SPAN=1, SS7CHAN=2, BR=64000; CONFIG DCCLINK=link1, SLC=0, DCCHOST=dccl1, PRIORITY=0, CHASSIS=2, BPS=3, SLOT=4, SPAN=1, CHANNEL=24, SS7SPAN=1, SS7CHAN=1, BR=64000; CONFIG DCCLINK=link2, SLC=1, DCCHOST=dccl1, PRIORITY=0, CHASSIS=2, BPS=3, SLOT=4, SPAN=2, CHANNEL=24, SS7SPAN=1, SS7CHAN=2, BR=64000; CONFIG LINKSET=ls1, DPC=2067, TYPE=FLINK, ACTIVELINK=2, LINKS=link1,link2; CONFIG LINKSET=ls2, DPC=2068, TYPE=FLINK, ACTIVELINK=2, LINKS=link3,link4; CONFIG CMB_LINKSET=cs1, LSETS=ls1; CONFIG CMB_LINKSET=cs2, LSETS=ls2; CONFIG ROUTE=rt1, DPC=2067, LSETS=cs1; CONFIG ROUTE=rt2, DPC=2068, LSETS=cs1;
Avaya CCSS 1000/2000 Feature Documentation August 2013 73 Configuration
A-Link Configuration Examples
Commands required for A link configuration: sample A-link configuration (ss7.conf)
#configure signaling point CONFIG NODE=CCSSA, OPC=2065, TYPE=SEP;
# DCCSS7 hosts CONFIG DCCHOST=dccl1, HOST=dcclink1; CONFIG DCCHOST=dccl2, HOST=dcclink2;
# SS7 links CONFIG DCCLINK=link1, SLC=0, DCCHOST=dccl1, PRIORITY=0, CHASSIS=2, BPS=1, SLOT=4, SPAN=1, CHANNEL=24, SS7SPAN=1, SS7CHAN=1, BR=64000; CONFIG DCCLINK=link2, SLC=1, DCCHOST=dccl1, PRIORITY=0, CHASSIS=2, BPS=1, SLOT=4, SPAN=2, CHANNEL=24, SS7SPAN=1, SS7CHAN=2, BR=64000; CONFIG DCCLINK=link3, SLC=2, DCCHOST=dccl2, PRIORITY=0, CHASSIS=2, BPS=2, SLOT=4, SPAN=1, CHANNEL=24, SS7SPAN=1, SS7CHAN=1, BR=64000; CONFIG DCCLINK=link4, SLC=3, DCCHOST=dccl2, PRIORITY=0, CHASSIS=2, BPS=2, SLOT=4, SPAN=2, CHANNEL=24, SS7SPAN=1, SS7CHAN=2, BR=64000;
# link sets CONFIG LINKSET=ls1, DPC=2066, TYPE=ALINK, ACTIVELINK=2, LINKS=link1,link2; CONFIG LINKSET=ls2, DPC=2067, TYPE=ALINK, ACTIVELINK=2, LINKS=link3,link4;
# combined linksets for the STP routes CONFIG CMB_LINKSET=stpcls1, LSETS=ls1, ls2; CONFIG CMB_LINKSET=stpcls2, LSETS=ls2, ls1;
# routes for the STP CONFIG ROUTE=stpr1, DPC=2066, LSETS=stpcls1; CONFIG ROUTE=stpr2, DPC=2067, LSETS=stpcls2;
# combined linksets for the ISUP DPCs CONFIG CMB_LINKSET=cs1, LSETS=ls1, ls2; CONFIG CMB_LINKSET=cs2, LSETS=ls2, ls1;
# routes for the ISUP DPCs CONFIG ROUTE=rt1, DPC=2068, LSETS=cs1; CONFIG ROUTE=rt2, DPC=2069, LSETS=cs2;
Sequential SLS based load sharing across linksets
The CCSS server has the capability of varying the default load sharing mechanism by introducing a MGMT_OPTION command with the option set to SEQUENTIAL_LOADSHARE and the value set to 1 in the ss7.conf file.
74 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Sequential SLS based load sharing across linksets
This command enables the CCSS server to assign SLS values in a sequential manner to the links in a particular linkset. This mechanism is shown in the following example. In this example, the CCSS system is connected to two STPs through two combined linksets. Sequential SLS based load sharing across linksets
CONFIG DCCLINK=link1, SLC=0, HOST=dccl1, PRIORITY=0, CHASSIS=2, BPS=1, SLOT=4, SPAN=3,CHANNEL=16, SS7SPAN=1, SS7CHAN=3, BR=64000;
CONFIG DCCLINK=link2, SLC=1, HOST=dccl1, PRIORITY=0, CHASSIS=2, BPS=1, SLOT=4, SPAN=4,CHANNEL=16, SS7SPAN=1, SS7CHAN=4, BR=64000;
CONFIG DCCLINK=link3, SLC=0, HOST=dccl1, PRIORITY=0, CHASSIS=2, BPS=1, SLOT=4, SPAN=1,CHANNEL=16, SS7SPAN=1, SS7CHAN=1, BR=64000;
CONFIG DCCLINK=link4, SLC=1, HOST=dccl1, PRIORITY=0, CHASSIS=2, BPS=1, SLOT=4, SPAN=8,CHANNEL=16, SS7SPAN=1, SS7CHAN=8, BR=64000;
CONFIG LINKSET=ls1, DPC=2067, TYPE=FLINK, ACTIVELINK=2, LINKS=link1, link2;
CONFIG LINKSET=ls2, DPC=2068, TYPE=FLINK, ACTIVELINK=2, LINKS=link3, link4;
CONFIG CMB_LINKSET=stp_cs1, LSETS=ls1, ls2;
CONFIG CMB_LINKSET=stp_cs2, LSETS=ls2, ls1;
In the previous sample configuration, the CCSS server has four links. Two links are configured to STP with point code 2068 and the other two links are configured to connect to STP 2067. In the default load sharing mechanism provided by CCSS, the SLS values received at the STPs are either only odd or only even. In the previous sample configuration, the CCSS first selects linkset ls1, link1 and assigns SLS 0. In the next iteration, linkset ls2, link3 is selected and SLS 1 is assigned. Ultimately, the SLS to link mapping will look like the following sample.
Linkset Link SLS ls1 link1 0 ls2 link3 1 ls1 link2 2 ls2 link4 3 ls1 link1 4 ls2 link3 5 ls1 link2 6 ls2 link4 7 ls1 link1 8
Avaya CCSS 1000/2000 Feature Documentation August 2013 75 Configuration
ls2 link3 9 ls1 link2 10 ls2 link4 11 ls1 link1 12 ls2 link3 13 ls1 link2 14 ls2 link4 15
The default load sharing mechanism causes all even SLS values to be assigned to the first linkset and the odd SLS values to be assigned to the second linkset. By enabling the SEQUENTIAL_LOADSHARE in the ss7.conf file, you can alter this mechanism of even and odd load sharing between linksets to provide a desired effect. In the following example, the CCSS distributes the SLS values equally between the configured linksets and assigns the SLS values to the links in a given linkset in a sequential fashion. In the following example, you can see SLS to link mapping in sequential load sharing.
Linkset Link SLS ls1 link1 0 ls1 link2 1 ls1 link1 2 ls1 link2 3 ls1 link1 4 ls1 link2 5 ls1 link1 6 ls1 link2 7 ls2 link3 8 ls2 link4 9 ls2 link3 10 ls2 link4 11 ls2 link3 12 ls2 link4 13 ls2 link3 14 ls2 link4 15
76 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Linkset Redundancy between TMSs
Linkset Redundancy between TMSs
The links of a linkset can be taken from multiple TMSs which ensures that if one TMS fails, the link from the other TMS can handle the traffic. That is, link1 can be taken from TMS1 and link2 from TMS2. As part of load sharing provided by MTP3, the traffic is distributed over link1 and link2 equally. When link1 is brought down then all of the traffic goes to link2. If TMS1 crashes and brings down span1, there will be no TMS1 related traffic, other than maintenance (that is, block messages going over link2). Traffic for TMS2 is carried over link2. The following diagrams give the F-link and A-link configuration for network redundancy.
F-link Configuration
sample F-link configuration (ss7.conf)
CONFIG DCCHOST=dcc3k1, HOST=dccss7_tms1; CONFIG DCCHOST=dcc3k2, HOST=dccss7_tms2; CONFIG DCCLINK=link1, SLC=0, DCCHOST=dcc3k1, PRIORITY=0, CHASSIS=1, BPS=1, SLOT=4, SPAN=1, CHANNEL=24, SS7SPAN=1, SS7CHAN=1, BR=64000; CONFIG DCCLINK=link2, SLC=1, DCCHOST=dcc3k2, PRIORITY=0, CHASSIS=1, BPS=2, SLOT=4, SPAN=1, CHANNEL=24, SS7SPAN=1, SS7CHAN=1, BR=64000; CONFIG LINKSET=ls1, DPC=2067, TYPE=FLINK, ACTIVELINK=2, LINKS=link1, link2; CONFIG CMB_LINKSET=cs1, LSETS=ls1; CONFIG ROUTE=rt1, DPC=2067, LSETS=cs1; CONFIG TRK_GRP=1, CIR_GRP=0, GRP_TYPE=T1, DPC=2067; CONFIG TRK_GRP=2, CIR_GRP=1, GRP_TYPE=T1, DPC=2067; CONFIG CCME_TMS_HOST=TMSHOST1, HOSTNAMES=tms1; CONFIG CCME_TMS_HOST=TMSHOST2, HOSTNAMES=tms2; CONFIG CCME_TMS_GRP=1, CCME_TMS_HOST=TMSHOST1, TMS_SPAN=1; CONFIG CCME_TMS_GRP=2, CCME_TMS_HOST=TMSHOST2, TMS_SPAN=1;
sample F-link configuration (ss7.conf)
Avaya CCSS 1000/2000 Feature Documentation August 2013 77 Configuration
[DTCMAP] ;------; TMS PLI Span SRV Mps Out Pool Protocol Options ; Num Slot Num type Num line Pkg List ;------LOAD 1 4 1 - - - - t1_esf_ss7_proxy_proto.cfg B=1-23 D=24 LOAD 2 4 1 - - - - t1_esf_ss7_proxy_proto.cfg B=1-23 D=24 ;------
[SS7] ;------; TMS PLI Span Chan SS7 Span Chan ; Num Slot Num Num Slot Num Num ;------SS7MAP 1 4 1 24 2 1 1 SS7MAP 2 4 1 24 2 1 1
A-link Configuration
sample A-link configuration (ss7.conf)
CONFIG DCCHOST=dcc3k1, HOST=dccss7_tms1; CONFIG DCCHOST=dcc3k2, HOST=dccss7_tms2;
78 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] A-link Configuration
# TMS1 CONFIG DCCLINK=link1, SLC=0, DCCHOST=dcc3k1, PRIORITY=0, CHASSIS=1, PS=1, SLOT=2, SPAN=1, CHANNEL=24, SS7SPAN=1, SS7CHAN=1, BR=64000; CONFIG DCCLINK=link2, SLC=1, DCCHOST=dcc3k1, PRIORITY=0, CHASSIS=1, BPS=1, SLOT=2, SPAN=2, CHANNEL=24, SS7SPAN=1, SS7CHAN=2, BR=64000; # TMS2 CONFIG DCCLINK=link3, SLC=0, DCCHOST=dcc3k2, PRIORITY=0, CHASSIS=1, BPS=2, SLOT=2, SPAN=1, CHANNEL=24, SS7SPAN=1, SS7CHAN=1, BR=64000; CONFIG DCCLINK=link4, SLC=1, DCCHOST=dcc3k2, PRIORITY=0, CHASSIS=1, BPS=2, SLOT=2, SPAN=2, CHANNEL=24, SS7SPAN=1, SS7CHAN=2, BR=64000; CONFIG LINKSET=LS1,DPC=2066,TYPE=ALINK,ACTIVELINK=2,LINKS=link1, link3; CONFIG LINKSET=LS2,DPC=2067,TYPE=ALINK,ACTIVELINK=2,LINKS=link2, link4; #Combined Linksets for STP CONFIG CMB_LINKSET=stpcs1, LSETS=LS1, LS2; CONFIG CMB_LINKSET=stpcs2, LSETS=LS2, LS1; #Routes for STP CONFIG ROUTE=stprt1, DPC=2066, LSETS=stpcs1; CONFIG ROUTE=stprt2, DPC=2067, LSETS=stpcs2; #Combined Linkset for ISUP DPC CONFIG CMB_LINKSET=cs1, LSETS=LS1, LS2; #Route for ISUP DPC CONFIG ROUTE=rt1, DPC=2068, LSETS=cs1; CONFIG TRK_GRP=1, CIR_GRP=0, GRP_TYPE=T1, DPC=2068; CONFIG TRK_GRP=2, CIR_GRP=1, GRP_TYPE=T1, DPC=2068; CONFIG CCME_TMS_HOST=TMSHOST1, HOSTNAMES=tms1; CONFIG CCME_TMS_HOST=TMSHOST2, HOSTNAMES=tms2; CONFIG CCME_TMS_GRP=1, CCME_TMS_HOST=TMSHOST1, TMS_SPAN=3; CONFIG CCME_TMS_GRP=2, CCME_TMS_HOST=TMSHOST2, TMS_SPAN=3;
sample A-link configuration (tms.cfg)
[DTCMAP] ;------; TMS PLI Span SRV Mps Out Pool Protocol Options ; Num Slot Num type Num line Pkg List ;------LOAD 1 4 1 - - - - t1_esf_ss7_proxy_proto.cfg D=24 LOAD 1 4 2 - - - - t1_esf_ss7_proxy_proto.cfg D=24 LOAD 1 4 3 - - - - t1_esf_ss7_proxy_proto.cfg B=1-24 LOAD 2 4 1 - - - - t1_esf_ss7_proxy_proto.cfg D=24 LOAD 2 4 2 - - - - t1_esf_ss7_proxy_proto.cfg D=24 LOAD 2 4 3 - - - - t1_esf_ss7_proxy_proto.cfg B=1-24 ;------[SS7] ;------; TMS PLI Span Chan SS7 Span Chan ; Num Slot Num Num Slot Num Num ;------SS7MAP 1 4 1 24 2 1 1 SS7MAP 1 4 2 24 2 1 2 SS7MAP 2 4 1 24 2 1 1 SS7MAP 2 4 2 24 2 1 2
Avaya CCSS 1000/2000 Feature Documentation August 2013 79 Configuration
F-Link Configuration
The ss7.conf.sample file, needed for the F-Link configuration, is located in $CCSSHOME/etc/ ss7.conf.sample.
Note: Note the order and syntax when configuration or modification is done in the ss7.conf file. It is important to follow this order. The order for configuration modification is: 1. Node 2. Links 3. Linksets 4. Combined Linksets 5. Routes 6. Trunkgroups For a description on links, linksets, and routes, see SS7/C7 Network Configuration on page 71. ss7.conf.sample file
# CCSS node CONFIG NODE=A1, OPC=2068, TYPE=SEP;
# MTP configuration CONFIG DCCHOST=dccl1, HOST=dcclink1; CONFIG DCCLINK=link1, SLC=0, DCCHOST=dccl1, PRIORITY=0, CHASSIS=2, BPS=2, SLOT=4, SPAN=1, CHANNEL=24, SS7SPAN=1, SS7CHAN=1, BR=64000; CONFIG DCCLINK=link2, SLC=1, DCCHOST=dccl1, PRIORITY=0, CHASSIS=2, BPS=2, SLOT=4, SPAN=2, CHANNEL=24, SS7SPAN=1, SS7CHAN=2, BR=64000; CONFIG LINKSET=ls1, DPC=2067, TYPE=FLINK, ACTIVELINK=2, LINKS=link1,link2; CONFIG CMB_LINKSET=cs1, LSETS=ls1; CONFIG ROUTE=rt1, DPC=2067, LSETS=cs1;
#ISUP configuration CONFIG TRK_GRP=1, CIR_GRP=0, GRP_TYPE=T1, DPC=2067; CONFIG TRK_GRP=2, CIR_GRP=1, GRP_TYPE=T1, DPC=2067; CONFIG TRK_GRP=3, CIR_GRP=2, GRP_TYPE=T1, DPC=2067; CONFIG TRK_GRP=4, CIR_GRP=3, GRP_TYPE=T1, DPC=2067;
# Call-control configuration CONFIG CCME_PROXY_HOST=VAS1, HOSTNAMES=vps1; CONFIG CCME_PROXY_GRP=1, CCME_PROXY_HOST=VAS1, VPS=1, LINE=1; CONFIG CCME_PROXY_GRP=2, CCME_PROXY_HOST=VAS1, VPS=1, LINE=25; CONFIG CCME_PROXY_GRP=3, CCME_PROXY_HOST=VAS1, VPS=1, LINE=49; CONFIG CCME_PROXY_GRP=4, CCME_PROXY_HOST=VAS1, VPS=1, LINE=73;
80 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] F-Link Configuration Examples
F-Link Configuration Examples
The following Diagram depicts a two node configuration deploying two F- Links with DCC3K cards.
A-Link Configuration Examples
The ss7.conf.sample.alink file shown, a sample needed for the A-Link configuration, is located in $CCSSHOME/etc/ss7.conf.sample.alink.
Avaya CCSS 1000/2000 Feature Documentation August 2013 81 Configuration
Note: The order and syntax for configuring or modifying the ss7.conf file is as follows: 1. Node 2. Links 3. Linksets 4. Combined Linksets 5. Routes 6. Trunkgroup For a description on links, linksets, and routes, see SS7/C7 Network Configuration on page 71. The following sample ss7.conf.sample.alink file matches the following diagram. ss7.conf.alink file
CONFIG NODE=CCSSA, OPC=2065, TYPE=SEP; # DCCSS7 host CONFIG DCCHOST=dccl1, HOST=dcclink1; # SS7 links CONFIG DCCLINK=link1, SLC=0, DCCHOST=dccl1, PRIORITY=0, CHASSIS=2, BPS=1, SLOT=4, SPAN=1, CHANNEL=24, SS7SPAN=1, SS7CHAN=1, BR=64000; CONFIG DCCLINK=link2, SLC=1, DCCHOST=dccl1, PRIORITY=0, CHASSIS=2, BPS=1, SLOT=4, SPAN=2, CHANNEL=24, SS7SPAN=1, SS7CHAN=2, BR=64000; CONFIG DCCLINK=link3, SLC=0, DCCHOST=dccl1, PRIORITY=0, CHASSIS=2, BPS=2, SLOT=4, SPAN=1, CHANNEL=24, SS7SPAN=1, SS7CHAN=1, BR=64000; CONFIG DCCLINK=link4, SLC=1, DCCHOST=dccl1, PRIORITY=0, CHASSIS=2, BPS=2, SLOT=4, SPAN=2, CHANNEL=24, SS7SPAN=1, SS7CHAN=2, BR=64000; # linksets CONFIG LINKSET=ls1, DPC=2066, TYPE=ALINK, ACTIVELINK=2, LINKS=link1,link2; CONFIG LINKSET=ls2, DPC=2067, TYPE=ALINK, ACTIVELINK=2, LINKS=link3,link4; # combined linksets for the STP routes CONFIG CMB_LINKSET=stpcls1, LSETS=ls1, ls2; CONFIG CMB_LINKSET=stpcls2, LSETS=ls2, ls1; # routes for the STPs CONFIG ROUTE=stpr1, DPC=2066, LSETS=stpcls1; CONFIG ROUTE=stpr2, DPC=2067, LSETS=stpcls2; # combined linkset for the SSPs (ISUP DPCs) CONFIG CMB_LINKSET=cs1, LSETS=ls1, ls2; CONFIG CMB_LINKSET=cs2, LSETS=ls2, ls1; # routes for the SSPs (ISUP DPCs) CONFIG ROUTE=rt1, DPC=2068, LSETS=cs1; CONFIG ROUTE=rt2, DPC=2069, LSETS=cs2 # ISUP Trunk Groups CONFIG TRK_GRP=1, CIR_GRP=0, GRP_TYPE=T1, DPC=2068; CONFIG TRK_GRP=2, CIR_GRP=1, GRP_TYPE=T1, DPC=2068; CONFIG TRK_GRP=3, CIR_GRP=0, GRP_TYPE=T1, DPC=2069; CONFIG TRK_GRP=4, CIR_GRP=1, GRP_TYPE=T1, DPC=2069; # MPS Host AP Lines CONFIG CCME_PROXY_HOST=VAS1, HOSTNAMES=vps1; CONFIG CCME_PROXY_GRP=1, CCME_PROXY_HOST=VAS1, VPS=1, LINE=1; CONFIG CCME_PROXY_GRP=2, CCME_PROXY_HOST=VAS1, VPS=1, LINE=25; CONFIG CCME_PROXY_GRP=3, CCME_PROXY_HOST=VAS1, VPS=1, LINE=49; CONFIG CCME_PROXY_GRP=4, CCME_PROXY_HOST=VAS1, VPS=1, LINE=73;
82 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] A-Link Configuration Examples
Note: This sample file provides a recommended configuration for ss7 a-links. This template should be strictly adhered to while setting up a-link configurations. The following lines configure the links.
# SS7 links CONFIG DCCLINK=link1, SLC=0, DCCHOST=dccl1, PRIORITY=0, CHASSIS=2, BPS=1, SLOT=4, SPAN=1, CHANNEL=24, SS7SPAN=1, SS7CHAN=1, BR=64000; CONFIG DCCLINK=link2, SLC=1, DCCHOST=dccl1, PRIORITY=0, CHASSIS=2, BPS=1, SLOT=4, SPAN=2, CHANNEL=24, SS7SPAN=1, SS7CHAN=2, BR=64000; CONFIG DCCLINK=link3, SLC=0, DCCHOST=dccl1, PRIORITY=0, CHASSIS=2, BPS=2, SLOT=4, SPAN=1, CHANNEL=24, SS7SPAN=1, SS7CHAN=1, BR=64000; CONFIG DCCLINK=link4, SLC=1, DCCHOST=dccl1, PRIORITY=0, CHASSIS=2, BPS=2, SLOT=4, SPAN=2, CHANNEL=24, SS7SPAN=1, SS7CHAN=2, BR=64000;
The following lines configure linksets. Traffic is balanced evenly across all links in a linkset.
CONFIG LINKSET=ls1, DPC=2066, TYPE=ALINK, ACTIVELINK=2, LINKS=link1,link2; CONFIG LINKSET=ls2, DPC=2067, TYPE=ALINK, ACTIVELINK=2, LINKS=link3,link4;
The following lines are required for STP configuration including two combined linksets. The combined linksets are normally setup in pairs. Each combined linkset lists the highest priority linkset first, the lower priority linksets next.
# combined linksets for the STP routes CONFIG CMB_LINKSET=stpcls1, LSETS=ls1, ls2; CONFIG CMB_LINKSET=stpcls2, LSETS=ls2, ls1; # routes for the STP CONFIG ROUTE=stpr1, DPC=2066, LSETS=stpcls1; CONFIG ROUTE=stpr2, DPC=2067, LSETS=stpcls2;
The route commands are listed in pairs (as shown in the preceding configuration). For the routing of traffic each of the STPs should always use the direct link to the STP as a priority. Hence traffic should route to DPC 2066 using ls1 as a priority and ls2 as a secondary. Traffic to DPC 2067 should route using ls2 as a priority and ls1 as a secondary. The following lines, found after the STP configuration lines, are for configuring the ISUP routes.This configuration shows the normal configuration for combined linkset, route, and ISUP trunk groups. A separate combined linkset is defined and is required for routes that are for ISUP. Combined linksets for the STP have a high and low priority mechanism. Combined linksets for ISUP have all linksets of the same priority and the linksets equally share load traffic.
# combined linkset for the ISUP DPC CONFIG CMB_LINKSET=cs1, LSETS=ls1, ls2; CONFIG CMB_LINKSET=cs2, LSETS=ls2, ls1;
Avaya CCSS 1000/2000 Feature Documentation August 2013 83 Configuration
CONFIG ROUTE=rt1, DPC=2068, LSETS=cs1; CONFIG ROUTE=rt2, DPC=2069, LSETS=cs2 CONFIG TRK_GRP=1, CIR_GRP=0, GRP_TYPE=T1, DPC=2068;
Caution: Configurations where ISUP SSP routes attempt to use the same combined linksets that were used by the STP routes will not work. The following diagram depicts multiple nodes connected through A-links using DCC3K cards.
ISUP Configuration
Note: The MPS host names must already be set in the server /etc/hosts file before performing the software installation. Complete the information worksheets in the Configuration Information Worksheets on page 375. This information is required to properly install the SS7 software.
84 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] ISUP Nodes
ISUP Nodes
An ISUP node is a signaling point on the SS7 network. In this configuration, the CCSS is the signaling point. This configuration information is set when configuring the server software, see A-Link Configuration Examples on page 81.
ISUP Circuit Groups
An ISUP circuit group is a group of T1/E1 circuits on the physical switch. In this configuration, a circuit group is a T1/E1 span. This configuration information is set when configuring the server software, see A-Link Configuration Examples on page 81.
ISUP Circuits
An ISUP circuit is an individual circuit from a circuit group. In this configuration, a circuit is a single line on a T1/E1 span. This configuration information is set when configuring the server software, see A-Link Configuration Examples on page 81. ss7.conf.sample file
#configure isup node CONFIG NODE=CCSSA, OPC=2068, TYPE=SEP; #configure circuit groups CONFIG TRK_GRP=1, CIR_GRP=0, GRP_TYPE=T1, DPC=2067; CONFIG TRK_GRP=2, CIR_GRP=1, GRP_TYPE=T1, DPC=2067; CONFIG TRK_GRP=3, CIR_GRP=2, GRP_TYPE=T1, DPC=2067; CONFIG TRK_GRP=4, CIR_GRP=3, GRP_TYPE=T1, DPC=2067; CONFIG CCME_PROXY_HOST=VAS1, HOSTNAMES=vps1; #isup circuits mapped to MPS lines CONFIG CCME_PROXY_GRP=1, CCME_PROXY_HOST=VAS1, VPS=1, LINE=1; CONFIG CCME_PROXY_GRP=2, CCME_PROXY_HOST=VAS1, VPS=1, LINE=25; CONFIG CCME_PROXY_GRP=3, CCME_PROXY_HOST=VAS1, VPS=1, LINE=49; CONFIG CCME_PROXY_GRP=4, CCME_PROXY_HOST=VAS1, VPS=1, LINE=73;
Avaya CCSS 1000/2000 Feature Documentation August 2013 85 Configuration
Mixed Mode System Configuration
A mixed system is a system that has ANSI and ITU variants configured on one CCSS server.
Note: The CCSS software version does not support a mixed system for configuring ITU (NATIONAL) and ITU (INTERNATIONAL) simultaneously. The software supports ITU and ANSI simultaneously.
Modify Commands
The following commands are primarily for advanced configuration of mixed systems. A mixed system is one that has multiple point codes. One is for ITU, and the other for ANSI. For a single- variant system, use the CONFIG VARIANT command. MODIFY NODE
Modifies the node to have variant and SSF values. MODIFY NODE=nodename, VARIANT=variant, SSF=val; NODE Node identifier configured in the CONFIG NODE command. VARIANT See CONFIG VARIANT on page 40 for supported variant values. SSF Supported subsystem field values: • NAT: National Network • INT: International Network • REV: Reserve • SPARE: Spare (for international use only)
MODIFY ROUTE
Configures the MTP3 and ISUP layers to route an ITU or ANSI message to the destination. MODIFY ROUTE=routename, VARIANT=variant; ROUTE Route identifier configured in the CONFIG ROUTE command. VARIANT See CONFIG VARIANT on page 40 for supported variant values.
86 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Modify Commands
MODIFY LINKSET
Configures the linkset of MTP3 to send a message to the user part. Note that this command does not contain a VARIANT parameter. MODIFY LINKSET=linkset_name, OPC=point code; LINKSET Linkset name configured in the CONFIG LINKSET command. OPC Origination Pointer Code
MODIFY LINK
Configures MTP2 and part of MTP3 to an appropriate variant. (Note that MTP2 does not differentiate between the ITU and ANSI variants.) MODIFY LINK=name, VARIANT=variant; LINK Link identifier configured in the CONFIG LINK command. VARIANT See CONFIG VARIANT on page 40 for supported variant values.
MODIFY LAYER
Forces to send all SCCP Management messages with a priority of 0. MODIFY LAYER=layer_name, MSU_PRIO_0=boolean; LAYER Specify LAYER=SCCP MSU_PRIO_0 Message Signal Unit. This parameter has two possible values: • TRUE: Force message priority of a specified layer to 0. • FALSE: Do not force message priority of a specified layer to 0.
Example MODIFY LAYER= SCCP, MSU_PRIO_0= TRUE;
MODIFY LAYER
Forces ISUP to send all messages with a priority of 0. ISUP messages are sent out depending on message priority. In some cases, ISUP messages are required to be sent with fixed priority (0). MODIFY LAYER=layer_name, MSU_PRIO_0=boolean; LAYER Specify LAYER=isup MSU_PRIO_0 Message Signal Unit. This parameter has two possible values: • TRUE:Force message priority of a specified layer to 0. • FALSE: Do not force message priority of a specified layer to 0.
Example MODIFY LAYER=isup, MSU_PRIO_0=TRUE;
Avaya CCSS 1000/2000 Feature Documentation August 2013 87 Configuration
MODIFY LAYER
Provides adjacent restart support option for MTP3 layer. MODIFY LAYER=MTP3, MSU_PRIO=priority, RESTART_REQD=0|1; LAYER Specify LAYER=MTP3 MSU_PRIO Message Signal Unit. This value will be used for all MTP3 messages having range of values starting from 0 through 3. RESTART_REQD Adjacent Restart support. Values are: • 1: Adjacent Restart is supported. • 0: Adjacent Restart not supported.
Examples MODIFY LAYER=MTP3, RESTART_REQD=1; MODIFY LAYER=MTP3, MSU_PRIO=1; MODIFY LAYER=MTP3, MSU_PRIO=1, RESTART_REQD=1;
MODIFY LAYER
Validation of Sub Service Field value on received Signal Unit at MTP3 layer. MODIFY LAYER=MTP3, SSFVALID=boolean; LAYER Specify LAYER=MTP3 SSFVALID Sub Service Field Validation. This parameter has two possible values: • TRUE:Sub Service Field Validation is turned on. • FALSE: Sub Service Field Validation is turned off.
Examples MODIFY LAYER=MTP3, SSFVALID=TRUE;
Note: The SSF Validation does NOT check the AB bits, only the CD bits of the SSF field. MODIFY LAYER
Provides number of retransmissions on a congested priority queue at MTP3 layer. MODIFY LAYER=MTP3, PRIO_0_QUEUE=32; LAYER Specify LAYER=MTP3 PRIO_0_QUEUE Specifies the count in bytes for the number of retransmissions on congestion at each priority ZERO queue. C7 system configures threshold values for congestion levels with multiples of PRIO_0_QUEUE, for priorities 1, 2, and 3. The value ranges from 1 to 32 (multiples of 2 is recommended)
88 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] ss7.conf Sample File
Example MODIFY LAYER=MTP3, PRIO_0_QUEUE=32;
Note: Only a mixed mode configuration that contains ANSI and ITU variants is supported. MODIFY LAYER
Configures the passOnFlag in ISUP to handle the unknown messages and parameters according to MCI and PCI instruction bits. MODIFY LAYER = ISUP, PASS_ON_FLAG = boolean; TRUE Ignores the PCI and MCI instruction bits when pass on is not possible. FALSE Handle the unknown parameters and messages according to the PCI and MCI instruction bits when pass on is not possible. Example MODIFY LAYER = ISUP, PASS_ON_FLAG = FALSE;
ss7.conf Sample File
The following is a sample ss7.conf file for a mixed system. This file assumes the linkset type is F-LINK. ss7.conf file for mixed systems
CONFIG NODE=A1, OPC=2065, TYPE=SEP; CONFIG NODE=A2, OPC=2066, TYPE=SEP; MODIFY NODE=A1, VARIANT=ITU, SSF=NAT; MODIFY NODE=A2, VARIANT=ANSI, SSF=NAT; CONFIG DCCHOST=dccl1, HOST=dcclink1; CONFIG DCCLINK=link1, SLC=0, DCCHOST=dccl1, PRIORITY=0, CHASSIS = 2, BPS=2, SLOT=4, SPAN=1, CHANNEL=24,SS7SPAN=1,SS7CHAN=1,BR=64000; CONFIG DCCLINK=link2, SLC=1, DCCHOST=dccl1, PRIORITY=0, CHASSIS = 2, BPS=2, SLOT=4, SPAN=2, CHANNEL=24,SS7SPAN=1,SS7CHAN=2,BR=64000; MODIFY LINK=link1, VARIANT=ITU; MODIFY LINK=link2, VARIANT=ANSI; CONFIG LINKSET=ls1, DPC=2067, TYPE=FLINK, ACTIVELINK=1, LINKS=link1; CONFIG LINKSET=ls2, DPC=2068, TYPE=FLINK, ACTIVELINK=1, LINKS=link2; MODIFY LINKSET=ls1, OPC=2065; MODIFY LINKSET=ls2, OPC=2066; CONFIG CMB_LINKSET=cs1, LSETS=ls1; CONFIG CMB_LINKSET=cs2, LSETS=ls2; CONFIG ROUTE=rt1, DPC=2067, LSETS=cs1; CONFIG ROUTE=rt2, DPC=2068, LSETS=cs2; MODIFY ROUTE=rt1, VARIANT=ITU; MODIFY ROUTE=rt2, VARIANT=ANSI;
Avaya CCSS 1000/2000 Feature Documentation August 2013 89 Configuration
CONFIG TRK_GRP=1, CIR_GRP=0, GRP_TYPE=T1, DPC=2067; CONFIG TRK_GRP=2, CIR_GRP=1, GRP_TYPE=T1, DPC=2068;
Note: The variant for the trunk group is derived from the variant specified in the modify route command in the ss7.conf file of the same DPC that the trunk group is configured for. For example, in the ss7.conf file previously mentioned, the mixed mode TRK_GRP 1 with DPC 2067 has an ITU variant whereas TRK_GRP 2 with DPC 2068 has an ANSI variant.
Changing the ISUP Variant
The ISUP variant is defined using the ss7.conf file. For additional information on variants, see CONFIG VARIANT on page 40. For additional information on Mixed mode, see Modify Commands on page 86.
ISUP Call Control Modes of Operation
Call Control Configuration
Call Control Modes of Operation
The newer version of CCSS supports only Proxy and TIM mode of operation.
90 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Call Control Modes of Operation
Mode SS7 Circuit Binding Signaling Data Path Circuit Status Awareness/Control Proxy Mode Applications have a All SS7 signaling CCSS does not make See Proxy static binding to a single data passes circuit status available. Mode ISUP circuit, defined by between the Applications fail to get the Configuratio CCSS Configuration applications and the CCSS Resource when a n CCSS server circuit is unavailable. Examples on through the proxy page 92. resource. SS7 data is manipulated through use of application folders and the "Access An External Resource" MPS Developer block. TMS Associations between All SS7 signaling The CCSS server reports Integrated TMS configuration and data passes circuit status to the TMS Mode CCSS configuration between the through a LAN connection See TMS create static bindings application and the to the TMS. Integrated between TMS and SS7 CCSS server From vshell, an operator Mode circuits. through a LAN may induce blocking of Configuratio connection to the circuits in the SS7 network, n on TMS. using various CCM page 94. SS7 data is commands. manipulated though use of an "SS7" toolkit. Hybrid Proxy Applications have a SS7 signaling data The CCSS server reports Mode static binding to a single for call setup and call circuit status to the TMS See Hybrid ISUP circuit, defined by tear down passes through a LAN connection Proxy Mode CCSS Configuration. between the to the TMS. The TMS Configuratio applications and the reports voice circuit status n on CCSS server to the CCSS using the page 96. through the proxy same LAN connection. resource. SS7 data From vshell, an operator is manipulated using may induce blocking of application folders circuits in the SS7 network, and the Access An using various CCM External Resource commands. block. LineID mode Applications send a SS7 signaling data The CCSS server reports (used for BIND message through for call setup and call circuit status to the TMS MPS N+1 the proxy resource to tear down passes through a LAN connection redundancy temporarily bind to a between the to the TMS. The TMS configuration circuit for the duration of applications and the reports the voice circuit only) a single call. The SS7 CCSS server status to the CCSS using See LineID circuit is identified in the through the proxy the same LAN connection. Mode BIND message using resource. SS7 data From vshell, you can cause
Avaya CCSS 1000/2000 Feature Documentation August 2013 91 Configuration
Mode SS7 Circuit Binding Signaling Data Path Circuit Status Awareness/Control Configuratio the Line Identifier is manipulated using circuit blocking in the SS7 n on returned by Get Line application folders network by using various page 99. Operation block (Line and the access an CCM commands. Ops). external Resource block.
Configuration Items
Each mode of operation requires unique configuration of various aspects of the system to work correctly. • Installation of compatible TMS and CCSS packages • CCSS configuration • TMS configuration • MPS Configuration For additional information on configuration items, see each individual mode of operation.
Proxy Mode Configuration Examples
Package Compatibility
For Proxy Mode the PERImps and PERItms packages are installed on the MPS application processor (SCN), and the PERIccss package is installed on the CCSS.
92 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Call Control Configuration for Proxy Mode
Call Control Configuration for Proxy Mode
Because there is no direct connection to the TMS in this mode, only the proxy connection must be configured in the $CCSSHOME/etc/ss7.conf file. The CCME_PROXY_HOST and CCME_PROXY_GROUP lines are required in the ss7.conf file. For each configured ISUP trunk group (CONFIG TRK_GRP=X command), there must be a proxy mapping of the circuits in ISUP trunkgroup X to application lines on an MPS Applicactions Proccessor (a corresponding CONFIG CCME_PROXY_GRP=X line). The following example maps the 60 circuits in E1 trunkgroups 1 and 2 to MPS (VPS) component number 1, lines 1 through 60 on the localhost. In this case the MPS AP and CCSS server are co-resident on the same Solaris 10 workstation.
CONFIG DCCHOST=dccl1, HOST=dcclink1b; CONFIG DCCLINK=link3, SLC=0, DCCHOST=dccl1, PRIORITY=0, CHASSIS = 2, BPS=2, SLOT=4, SPAN=2, CHANNEL=24,SS7SPAN=1,SS7CHAN=2,BR=64000; CONFIG TRK_GRP=1, CIR_GRP=0, GRP_TYPE=E1, DPC=5904; CONFIG CCME_PROXY_HOST=SCN1, HOSTNAMES=localhost; CONFIG CCME_PROXY_GRP=1, CCME_PROXY_HOST=SCN1, VPS=1, LINE=1; For additional information, see Call Control Configuration on page 90. In a variation of Proxy Mode called Hybrid Proxy Mode, there is a connection to the TMS for circuit status and maintenance messages only. As far as application flow, call setup and call tear-down procedures are concerned hybrid proxy mode is the same as proxy mode. See Hybrid Proxy Mode Configuration on page 96.
MPS Configuration For Proxy Mode
For the proxy software to run on the client MPS, the following line must be specified in the file gen.cfg ($MPSHOME/common/etc/gen.cfg) on the MPS system. $MPSHOME/common/etc/gen.cfg
# Example gen.cfg file. # # NAME NODE PORT is-VOS-CLASS PRI COMMAND LINE # proxy - - 0 0 "proxy -S ccss -L cons -l info -k 10 -n"
Avaya CCSS 1000/2000 Feature Documentation August 2013 93 Configuration
TCAPProxy Configuration
Add the following line to $MPSHOME/common/etc/gen.cfg to automatically start tcapproxy. $MPSHOME/common/etc/gen.cfg
# Example gen.cfg file. # # NAME NODE PORT is-VOS-CLASS PRI COMMAND LINE # tcapproxy - - 0 0 "tcapproxy -S tcap -s 9892 - L /opt/vps/common/log/tcapproxy.log -l deb1 -k 10 -n"
TMS Configuration
For proxy mode, there are some dependencies between TMS configuration and CCSS configuration. The LOAD command in file tms.cfg ($MPSHOME/common/etc/tms/tms.cfg) are affected
LOAD 2 4 1 SS7 - - - t1_sf_ss7_proxy_proto.cfg
In the LOAD command, the service type must be "SS7" for SS7 lines. The protocol configuration must be t1_sf_ss7_proxy_proto.cfg or t1_esf_ss7_proxy_proto.cfg for T1 spans and e1_mf_ss7_proxy_proto.cfg for E1 spans.
TMS Integrated Mode Configuration
Package Compatibility
Requires: • PERIccss on the CCSS server • PERImps and PERItms on the MPS applications processor.
94 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] CCSS Configuration
CCSS Configuration CCME_TMS_HOST and CCME_TMS_GRP In TMS Integrated mode, circuit status and call-related signaling are sent to the MPS and MPS applications through the TMS. CCSS configuration uses the CCME_TMS_HOST command to configure the TMS host names for the purposes of connecting to the TMS. The CCME_TMS_GRP command maps trunk groups (configured using the CONFIG TRK_GRP command) to spans on TMS hosts. Syntax: CONFIG CCME_TMS_HOST=symbolic_name,HOSTNAMES=host_name1,host_name2; Example: CONFIG CCME_TMS_HOST=TMS1, HOSTNAMES=dtc_b27a,dtc_b27b; The
... # ISUP trunk groups CONFIG TRK_GRP=1, CIR_GRP=0, GRP_TYPE=T1, DPC=2067; CONFIG TRK_GRP=2, CIR_GRP=1, GRP_TYPE=T1, DPC=2067; CONFIG TRK_GRP=3, CIR_GRP=2, GRP_TYPE=T1, DPC=2067; CONFIG TRK_GRP=4, CIR_GRP=3, GRP_TYPE=T1, DPC=2067;
Avaya CCSS 1000/2000 Feature Documentation August 2013 95 Configuration
# TMS host for TMS-Integrated Mode # Map TMS-Integrated Mode trunkgroups 1 through 4 to TMS1 spans 1 through 4 CONFIG CCME_TMS_HOST=TMS1, HOSTNAMES=tms1a, tms2a; CONFIG CCME_TMS_GRP=1, CCME_TMS_HOST=TMS1, TMS_SPAN=1; CONFIG CCME_TMS_GRP=2, CCME_TMS_HOST=TMS1, TMS_SPAN=2; CONFIG CCME_TMS_GRP=3, CCME_TMS_HOST=TMS1, TMS_SPAN=3; CONFIG CCME_TMS_GRP=4, CCME_TMS_HOST=TMS1, TMS_SPAN=4; ...
TMS Configuration
When TMS Integrated mode is used with a TMS system, there are some dependencies between TMS configuration and CCSS configuration. The following commands in file $MPSHOME/common/etc/tms/tms.cfg are affected:
LOAD 2 4 1 DSSI - -SS7In t1_esf_ss7_proto.cfg The protocol configuration must be t1_sf_ss7_proto..cfg or t1_esf_ss7_proto.cfg for T1 spans and e1_mf_ss7_proto.cfg for E1 spans.
Note: The associated link in the ss7.conf file must be configured with the appropriate BR value. If the link is using a sf configuration only a BR of 56000 is supported. The BR can be set to either 56000 or 64000 for an esf configuration.
Hybrid Proxy Mode Configuration
Package Compatibility
Requires: • PERIccss on the CCSS server • PERImps and PERItms on the MPS applications processor
96 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] CCSS Configuration
CCSS Configuration
In Hybrid Proxy Mode, the CCSS has a connection to both PROXY and TMS. The CCSS communicates circuit status and circuit maintenance messages with the TMS, through a connection to the TMS as configured in TMS Integrated Mode. The call establishment and call teardown messaging between the CCSS and the application is communicated through the Proxy API as in Proxy Mode. For Hybrid Proxy Mode the syntax of the CONFIG CCME_PROXY_GROUP is modified to include both the proxy host information (proxy host, mps component number and starting line) and the TMS host information (TMS host and span).
Syntax: CONFIG CCME_PROXY_GRP=trunk_group_number, CCME_PROXY_HOST=proxy_host_alias, VPS=component_number, LINE=start_line, CCME_TMS_HOST=tms_host_alias, TMS_SPAN=tms_span_number; Example:
CONFIG CCME_PROXY_GRP=2, CCME_PROXY_HOST=VAS1, VPS=2, LINE=31, CCME_TMS_HOST=TMS1, TMS_SPAN=2; The
Avaya CCSS 1000/2000 Feature Documentation August 2013 97 Configuration
The
CONFIG CCME_PROXY_HOST=VAS1, HOSTNAMES=mps03; CONFIG CCME_TMS_HOST=TMS1, HOSTNAMES=tms1; CONFIG CCME_TMS_HOST=TMS2, HOSTNAMES=tms2; CONFIG CCME_PROXY_GRP=1, CCME_PROXY_HOST=VAS1, VPS=2, LINE=1,CCME_TMS_HOST=TMS2, TMS_SPAN=1; CONFIG CCME_PROXY_GRP=2, CCME_PROXY_HOST=VAS1, VPS=2, LINE=31,CCME_TMS_HOST=TMS2, TMS_SPAN=2; CONFIG CCME_PROXY_GRP=3, CCME_PROXY_HOST=VAS1, VPS=2, LINE=61,CCME_TMS_HOST=TMS2, TMS_SPAN=3; CONFIG CCME_PROXY_GRP=4, CCME_PROXY_HOST=VAS1, VPS=2, LINE=91,CCME_TMS_HOST=TMS2, TMS_SPAN=4; CONFIG CCME_PROXY_GRP=5, CCME_PROXY_HOST=VAS1, VPS=1, LINE=1,CCME_TMS_HOST=TMS1, TMS_SPAN=1; CONFIG CCME_PROXY_GRP=6, CCME_PROXY_HOST=VAS1, VPS=1, LINE=31,CCME_TMS_HOST=TMS1, TMS_SPAN=2; CONFIG CCME_PROXY_GRP=7, CCME_PROXY_HOST=VAS1, VPS=1, LINE=61,CCME_TMS_HOST=TMS1, TMS_SPAN=3; CONFIG CCME_PROXY_GRP=8, CCME_PROXY_HOST=VAS1, VPS=1, LINE=91,CCME_TMS_HOST=TMS1, TMS_SPAN=4;
The following is an example of a ss7.conf file using the Hybrid Proxy mode. Example ss7.conf file
CONFIG NODE=MPS, OPC=2068, TYPE=SEP; #CONFIG TMSHOST=TMSl1, HOST=TMSss72; #CONFIG TMSLINK=link1, SLC=0, HOST=TMSl1, PRIORITY=0, CHASSIS=1, BPS=2, SLOT=2, SPAN=1, CHANNEL=16, SS7SPAN=1, SS7CHAN=1, BR=64000; CONFIG LINKSET=ls1, DPC=2067, TYPE=FLINK, ACTIVELINK=1, LINKS=link1; CONFIG CMB_LINKSET=cs1, LSETS=ls1; CONFIG ROUTE=rt1, DPC=2067, LSETS=cs1; ###################################################### # Trunk Group Definitions are here # ###################################################### CONFIG TRK_GRP=1, CIR_GRP=0, GRP_TYPE=E1, DPC=2067; ###################################################### # Proxy Host Definitions are here # ###################################################### CONFIG CCME_PROXY_HOST=VAS2, HOSTNAMES=mps; ###################################################### # TMS Host Definitions are here # ######################################################
98 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] TMS Configuration
CONFIG CCME_TMS_HOST=TMS, HOSTNAMES=tms1; ###################################################### # Proxy Group Definitions are here # ###################################################### CONFIG CCME_PROXY_GRP=1, CCME_PROXY_HOST=VAS2, VPS=1, LINE=1, CCME_TMS_HOST=TMS, TMS_SPAN=1; ###################################################### # CCME options are here # ######################################################
TMS Configuration
When Hybrid Proxy mode is used with a TMS system, there are some dependencies between TMS configuration and CCSS configuration. The following commands in file $MPSHOME/common/etc/tms/tms.cfg are affected:
LOAD 1 4 1 SS7 - - - e1_mf_ss7_proto.cfg B=1-15:17-31 D=16 LOAD 2 4 1 SS7 - - - t1_sf_ss7_proto.cfg B=1-23 D=24 The protocol configuration must be t1_esf_ss7_proto.cfg for T1 spans and e1_mf_ss7_proto.cfg for E1 spans.
LineID Mode Configuration
Package Compatibility
Requires: • PERIccss package on the CCSS server • PERImps and PERItms on the MPS applications processor
Avaya CCSS 1000/2000 Feature Documentation August 2013 99 Configuration
CCSS Configuration
LineID mode is use with the MPS N+1 AP redundancy feature to support changeover to the proxy on the backup MPS applications processor when an MPS failover has occurred. In LineID Mode, the CCSS has a connection to both PROXY and TMS. The call establishment and call teardown messaging between the CCSS and the application is through the Proxy API. Maintenance messaging for circuits occurs between the CCSS and TMS. LineID mode configuration has the following additional commands in the ss7.conf file: • CCME_STANDBY_MAP • CCME_PROXY_STANDBY_HOST • CCME_MPSLINE_MAP_GRP Examples of relevant commands in the ss7.conf file
CONFIG CCME_PROXY_HOST=VAS1And2, HOSTNAMES=tmsi01, TYPE=MPS; CONFIG CCME_PROXY_STANDBY_HOST=VAS101And102, HOSTNAMES=tmsi100;
CONFIG CCME_TMS_HOST=TMS1, HOSTNAMES=tms1a; CONFIG CCME_TMS_HOST=TMS2, HOSTNAMES=tms2a;
CONFIG CCME_PROXY_GRP=1, CCME_PROXY_HOST=VAS1And2, VPS=1, LINE=1, CCME_TMS_HOST=TMS1, TMS_SPAN=1; CONFIG CCME_PROXY_GRP=2, CCME_PROXY_HOST=VAS1And2, VPS=2, LINE=1, CCME_TMS_HOST=TMS2, TMS_SPAN=1;
CONFIG CCME_STANDBY_MAP=MAP1, CCME_PROXY_HOST=VAS1And2, VPS=1, CCME_PROXY_STANDBY_HOST=VAS101And102, STANDBY_MPS=101; CONFIG CCME_STANDBY_MAP=MAP2, CCME_PROXY_HOST=VAS1And2, VPS=2, CCME_PROXY_STANDBY_HOST=VAS101And102, STANDBY_MPS=102;
CONFIG CCME_MPSLINE_MAP_GRP=1, TMS=1, CHASSIS=1, SLOT=1, LINE=1, CCME_TMS_HOST=TMS1, TMS_SPAN=1; CONFIG CCME_MPSLINE_MAP_GRP=2, TMS=2, CHASSIS=1, SLOT=2, LINE=1, CCME_TMS_HOST=TMS2, TMS_SPAN=1;
CONFIG CCME_TIMER=P13, VALUE=60;
100 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] MPS Configuration for LineID Mode
MPS Configuration for LineID Mode
The following example shows a sample gen.cfg file for configuring the MPS for LineID mode. Example gen.cfg file for LineID Mode
$MPSHOME/common/etc/gen.cfg # Example gen.cfg file. # # NAME NODE PORT is-VOS-CLASS PRI COMMAND LINE # proxy - - 0 0 "proxy -S ccss -L cons -l info -k 10 -n -c"
Note: The -c argument passed to PROXY line in gen.cfg enables the process to operate in N+1 redundancy or Call Protect.
TMS Configuration
When LineID mode is used with a TMS or MPS system, there are some dependencies between TMS configuration and CCSS configuration. The following commands in the $MPSHOME/common/etc/tms/tms.cfg file are affected: LOAD 1 4 1 SS7 - - - e1_mf_ss7_proto.cfg B=1-15:17-31 D=16 LOAD 2 4 1 SS7 - - - t1_sf_ss7_proto.cfg B=1-23 D=24 The protocol configuration must be t1_esf_ss7_proto.cfg or t1_sf_ss7_proto.cfg for T1 spans and e1_mf_ss7_proto.cfg for E1 spans.
Fault Tolerant Configuration.
In a fault tolerant CCSS configuration, the CCSS servers that form a pair should have identical ss7.conf configuration files. The two configurations must be identical, differing only in the server lines, where each server identifies the other as its redundant peer.
Avaya CCSS 1000/2000 Feature Documentation August 2013 101 Configuration
In the following example ccss1 and ccss2 are the two servers that form a Fault Tolerant pair. Both servers must have a common REDUNDANT_SERVER alias. REDUNDANT_SERVER line ccss1 (ss7.conf)
CONFIG REDUNDANT_SERVER=ccssftpair, SERVER_ID=A, HOSTNAMES=ccss2;
REDUNDANT_SERVER line ccss2 (ss7.conf)
CONFIG REDUNDANT_SERVER=ccssftpair, SERVER_ID=B, HOSTNAMES=ccss1;
102 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] SCCP/TCAP Configuration
The possible values for SERVER_ID are "A" and "B". For example, if one of the servers assumes a SERVER_ID of "A", then its peer must take SERVER_ID "B". The HOSTNAME specifies the LAN interfaces over which the server communicates with its peer.
SCCP/TCAP Configuration
SCCP Layer Configuration
This section outlines the CCSS SS7 SCCP layer options and the configuration procedures. • Signaling Point Code (SPC) When provided, the SPC is the destination address, or the next global title translation node address. • SubSystem Number (SSN) The SSN identifies an SCCP user function within a certain signaling point. Within a system (SPC or DPC) there can be multiple applications running. A Signalling Point Code (which is addressed as a Destination Point Code) might be the location of both a Credit Card Database and an 800 Number Database. Using the DPC as the SS7 address, the message is delivered to the system but the message is not delivered to the appropriate application. A separate identifier of a system within the system is required. That identifier is the Subsystem Number (SSN). SSN is used to sub-address any location where multiple applications are running.
• Global Title (GT) One significant functionality provided by the SCCP is the ability to perform incremental routing using a capability called Global Title Translation (GTT). GTT provides the originating node the convenience of not having to maintain a list of all destinations to which it might route a message. An originating node can build a message, add a GT as called address and send it to a node which is capable of performing GTT, generally an
Avaya CCSS 1000/2000 Feature Documentation August 2013 103 Configuration
STP. The STP (or GTT node) performs the translation and routes the message to the desired destinations. Global Title is an address, such as dialed digits, that does not explicitly contain information that enables routing in the signaling network. A Global Title can be viewed as an alias address. The translation of an alias address results in at least a point code and an optional subsystem number. If the Global Title translation function is not available at the signaling point, the message is given to message routing for transmission back onto the network. • Global Title Translation (GTT) The SCCP layer of the CCSS SS7 stack is equipped with GTT and can perform GTT on incoming dialogues where the routing indicator is set for a route on GT. Using GTT, called party address translation can be done locally by the SCCP layer. To enable this feature, the ss7.conf file must include the following configuration commands.
CONFIG SCCP_GTMAP = periGT, GTTFORMAT= 4, GTFORMATPARAM= (NAI= 004, OE =0, TT=000, NP=1, ES=2), MY_ADDR='9997', REPLACE= REP_YES, ROUTING = ROUTE_GT, OUTPC =572, SSN =148, GTACTION =CONST; CONFIG SCCP_GTASSO = PERIasso, GTTFORMAT= 4, GTFORMATPARAM= (NAI= 004, OE =0, TT = 000, NP =1, ES =2), GTACTIONS= (CONST), GTFUNCSET= 'PERI'; The two preceding commands facilitate the SCCP layer to perform bi-directional GT when the called and calling party routing indicator is set for route on GT. Because the CCSS is doing the GTT, the CCSS helps to balance the load of the network where the STP is not required to do the translation. For translation of the called party GT of an incoming message, the GT format, GT parameters, and the address to translate must be mentioned in the SCCP_GTMAP command. In CCSS, the SCCP_NETWORK command in the ss7.conf file configures the remote subsystems and the far end signaling point code whereas the SCCP_LOCAL_SS command is used for configuring local subsystem. The SCCP_GTTNODE configurations are used to specify the signaling points that are capable of performing global title translation functions. The Global Title Translation functions are normally provided by STPs and can be located regionally or within several STPs. CCSS routes the SCCP messages to the specified GTTNODE for global title based routing. Because the GTTNODE provides global title translation functions, CCSS does not need to know the destination point code or subsystem number of the associated service. Only the GTTNODEs need to maintain a database of destination point codes and subsystem numbers associated with specific services and possible destinations. The TCAP applications use the SCCP_LOCAL_GT command to associate the global title address to the local node.
104 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] SCCP Layer Configuration
Signalling Point Code: 1-2-1 = 2065 Signalling Point Code: 1-2-2 = 2066 Signalling Point Code: 1-2-3 = 2067 Signalling Point Code: 1-2-4 = 2068 Signalling Point Code: 1-2-5 = 2069 Signalling Point Code: 1-2-6 = 2070 Signalling Point Code: 1-2-7 = 2071 The following configuration commands explain the sample SCCP Configuration taking the preceding network diagram as example. Configuration on node 1-2-3
#======# Local #======# The SCCP_LOCAL identifies the local opc only CONFIG SCCP_LOCAL=A1; OPC=2067; # Configure the local sub-system; # Here we support multiple local sub-system. # The idea of name (periIPa, periIPb) is used in peripro folder # origination to identify # themselves to be attached to which sub-system. CONFIG SCCP_LOCAL_SS=periIPa, NODENAME=A1, SSN=20; CONFIG SCCP_LOCAL_SS=periIPb, NODENAME=A1, SSN=21; # Our Global Title is 393358817136 with Format 1 CONFIG SCCP_LOCAL_GT=localGT, LOCAL_SS=periIP, TT=000, NP=1, NAI=004, ES=2, ADDR=’393358817136’; #======# Remote #======
Avaya CCSS 1000/2000 Feature Documentation August 2013 105 Configuration
# the periGTT can be used by application to specify where # that global title address to # be translated no matter what format the GT is using. # the backup global title translation node is 2066 CONFIG SCCP_GTTNODE=periGTT,SPC=2065, SSN=8,BPC=2066; # the two SCPs are mated pair # they are backup to each other CONFIG SCCP_NETWORK=periSCPa, DPC=2069, SSN=20, BPC=2070; CONFIG SCCP_NETWORK=periSCPb, DPC=2070, SSN=20, BPC=2069; Configuration on Node 1-2-7
# Global title address translation database # the following command will translate all incoming # address with digits (111xxxxx) # to be translated to 2071, 253. # The routing indicator = ROUTING ON GT CONFIG SCCP_GTMAP=periGTa, GTTFORMAT=1, GTFORMATPARAM= (NAI=020, OE=001, TT=100, NP=000, ES=000), ADDR=’111’, REPLACE=REP_YES, ROUTING=ROUTE_GT, OUTPC=2071, SSN=146, GTACTION=FIX:1:3;
Application Context Group Configuration
A TCAP message is composed of a transaction portion and a component portion (compliant with ITU recommendation Q.773). A TCAP message consists of the following: • A Transaction Portion, which contains information used by the Transaction sub-layer • A Component Portion, which contains information used by the Component sub-layer related to components • A Dialogue Portion, which contains the Application Context and user information (optional). A TCAP dialogue is identified by the Application Context Name (ACN). In CCSS, the Application Context is used by the TCU software to route dialogues to the application correctly. The application context string is in ASCII string format and enables the system to pass multiple application contexts across a single SSN. ACN is used by the TCU for selecting a proper application based on dialogue portion in the received TCAP BEGIN. If no application context is provided, the TCAP provider binds the stream to the default destination. In CCSS, the application context name should be specified in the ACN_GRP configuration, which defines the rules for TCU handling the inbound transaction requests. TCU maintains pools for each application group defined in ACP_GRP and a default pool for an application registering itself without application context name specified. The following command in the ss7.conf file is used to configure ACN Group. CONFIG ACN_GRP=CAMEL, LOCAL_SS=periIP, ACN='0.4.0.0.1.0.50.1', RULE=RULE_DMSIP;
106 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Multiple Application Contexts Configuration
Multiple Application Contexts Configuration
In CCSS, multiple application context names are supported for a single Application Context Group (ACG) by the TCU. The following command in the ss7.conf file is used to configure multiple application context names in an ACN Group. CONFIG ACN_ADD=CAMEL3, ACN_GRP=CAMEL, ACN='0.4.0.0.1.21.3.4'; If an application context name is added to the default Application Context Group, this will be added to the default ACN Groups of all SubSystem Numbers (SSNs). CONFIG ACN_ADD=periACN, ACN_GRP=DEFAULT, ACN='0.4.0.0.1.21.1.1';
TCAP Layer
The following commands are available for configuration of the TCAP layers.
Avaya CCSS 1000/2000 Feature Documentation August 2013 107 Configuration
Host MCP1 requires TCAP access CONFIG TCUSER_HOST=MCP1, VAS=VAS2 MCP1 has two tms, TMS #18 & TMS #20, which use two T1s each (Each TMS can support upto 8 T1/E1 spans):
CONFIG TCUSER_CLIENT=VAS2, GROUP=1, TYPE=T1, VPS=18,LINE=1; CONFIG TCUSER_CLIENT=VAS2, GROUP=2, TYPE=T1, VPS=18,LINE=25; CONFIG TCUSER_CLIENT=VAS2, GROUP=3, TYPE=T1, VPS=20,LINE=1; CONFIG TCUSER_CLIENT=VAS2, GROUP=4, TYPE=T1, VPS=20,LINE=25;
108 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] TCU Timer Configuration
TCU Timer Configuration
This command is used to configure the values of timers used by TCU. The following timers are supported: • T_RULEDEFAULT is the time that TCU holds an inbound request before it aborts if no application is ready for application groups using default rule. • T_RULEDMSIP is the time that TCU holds an inbound request before it aborts if no application is ready for application groups using DMS Internal IP rule. • T_RUOS is the time that TCU holds before aborting all active applications after a remote subsystem is detected as being temporarily out of service. For T_RUOS timer, value between 0 and 60 seconds is recommended. • T_AUDIT is the timer used for freeing up outstanding dialogs. For T_AUDIT timer, value between 30 and 86400 seconds (24 hours) is recommended. The following line in ss7.conf shows the example configuration command: CONFIG TCUSER_TIMER=T_RULEDMSIP, LEN=10;
TCU Option Configuration
This command is used to configure various options in TCU. The only TCU option supported is NO_AGAPP_SORT. • NO_AGAPP_SORT: CCSS TCU application get sorting on group number and circuit number which disables ability to deliver tcap to multiple MPS in the order in which the event happened.That means, by default, applications will be inserted into the wait list after sorting it based on group number and circuit number for handling incoming events. To disable this, that is, to have applications in the sequence in which "GET" messages received, this option can be used. The following line shows the example configuration command in the ss7.conf file: CONFIG TCU_OPTION=NO_AGAPP_SORT; • FT_ISUP - Enabes the ISUP fault tolerant to remain active when TCAP is configured and enables ISUP calls to be maintained on failover. This option provides the option of call recovery when a TCAP dialog is in place. CONFIG TCU_OPTION = FT_ISUP; • DLG_RSP - A dialog response is sent as a reply to a Dialog Request whereas a Dialog Abort is used to terminate the Dialog abnormally. User Abort message does not include a Dialog Response Result information in its U-Abort. Dialog result diagnostic value being
Avaya CCSS 1000/2000 Feature Documentation August 2013 109 Configuration
checked for NULL at service user level, and then reasoned with “ACN not supplied”. Result field is populated with ACN not supplied for a User Abort dialog. A configurable option is introduced to offer such functionality. It s a TCU OPTION, which in turn enables TCAP layer to include Reason Field in Dialogue Response Application protocol data unit. CONFIG TCU_OPTION=DLG_RSP; • TSTATINFO - A subsystem status test associated with a prohibited subsystem is commenced by starting a timer (stat info). It is a delay timer value set. between requests for subsystem status information. It is set to 2 secs by default but it can be set to any value between 2 - 10 secs by using the following configuration command. CONFIG TCU_OPTION=TSTATINFO, VALUE=value;
Suppress Subsystem Test
This section describes how to prevent sending Subsystem Status Test (SST) messages by enabling the SUPPRESS_SST option flag in the SCCP_NETWORK and SCCP_GTTNODE configuration commands. A CCSS SS7 server responds to all configured SSNs for each SCCP network by sending a SST message. SST is a SCCP management message that is responsible to query the status of remotely configured SSNs. The SCCP network responds with Subsystem Status Acknowledgement (SSA) for each SST message sent with information for the Subsystem under Query is In-Service. If there is a failure, the SCCP network acknowledges the failure with a Subsystem Status Prohibited (SSP) message. After the SCCP is configured on the CCSS server, the CCSS sends an SST message for every SSN that is configured for the remote SCCP layer. The message is a SCCP management message that checks the status of the remote SSN. The network responds with an SSA message that indicates that the SSN is in service. The CCSS server can optionally send the SST message to the network SCCP layer by including the SUPPRESS_SST option in the SCCP_NETWORK and SCCP_GTTNODE commands of the ss7.conf file. A CCSS SS7 server can be configured to clear the SST management message that is sent at start-up to the network. To clear the management message, include the SUPPRESS_SST option for the SCCP_NETWORK or SCCP_GTTNODE configuration entries of the ss7.conf file located in $CCSSHOME/etc. When the SUPPRESS_SST option is included in the SCCP_NETWORK or SCCP_GTTNODE commands, the SST message is not transmitted from the CCSS for the SSN that is configured. The SCCP layer indicates to the TCAP and TCU layers that the remote SSN is in service and is ready for the TCAP applications. After using the SUPPRESS_SST in SCCP_NETWORK or SCCP_GTTNODE, the CCSS SS7 system prohibits sending a Subsystem Test message to the network on all SSNs that are
110 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Call Protect
configured. The configured SSN for the identified SCCP network is brought to in-service on the accessible SCCP route.
Call Protect
Call Protect is a licensed feature of MPS that enables an MPS to resume call processing after a software or non-TMS hardware failure occurred. Call Protect is primarily used by a secondary node in an MPS N+1 cluster configuration to resume calls on a failover. Call Protect can be performed by a MPS primary node that was restarted by SRP or on a failback.
Note: A Call Protect enabled system can only resume connected and protected calls on a failover. Call Protect is enabled only when the TMS is in the READY state.
Integration of MPS N+1 Redundancy and Call Protect
In an N+1 redundant MPS system, CCSS ISUP call control can identify the active VOS component and route the messages received from the network to an application and vice- versa. For MPS N+1 redundancy, a secondary node serves as a back up for multiple primary nodes. After a failover, the secondary node loads the VOS, GEN, and ASE process configurations of the failed primary node. When Call Protect is configured on an MPS system, the secondary and primary nodes share a single TMS or multiple TMSs. The MPS component attempts to resume the resources that it provides and applications that it contains. The CCSS must be configured to identify primary and secondary nodes and the line numbers on each VOS component associated with each circuit in a trunk group. The group of primary components and their backup components is referred to as a cluster. The following diagram identifies a basic MPS N+1 redundancy system configuration that is integrated with a CCSS PROXY mode configuration. MPS N+1 redundancy is designed to protect against MPS and node function failures. N+1 redundancy and Call Protect do not protect against TMS hardware failures.
Avaya CCSS 1000/2000 Feature Documentation August 2013 111 Configuration
Call Protect CCSS SS7 Configuration
The following is a sample ss7.conf file for Call Protect CCSS SS7 configuration. ss7.conf File
CONFIG NODE=CCSSTESTA, OPC=2068, TYPE=SEP; CONFIG DCCHOST=dccl1, HOST=dccss72; CONFIG DCCLINK=link1, SLC=0, HOST=dccl1, PRIORITY=0, CHASSIS=1, BPS=2, SLOT=2, SPAN=1, CHANNEL=16, SS7SPAN=1, SS7CHAN=1, BR=64000; CONFIG LINKSET=ls1, DPC=2067, TYPE=FLINK, ACTIVELINK=1, LINKS=link1; CONFIG CMB_LINKSET=cs1, LSETS=ls1;
CONFIG ROUTE=rt1, DPC=2067, LSETS=cs1; CONFIG TRK_GRP=1, CIR_GRP=0, GRP_TYPE=E1, DPC=2067; CONFIG TRK_GRP=2, CIR_GRP=1, GRP_TYPE=E1, DPC=2067; CONFIG TRK_GRP=3, CIR_GRP=2, GRP_TYPE=E1, DPC=2067; CONFIG TRK_GRP=4, CIR_GRP=3, GRP_TYPE=E1, DPC=2067; CONFIG TRK_GRP=5, CIR_GRP=4, GRP_TYPE=E1, DPC=2067; CONFIG TRK_GRP=6, CIR_GRP=5, GRP_TYPE=E1, DPC=2067; CONFIG TRK_GRP=7, CIR_GRP=6, GRP_TYPE=E1, DPC=2067; CONFIG TRK_GRP=8, CIR_GRP=7, GRP_TYPE=E1, DPC=2067; /* TYPE = MPS is a new field with value MPS that denotes CCSS SS7 PROXY is configured on a MPS N+1 cluster, It's must set for MPS N+1 redundancy and Call-Protect to WORK */ CONFIG CCME_PROXY_HOST=VAS1And2, HOSTNAMES=tmsi01, TYPE=MPS; /* Standby AP PROXY host config item for +1 on failover */ CONFIG CCME_PROXY_STANDBY_HOST=VAS101And102, HOSTNAMES=tmsi100; CONFIG CCME_TMS_HOST=TMS1, HOSTNAMES=TMS1a; CONFIG CCME_TMS_HOST=TMS2, HOSTNAMES=TMS2a; CONFIG CCME_PROXY_GRP=1, CCME_PROXY_HOST=VAS1And2, VPS=1, LINE=1, CCME_TMS_HOST=TMS1, TMS_SPAN=1;
112 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] CCSS System Limits
CONFIG CCME_PROXY_GRP=2, CCME_PROXY_HOST=VAS1And2, VPS=1, LINE=31, CCME_TMS_HOST=TMS1, TMS_SPAN=2; CONFIG CCME_PROXY_GRP=3, CCME_PROXY_HOST=VAS1And2, VPS=1, LINE=61, CCME_TMS_HOST=TMS1, TMS_SPAN=3; CONFIG CCME_PROXY_GRP=4, CCME_PROXY_HOST=VAS1And2, VPS=1, LINE=91, CCME_TMS_HOST=TMS1, TMS_SPAN=4; CONFIG CCME_PROXY_GRP=5, CCME_PROXY_HOST=VAS1And2, VPS=2, LINE=1, CCME_TMS_HOST=TMS2, TMS_SPAN=1; CONFIG CCME_PROXY_GRP=6, CCME_PROXY_HOST=VAS1And2, VPS=2, LINE=31, CCME_TMS_HOST=TMS2, TMS_SPAN=2; CONFIG CCME_PROXY_GRP=7, CCME_PROXY_HOST=VAS1And2, VPS=2, LINE=61, CCME_TMS_HOST=TMS2, TMS_SPAN=3; CONFIG CCME_PROXY_GRP=8, CCME_PROXY_HOST=VAS1And2, VPS=2, LINE=91, CCME_TMS_HOST=TMS2, TMS_SPAN=4; # Primary/Active to Secondary/Standby PROXY map entries to allow Failover/ # Failback checked against pre-configured vas/vps Num to Discrimination CONFIG CCME_STANDBY_MAP=MAP1, CCME_PROXY_HOST=VAS1And2, VPS=1, CCME_PROXY_STANDBY_HOST=VAS101And102, STANDBY_MPS=101; CONFIG CCME_STANDBY_MAP=MAP2, CCME_PROXY_HOST=VAS1And2, VPS=2, CCME_PROXY_STANDBY_HOST=VAS101And102, STANDBY_MPS=102; # In MPS N+1, unique upon failover is Chassis/Slot & Channel, This # mapping allows callcontrol to derive which LineID mapped to a # specific CIC In MPS N+1, unique upon failover is Chassis/Slot & Channel, This mapping allows callcontrol to derive which LineID mapped to a specific CIC */ CONFIG CCME_MPSLINE_MAP_GRP=1, TMS=1, CHASSIS=1, SLOT=1, LINE=1, CCME_TMS_HOST=TMS1, TMS_SPAN=1; CONFIG CCME_MPSLINE_MAP_GRP=2, TMS=1, CHASSIS=1, SLOT=1, LINE=31, CCME_TMS_HOST=TMS1, TMS_SPAN=2; CONFIG CCME_MPSLINE_MAP_GRP=3, TMS=1, CHASSIS=1, SLOT=1, LINE=61, CCME_TMS_HOST=TMS1, TMS_SPAN=3; CONFIG CCME_MPSLINE_MAP_GRP=4, TMS=1, CHASSIS=1, SLOT=1, LINE=91, CCME_TMS_HOST=TMS1, TMS_SPAN=4; CONFIG CCME_MPSLINE_MAP_GRP=5, TMS=2, CHASSIS=1, SLOT=2, LINE=1, CCME_TMS_HOST=TMS2, TMS_SPAN=1; CONFIG CCME_MPSLINE_MAP_GRP=6, TMS=2, CHASSIS=1, SLOT=2, LINE=31, CCME_TMS_HOST=TMS2, TMS_SPAN=2; CONFIG CCME_MPSLINE_MAP_GRP=7, TMS=2, CHASSIS=1, SLOT=2, LINE=61, CCME_TMS_HOST=TMS2, TMS_SPAN=3; CONFIG CCME_MPSLINE_MAP_GRP=8, TMS=2, CHASSIS=1, SLOT=2, LINE=91, CCME_TMS_HOST=TMS2, TMS_SPAN=4; # Timer to allow Failover to complete for a specific duration, on timer expiry call-control releases the call and forces the network to give up the trunk Timer to allow Failover to complete for a specific duration, on timer expiry call-control releases the call and forces the network to give up the trunk */ CONFIG CCME_TIMER=P13, VALUE=60;
CCSS System Limits
Parameter Maximum Value Number of Signalling Point Codes (SPC) 64 Number of adjacent SPCs 16
Avaya CCSS 1000/2000 Feature Documentation August 2013 113 Configuration
Parameter Maximum Value Number of C7 links per linkset 16 Number of linksets that can be configured 16 Number of combined Linksets 16 Number of Routes 64 Number of DCCSS7s per CCSS server Depends on N/w BHCA. Refer to Tested Sample data below.
Required DCCSS7 links to support BHCA of 360,000 ------INPUT VARIABLES Value Avg. Message Size 112 Avg. number of Messages per call (normally successful) 2 BHCA 360,000.00 Bits per bite 8 Link Speed 65,536 Link Utilization 0.40
Emprical Formula to arrive on required links ------Bits per call 1,784 Calls per second 100 Bits per sec (bps) 178,400.00
OUTPUTS ------Number of ss7 links 7 Number of ss7 links per CCSS server 4
114 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Chapter 4: CCSS Commands
This chapter covers: 1. Administration Commands
MGMTUI
The MGMT UI prompt is for entering MGMT UI commands. At any time, issue the command help to display all supported MGMT UI commands.
mgmtui * * * MGMT @ swsunfire6 * * * > help help show this information ======REPORT COMMANDS======report node = nodename; Report status of one specify node report node = all; Report status of all configured nodes report link = linkname; Report status of one specify link report link = all; Report status of all configured links report linkset = linksetname; Report a status of one specify link set report linkset = all; Report a status of all configured link sets report cmb_linkset = Name; Report a status of one specify combine link sets report cmb_linkset = all; Report a status of all configured combine link sets report route = Name; Report a status of one specify route report route = all; Report a status of all configured routes report trk_grp = #, circuit = #; (1-24 for T1 or 1-31 for E1) Report a status of one specified circuit in the specified trunk group report SCCP_NETWORK = Name or all; Report status of the network node or nedes report server=local; Report the status of local server report server=remote; Report the state of remote server in FT configuration report server=all; Report the status of local and remote server in FT configuration report link_info=linkname; Report the image info for the link
======CONTROL COMMANDS======
Avaya CCSS 1000/2000 Feature Documentation August 2013 115 CCSS Commands
control node = name , action = rst; Restart node control node = name , action= flow_on Turn on flow control control node = name , action= flow_off Turn off flow control control link = Name , action = disable; Disable a link control link = Name , action = enable; Enable a link control link = Name , action = lpo; Setlocal processor outage of a link control link = Name , action = lpr; Clear local processor outage of a link control link = Name , action = inh; Inhibited a link control link = Name , action = uninh; Unhitbited a link control link = Name , action = REBOOT; Reboot the comm100 card control linkset = name , action = disable; Disable a link set control linkset = name , action = enable; Enable a link set control server=local, action=make _active|active; Make local server Active control server=local, action=make _standby|standby; Make local server Standby control server=local, action==in service|make_inservice|make_ins| ins; Make local server inservice
======STATISTICS COMMANDS======
stats sccp = gen; Query general statistics of sccp layer stats sccp = upper_node, local_ss = ssn name; Query upper sap statistics of sccp layer stats sccp = lower_node, local_ss = ssn name; Query network sap statistics of sccp layer stats link=link_name, QUERY=MEM_U SAGE; Memory Usage request for com-1000
116 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Report Commands
SAGE;
======TRACE COMMANDS======trace link = link#|all, action = enable|disable; Turn on|off trace trace layer = ISUP, node = nodename, action=enable|disable; turn on|off Trace for isup layer trace layer = TCAP, action = enable|disable; Turn on|off trace for TCAP layer trace layer = SCCP, action = enable|disable; Turn on|off trace for SCCP layer trace layer=MTP2, link=link_name, action=enable|disable; Toggle enable/disable layer 2 (MSU/LSSU) tracing trace ft_component=ft_manager|ft_agent|ft_router|psf_isup|psf_mtp3, MASK=mgmt|local|all, action=enable|disable; Turn on|off trace for ft components.p sf_isup and psf_mtp3 do not require mask field in this command quit or q to quit mgmtui program * * * MGMT @ swsunfire6 * * * > q
Report Commands
REPORT NODE
Reports node status. REPORT NODE=node_name|all; NODE Specifies either a node name previously defined in the CONFIG NODE command or all nodes configured in the system. Examples REPORT NODE=A1; REPORT NODE=all; Output Fields name Node name defined in the CONFIG NODE command. OPC Origination Point Code. type Type (SEP/STP) defined in the CONFIG NODE command. Signaling point restart status: RST YES: Signaling point restarted NO: Signaling point not restarted
Avaya CCSS 1000/2000 Feature Documentation August 2013 117 CCSS Commands
N/A: Status is not available Sample output: > report node=all;
NAME OPC TYPE RST VARIANT A1 2068 SEP NO ******
REPORT CMB_LINKSET
Reports a combined link set configuration. REPORT CMB_LINKSET=cset|all; CMB_LINKSET Specifies either a combined linkset name previously defined in the CONFIG LINKSET command or all combined link sets configured in the system. Examples REPORT CMB_LINKSET=cset1; REPORT CMB_LINKSET=all; Output Fields name Combined linkset name configured in the CONFIG CMB_LINKSET command. linkset Linkset identifier configured in the CONFIG LINKSET command. priority Priority of the combined linkset.
Sample output: > report cmb_linkset=all; NAME (LINKSET PRIORITY) cs1 ( ls1 0 ) ******
REPORT LINK
Reports a signaling link configuration. REPORT LINK=link|all; LINK Specifies either a link name previously defined in the CONFIG LINK command or all links configured in the system. Example REPORT LINK=link1; REPORT LINK=all; Output Fields name Link identifier
slc Signaling link code
host Host identifier
Terminal type: type
priority Priority within a linkset
118 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Report Commands
link_state Signaling link operating state. Values are: ALIGNING: Attempting to align the link through layer 2 and layer 1 ALIGNED: In service OOS: Out of service N/A: Value not currently available admin_state Signaling link management state. Values are: can be NORMAL, N/A or any combination from the rest of the following values. NORMAL: Normal operating state CONG: Congested RBLK: Remotely blocked LBLK: Locally blocked RINH: Remotely inhibited LINH: Locally inhibited N/A: Status not currently available VARIANT Link variant
FLOW-CTRL Flow control state.When the Flow Control is TRUE, any data to be transmitted on the link will be queued in the transmit queue of the link control block. QTSIZE Transmit queue size. Gives the number of messages queued in the link transmit queue QRTSIZE Retransmit queue size. Gives the number of messages present in link retransmit queue. Messages in retransmit queue are present only for a short duration until the buffer retrieval is completed during the changeover procedure.
> report link=all; NAME SLC HOST TYPE PRIORITY LINK STATE link1 0 dccl1 0 ALIGNED link2 1 dccl1 0 ALIGNED
ADMIN STATE VARIANT FLOW-CTRL QTSIZE QRTSIZE NORMAL FALSE 0 0 NORMAL FALSE 0 0
REPORT ROUTE
Display the status of a single route or all routes. REPORT ROUTE=name|all; ROUTE Route name defined in the CONFIG LINKSET command. To report all configured routes in the system, specify all. Example REPORT ROUTE=route1; REPORT ROUTE=all;
Avaya CCSS 1000/2000 Feature Documentation August 2013 119 CCSS Commands
Output Fields name Route identifier
dpc Destination Point Code
route state Route operating state. Values are:
AVAIL: Route is available UNAVAIL: Route is unavailable N/A: Status not currently available act lset Number of active link sets over the total number of link sets in this route. cong Congestion state. Values are:
Yes: All linksets in this route are congested NO: Route is not congested N/A: Status not currently available variant The variant of a given route:
ITU: Configured as ITU route ANSI: Configured as ANSI route ETSI: Configured as ETSI route TELCORDIA: Configured as TELCORDIA route Sample output: > report route=all; NAME DPC ROUTE STATE ACT LSET CONG VARIANT rt1 2067 AVAIL 1/1 NO ETSIV2
REPORT SCCP_NETWORK
Displays the status of the SCCP network. REPORT SCCP_NETWORK=name|all; SCCP_NETWORK Network node with which SCCP is to communicate. Example REPORT SCCP_NETWOORK=perisccp; REPORT SCCP_NETWOORK=all; Output Fields Net_name Name of a network node defined a previous CONFIG SCCP_NETWORK command. dpc Destination Point Code
pc_status Status of a point code. Values are:
pc_acc: Point code is accessible pc_inacc: Point code not accessible SSN A defined SSN number (decimal format)
SSN_Status Status of an SSN. Values are: SS_UIS: SSN is in service SS_UOS: SSN is out of service
120 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Report Commands
variant The variant with which the SCCP is configured. Values are: ITU, ITU88, ITU92, ANSI, ANSI88, ANSI92, ETSI, ETSIV2, ETSIV3 and TELCORDIA Sample output: > report sccp_network=all; Net_Name DPC PC_STATUS periscp 2067 1-2-3 SP_ACC SSN SSN_STATUS VARIANT 253 SS_UOS ITU ******
REPORT TRUNK_GRP
Reports the status of one circuit in a given trunk group. REPORT TRUNK_GRP=tid, CIRCUIT=cid; TRUNK_GRP Trunk group ID defined in the CONFIG TRK_GRP command. CIRCUIT Circuit ID belonging to the trunk group. Example REPORT TRK_GRP= 1, CIRCUIT= 1; REPORT TRK_GRP= 2, CIRCUIT= 20; Output Fields trk_grp Trunk group ID number.
circuit Circuit ID number. Values are: T1: 1-24 E1: 1-30 grp_type Circuit group type, either T1 or E1.
dpc Destination point code
call state Circuit call state. Values are: IDLE: Idle INCBUSY: Incoming busy OUTBUSY: Outgoing busy TRANS: Transient COTCHK: Continuity check N/A: Status not currently available. trans state There are four types of transient states: Local Maintenance, Local Hardware, Remote Maintenance, and Remote Hardware. Values are: IDLE: Idle MLOCBLKED: Locally Blocked (Maintenance Block) MRMTBLKED: Remotely Blocked (Maintenance Block) HLOCBLKED: Locally Blocked (Hardware Block) HRMTBLKED: Remotely Blocked (Hardware Block)
Avaya CCSS 1000/2000 Feature Documentation August 2013 121 CCSS Commands
Sample output: > report trk_grp=1, circuit=1;
TRK_GRP CIRCUIT GRP_TYPE DPC CALL_STATE 1 1 E1 2067 IDLE
TRAN_STATE (Lcl Mnt, Lcl mt Mnt, Rmt HW) IDLE IDLE IDLE IDLE ******
REPORT SERVER
Displays local and remote server status. For each server, the report includes the hostnames, management state, system configuration, and server type in an fault-tolerant configuration. REPORT SERVER=local|remote|all; SERVER One of the following: local: Server on which the MGMTUI command is executed. remote: Remote server in a fault-tolerant configuration. all: Both servers in a fault-tolerant configuration. Examples REPORT SERVER=local; Local Host Details: Local Host Name: ccss1 Local Server state: ACTIVE_WITH_STANDBY System Configuration: Fault Tolerant Local Server Type: A Remote Server Alias Name: ccssredund Remote Server Hostname1: ccss2
REPORT SERVER=remote; Remote Server state: STANDBY
REPORT SERVER=all; Local Host Details: Local Host Name: ccss1 Local Server state: ACTIVE_WITH_STANDBY System Configuration: Fault Tolerant Local Server Type: A Remote Server Alias Name: ccssredund Remote Server Hostname1: ccss2 Remote Server state: STANDBY
REPORT LINK_INFO
Displays the information about the dcc3k_ss7.smod image of the DCCSS7 or the ss7.smod image for a Com1000 card. REPORT LINK_INFO=linkname;
122 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Control Commands
LINK_INFO Link identifier configured in the CONFIG LINK command. Examples > report link_info=link1; Image Info: dcc3k_ss7.elf, Release Developmental [04/29/13 05:24:55 PM] Copyright (C) 2013, Avaya Inc. All rights reserved Ether: 00:80:01:d0:0d:4c DownLoad image: /dcc3k_ss7.smod Board IP:10.7.19.42
Control Commands
The following control commands are for the user to interact with the system while it is running. Control commands are entered at the mgmtui prompt. CONTROL LINK
Temporarily takes the link in or out of service. CONTROL LINK=linkname, ACTION=action; LINK Link identifier configured in the CONFIG LINK command. ACTION One of the following values:
• enable: Enables a disabled link • disable: Disables an enabled link • inh: Inhibits a link • uninh: Uninhibits a link • lpo: Local Processor Outage • rpr: Local Processor Outage Clear • reboot: Reboots the com1000 card or the DCCSS7
Examples CONTROL LINK=link1, ACTION=disable; CONTROL LINK=link2, ACTION=enable;
Note: The reboot for a link on a DCC3K will reboot ALL the DCCSS7 links configured.
CONTROL LINKSET
Enables / disables a configured linkset. CONTROL LINKSET=
Avaya CCSS 1000/2000 Feature Documentation August 2013 123 CCSS Commands
LINKSET Link identifier configured in the CONFIG LINKSET command. ACTION One of the following values:
• enable:Enables a disabled link • disable:Disables an enabled link
Examples CONTROL LINKSET=ls1, ACTION=disable; CONTROL LINKSET=ls2, ACTION=enable;
CONTROL LAYER
Performs various functions for ISUP layer debugging. CONTROL LAYER=
Note: VALUE is always set to DBG_UI in case of MTP3 layer. ACTION One of the following values: enable: Enables logging disable: Disables logging Examples control layer= MTP3, node = ccssa, value = DBG_UI, action = enable;
CONTROL SERVER
Performs a state change on a local server. CONTROL SERVER=local, ACTION=action; SERVER The server that the control action should be taken on. This command is valid only for a local server. SERVER=local refers to the server that the MGMTUI command is executed on.
124 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Control Commands
ACTION Valid actions, with alternative shortened forms in parentheses, are as follows: • make_active (active): Make the server active. • make_standby (standby): Make the server standby. • shutdown (sd): Bring the server to shutdown state. • make_inservice (ins, inservice): Make this server active or on standby if the peer is already active. • forced_switchover (fs, force_switch): Make the standby active by forced-switchover. The standby server becomes active immediately without synchronizing the two servers to avoid message or call loss. This command is valid only on a redundant server configuration when one server is active and the other is standby. fs and force_switch are the aliases for forced switchover. • controlled_switchover (cs, control_switch): Make the standby server active and the active server standby by controlled- switchover. The active server and the standby server swap states in a synchronized manner that prevents message loss between protocol layers. Calls in progress are maintained regardless of their state. This command is valid only on a redundant server configuration, when one server is active and the other is standby. cs and control_switch are the aliases for controlled switchover. See section Fault Tolerance on page 469 for more information. Examples: CONTROL SERVER=local, ACTION=make_active; CONTROL SERVER=local, ACTION=active; CONTROL SERVER=local, ACTION=make_standby; CONTROL SERVER=local, ACTION=standby; CONTROL SERVER=local, ACTION=inservice; CONTROL SERVER=local, ACTION=ins; CONTROL SERVER=local, ACTION=make_inservice; CONTROL SERVER=local, ACTION=make_ins; CONTROL SERVER=local, ACTION=shutdown; CONTROL SERVER=local, ACTION=sd; CONTROL SERVER=local, ACTION=forced_switchover; CONTROL SERVER=local, ACTION=fs; CONTROL SERVER=local, ACTION=force_switch; CONTROL SERVER=local, ACTION=controlled_switchover; CONTROL SERVER=local, ACTION=cs; CONTROL SERVER=local, ACTION=control_switch;
Caution: CONTROL SERVER The control server command may consume excessive CPU time and overload the system.
Avaya CCSS 1000/2000 Feature Documentation August 2013 125 CCSS Commands
Statistics Commands
The STATS command of the SCCP layer is in the following format: STATS SCCP
Queries the statistics of a live system. STATS SCCP=gen |upper_node/lower_node [,LOCAL_SS=ssn_name/ all]; SCCP Specifies the sccp layer. Values for the support alias are: gen: General statistics upper_node: Node where SCCP communicates with TCAP lower_node: Node where SCCP communicates with MTP3 LOCAL_SS An alias-defined local subsystem. Examples CONFIG NODE=ccssa, OPC=2067, TYPE=sep; ... CONFIG SCCP_LOCAL=A1, OPT=2067; CONFIG SCCP_LOCAL_SS=periIPA, NODENAME=A1, SSN=253; CONFIG SCCP_LOCAL_SS=periIPB, NODENAME=A1, SSN=254; • To display the statistics of node periIPA, issue the following command at the mgmtui prompt: STATS SCCP=upper_node, LOCAL_SS=periIPA; • To display the statistics of all the local nodes: STATS SCCP=lower_node, LOCAL_SS=all;
STATS TCAP LOCAL_SS
Provides TCAP statistics. STATS TCAP LOCAL_SS=ssn_name |all; LOCAL_SS An alias-defined local subsystem. Examples STATS TCAP LOCAL_SS=periIPA; STATS TCAP LOCAL_SS=all; • To display the TCAP statistics of node periIPA: STATS TCAP LOCAL_SS=periIPA; • To display the TCAP statistics of all the local nodes: STATS TCAP LOCAL_SS=all;
STATS LINK
126 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Trace Commands
Displays MTP3 statistics for the specified link. MTP3 provides message routing between signaling points in a SS7 network. STATS LINK=linkname|all [, QUERY=mem_usage]; LOCAL_SS An alias-defined local subsystem. Examples STATS LINK=link1; STATS LINK=all; STATS LINK=link1, QUERY=mem_usage; • To display the MTP3 statistics for link1: STATS LINK=link1; • To display the MTP3 statistics for all links: STATS LINK=all; • To display memory usage statistics for a link: STATS LINK=link1, QUERY=mem_usage; • STATS LINK=link1, QUERY=mem_usage;
memory usage: pool size = 126711 number of buffer = 127749 Pool available = 99%
Trace Commands
Using trace commands, the user can watch a message transmit to and be received by the CCSS server. The trace works similar to a protocol analyzer, except there is no decoding of the data content. Trace commands are issued from the mgmtui prompt.
Caution: CPU usage should be monitored when tracing is enabled. Overuse of tracing can consume excessive CPU time and overload the system. Tracing should be avoided on multiple layers simultaneously, or at times of peak call load. TRACE LINK
Traces the MTP3 messages that are transmitted and received. The display includes Layer, Time, msg transmitted or received, Link on which msg was transmitted or received, MSG_TYPE,DPC,OPC, Signaling Link Selection (SLS), Msg Data. MTP3 provides message routing between signaling points in a SS7 network. TRACE LINK=link_name|all, ACTION=enable|disable; LINK Link identifier configured in the CONFIG LINK command or all links. ACTION One of the following values: enable: Enables the display of MTP3 tracing messages. disable: Disables the display of MTP3 tracing messages.
Avaya CCSS 1000/2000 Feature Documentation August 2013 127 CCSS Commands
Example
trace link=link1,action=enable; Layer TIME DIR LINK MSG_TYPE DPC MTP3 05/06/13 12:55:58 T 0 SLA 2067 1-2-3 MTP3 05/06/13 12:56:51 T 0 SLT 2067 1-2-3 MTP3 05/06/13 12:56:51 R 0 SLA 2068 1-2-4
OPC SLS DATA 2068 1-2-4 0 b b1 13 8 5 2 21 40 50 45 52 49 2068 1-2-4 0 b b1 13 8 5 2 11 40 50 45 52 49 2067 1-2-3 0 b b1 14 c8 4 2 21 40 50 45 52 49
Layer : Protocol Layer e.g MTP3 TIME : Timestamp at which message on SS7 link transmitted/received DIR : Direction of message(T= Transmit & R = Receive) from C7 server LINK : SS7 Link id on which message is transmitting MSG_TYPE : MTP3 messages e.g SLT/SLA DPC : Destination Point Code OPC : Origination Point Code SLS : Signalling Link Selection DATA : Content of message body transmitted/received on the link
TRACE LAYER=isup
Traces the ISUP messages that are transmitted and received by the CCSS server. The display includes the Layer, time, message transmitted or received, circuit number, message type, Destination point code and message data. TRACE LAYER=isup, NODE=node_name, ACTION=enable|disable; NODE Node alias configured in the ss7.conf file. ACTION One of the following values: enable: Enables the display of ISUP tracing messages. disable: Disables the display of ISUP tracing messages. Example TRACE LAYER=isup, NODE=A1, ACTION=enable; Layer TIME DIR Cic MSG_TYPE DPC DATA ISUP 07/03/02 19:03:31 T 7 IAM 2068 1-2-4 7 0 1 0 20 1 a 0 2 8 6 1 10 55 15 12 ISUP 07/03/02 19:03:32 R 7 ACM 2068 1-2-4 7 0 6 14 4 0 ISUP 07/03/02 19:03:32 R 7 ANM 2068 1-2-4 7 0 9 1 11 2 0 0 0 ISUP 07/03/02 19:03:33 T 7 REL 2068 1-2-4 7 0 c 2 0 3 0 80 90 ISUP 07/03/02 19:03:34 R 7 RLC 2068 1-2-4 7 0 10 0 Layer : Protocol Layer e.g ISUP/MTP2 TIME : Timestamp at which SS7 messages being transmitted/received DIR : Direction of message(T= Transmit & R = Receive) from C7 server CIC : Circuit Identification Code of the circuits carrying message MSG_TYPE : ISUP messages e.g IAM/ACM/ANM/REL/RLC DPC : Destination Point Code DATA : Content of ISUP message transmitted/received by ISUP layer
128 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Trace Commands
TRACE LAYER=mtp2
Traces the MTP2 messages that are transmitted and received. The display includes the Layer, time, message transmitted or received, circuit number, Backward Indicator Bit (BIB), Backward Sequence Number (BSN), Forward Indicator Bit (FIB), Forward Sequence Number (FSN), message length, Status shows if the signaling unit is Message signaling unit (MSU), Fill-In signaling unit (FISU), link status signaling unit (LSSU) and message data. TRACE LAYER=mtp2 LINK=link_name, ACTION=enable|disable; LINK Link configured in the ss7.conf file. ACTION One of the following values: enable: Enables the display of ISUP tracing messages. disable: Disables the display of ISUP tracing messages. Examples trace layer=MTP2, link=link2, action=enable; Layer TIME DIR BIB BSN FIB FSN LENGTH STATUS DATA MTP2 07/03/02 19:29:26 T 1 1241 44 34 MSU MTP2 07/03/02 19:29:26 R 1 441 125 11 MSU
TRACE LAYER=SCCP
Traces the SCCP messages that are transmitted and received by the CCSS server. The display includes the Layer, time, message transmitted or received and message data. TRACE LAYER=SCCP, ACTION=enable|disable; ACTION One of the following values: enable: Enables the display of SCCP tracing messages. disable: Disables the display of SCCP tracing messages. Example TRACE LAYER=SCCP, ACTION=enable;
Layer TIME DIR SCCP 07/22/03 07:19:13 T 9 81 3 7 b 4 43 13 8 92 4 43 14 8 92 45 62 43 48 1 2 6c 3e a1 80 2 1 0 2 1 37 16 13 36 20 20 48 65 6c 6c 6f 0 4e 75 6c 6c 76 61 6c 75 65 31 0 0 a1 80 2 1 1 2 1 38 16 13 36 20 20 48 65 6c 6c 6f 0 4e 75 6c 6c 76 61 6c 75 SCCP 07/22/03 07:19:13 R 9 81 3 7 b 4 43 14 8 92 4 43 13 8 92 18 65 16 48 1 2 49 1 2 6c e a2 80 2 1 0 0 0 a2 80 2 1 1 0 0 Layer : Protocol Layer e.g ISUP/MTP2/SCCP/TCAP TIME : Timestamp at which SS7 messages being transmitted/received DIR : Direction of message(T= Transmit & R = Receive) from C7 server : Content of SCCP message transmitted/received by SCCP layer
TRACE LAYER=TCAP
Traces the TCAP messages that are transmitted and received by the CCSS server. The display includes the Layer, time, message transmitted or received and message data.
Avaya CCSS 1000/2000 Feature Documentation August 2013 129 CCSS Commands
TRACE LAYER=TCAP, ACTION=enable|disable; ACTION One of the following values: enable: Enables the display of TCAP tracing messages. disable: Disables the display of TCAP tracing messages. Example TRACE LAYER=TCAP, ACTION=enable;
Layer TIME DIR TCAP 07/22/03 07:16:16 T 62 43 48 1 1 6c 3e a1 80 2 1 0 2 1 37 16 13 36 20 20 48 65 6c 6c 6f 0 4e 75 6c 6c 76 61 6c 75 65 31 0 0 a1 80 2 1 1 2 1 38 16 13 36 20 20 48 65 6c 6c 6f 0 4e 75 6c 6c 76 61 6c 75 65 31 0 0 TCAP 07/22/03 07:16:16 R 65 16 48 1 1 49 1 1 6c e a2 80 2 1 0 0 0 a2 80 2 1 1 0 0 Layer : Protocol Layer e.g ISUP/MTP2/SCCP/TCAP TIME : Timestamp at which SS7 messages being transmitted/received DIR : Direction of message(T= Transmit & R = Receive) from C7 server : Content of TCAP message transmitted/received by TCAP layer
TRACE FT_COMPONENT
Enables and disables the tracing of the specified fault tolerance component. TRACE FT_COMPONENT=ft_manager|ft_agent|ft_router|psf_isup| psf_mtp3, ACTION=enable|disable, [,MASK=mgmt| local|all]; LINK Link configured in the ss7.conf file. FT_COMPONENT Component identified for tracing. One of the following: ft_manager: Trillium System Manager (SG) (not currently supported) ft_agent: Trillium System Agent (SH) ft_router: Trillium Router psf_isup: Trillium PSF-ISUP Component (psf-isup) psf_mtp3: Trillium PSF-MTP3 Component (psf-mtp3) ACTION One of the following values: enable: Enables the display of tracing messages. disable: Disables the display of tracing messages. MASK One of the following values:
• mgmt • local • all
Examples TRACE FT_COMPONENT=psf_isup, MASK=all, ACTION=enable;
130 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] UI
UI
The UI prompt is for entering UI commands. At any time, enter the command help to display the supported UI commands. HELP
> help > help Commands: help show this information block
help
Displays a summary of all the UI commands and their usage. help
!!
Repeats the previous command. !! Example > status cic 1 2 state Trk:1 (0-8-19,0,2)(vps1/1/32) last call: 01/09/03 05:44:58 IDLE: [ ] 1 circuit states * * * UI @ ccss3 * * * > !! Trk:1
Avaya CCSS 1000/2000 Feature Documentation August 2013 131 CCSS Commands
(0-8-19,0,2)(vps1/1/32) last call: 01/09/03 05:44:58 IDLE: [ ] 1 circuit states
block
Causes a block or a group block to be transmitted on the circuits to prohibit non-test calls from C7. block
Caution: Blocking all circuits at once by issuing block cic * * may consume excessive CPU time and overload the system.
unblock
Causes a unblock or a group unblock to transmit on the circuits. ISUP unblocking acknowledgement message brings individual lines or circuit groups in service unblock
132 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] UI
cgroup_start is the first circuit group in the range cgroup_end is the last circuit group in the range circuit_start is the first circuit in the range circuit_end is the last circuit in the range = mps mps_hostname mps_start - mps_end line_start - line_end mps_hostname is the alias name of the mps host mps_start is the 1st mps component in the range mps_end is the last mps component in the range line_start is the first mps line in the range line_end is the last mps line in the range (range is optional and can be replaced by '*' to indicate all configured groups,circuits,mps's,or lines) Examples > unblock cic 1 1 unblock individual circuits. > unblock mps mps1 1 1 > unblock cic 1 * unblock all circuits in a circuit group. > unblock mps mps1 1 * > unblock cic 1 1-10 unblock certain circuits in a circuit group. > unblock mps mps1 1-10 > unblock cic * * unblock all the circuits. > unblock mps mps1 * *
Caution: Unblocking all circuits at once by issuing unblock cic * * might consume excessive CPU time and overload the system.
reset
Causes a reset or a group reset to transmit on lines or circuit groups to make them available reset
Avaya CCSS 1000/2000 Feature Documentation August 2013 133 CCSS Commands
(range is optional and can be replaced by '*' to indicate all configured groups,circuits,mps's,or lines) Examples > reset cic 1 1 reset individual circuits. > reset mps mps1 1 1 > reset cic 1 * reset an entire circuit group. > reset mps mps1 1 * > reset cic 1 1-10 > reset mps mps1 1-10 reset a range of circuits in a circuit group. > reset cic * * reset all configured circuits > reset mps mps1 * *
Caution: Resetting all circuits at once by issuing reset cic * * might consume excessive CPU time and overload the system.
stats
Obtains the statistics on individual lines or groups of lines. Optionally resets statistics stats
> stats cic * * CIC *.* [11/04/02 18:43:11 - 11/05/02 09:11:05] Call Statistics I_ATTMPT I_ANSWR I_RJCT I_TIMOUT I_FAIL O_ATTMPT O_ANSWR O_RJCT O_TIMOUT O_FAIL
134 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] UI
101679 100574 0 0 1105 0 0 0 0 0 System Statistics MTP_DOWN MTP_FAIL EXP_IUP EXP_GDTM EXP_NWTM AP_IUP AP_RGSUC AP_RGFL VAS_CONN 30 30 0 0 0 0 100990 58 0
> stats cic 1 1 obtain statistics on individual circuits. > stats mps mps1 1 1 > stats cic 1 * obtain statistics on an entire circuit group. > stats mps mps1 1 * > stats cic 1 1-10 obtain statistics on certain circuits in a circuit group. > stats mps mps1 1 1-10 > stats cic * * obtain statistics on all configured circuits. > stats mps mps1 * *
status
Obtains the circuit states of individual circuits or circuit groups. status
> status cic 1 2 state Trk: 1 (0-8-19, 0, 2) (vps1/ 1/32) last call: 01/09/03 05:44:58 IDLE : [ ] 1 circuit states * * * UI @ ccss3 * * *
> status cic 1 1 state obtain circuit state of individual > status mps mps1 1 1 state circuits. > status cic 1 * active obtain circuit states for an entire > status mps mps1 1 * active circuit group. > status cic 1 1-10 blocked obtain circuit states for certain > status mps mps1 1 1-10 circuits in a circuit group.
Avaya CCSS 1000/2000 Feature Documentation August 2013 135 CCSS Commands
> status cic * * unblocked obtain circuit states for all > status mps mps1 * * unblocked configured circuits
Caution: Obtaining status on all circuits at once by issuing status cic * * state might consume excessive CPU time and overload the system.
debug
Toggle debug on/off for lines. debug
Caution: Selecting a high debug level may consume excessive CPU time and overload the system.
log
Toggle call event logging.
136 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] UI
log
Caution: Turning on logging on all circuits may consume excessive CPU time and overload the system.
term
Request call control exit. term hard Examples > term hard Request call control exit.
show
Obtain configuration information. show config timers|isup_parms|ccme_options|tms_hosts| proxy_hosts
Avaya CCSS 1000/2000 Feature Documentation August 2013 137 CCSS Commands
Examples: > show help SHOW command summary config timers - show Call control Timer value configuration config isup_parms - show Call control Default value configuration config ccme_options - show Call control Option value configuration config tms_hosts - show Call control TMS host information configuration config proxy_hosts - show Call control PROXY host information configuration OK
> show config timers Get information on configured values for the Timer No: 0 Timer Value: 1 ccme timers P1 - P13 Timer No: 1 Timer Value: 170 Timer No: 2 Timer Value: 30 Timer No: 3 Timer Value: 15 Timer No: 4 Timer Value: 5 Timer No: 5 Timer Value: 60 Timer No: 6 Timer Value: 45 Timer No: 7 Timer Value: 20 Timer No: 8 Timer Value: 1 Timer No: 9 Timer Value: 1 Timer No: 10 Timer Value: 5 Timer No: 11 Timer Value: 5 Timer No: 12 Timer Value: 15 Timer No: 13 Timer Value: 5 OK * * * UI @ ccss3 * * *
> show config proxy_hosts show configured proxy hosts PROXY_HOST: VAS1 OK
> show config isup_parms show alll the default/configured ISUP parameters. > show config ccme_options show alll the default/configured ccme options. > show config tms_hosts show the configured tms hosts
logpsf
Log circuit state updates. logpsf
138 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] UI
line_end is the last mps line in the range (range is optional and can be replaced by '*' to indicate all configured groups, circuits, MPs, or lines) Examples > logpsf cic 1 1 on Turn psf logging on for individual > logpsf mps mps1 1 1 on circuits. > logpsf cic 1 * on Turn psf logging on for all circuits in > logpsf mps mps1 1 * on a circuit group. > logpsf cic 1 1-10 off Turn psf logging off for a range of > logpsf mps mps1 1 1-10 off circuits in a circuit group. > logpsf cic * * off Turn psf logging off for all the > logpsf mps mps1 * * off circuits.
Caution: Turning on psf logging on all circuits might consume excessive CPU time and overload the system.
msg
Avaya CCSS 1000/2000 Feature Documentation August 2013 139 CCSS Commands
>msg plibon Turn on display of proxy library debugging >msg pliboff Turn off display of proxy library debugging >msg monon Turn on display of one second message monitoring. Note : hblock/hunblock/sus and res are only applicable on Active C7 server with redundant mode configured. >msg monoff Turn off display of one second message monitoring >msg mainton Set maintenance message/timer message to log at the alert level >msg maintoff Set maintenance messages to log at the debug2 level >msg qstats Display a statistics report for all queues >msg fd Display proxy file descriptors >msg db 7 Set message debug level to 7 that is, CC_DEBUG >msg dump
140 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] TCU User Interface (TCUUI) Commands
quit|q|exit
Exit UI. quit
Caution: UI commands can be run in batch mode. Looping UI commands in batch mode can severely consume CPU time and overload the system. Looping UI commands in batch mode should be avoided. For example, running a command like ui -b "status cic * * state" in a for loop continuously consumes CPU time.
TCU User Interface (TCUUI) Commands
Command Description help Displays the usage of another command. !! Repeats previous command. acg Application context group command. db Sets debug level. history Displays message history logged on a specified group. info Displays configured local or remote sub-system status. log Redirects log. logclose Closes log. loginfo Displays log info. logsize Sets size of log. logt Toggles timestamp on/off on logging. monoff Turns statistics monitor off. monon Turns statistics monitor on. monreset Resets monitor statistics. monsample Sets monitor average samples. montime Sets time interval between monitor. msgrep Reports tcap message statistics.
Avaya CCSS 1000/2000 Feature Documentation August 2013 141 CCSS Commands
Command Description rep Reports state machine statistics. reset Resets app on specified group circuit. statsreset Resets all collected stats. status Displays status of specified group circuit. summary Displays summary of current activity. time Displays current time. trace Toggles trace flag on specified group, circuit. tset Sets trace flag. uis Places local subsystem in service. uos Places local subsystem out of service.
help
Displays a command summary, the usage of specified command, or the usage of all commands. help command |all Example OK help db Syntax: db < debug level #> Description: set debug level to # debug level # ranges from 1 to 7 OK
!!
Repeats the previous command. !! Example trace 1 1
11/03/99 10:45:51 tcap0 (debug): (1, 1) -- ISSUEGET OutboundMode; Folder Version 2; Dest:periSCP 11/03/99 10:45:51 tcap0 (debug): (1, 1) -- Register Success . . 11/03/99 10:46:05 tcap0 (debug): (1, 1) -- Continue !! (1 1) trace turned OFF
acg
142 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] TCU User Interface (TCUUI) Commands
Generates reports for individual application context groups. acg info|st|summary
db
Sets the debug level. db # Example db 7
history
Displays the history of dialogs on specified group circuit. history group# circuit# group Group number. circuit Circuit number. Example history 2 1
time interval NewAppSt NewDlgSt Dlg SPDLGID APPL Message TCAP InvID LnkID . . 10:24:26.083357 0.550388 Active DlgInvInit 0 0 -- INVOKE_L -- 0
Output fields time Time stamp of the message interval Time between this and previous message New App St New application state after processing the message New Dlg St New dialog state after processing the message Dlg Dialog ID specified by the application SPDLGID Service provider dialog ID assigned by TCAP APPL Direction of message flows to/from application Message Message name TCAP Direction of message flows to or from the TCAP layer
Avaya CCSS 1000/2000 Feature Documentation August 2013 143 CCSS Commands
InvID Invoke ID if exists LnkID Linked ID if exists
info
Displays system information. info Example
Output fields [Point Code] Shows both integer and ITU(3-8-3) ANSI(8-8-8) representation of a point code [SCCP] INIT Initializing; State Unknown SP_ACC Signaling Point Accessible SP_INACC Signaling Point Inaccessible SP_CONG Signaling Point Congested [Subsystem] INIT Initializing; State Unknown SS_UOS Subsystem user out of service SS_UIS Subsystem user in service
logsize
Sets the maximum size of the log in bytes. logsize #
logclose
144 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] TCU User Interface (TCUUI) Commands
Closes any opened log redirection. logclose
loginfo
Displays redirected log name. loginfo
logt
Toggles timestamp on or off for logging. logt
log
Redirects login to specified file or device. log file/tty Example
OK tty OK /dev/pts/2 tcuui OK log /dev/pts/2 11/03/99 10:44:44 tcap0 (alert): log redirected to /dev/pts/2 redirecting to: /dev/pts/2 OK
monon
Turns on monitor to redirected output. monon Example
monon OK 01/24/00 17:08:06 tcap0 (alert):::::::::::::[1/24/00 17:08:06.074732]: ::::::::::: 01/24/00 17:08:07 tcap0 (alert): monitor: totals /this ls period/ max 01/24/00 17:08:07 tcap0 (alert): Network Write: 2 0 1 . . 01/24/00 17:08:07 tcap0 (alert):::::::::::::[1/24/00 17:08:07.074939]: :::::::::::
Avaya CCSS 1000/2000 Feature Documentation August 2013 145 CCSS Commands
Output Fields Network Write TCIF number of outbound messages Network Read TCIF number of inbound messages Proxy Read Number of proxy messages received Proxy Written Number of proxy messages sent Dialogs In Number of incoming dialog requests Dialogs Out Number of outgoing dialog requests Components In Number of incoming components Components Out Number of outgoing components Maximum TCIF Read TCIF polling idle idle time Maximum TCIF TCAP msg processing time Process time Maximum Proxy Proxy polling idle Read idle time Maximum ProxyMsg Proxy msg processing time Process time Proxy message Polling ratio polling hit ratio
monoff
Turns off logging monitor. monoff
montime
Sets the Monitor Time Interval in seconds ranging from 1 to 300. montime #
monreset
Resets data collected by the monitor. monreset
monsample
Sets the monitor sample number to specified monitor. monsample #
146 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] TCU User Interface (TCUUI) Commands
msgrep
Displays the message statistics report. msgrep Example OK msgrep
::::::::::::::::: ANSI Message Report ::::::::::::::::: QryP QryNP CnvP CnvNP Resp UAbort PAbort NOTICE Sent 0 0 80485 0 0 0 - - Received 13450 0 0 67038 13377 0 0 0 - INVL INVNL RRL RRNL REJL REJR CANCEL Sent - 0 0 160974 0 0 - - Received - 187730 0 0 0 0 0 0 Get V2 Outbound: 0 Get V2 Inbound: 0 FREE: 13440 Register Succ: 13495 Register Fail: 64 Inbound No App: 0 :::::::::::::::::: ANSI ENDofReport :::::::::::::::::::
rep
Report application state machine or dialogue state machine statistics. rep appst | dlgst | all [group#, circuit#] appst Application state machine stats. dlgst Dialogue state machine stats. all Application state machine and dialogue state machine stats. group Application state machine stats for the specified group and line. circuit Application state machine stats for the specified group and line.
reset
Resets dialogs on the specified group circuit. reset [group# [circuit#]] group Group number (or all or * for all groups). circuit Circuit number (or all or * for all circuits).
statsreset
Resets collected statistics.
Avaya CCSS 1000/2000 Feature Documentation August 2013 147 CCSS Commands
statsreset
status
Displays message status of the specified circuits. status [group# [circuit#]] group Group number (or all or * for all groups). circuit Circuit number (or all or * for all circuits).
summary
Displays summary of status of the specified circuits. Only configured (group, circuit) applications that have at least one message sent or received are displayed. summary [group# [circuit#]] group Group number (or all or * for all groups). circuit Circuit number (or all or * for all circuits). Examples summary Displays status of all configured groups and circuits. summary 1 1 Displays status of group 1 circuit 1. summary 1 * Displays status of all circuits on group 1. summary 1 all summary 1 summary all 1 Displays all status messages for circuit 1. summary * 1 summary 1
[GROUP 1] Grp, Cir spdlgid STATE Abort TotalDlg Last CompletedDLG Destination [1, 2] 6098 DlgActive 0 133 11/03/99 10:54:08 periSCP(2068,252)
time
Displays the current time. summary [group# [circuit#]] group Group number (or all or * for all groups). circuit Circuit number (or all or * for all circuits).
148 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] TCU User Interface (TCUUI) Commands
Example time Current time is: 11/03/99 10:49:17.746975
trace
Toggles tracing on or off for the specified group and circuit. status group# circuit# group Group number. circuit Circuit number. Example trace 1 1
11/03/99 10:45:51 tcap0 (debug): (1, 1) -- ISSUEGET OutboundMode; Folder Version 2; Dest:periSCP 11/03/99 10:45:51 tcap0 (debug): (1, 1) -- Register Success . . 11/03/99 10:46:05 tcap0 (debug): (1, 1) -- Continue
trace 1 1 (1 1) trace turned OFF
Caution: Tracing might consume excessive CPU time and overload the system.
tset
Sets tracing options while using the trace command. tset [options] Options close Turns off all trace flag. flow Toggles on/off message flow trace flag (default on). appmsg (TCAPPROXY interface) Turns on app folder msg trace flag for both direction. noappmsg (TCAPPROXY interface) Turns off app folder msg trace flag for both direction. sndappmsg (TCAPPROXY interface) Toggles on/off folders sent to app. rcvappmsg (TCAPPROXY interface) Toggles on/off folders received from app.
Avaya CCSS 1000/2000 Feature Documentation August 2013 149 CCSS Commands
tcapmsg (TCIF interface) Turns on tcap msg trace flag for both directions. notcapmsg (TCIF interface) Turns off tcap msg trace flag for both directions. sndtcapmsg (TCIF interface) Toggles on/off messages sent to TCAP layer. rcvtcapmsg (TCIF interface) Toggles on/off messages received from TCAP layer.
uis
Places the specified subsystem in service (that is, sends a Broadcast Subsystem Allowed (SSA) message). uis local-sub-system Example uis periIp
uos
Places the specified subsystem out of service (that is, sends a Broadcast Subsystem Prohibited (SSP) message). uis local-sub-system Example uos periIp
150 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Chapter 5: Operations, Administration, and Maintenance
This chapter covers: 1. System Startup Procedures 2. System Shutdown Procedures 3. Backup and Restore Procedures 4. System Status and Statistics 5. Diagnostics and Troubleshooting
System Startup Procedures Starting the CCSS 2000
1. Turn on the main power switch. Wait for the login prompt. 2. Log in as root (enter ‘root;’ as the password). If the server software is not installed yet, follow the procedures in the Installation and Configuration section. If the software is installed, all processes are started automatically. If you need to start the SS7/C7 software manually, enter ccss_start at the command line. ccss_start must be run as super user. To change to super user, enter the set user command (su) at the system prompt, and then the super user password. ccss_start
Starts SS7/C7 stack and Call Control processes. This command is put into the /etc/rc3.d/ S50ccss file during software installation and configuration.
Avaya CCSS 1000/2000 Feature Documentation August 2013 151 Operations, Administration, and Maintenance
Note:
• S50ccss is executed during system startup. It is normally not necessary to use ccss_start from the command line. The only time it would be valid is if the system were brought down manually and had to be restarted without rebooting. • ccss_start and ccss_stop must be run as user root. • In a fault tolerant server configuration, restarting a server that was brought down puts that server into the standby state. • If the system is configured for IUP, ccss_start checks for the $CCSSHOME/ etc/.noredund file on startup. If this file is present, the server boots up in non-redundant mode. If the file does not exist, ccss_start assumes a redundant server configuration.
System Shutdown Procedures Shutting Down the CCSS 2000
1. Block the circuits to keep new calls from being handled. Use the ccss_down command. Do not continue until ccss_down reports that there are no more calls in progress. 2. Enter super user mode by typing su at the system prompt. 3. For a Fault Tolerant system: • If the active server is being shut down: - Enter the "control server=local, action=shutdown;" command from mgmtui on the active server - Enter ccss_stop. • If the standby server is being shut down: - Enter the "control server=local, action=shutdown" command from mgmtui on the standby server - Enter ccss_stop. 4. Shut down the SS7/C7 processes using the ccss_stop command. Any applications that are running when ccss_stop is executed will be brought down immediately. See ccss_stop on page 153 for information on ccss_stop. 5. Stop the system by entering halt at the system prompt.
ccss_down
Blocks all configured circuits and reports the number of circuits with active calls until all circuits are idle.
152 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] CCSS Shutdown from mgmtui
Note:
• ccss_down blocks all circuits so they cannot take any more calls. Circuits with calls in progress can finish the current call, but no more calls are taken on that circuit. Calls in a transient state will be cleared. ccss_down reports the number of calls in progress every three seconds until there are no more calls. • Use ccss_down to bring down a system without killing any calls in progress. ccss_down does not kill any SS7/C7 or Call Control processes. Use ccss_stop to kill the processes.
ccss_stop
Stops the Call Control and SS7/C7 stack processes. See also ccss_start: ccss_start on page 151 ccss_down: ccss_down on page 152
Note:
• ccss_stop terminates all of the call control and SS7/C7 stack processes. All calls in progress are lost when ccss_stop is executed. • ccss_stop is used in conjunction with the ccss_down. Do not use this until ccss_down reports that there are no more calls in progress. • ccss_stop must be run as "root" user.
CCSS Shutdown from mgmtui
shutdown
Halts the Call Control and SS7/C7 stack processes. CONTROL SERVER=local, ACTION=shutdown;
Note:
• This command is issued from mgmtui to command an active or standby CCSS server to shut down. When issued on an active CCSS server, this command has the effect that it will halt the Call Control and the SS7/C7 stack processes. • It is always recommended, though not required, that the operator enters ccss_down from the Solaris command line before performing the 'control server=local, action=shutdown;' mgmtui command or ccss_stop from the command line on a server. Failure to do so may cause call-loss and forced-switchover if the server being shutdown is the active server in a fault-tolerant configuration.
Avaya CCSS 1000/2000 Feature Documentation August 2013 153 Operations, Administration, and Maintenance
• If the server being shutdown is the active server, the operator should enter the "control server=local, action=shutdown;" command on the active server before ccss_stop. Controlled switchover occurs before the active server is shutdown, and the remaining server remains active as a standalone (non-fault-tolerant) server. • If the server being shutdown is the standby server, then the operator should enter the control server=local, action=shutdown command on the standby server before ccss_stop. This command shuts the server down gracefully, leaving the active server active as a standalone (non-fault-tolerant) server. • ccss_down is only necessary if both servers are to be brought down.
Backup and Restore
The backup and restore procedures in this section assume that you have the original software installation and update (patch) media (including Solaris, in the event of a total disk failure). In this case, backup involves only making copies of those files that have been changed since the initial installation and any custom application files (if applicable). Restoring the system depends on how much needs to be restored. In the event of a total disk failure, the OS must be installed on the new disk first, followed by the SS7/C7 software (with any updates) and the custom files. To restore to an earlier software version, reinstall the desired SS7/C7 software (see SS7/C7 Server Software Installation on page 26) and any custom files.
Backup Devices and Options
You have several choices for backup devices. The Avaya Media Processing Server can be equipped with one or more drives or internal hard drives. Each device has a unique name.
Device Name Capacity Use internal drive varies with system varies with system daily or weekly configuration configuration backup of all system and application files secondary drive varies with system varies with system weekly backup of all configuration configuration system and application files
154 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Backup Methods
Backup Methods
You can choose different backup methods.
Method Use tar Transferring files to an internal/secondary drive. Use tar to archive files to a single 'tar' file. cp (copy) Backing up individual files or groups of files to other internal drives or directories.
Backing up with the tar Utility
The tar command combines and saves files to an internal or secondary drive.
Note: The tar command does not support multivolume backups. Use the command df to display the amount of disk space used by the file system. If you need to back up more than the capacity of your hard drive, split the backup into several backups (that is, back up individual partitions), and save the tar archives on a network drive or external USB drive.. Backing Up with the tar Utility
1. Open a UNIX command shell. 2. Move to the directory where the files are located (source directory). 3. Enter the tar command. • To backup to the present working directory, use the syntax: tar cvf
Note: Use a descriptive file name with the .tar extension for
Avaya CCSS 1000/2000 Feature Documentation August 2013 155 Operations, Administration, and Maintenance
You can also backup to an alternate directory or internal drive. See the Media Processing Server Series System Reference Manual for details on the tar command and for details and examples for using cp.
Displaying the Contents of a tar Backup
Display the table of contents for each backup to ensure that it is readable and complete. Displaying the tar Backup Contents
1. Open a UNIX command shell. 2. Enter the tar command. • To verify the contents of an internal, external or network mapped drive, move to the directory that contains the tar file and use the syntax tar tvf
Restoring with the tar Utility
Use the tar command to restore selected files or the entire backup. Restoring files with tar
1. Open a UNIX command shell. 2. Move to the directory where the files will be located (destination directory). 3. Enter the tar command. • To restore files from an internal, external, or network mapped drive, use cp to put the tar file in the destination directory and use the syntax tar xvf
Backing up to a Secondary Drive
The tar utility is used to archive the files to the secondary drive. It does not delete files from the destination file system that no longer exist in the source file system.
156 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Backing up to a Secondary Drive
1. Terminate applications that are using any of the files about to be backed up. 2. Use the format command to see the partition table sizes for the system and backup disks. For example:
# format Searching for disks...done AVAILABLE DISK SELECTIONS: 0 c1t0d0
# newfs /dev/rdsk/c1t1d0s0
Note: Do not execute newfs on the backup swap slice (usually slice 1). 4. Use the df command to verify where the slices are mounted.
# df -k Filesystem kbytes used avail capacity Mounted on /dev/dsk/c1t0d0s0 192807 161172 12355 93% / /dev/dsk/c1t0d0s6 1488575 799852 629180 56% /usr /proc 0 0 0 0% /proc fd 0 0 0 0% /dev/fd mnttab 0 0 0 0% /etc/mnttab swap 831000 16 830984 1% /var/run /dev/dsk/c1t0d0s4 192807 3767 179400 3% /var /dev/dsk/c1t0d0s5 5523086 1721729 3525203 33% /opt As shown previously, slices 0,6,4, and 5 should be backed up. Some file systems, such as proc, fd, mnttab, and swap are temporary memory for the duration of the bootup and can be ignored while backing up. Note that swap can also consist of slice1, the swap slice does not need to be backed up. Use swap -l to verify the device file (/dev/....) swap is using. In the example below, c1t0d0s1 can be omitted from backup.
# swap -l swapfile dev swaplo blocks free /dev/dsk/c1t0d0s1 32,25 16 1229664 1229664 5. Mount the corresponding root slice from the backup drive.
# mount /dev/dsk/c1t1d0s0 /mnt 6. Create a tar exclude file that shows the mounted filesystems not to tar from root.
# cd / # \df | awk ?{print $1}? > tarex (escape the df with a preceding \ in case an alias is modifying the output behavior) 7. Edit the tarex exclude file to delete the line containing root (do not exclude /). Add the ./ directory prefix to the file. Example of resulting exclude file:
# cat /tarex ./usr ./proc
Avaya CCSS 1000/2000 Feature Documentation August 2013 157 Operations, Administration, and Maintenance
./dev/fd ./etc/mnttab ./mnt ./var ./var/run ./opt 8. Tar root, excluding the mounted file systems.
# cd / # tar cvfX - tarex . | (cd/mnt; tar xfBp - ) 9. Create the mount points, on the root backup slice for the excluded directories. The directories to create are determined from the Mounted on column in the df command output. Based on the list of mounted /dev/[x], the following creates mount points on the backup root slice, presently mounted on /mnt.
# mkdir -p /mnt/usr /mnt/var /mnt/opt /mnt/proc /mnt/etc/mnttab /mnt/var/run 10. Install the boot block on the root backup slice. If the backup drive is not c1t1, change c1t1 to the backup target. The back-quoted command inserts the machine type that this command is executed on. # /usr/sbin/installboot /usr/platform/’/sbin/uname -i’/lib/fs/ufs/bootblk \ /dev/rdsk/ c1t1d0s0 11. Unmount the backup slice.
# cd / # umount /mnt 12. You can tar non root slices without an exclude file. Mount the corresponding slice from the backup drive. The following command mounts slice 5 of backup disk c1t1 onto /mnt.
# mount /dev/dsk/c1t1d0s5 /mnt 13. Change directory to the corresponding system drive mount point.
# cd /opt 14. Use tar to create an archive copy onto the backup drive. The following creates a tar file to standard output, which is piped to another tar command that changes directory to the backup drive and extracts the tar archive from standard input.
# tar cvf - . | (cd /mnt; tar xfBp - ) 15. Unmount the backup slice.
# cd / # umount /mnt 16. Continue steps 12 through 15 to mount, cd, tar, and umount each of the slices that need to be backed up.
158 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Restoring Entire Drive Using tar Utility
Restoring Entire Drive Using tar Utility
1. When the system drive fails, power down the system and remove the system drive (c1t0). 2. Remove the backup drive at c1t1 and place it in c1t0. 3. Power on and boot -rs.
Individual Directory Backup Using tar
Filesystem subdirectories can be backed up with tar when updates are isolated and only certain areas need to be backed up. The tar utility does not delete files from the backup slice, even if they no longer exist in the file system being copied from. To delete files on the backup slice, manually remove individual files and directories while keeping the remaining backup file system intact, or run newfs to delete the entire backup slice, then execute tar from scratch for the effected slice, as described in Backing up to a Secondary Drive on page 156. The following shows how to backup /opt/home/peri using tar. 1. Use the df command to see what slice is mounted on /opt.
# df -k /opt Filesystem /dev/d kbytes used avail capacit Mounted on sk/c1t0d0s5 11878657 6181095 5578776 y 53% /opt
2. Mount the corresponding slice from the backup. The following command mounts slice 5 of backup disk c1t1 onto /mnt.
# mount /dev/dsk/c1t1d0s5 /mnt 3. Change the present directory to backup.
# cd /opt/home/peri 4. Use tar to create an archive copy onto the backup drive. Be certain to specify the corresponding subdirectory on the target backup drive. The following commands create a tar file to standard output from /opt/home/peri, which is sent to another tar command that changes directory /mnt/home/peri and extracts the tar archive from
Avaya CCSS 1000/2000 Feature Documentation August 2013 159 Operations, Administration, and Maintenance
standard input. The directory being tarred to, /mnt/home/peri in this case, must already exist.
# tar cf - . | (cd /mnt/home/peri; tar xfBp - ) 5. Unmount the backup slice.
# cd / # umount /mnt
Restoring the Directories using tar
Subdirectories or an entire file system can be restored using tar on the backup file system. The following restores files onto /opt/bin. 1. Use the df command to see what slice is mounted on /opt.
# df -k /opt Filesystem kbytes used avail capacity Mounted on /dev/dsk/c1t0d0s5 11878657 6181095 5578776 53% /opt 2. Mount the corresponding slice from the backup drive. The following command mounts slice 5 of backup disk c1t1 onto /mnt.
# mount /dev/dsk/c1t1d0s5 /mnt 3. Change to the backup directory you want to restore.
# cd /mnt/bin 4. Use tar to restore an archive copy. Be certain to specify the corresponding subdirectory on the target drive. The following creates a tar file to standard output from /mnt/bin, which is sent to another tar command that changes directory /opt/bin and extracts the tar archive from standard input.
# tar cf - . | (cd /opt/bin; tar xfBp - ) 5. Unmount the backup slice.
# cd / # umount /mnt
Backing up with cp (Copy)
The UNIX cp command copies individual files or groups of files. Use this command to back up files to alternate directories and to copy files between directories. See the system manual pages for details and examples on using cp.
160 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Backup Tips
Backup Tips
• Store backup media in a safe place. • Write the date and the files you backed up on the label of each tape. • Handle backup media carefully. Follow all instructions included with the media • Write protect the media after you backup. Follow the instructions included with the backup media.
SS7/C7 Server Backup
At least two files need to be backed up on the SS7/C7 server: Example • $CCSSHOME/etc/ss7.conf: You should make a list of other files modified on the server. To backup the SS7/C7 server (note that this procedure assumes you are using tar to backup the files): Enter the following command at the command line: tar cvf
SS7/C7 Server Restore
To restore the SS7/C7 server (this assumes you have used tar for all of the backups): 1. Install the Solaris operating system (if required). Refer to the Sun system documentation for information. You will need a standard "peri" account. 2. Insert the SS7/C7 server software distribution tape into the tape drive and install the server software and any updates. See SS7/C7 Server Software Installation on page 26. 3. Connect external media or map a network drive containing tar backup archive files. 4. Enter the following commands in the order shown here to stop the CCSS server: ccss_down ccss_stop 5. Use the tar tvf command to view the contents of a tar archive.
Avaya CCSS 1000/2000 Feature Documentation August 2013 161 Operations, Administration, and Maintenance
Note the restore path of the files in the archive. tar tvf < archive_file_name>.tar. 6. Use cd to change to the root of the restore path on the CCSS system. 7. Use the tar xvf command to restore the archive to the CCSS system: tar tvf < archive_file_name>.tar.
Note: The tar archive file will not be in the current working directory. Use the full path to the archive tar file on the backup filesystem in the 'tar xvf' command. 8. Enter the following command to restart the CCSS system: ccss_start 9. Enter the following commands in the order shown here to use the restored software: ccss_down ccss_stop ccss_stop ccss_start
System Status and Statistics
Call Control Statistics
The ui Call Control User Interface program displays call control statistics, such as the number of outbound call attempts, and so on. Enter ui at the prompt to start in interactive mode. To get call control statistics, enter stats
The sample status report was taken from a live system with calls in progress. Therefore, not all of the statistics add up (for example, a call can be started by an application but the called party has not yet answered or rejected the call). When the system is idle, the statistics add up.
CIC 1.0-29 18:54:19-18:55:42 Call Statistics I_ATTMPT I_ANSWR I_RJCT I_TIMOUT I_FAIL O_ATTMPT 852 696 156 0 0 348 O_ANSWR O_RJCT O_TIMOUT O_FAIL 120 228 144 1032
System Statistics MTP_DOWN MTP_FAIL EXP_ISUP EXP_GDTM EXP_NWTM 588 804 0 0 0
162 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Call Control Statistics
AP_ISUP AP_RGSUC AP_RGFL VAS_CONN 0 1068 0 0
Inbound Call Attempts: The number of IAMs received by the server from I_ATTMPT the network. Inbound Calls Answered: The number of ANMs sent by the I_ANSWR applications. Inbound Call Rejected: The number of times the release messages (REL) I_RJCT were sent in response to IAMs from the network. Inbound Call Timeouts: The number of calls that could not be answered I_TIMOUT because no applications were available to respond to IAMs in time. Inbound Call Generic Failure: Any other type of inbound call failure. I_FAIL
Outbound Call Attempts: The number of IAMs sent by the applications. O_ATTMPT
Outbound Calls Answered: The number of answer messages (ANM) O_ANSWR received by the server from the network. Outbound Calls Rejected: The number of release (REL) messages O_RJCT received by the server in response to IAM requests sent by the applications. Outbound Call Timeouts: The number of outbound calls that were O_TIMOUT unsuccessful because the previous call had not been cleared by the network. Outbound Call Generic Failure: Any other outbound call failure. O_FAIL
MTP Down: The number of times the MTP was reported as down. The MTP_DOWN MTP has 30 seconds to come back up so all calls in progress can be resumed. This statistic is kept on a per-circuit basis, so the number indicates the number of lost connections multiplied by the number of active circuits. For example, assume a system has 100 active circuits. If the MTP goes down, each circuit will report the MTP down, thus changing this statistic to 100. If MTP_DOWN is reported as 500, it means that the MTP went down five times (100 lines reporting five MTP downs each) MTP Failure: The number of times the MTP was reported as down for MTP_FAIL more than 30 seconds. After 30 seconds, if the MTP does not come back, all calls are terminated (the applications receive REL messages). This statistic is kept on a per-circuit basis (see MTP_DOWN). Unexpected ISUP Message: The Call Control process received a EXP_ISUP message from the network which it was not expecting. This should not occur. Unexpected Guard Timer Expiration: Internal Call Control process timers EXP_GDTM expired when not expected. This should not occur.
Avaya CCSS 1000/2000 Feature Documentation August 2013 163 Operations, Administration, and Maintenance
Unexpected Network Timer Expiration: Network timers (kept by the Call EXP_NWTM Control process) expired when not expected. This should not occur. Application ISUP Error: The application sent a poorly formatted message AP_ISUP to the network (that is bad data) or sent a specific message during the wrong time of the call (for example, sending an IAM while a call is connected). Application Resource Request Successful: The number of times AP_RGSUC applications successfully allocated the ccss resource. Application Resource Request Failed: The number of times applications AP_RGFL requested the ccss resource and the request was denied. This statistic will be incremented only if the failure was a "hard" failure (see page 69). VAS or MPS Connection Failure: The number of times the link to the VAS_CONN application server was lost. This statistic is kept on a per-circuit basis (see MTP_DOWN).
Reset Call Control Statistics
Clear the call control statistics whenever the caller applications change. In a multiple server environment, this procedure must be performed on both servers. Resetting Call Control Statistics
1. Prevent any new call from coming in by entering ccss_down. 2. Enter ui to start the CCME user interface. 3. Enter stats cic * * reset to reset the CCME statistics. 4. Enter unblock cic * * to allow new calls to start coming in. 5. Enter q (or quit) to exit the user interface.
Redundancy Status
Use mgmtui User Interface program to query the redundancy status. Enter mgmtui at the prompt to start in interactive mode. To get the redundancy status:
Enter report server=all; at the command line (mgmtui). report server=all
164 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] MPS Resource Daemon (proxy) Command Summary
report server=all; report server=all; The Local Host Details: Local Host Name: ccss1 Local Server state : ACTIVE_WITH_STANDBY System Configuration: Fault Tolerant Local Server Type: A Remote Server Alias Name: ccssredund Remote Server Hostname1: ccss2 Remote Server state : STANDBY
MPS Resource Daemon (proxy) Command Summary
proxy
The MPS resource message server daemon, proxy is the message transport between CCME and the local CCSS resources. proxy translates messages between CIC format and VAS/MPS/Line number format. proxy -S resource -s service -E -k -n [-L destination] [-l logging] [-X a | i | o | n] -p -d proxy -H | -h proxy -v -S Sets the VVP resource name. This must be set to ccss for ISUP, or tcap for TCAP.. -s Sets the TCP service name or port. This is not needed for ISUP. For TCAP it should be 9892. -E Disables use of environment conditions. -k Sets the keepalive interval. -n Sets the redundancy mode. -n implies only one LAN is in use. Calls may be lost if the LAN fails. No -n implies that redundancy is active, and this may increase system load. -L Sets the destination for logging messages to one of the following values: console for main console window/screen or file for the log file name. -l Sets the logging level to one of the following values: emerg, alert, critical, error, warning, notice, info, deb1, deb2, or deb3. -p Enables ptimer child debugging. This is for use by Avaya only. -d Enables plib debugging. This is for use by Avaya only. -t Enables terse logging. Logging messages will not have process ID or timestamp information. This is for use by Avaya only. -h -H Displays the options list. -v Print the proxy version number and exit.
Avaya CCSS 1000/2000 Feature Documentation August 2013 165 Operations, Administration, and Maintenance
-c Enable call-protect/N+1 redundancy proxy behavior.
Note: The proxy command is normally inserted into the $MPSHOME/common/etc/gen.cfg file during software installation. The minimum usage is: proxy -S ccss The recommended usage is: proxy -S ccss -L console -l info -k 10 -n
Proxy Debug
The proxy executable implements the CCSS resource. Proxy debugging is required when application and call control have lost sync of each other. The steps to execute are as follows: peri@ccss1 {1} tty /dev/pts/1 peri@ccss1 {2} cat >> /tmp/proxy logd redir /dev/pts/1 ---> Press return to get the following menu which confirms about redirect completion Usage: Status Requests:
st[atus] < arg> cl[ient] - information on client network connections app[liciation] - information on application resource usage sock[et] - information on all connections pro[xy] - proxy process status lim[its] - information on resource compile time limits all - complete status report in[fo] report message statistics
Log Level: logl[evel] < level> em[erg] - emergency / fatal al[ert] - serious system failure requiring attention cr[itical] - serious system error er[ror] - system error wa[rning] - possible system error in[fo] - information message deb1 - message flow debugging deb2 - internal systems debugging deb3 - network message dump deb3 is known to cause problems cause problems API debugging: libd[bg] # Log Destination: logd[st] co[nsole] | er[ror] [on|off] logd[st] redirect [file|device] logd[st] redirect close
Commands: re[set] - reset all i/o connections term - terminate
st all <------To get the complete status report on proxy
::::::::: Proxy Status Report [9/17/98 17:35:02] :::::::::
166 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Proxy Debug
:::::::::::::::::::: Proxy Report :::::::::::::::::::::
version: 3.2 Version info build date: Wed Oct 8 08:56:07 1997 api version: 4.2 api build date: Tue Oct 7 16:26:54 1997 Network Mode: Standby Network Keepalive: 10 seconds
Longest vvp op: access lockfile (0 sec)
Last Reset: 9/14/98 14:22:14 Resets since start: 0 Argument List: proxy -S ccss -L cons -l info -k 10 -n
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
::::::::::::::: Proxy Client List :::::::::::::::::::::::: client [pintail/25256]: 22: 192.84.160.137:40991 [Traffic Lan] Available [Q: 0] Seq No: last in = 113 next out = 3 servicing vps 18 lines 1-48 :::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Above is the information for the CCSS systems which are connected.
::::::::::::: Proxy Open File Descriptor List :::::::::::: 00 : (reserved) 01 : (reserved) 02 : (reserved) 08 : connection to alarmd (VOS) vps #17 09 : connection to alarmd (VOS) vps #18 10 : connection to alarmd (VOS) vps #19 11 : connection to alarmd (VOS) vps #20 12 : connection to alarmd (VOS) vps #317 14 : ptimer pipe 15 : debug fifo at /tmp/proxy 16 : bound local tcp endpoint 192.84.101.1:9891 17 : bound local tcp endpoint 207.94.85.29:9891 18 : bound local tcp endpoint 210.6.30.213:9891 19 : bound local tcp endpoint 210.6.31.213:9891 20 : bound local tcp endpoint 210.6.32.213:9891 21 : bound local tcp endpoint 210.6.33.213:9891 22 : client [pintail/25256] tcp socket (Available) 192.84.160.137:40991 [Q: 0] 24 : vms socket to vps MCP1.18:18 vvp port 1 25 : vms socket to vps MCP1.20:20 vvp port 2 26 : vms socket to vps MCP1.19:19 vvp port 3 27 : vms socket to vps MCP1.17:17 vvp port 4
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ::::::::::::::::: Proxy Bind List ::::::::::::::::::::::: No unbound sockets :::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ::::::::::::::: Proxy App Status :::::::::::::::::::::::: VPS #17: Line #001: state=[ WO_RSC] Wait: N [Q: 0] Last io: 9/17/98 17:25:52 Line #002: state=[ WO_RSC] Wait: N [Q: 0] Last io: 9/14/98 16:55:45 Line #003: state=[ WO_RSC] Wait: N [Q: 0] Last io: 9/14/98 16:55:45 Line #004: state=[ WO_RSC] Wait: N [Q: 0] Last io: 9/14/98 16:55:45 Line #005: state=[ WO_RSC] Wait: N [Q: 0] Last io: 9/14/98 16:55:45 Line #006: state=[ WO_RSC] Wait: N [Q: 0] Last io: 9/14/98 16:55:46 Line #007: state=[ WO_RSC] Wait: N [Q: 0] Last io: 9/14/98 16:55:46 ...... Line #042: state=[ WO_RSC] Wait: N [Q: 0] Last io: 9/14/98 16:55:52
Avaya CCSS 1000/2000 Feature Documentation August 2013 167 Operations, Administration, and Maintenance
Line #043: state=[ WO_RSC] Wait: N [Q: 0] Last io: 9/14/98 16:55:52 Line #044: state=[ WO_RSC] Wait: N [Q: 0] Last io: 9/14/98 16:55:52 Line #045: state=[ WO_RSC] Wait: N [Q: 0] Last io: 9/14/98 16:55:52 Line #046: state=[ WO_RSC] Wait: N [Q: 0] Last io: 9/14/98 16:55:52 Line #047: state=[ WO_RSC] Wait: N [Q: 0] Last io: 9/14/98 16:55:52 Line #048: state=[ WO_RSC] Wait: N [Q: 0] Last io: 9/14/98 16:55:53 VPS #18: Line #001: state=[ WO_RSC] Wait: N [Q: 0] Last io: 9/17/98 17:33:19 VPS #19: Line #001: state=[ WO_RSC] Wait: N [Q: 0] Last io: 9/17/98 16:58:50 Line #002: state=[ WO_RSC] Wait: N [Q: 0] Last io: 9/14/98 16:55:16 Line #003: state=[ WO_RSC] Wait: N [Q: 0] Last io: 9/14/98 16:55:09 Line #004: state=[ WO_RSC] Wait: N [Q: 0] Last io: 9/14/98 16:55:24 Line #005: state=[ WO_RSC] Wait: N [Q: 0] Last io: 9/14/98 16:55:18 Line #006: state=[ WO_RSC] Wait: N [Q: 0] Last io: 9/14/98 16:55:26 Line #007: state=[ WO_RSC] Wait: N [Q: 0] Last io: 9/14/98 16:55:26 Line #046: state=[ WO_RSC] Wait: N [Q: 0] Last io: 9/14/98 16:55:32 Line #047: state=[ WO_RSC] Wait: N [Q: 0] Last io: 9/14/98 16:55:32 Line #048: state=[ WO_RSC] Wait: N [Q: 0] Last io: 9/14/98 16:55:32 VPS #20: Line #001: state=[ WO_RSC] Wait: N [Q: 0] Last io: 9/17/98 17:35:00 ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
::::::::::::::: Proxy Queue Status ::::::::::::::::::::::: queue buffer pool : 1536 of 1536 1024 byte buffers available :::::::::::::::::::::::::::::::::::::::::::::::::::::::::: What follows are proxy hardcoded limits.
:::::::::::::::::: Proxy Compile Limits ::::::::::::::::::
Maximum Hostname Length: 32 Maximum TCP Service Name Length: 32 TCP Send Buffer Size: 65536 TCP Receive Buffer Size: 65536 Maximum Simultaneous VPS’s: 16 Maximum Application per VPS: 256 Maximum Connections per Client: 4 Maximum Simultaneous Clients: 6 Maximum Active Descriptors: 60 Maximum Local IP Interfaces: 8 Message Queue Buffer Size: 1024 bytes Message Queue Buffer Pool Size: 1536 entries Total Message Queue Memory Usage: 1683456 bytes getfail data on no resources: ’server unavailable’
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Usage:
Status Requests: t[atus]
168 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Diagnostics and Troubleshooting
in[fo] - information message deb1 - message flow debugging deb2 - internal systems debugging deb3 - network message dump API debugging: libd[bg] # Log Destination: logd[st] co[nsole] | er[ror] [on|off] logd[st] redirect [file|device]> logd[st] redirect close
Commands: re[set] - reset all i/o connections term - terminate
Diagnostics and Troubleshooting
User Interface to the Call Control Process
ui
Text-based interface to the Call Control process. ui provides control over many lower-level functions of the system and is not intended for normal system operations. ui [-h | -n #] [ -b
Avaya CCSS 1000/2000 Feature Documentation August 2013 169 Operations, Administration, and Maintenance
cic 1 * (all lines in trunk 1) mps vas1001 3 1 (VPS 3 on vas1001, circuit 1) mps vas1001 3 1-10 (VPS 3 on vas1001, circuits 1-10) mps vas1001 3 * (VPS 3 on vas1001, ALL circuits) mps vas1001 * * (all circuits associated with vas1001)
Interactive mode The commands available within ui are: commands • help - Display the commands available • block
See Call Control Statistics on page 162 for sample output and an explanation of the statistics fields.
status
status description DOWN Hard Circuit is down and cannot support calls, ISSUE GET ccss will fail. IDLE Circuit is idle. The application has not allocated the CCSS resource.
170 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] User Interface to the Call Control Process
status description IAM seen, No Get Inbound call is detected but application has not allocated the resource. GET received Application has allocated the resource, no call is currently active. IAM seen, GET seen Inbound call delivered to application, waiting for response. Inbound busy Inbound call setup complete.
Release Sent Out Circuit is releasing, awaiting release complete from the network IDLE No Free RLC has been received, APP has not freed the resource
IAM sent Application IAM has been transmitted (for outbound calls only). ACM seen ACM message received for outbound call setup.
Outbound Busy Outbound call setup complete.
Outbound Suspended Outbound call suspended.
delayed release Delayed release sequence in progress.
ACM seen Non-C7 ACM message received for outbound call setup. Interworking was encountered Outbound Busy Non-C7 Outbound call setup complete. Interworking was encountered. Outbound-C7 Suspended Outbound call suspended. Interworking was encountered.
Proxy Down Connection with the VAS or MPS is down.
Circuit Clearing The circuit is busy. The flags will identify the operation in progress. GET seen, Clearing The circuit is busy. The application has allocated the resource. IDLE, must RLC Release Acknowledge must be sent on this circuit.
Outbound held, Clearing An outbound call is held while the circuit is busy.
Address Incomplete, No Overlap receiving of the called party address is still in GET progress. No application attached to the line. Address Incomplete, GET Overlap receiving of the called party address is still in seen progress. Application is attached to the line. In Suspend The call on the circuit had been suspended.
IAM (COT) Performed, No IAM indicating continuity check of previous circuit received. Get The application has not yet allocated the CCSS resource
Avaya CCSS 1000/2000 Feature Documentation August 2013 171 Operations, Administration, and Maintenance
status description IAM (COT) Performed, Get IAM indicating continuity check of previous circuit received. The application has allocated the CCSS resource. IAM (COT) Current, Get IAM indicating continuity check of current circuit received. The application has allocated the resource. \CCR, GET A continuity check is being performed on the current circuit. The application has allocated the resource. CCR, Wait (COT) Out A continuity check has been requested on the current circuit. Waiting for COT from application. Soft Down, CCR Held CCR held. Waiting for existing call to clear.
IAM (COT) Overlap Overlap receiving. IAM indicating continuity check of Performed, No Get previous circuit received. The application has not yet allocated the CCSS resource IAM (COT) Overlap Overlap receiving. IAM indicating continuity check of Performed, Get previous circuit received. The application has allocated the CCSS resource. IAM (COT) Overlap Overlap receiving. IAM indicating continuity check of Current, Get current circuit received. The application has allocated the resource. Loop Response (CCR) Wait Waiting for response from DSSI for CCR received from N/ W Loop Response (IAM) Wait Waiting for response from DSSI for IAM with continuity required from N/W SHUTDOWN When the "control sever=lcoal, action=shutdown;" command is used to shut down a server. Call control circuit status report will show the circuit state as "Shutdown [ ]"
There may be some overlap in how lines are reported. For example, a circuit that has a block put on it but is still handling a call is considered blocked and active. After the call is terminated, the line is reported only as blocked.
SS7/C7 Process Logging Messages
Some SS7/C7 processes produce logging messages for diagnostics and debugging. Generally, most of the message are intended for Avaya personnel only. However, there are some log files which indicate system/SS7/C7 process startup information and the time of the last full software installation. The following table outlines the log files on the CCSS 1000/2000:
172 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] SS7/C7 Process Logging Messages
File (in $CCSSHOME/etc) Description ccme0.log The call control process log. The messages in this file are intended only for Avaya personnel. mgmt.log The Management process log. The messages in this file are intended only for Avaya personnel. tcu0.log The TCAP User process log. The messages in this file are intended only for Avaya personnel. start.log The system/ccss start log. The messages in this file are intended only for Avaya personnel. The following are SS7/C7 process start or stop logs procmon.ccme.log When the ccme process is started or stopped, it is noted in the process monitor logs. procmon.ccss_logd.log When the ccss_logd process is started or stopped it is noted by the process monitor logs. procmon.ccss_stat.log When the ccss_stat process is started or stopped it is noted by the process monitor logs. procmon.ccssalarm.log When the alarm collector process is started or stopped it is noted by the process monitor logs. procmon.mgmt.log When the configuration manager process is started or stopped it is noted by the process monitor logs. procmon.mti.log When the MTP3/ISUP/TCAP software process is started or stopped it is noted by the process monitor logs. procmon.mb.log When the MTP3/btoss software process is started or stopped it is noted by the process monitor logs. procmon.st_collect When the statistics collection process is started or stopped it is noted by the process monitor logs. The following are for Avaya internal use only ptimer.log1 ptimer.log2 Debug data for the CCSS timer processes. timer.log1 timer.log2
procmon procmon is the process manager used on the CCSS. procmon is responsible for monitoring the start and stop of all software processes. In cases where a process crash occurs, procmon will restart that process. The procmon process checks if the environment variable CCSSNOLOOP exists and if the file that the variable references is executable. If the file is executable, procmon invokes the system command passing as the parameter as the system file name when the process is terminated. If CCSSNOLOOP is not set or if the file is not executable, the normal procmon functionality is invoked. A maximum number of process restarts can take place in one hour. If the process
Avaya CCSS 1000/2000 Feature Documentation August 2013 173 Operations, Administration, and Maintenance
fails more than MAX_RESTARTS (which is set to 20) times in the hour, the process is not restarted.
Note: If the process to monitor is ccss_stat then the CCSSNOLOOP check is not completed and the normal functionality of procmon is invoked. Example of normal start and stop of process
[10/29/98 08:47:21]procmon.14715: INIT [10/29/98 08:47:21]procmon.14716: START [/opt/ccss/bin/ccme] [10/29/98 08:47:54]procmon.14715: KILLING [/opt/ccss/bin/ccme] [10/29/98 08:47:54]procmon.14715: EXIT
Example of crash and restart of process
[10/29/98 10:16:11]procmon.15327: INIT [10/29/98 10:16:11]procmon.15328: START [/opt/ccss/bin/ccme] [10/29/98 10:31:51]procmon.15327: ABNORMAL EXIT [/opt/ccss/bin/ccme] signal 11 core: N [10/29/98 10:31:51]procmon.15367: RESTART [/opt/ccss/bin/ccme]
Service Affecting Commands
Note: The following list is a list of the commands that affect the services in action. You should take caution before executing any of the following commands: • Shutdown of CCSS machine • ccss_stop or ccss_down on CCSS system • Shutdown command (control action=shutdown) from MGMTUI • Rebooting of DCC3K hardware • Resetting the circuits from UI might affect service (UI reset) In addition to the preceding commands, the following commands might affect the service. It is strongly recommended not to give the following: • TRACE for multiple layers should not be enabled at the same time. For details on how to enable trace for a layer, see Trace Commands on page 127. • Status on all circuits from UI prompt ( that is, " status cic * * state" command ) might consume the CPU capacity. It is recommended to issue commands in a circuit group
174 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Service Affecting Commands
manner ( that is, "status cic
Avaya CCSS 1000/2000 Feature Documentation August 2013 175 Operations, Administration, and Maintenance
176 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Chapter 6: ISUP Application Programming
This chapter covers: 1. Basic Call Setup, Processing and Teardown Procedures 2. Call Referral Setup and Message Exchange 3. ISUP Message Data Items
ISDN User Part (ISUP) Applications that run in an SS7 environment have access to network signaling messages (the signaling messages are passed from the CCSS to the application server). The MPS application server views the signaling server as a shared resource. An application can obtain the resource when it is ready to handle a call, process the signaling information, and free the resource when the call is completed. Direct access to the signaling messages enables call setup, coordination, and teardown using application logic. The network messages contain information about a call that can be used for a variety of applications such as answering a call based on the caller ID, using caller information to allow different levels of access to the application functions, and so on. Avaya provides sample applications ($CCSSHOME/samples/ppro/*) that perform the basic call setup and teardown procedures that are documented in the following sections. These samples demonstrate how an application receives calls, originates calls, and performs call transfer functions. The sample MPS Developer application files for ANSI ISUP are placed in $CCSSHOME/samples/ppro/* during installation. ISUP can be run in both ANSI, ETSI, ITU, and Telcordia modes. The applications assigned to a particular trunkgroup must be of the same variant. The system can run in mixed mode with some of the trunkgroups configured for ITU and the others for ANSI88 or ANSI (default ANSI92). The configuration files must be set up appropriately.
Application Setup - Resource Allocation
Allocate the CCSS resource using an ISSUE GET ccss. In most circumstances, when you use the MPS Developer examples as a starting template, it is not necessary to modify the Containers that interact with the CCSS.
Avaya CCSS 1000/2000 Feature Documentation August 2013 177 ISUP Application Programming
Condition Mode
When Condition Mode (recommended) is used for receiving messages from CCSS, all messages are sent to the application as condition data. To indicate condition mode, the mode field of the GET CCSS must have the value isup, cond_msg. If the allocation fails, delay application execution for 10 seconds (recommended) before continuing any other processing (the delay prevents the server from becoming overwhelmed with allocation requests). Do not delay less than 5 seconds. Delays longer than 10 seconds can cause calls to be rejected because the application did not respond in time. After the delay, the application should retry allocating the resource. If the resource cannot be allocated, one of the following is returned as part of the failure condition (getfail ) data (check the ConditionData System data card):
Message Cause ccss The application server side CCSS software is not active. ccss: server unavailable The application server side CCSS software has lost contact with the CCSS. ccss-hard: Circuit Blocked The network will perform no more call processing. ccss-hard: MTP Down There is a problem with the physical link between the CCSS and the switch.
The last two messages are generated because of network problems that can only be fixed at the network level. If the application receives these messages, call availability might not be restored quickly (it is up to the network to determine when everything is working again). The following diagram illustrates the message exchange during call setup:
178 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Network Message Exchange
1. The application tries to get the CCSS signaling resource. 2. The application receives the resource allocation success or failure condition (it does not need to explicitly handle the gotres success condition).
Network Message Exchange
SS7/C7 signaling does not generate or use the same types of conditions and automatic call setup or teardown functions provided with other phone line protocols. For example, in most standard environments, the application receives a disc condition if the caller hangs up. In an SS7/C7 environment, the application receives a single condition from the CCSS that it must analyze to determine the message type.
Note: The application must first allocate the message signaling resource to send or receive network messages (see Application Setup - Resource Allocation on page 177). The following table lists the messages that are commonly exchanged in ISUP SS7/C7 applications:
Message Name Application Comments Message Delivery Type IAM Initial Inbound or In an inbound receive resource/ send Address Outbound application, there is a resource. Message call ready to be handled. In Condition Mode: This should not come ccs7cc condition (with from the network while a condition cause) call is in progress. In an outbound application, IAM starts an outbound call. IAM is used only when initiating the call.
Avaya CCSS 1000/2000 Feature Documentation August 2013 179 ISUP Application Programming
Message Name Application Comments Message Delivery Type ACM Address Outbound The call placed by an receive resource Complete outbound application In Condition Mode: Message has found the ccs7cc condition (with destination party's line. condition cause) This is normally returned after sending an IAM. ANM Answer Inbound/ In an outbound receive resource/send Message Outbound application, the called resource party has picked up the In Condition Mode: line and there is an end- ccs7cc condition (with to-end voice/data condition cause) connection between the two parties. This is normally sent after an ACM. In an inbound application, ANM informs the network that the application will accept the incoming call. This is sent after an IAM is received from the network. CON Connect Outbound The called party has receive resource picked up the line and In Condition Mode: there is an end-to-end ccs7cc condition (with voice or data connection condition cause) between the two parties. CON replaces ACM and ANM in some environments. CPG Call Outbound There are call progress ccs7cc condition (with Progress events occurring on the condition cause) called party's line. The CPG messages are sent in the interval between sending an IAM and receiving the ANM. Take appropriate action depending on the Call Progress message. REL Release Inbound or In an inbound ccs7cc condition (with Outbound application, sending condition cause) REL immediately after receiving an IAM informs the network that
180 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Sending Messages
Message Name Application Comments Message Delivery Type the application does not want the call. After the call is connected in inbound and outbound applications, sending REL terminates the call. Receiving REL means that the other party has disconnected. If a REL is received without containing any parameters, it is implicit that the circuit was reset by the network. SUS Suspende Inbound or The other party has put ccs7cc condition (with d Outbound the call on hold. The condition cause) application can either end the call (send a REL) or wait for a resume message (RES) from the network. This can occur anytime after the call is established. RES Resume Inbound or The other party has ccs7cc condition (with Outbound taken the call off hold. condition cause) This is sent after a call is suspended (SUS). OLM Overload Outbound The network is in an ccs7cc condition (with Overload state for this condition cause) circuit.
Note: There is an additional header for condition data. This header will contain the msg-present flag to indicate if there is additional data in the message. In addition, there will be a textual string at the start of the message to indicate the type of message. (for example, REL).
Sending Messages
Messages are sent using the SEND RESOURCE ccss function:
Avaya CCSS 1000/2000 Feature Documentation August 2013 181 ISUP Application Programming
Always check the Wait and Failure options when you send a message to the network. This prevents the application from continuing execution in case the SEND RESOURCE fails. If the SEND fails, the reason for failure is passed back in the ConditionData System data card.
Message Cause ccss: Circuit Seized An outbound call attempt failed because the circuit was already being used for an inbound call. ccss: Wrong State The message is not valid for the current state of the circuit. ccss: Invalid Message Content The message has missing/invalid contents. ccss: Transmit Error An error occurred while the message was being transmitted. ccss: MTP Down The message could not be transmitted because the signaling links are unavailable. ccss: Circuit Remotely The message could not be transmitted because the circuit Blocked was remotely blocked. ccss: Circuit Locally Blocked The message could not be transmitted because the circuit was locally blocked. ccss: Transmit Timeout IAM transmission failed because the previous call was not cleared.
For information about the parameters that must be provided for outbound messages, see ISDN User Part (ISUP) Message Data Items on page 212.
Receiving Messages
The application receives network messages in two ways:
1. The application waits on a RECEIVE RESOURCE ccss. The data variable is filled when the network message arrives:
182 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Voice Path Connection
The sample applications define two data structures for receiving and comparing network messages. The ISUP-Message-Out folder contains native MPS Developer data structures which represent the messages in the ISUP message specification of the appropriate country variant. Refer to the specification document for information about the available messages and their structure. The ISUP- Message-In composite is a set of data structures meant to hold incoming network messages.
Always receive network messages into the ISUP-Message-In.Msg-Read- Buffer data record. To determine the message type, compare the message- type variable from the ISUP-Message-In composite to the appropriate message type in the ISUP-Message-Out folder. 2. The application receives the ccs7cc condition. The network message is retrieved by calling the external function condition-data with the argument ISUP-Var- CCS7CC-COND-DATA.CCS7CC-COND-BUF.
The ISUP-Var.CCS7CC-COND-DATA.CCS7-COND-BUF variable is intended to receive any incoming server messages passed through the ccss7cc condition data. ccs7cc is also generated for conditions other than incoming network messages. The CCS7CC-ISUP- PRESENT variable is set to a non-zero value if the condition is generated by an incoming network message.
If it is non-zero then the contents of ISUP-Var.CCS7CC-COND-DATA.CCS7CC-COND- STRUCT.CCS7CC-ISUP-MSG-PARTS should be assigned to ISUP-Message-In.Msg- Read-Buffer.
Voice Path Connection
In the SS7/C7 environment, the application is not automatically connected to the voice path when an incoming or outgoing call is ready to begin. The application must force the line into a connected state by using an Originate block.
Avaya CCSS 1000/2000 Feature Documentation August 2013 183 ISUP Application Programming
Originate should not be issued until all call setup messages have been exchanged and Avaya Media Processing Server (MPS) I/O operations are about to begin. This ensures that the call is not reported as connected by the statistics and status processes until the call is established and the voice paths are connected.
Receiving an Incoming Call (Receive Resource Mode)
A network call attempt is indicated when the application receives an IAM from the network and is answered when the application sends an ANM.
After successfully allocating the CCSS resource, handle the vrto condition. vrto is generated if the vpsrcvtime timer expires (waiting for the IAM from the network). Do not ignore the vrto condition. Ignoring vrto might cause the application to wait forever for input from the signaling server. Repeat the receive resource request if vrto is generated.
To get the IAM message from the network, issue a RECEIVE RESOURCE ccss. When the application receives a message from the network, verify that it is an IAM (compare IAM- MESSAGE-TYPE from the provided IAM folder to message-type in the provided incoming message composite). If the message is an IAM, you can check other information in the IAM message to determine if you want to accept or reject the call. For this discussion, it is assumed that all calls are accepted.
To accept a call, send an ANM using SEND RESOURCE ccss (with Wait and Failure selected), then send the Originate to connect the voice paths (see Voice Path Connection on page 183).
Note: You can also configure ISUP to support application transmission of the message CON. For the application to transmit CON, AUTO_ACM must be set to 0 (disabled). CON is equivalent to ACM (Address Complete) and ANM (Answer). The following diagrams illustrate the message exchange while accepting an incoming call:
184 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Incoming Call Message Exchange
Incoming Call Message Exchange ISUP, with AUTO_ACM
1. The application waits on a RECEIVE RESOURCE ccss for the incoming IAM. 2. The network sends the IAM message. When the application receives the message, it can check the message data and determine whether to accept or reject the call. 3. The server automatically responds with an ACM message when it receives an IAM. 4. The application sends either an answer message (ANM) or a release message (REL). 5. If the application accepts the call, it sends an Originate to force the voice path connection (and set the MPS in a connected state for status and statistics reports). 6. The MPS returns the origcmp condition. This is normally ignored.
ISUP, without AUTO_ACM
Avaya CCSS 1000/2000 Feature Documentation August 2013 185 ISUP Application Programming
1. The application waits on a RECEIVE RESOURCE ccss for the incoming IAM. 2. The network sends the IAM message. When the application receives the message, it can check the message data and determine whether to accept or reject the call. 3. The application sends a connect message (CON). 4. If the application accepts the call, it sends an Originate to force the voice path connection (and set the MPS in a connected state for status and statistics reports). 5. The MPS returns the origcmp condition. This is normally ignored.
When the ANM is sent in response to an IAM and the voice path is connected, the call is connected "end to end" and is now billable. Avaya suggests that the application play a ring tone so the caller knows the phone is ringing. The number of ring tones is similar to the answer environment statement in a normal call processing environment where the phone rings before the call is answered. ISUP with AUT_ACM OFF and OVERRIDE_ACM ON
Network Server Application MPS
------IAM------IAM------>|
|<------CPG------|
186 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Originating an Outbound Call (Receive Resource Mode)
<------ACM------|
<------CPG------|
<------ANM--- |<------CON------|
|---orignate------>|
|<---origcmp------|
1. The application waits on a receive resource CCSS for an incoming IAM. 2. The network sends IAM message. When the application receives the message, it checks the message data to determine whether to accept or reject the call. 3. The application sends a Progress (CPG) message. 4. The server automaticall responds with an ACM message when it receives a CPG message from application. 5. If the application accepts the call, it sends the Originate to force the voice path connection. 6. The MPS returns the origcmp condition. This is normally ignored. It is the ability to configure the CCSS server to selectively send ACM, CPG, and optionally, ANM, when AUTO_ACM ccme option is OFF and Override_ACM is ON. To achieve the call-flow described in the previous procedure, one application must have the ability to send ACM, CPG (cpg is used to open voice path), and ANM. If the call is to be billed, send a ANM; if the call is not to be billed (free network call announcement) then the application does not send ANM.
Originating an Outbound Call (Receive Resource Mode)
Originating an outbound call involves sending an IAM to the network and waiting for the network confirmation that the call is established. To start a call, fill in the appropriate information into the IAM fields and send the IAM to the network using SEND RESOURCE ccss. After sending the IAM, the application should receive an ACM and ANM consecutively (the application waits on two consecutive RECEIVE RESOURCE ccss functions). If the ACM or ANM does not arrive as indicated by vrto, assume that the call cannot be completed and begin normal call teardown. In some SS7/C7 implementations, a CON message replaces the ACM and ANM so the incoming message type should always be checked.
Avaya CCSS 1000/2000 Feature Documentation August 2013 187 ISUP Application Programming
In general, the ACM means that the called party is alerted (that is, the phone is ringing) and the ANM means the called party has picked up and there is an end-to-end voice connection. However, in some specific implementations of SS7/C7, there is already be an end-to-end voice connection by the time the ACM returns. ANM always indicates that there is an end-to-end connection at that time. After receiving an ANM (or CON), send an Originate to connect the voice paths (see Voice Path Connection on page 183). The following diagram shows the messages exchanged when starting an outbound call:
188 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Originating an Outbound Call (Receive Resource Mode)
1. The application sends out the IAM to start a phone call. The message contains all of the information necessary to reach the desired party. 2. The application waits for an ACM message from the network. 3. The network sends the ACM message. This indicates that the called party has been reached. 4. The application waits for an ANM message from the network. 5. The network sends the ANM message. This indicates that the called party has picked up and there is now an end-to-end voice connection. The application can begin normal call processing. 6. The application sends Originate to connect the voice paths. 7. The MPS returns the connect (origcmp) condition (usually ignored).
Avaya CCSS 1000/2000 Feature Documentation August 2013 189 ISUP Application Programming
Receiving an Incoming Call (Condition Mode)
A network call attempt is indicated when the application receives an IAM from the network and is answered when the application sends an ANM.
190 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Handle the ccs7cc and vrto condition
Handle the ccs7cc and vrto condition
Example • ccs7cc is generated if CCSS has sent condition data to the application. • vrto is generated if the vpsrcvtime timer expires. If the ccs7cc condition is received, the handler should check the type of the message received and verify that an IAM was received.
If the vrto condition is received, the application should continue to wait for IAM. The application should issue a wait system service command. This command will be interrupted if a ccs7cc or vrto condition occurs. A vrto condition should cause the application to issue a wait system service command again. A ccs7cc condition should be checked to verify that an IAM was received.
When a ccs7cc condition occurs, copy the data received in the condition using the External Function condition-data with the argument ISUP-Var.CCS7CC-COND-DATA.CCS7CC- COND-BUF. Check if the CCS7CC-ISUP-PRESENT flag is set to 1. If the flag is set to 1, copy the data from CCS7CC-ISUP-MSG-PARTS to Msg-Read-Buffer. When the application receives a message from the network, verify that it is an IAM by comparing IAM-MESSAGE-TYPE from the provided IAM folder to message-type in the provided incoming message composite. If the message is an IAM, you can check other information in the IAM message to determine if you want to accept or reject the call. For this discussion, it is assumed that all calls are accepted.
To accept a call, send an ANM using SEND RESOURCE ccss (with Wait and Failure selected) and send the Originate to connect the voice paths (see Voice Path Connection on page 183).
Note: You can configure ISUP to support application transmission of the message CON. For the application to transmit CON, AUTO_ACM must be set to 0 (disabled). For configuration details, see CONFIG CCME_OPTION on page 63. CON is equivalent to ACM (Address Complete) and ANM (Answer). The following diagrams illustrate the message exchange while accepting an incoming call:
Avaya CCSS 1000/2000 Feature Documentation August 2013 191 ISUP Application Programming
Incoming Call Message Exchange ISUP, with AUTO_ACM
1. The application issues a wait system service command to wait for a ccs7cc condition. 2. The network sends the IAM message. When the application receives the message, it can check the message data and determine whether to accept or reject the call. 3. The server automatically responds with an ACM message when it receives an IAM. 4. The application sends either an answer message (ANM) or a release message (REL). 5. If the application accepts the call, it sends an Originate to force the voice path connection (and set the MPS in a connected state for status or statistics reports). 6. The MPS returns the origcmp condition. This is normally ignored.
ISUP, without AUTO_ACM
192 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Originating an Outbound Call (Condition Mode)
1. The application issues a wait system service command to wait for a ccs7cc condition. 2. The network sends the IAM message. When the application receives the message, it can check the message data and determine whether to accept or reject the call. 3. The application sends a connect message (CON). 4. If the application accepts the call, it sends an Originate to force the voice path connection (and set the MPS in a connected state for status or statistics reports). 5. The MPS returns the origcmp condition. This is normally ignored.
When the ANM is sent in response to an IAM and the voice path is connected, the call is connected end-to-end" and is now billable. It is suggested that the application play a ring tone so the caller knows the phone is ringing. The number of ring tones is similar to the answer environment statement in a normal call processing environment where the phone rings before the call is answered.
Originating an Outbound Call (Condition Mode)
Originating an outbound call involves sending an IAM to the network and waiting for the network confirmation that the call has been established. To start a call, fill in the appropriate information into the IAM fields and send the IAM to the network using SEND RESOURCE ccss. After sending the IAM, the application should receive an ACM and ANM consecutively (the application will
Avaya CCSS 1000/2000 Feature Documentation August 2013 193 ISUP Application Programming
handle two ccs7cc conditions). If the ACM or ANM does not arrive before a vrto condition is received assume that the call cannot be completed and begin normal call teardown. In some SS7/C7 implementations, a CON message replaces the ACM and ANM so the incoming message type should always be checked. In general, the ACM indicates that the called party is being alerted (that is, the phone is ringing) and the ANM means the caller picked up and there is an end-to-end voice connection. However, in some specific implementations of SS7/C7, there is already an end-to-end voice connection by the time the ACM returns. ANM always indicates that there is an end-to-end connection at that time. After receiving an ANM (or CON), send an Originate to connect the voice paths (see Voice Path Connection on page 183). The following diagram shows the messages exchanged when starting an outbound call:
1. The application sends out the IAM to start a phone call. The message contains all of the information necessary to reach the desired party. 2. The application waits for an ACM message from the network. 3. The network sends the ACM message. This means that the called party has been reached. 4. The application waits for an ANM message from the network. 5. The network sends the ANM message. This means that the called party has picked up and there is now an end to end voice connection. The application can begin normal call processing. 6. The application sends an Originate to connect the voice paths. 7. The MPS returns the connect (origcmp) condition (usually ignored).
194 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Interworking With a non-SS7/C7 Server (Condition Mode)
Interworking With a non-SS7/C7 Server (Condition Mode)
To verify the type of destination server, check the appropriate ACM message interworking indicator data item after receiving an ACM (if the specific SS7/C7 implementation supports it, see Data Items on page 214). If the data item is set to 1, the destination server is SS7/C7. If
Avaya CCSS 1000/2000 Feature Documentation August 2013 195 ISUP Application Programming
the data item is set to 2, the destination server is not SS7/C7 (that is, there is interworking) so the application needs to enable the CPD hardware and receive the ANM message in a different manner. The Call Progress Detection block is used to register and unregister tone events during the course of a call. When registering, the application must handle the Phone Line Status Condition cpd. When interworking with a non-SS7/C7 server, the application receives the ANM message as the condition data to a ccs7cc condition. The following application segment shows how to handle waiting for the ANM on an interworked call:
1. Get the ACM message from the network. 2. Check the ACM for the interworking value. If the value is 1, the other server is a C7 server. If the value is 2, the other server is not C7 and will require other processing. 3. Perform Call Progress Detection (CPD) on the tones received from the network. 4. If CPD detects a busy signal, disconnect. If the CPD detects a ring, stay in a loop until the ANM message is passed through the ccs7cc condition. 5. After ccs7cc is generated, the application sends an Originate to connect the voice paths, while ignoring the origcmp condition, then continue with the call.
196 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] During the Call
During the Call
After the call is connected, the application can begin any normal call processing logic (caller message recording, getting touch tones, host interaction). The only SS7/C7-specific call handling required is to handle the ccs7cc condition. The condition data contains incoming network messages or other condition data which may be sent from the server. During a normal call, the following messages may appear: Example • REL - The call is released • SUS - The call is suspended • RES - The suspended call is resumed. The ISUP-PRESENT variable is set to a non-zero value if ccs7cc is generated by an incoming network message. If the calling party hangs up, the message is REL. If the message is a REL, the application should start normal call teardown procedures. Note that the application does not need to send a REL if the network sent a REL.
Call Progress Detection
Receiving Call Progress Detection (CPD) messages depends on the type of server called. If the server is an SS7 server, CPD messages are sent back as Call Progress messages (CPG) between the IAM and the ANM messages. If the server is a non-SS7/C7 server, the application must enable the MPS CPD hardware to check for progress tones For information about enabling MPS CPD hardware, see Interworking With a non-SS7/C7 Server (Condition Mode) on page 195.
Call Teardown (Application Initiated)
If the application terminates the call, it must send a release message (REL) to the network. If the other party terminates the call, the application receives a release from the network (as part of the condition data of the ccs7cc condition). After the call is released (either by the other party or the application), the application must disconnect the line and free the resource. Send an ISSUE DISCONNECT to disconnect the line and an ISSUE FREE ccss to free the messaging resource.
Avaya CCSS 1000/2000 Feature Documentation August 2013 197 ISUP Application Programming
The following diagram illustrates messaging during call teardown when the application sends a REL:
1. The application terminates the call and sends a release message to the network. 2. The application sends an ISSUE DISCONNECT using the MPS Developer Disc block to disconnect from the call. 3. The line disconnects and returns the disc condition to the application. 4. The application frees the message server resource.
In some cases, the application and the network send a REL at the same time (that is, the caller and application hang up simultaneously). If the server receives the application REL first, the call is handled as expected. If the server receives the network REL first, the REL is sent to the application, even though the application also sent a REL. In this case, the application must be able to handle a false REL message after sending a REL.
Call Teardown (Network Initiated)
If the network terminates the call, a REL message is delivered to the application as part of the condition data of the ccs7cc condition. As soon as the message is delivered, the MPS must abort any phone input or output in progress. This is required when the caller hangs up and the voice path is disconnected so the next call can be delivered by the switch almost immediately. If the MPS is speaking a long prompt when the caller disconnects (and the application receives the REL) or is waiting for touch-tones, an ISSUE DISCONNECT waits until any phone input or output (such as a prompt) has finished. In the MPS, use an ABORT block and an ISSUE DISCONNECT to abort all phone I/O before disconnecting. The application flow below illustrates the actions to take upon handling a ccs7cc condition with REL message from the network.
198 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Call Teardown (Network Initiated)
1. The network sends a release message to the application. This indicates that the other party hung up. 2. The application uses an ABORT block and an ISSUE DISCONNECT (disc block) to abort all phone I/O , while handling the disc condition. 3. The line disconnects and returns the disc condition to the application. 4. The application frees the message server resource. 5. The application resets and starts again. 6. The application requests the CCSS resource. 7. The server sends a Release Complete message to the network. The server delays sending a RLC to the network to prevent calls from overlapping. In a high- volume environment, an IAM may be available immediately after the last call is released. If the RLC is sent immediately after receiving the REL, the application could accept the IAM and the voice path would be connected. The caller would hear the last part of the previous call before the application could complete cleaning it up. Sending RLC only at the time of the next allocation request ensures that the application is ready to receive a new call.
Avaya CCSS 1000/2000 Feature Documentation August 2013 199 ISUP Application Programming
Performing a Referral
Referral is handled by two applications: one running on the inbound line (the line a caller dials into) and one running on the outbound line (the referral line). Referral functions are not handled automatically (that is, no ISSUE REFER or ISSUE BRIDGE) and must be coordinated between the two applications. The applications talk to each other using Inter-Process Communications (IPC) through the phone resource.
Application Procedure
The inbound application, referred to as the master application, waits for a call from a caller. When a referral is required, the application uses IPC to contact the application on the referral line, herein referred to as the slave application. The slave application dials out and reports the success or failure of the outdial to the master application. If the outdial was successful, the master application forces the lines to bridge using the Bridge operation in the Bridge block. After the bridge is established, both applications stop performing further phone I/O. Both applications wait for a release from their individual line and must report the release to the other application when it occurs. After a release, the master application can continue with other call processing or perform its own call cleanup and reset procedures. The slave application should immediately disconnect, cleanup, and reset after receiving a release indication (either as a REL from the network or a release message from the master application).
Note: The current implementation of call referral is to connect the caller and referral parties. After the referral is bridged, the applications should not perform any other phone I/O (for example, speaking a prompt or get touch-tones) and should wait for a release message. However, after the referral party has hung up, the master application can continue phone I/O with the caller.
200 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Application Message Exchange
Note: The current implementation of call referral does not enable the caller to hear call progress tones on the referral line. The caller cannot hear the tones unless the lines are bridged and the lines are bridged after the outbound call is already established. The master application can send output to the caller (for example, play music) while the referral line establishes the outbound call.
Application Message Exchange
Messages are passed between the master and slave applications using the phone resource. If the destination application is waiting on a RECEIVE from the phone resource, the data in received in the specified data variable. Otherwise, the destination application receives a fromphone condition, and the message data is available from the condition data. The following diagram illustrates the events and message exchange between the master and slave applications:
Avaya CCSS 1000/2000 Feature Documentation August 2013 201 ISUP Application Programming
When either side of the referral hangs up, the application that receives the network REL message must notify the other application that the party has disconnected. After notifying the other application (using SEND RESOURCE phone), it can begin normal call teardown. The following diagrams illustrate message flow when the caller line and referral line receive REL messages: Master application receives REL:
202 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Application Referral Hunt Groups
Slave application receives REL:
Application Referral Hunt Groups
The previous referral procedures assume that there is one referral line always available for any caller line that will perform a referral. You may want to set a group of lines as a hunt group. See the MPS System Reference Manual or the Telephone Line Configuration Reference Guide (MPS) for information about referral line hunt groups. In the case of a hunt group, the inbound applications can use the shared locks mechanism to keep track of what lines in the hunt group are being used. Create an array of variables (each element a three character numeric) which represents the referral span (one element per
Avaya CCSS 1000/2000 Feature Documentation August 2013 203 ISUP Application Programming
referral line). When an element is locked, the corresponding referral line is considered unavailable (probably being used by another application).
To obtain a referral line, the inbound application runs a loop to check all data item in the shared array. If the current data item is locked, it checks the next sequential item. If the data item is not locked, the application locks that shared data item and makes the referral to the appropriate line (using the previously discussed procedures).
The outbound referral application (one being run on each referral line in the hunt group) does not change.
Note: See the MPS Developer User Guide for information about using Shared Locks.
204 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Using Call Progress Detection With Referral
Using Call Progress Detection With Referral
In some environments, call progress tones may not properly interwork to the MPS. In this case, the MPS must be equipped with digital (E1) Call Progress Detection (CPD) hardware to detect some call progress tones such as ring, busy, and so on. If your system requires the MPS CPD hardware, contact Avaya for assistance on required hardware and configuration.
Note: See the MPS System Configuration Reference Manual for information about resource requirements.
Avaya CCSS 1000/2000 Feature Documentation August 2013 205 ISUP Application Programming
Application Message Exchange
Messages are passed between the master and slave applications using the phone resource. If the destination application is waiting on a RECEIVE from the phone resource, the data in received in the specified data variable. Otherwise, the destination application receives a fromphone condition, and the message data is available from the condition data.
Release Link Trunk (RLT)
Note: RLT implementation over CCSS SS7 is switch and vendor dependent. Implementation of RLT on a network must have specific call-flows laid by Single port RLT and Dual port RLT. Specific versions of the DMS-MTX switch comply with existing the RLT implementation. Study the programming interface provided in this document before you implement the RLT feature. If a call is received by an IVR system after the service required is offered; it would be best to release that call so that availability of ports is increased. Release Link Trunk (RLT) feature enables CCSS to send a request to the switch that originated the call to release or route to another destination. This functionality improves CCSS overall availability of circuits by requesting the release of the circuits after the requested service has been serviced. Without the use of RLT, calls that are extended to an IVR system and subsequently bridged to a third party would need to be maintained, tying up additional resources. CCSS ISUP supports Single Port RLT and Dual Port RLT by sending a FACILITY REQUEST (FAR) message. This message is sent from the application to the CCSS. CCSS forwards this message to the network. If the network accepts the FAR message, it returns a FACILITY ACCEPT (FAA) message. On receipt of FAA message from the network, the CCSS forwards the FAA message to the application. The network also sends a Release (REL) message to the CCSS to release the port. CCSS sends REL message to the application and waits for the application to recycle. After the application recycles and sends down an ISSUE GET message, the CCSS sends a Release Complete (RLC) message to the network to confirm that the circuit is free.
Single Port RLT
Single Port RLT extends the single leg of the call of a value added services platform. When an Incoming call (IAM) arrives, CCSS sends ACM to the Network if the application is ready
206 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Dual Port RLT
and forwards the IAM to the application. The application accepts the call and responds with an ANM message in a folder CCSS can understand. CCSS converts the ANM message folder to Network format and forwards it to the appropriate Network. The application provides the necessary service requested by the caller. After the service is provided to the caller, the application fills the appropriate fields and sends FAR message folder to float the call back to the originating switch. CCSS converts from folder format to Network format and sends to the Network. On acceptance of the FAR message, the Network side sends FAA (Facility Accept) message followed by REL (Release) message to release the line.
Dual Port RLT
Dual Port RLT is similar to Single Port RLT except that two legs of a call are involved (inbound, outbound). CCSS requests network side switching equipment to bridge inbound and outbound legs of the call and to release the lines. CCSS supports Single FAR Dual Port RLT and Multiple FAR Dual Port RLT. In Single FAR Dual Port RLT, the application fills Call Reference field in the FAR message folder from the ACM message it received from the Network. In Multiple FAR Dual Port RLT, the application fills the User-to-User Information field with a unique Call Bridge ID (0 - 65535) and sends a FAR message folder for each leg to be bridged to the call.
RLT Applications
RLT Applications must fill correct values in appropriate fields in the message folders. The application decides if it is a Single Port RLT or a Dual Port RLT implementation. In Single Port RLT, the application has to fill the value 017 in facility indicator field and for Dual Port RLT the value is 016. CCSS uses this value to determine the mode of operation. If the application needs pullback feature then it should fill the subsequent number field. This feature is available in Single Port RLT only. In Dual Port RLT, the application has to copy the Call Reference parameter it received in the incoming ACM message to the outgoing FAR message. The Call Reference field is filled in Single FAR Dual Port RLT mode only. In Single FAR Dual Port RLT, the FAR message is sent on the first leg of the call. In Multiple FAR Dual Port RLT, the application should fill the User- to-User information fields of the FAR message with an uniquely generated Call Bridge ID and send it out on both inbound and outbound circuits.
Avaya CCSS 1000/2000 Feature Documentation August 2013 207 ISUP Application Programming
Message Sequence Diagrams
Single Port RLT - Success
208 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Single Port RLT - Failure
Single Port RLT - Failure
Avaya CCSS 1000/2000 Feature Documentation August 2013 209 ISUP Application Programming
Single Port with Pullback
210 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Single FAR Dual Port RLT
Single FAR Dual Port RLT
Avaya CCSS 1000/2000 Feature Documentation August 2013 211 ISUP Application Programming
Multiple FAR Dual Port RLT
ISDN User Part (ISUP) Message Data Items
This section defines the folders and data cards used by the ISUP (ISDN User Part) applications distributed with the CCSS. The data items used by any SS7/C7 application depend on the specific country variant (some country variants will use different data items). For specific information on the variables needed for a specific protocol, refer to the following documents:
Protocol Document ANSI ANSI T1.113-1992ANSI ANSI T1.113-1996 ETSI ETSI V3 EN 300 356-1 ETSI V2 ETS 300 356 ETSI V1 ETS 300 121
212 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Backward Compatibility
Protocol Document ITU Blue Book Q.761-Q.764, '88 White Book Q.761- Q.764, '92 Q.767 Telcordia Telcordia GR-317-CORE Telcordia GR-394- CORE Telcordia GR-905-CORE
For more information on the variants supported, see CONFIG VARIANT on page 40. Most data items are named according to the message which they belong to and any message subcategory. For example, an IAM nature of connection indicator variable will have the prefix IAM-NTCI-. The data items have been named as close as possible to the network message data they represent.
Note: The values listed with each data item are the values that the application sends to/expects from the CCSS. If the data from the network is numeric, the CCSS will add 1 to the value and return the modified value to the application. For example, if an internetworking indicator is sent as 1 from the network, the application receives a 2 in the appropriate data variable. Likewise, the application must set the data item to 2 in order for the network to receive a 1. Any data item which is set to 0 means that the network did not deliver that data to the server. If a data variable accepts characters, a blank string means that the data item was not delivered. The application can set a data item to 0/blanks and the information will not be transmitted to the network.
Note: The Application Folder used should be same as the 'OPTION EXTENDED' used in the ss7.conf file. For example if we have 'OPTION EXTENDED 1' in ss7.conf file then we should use the corresponding Application Folder for the data items.
Backward Compatibility
Any modifications to the CCSS must allow for backward compatibility. The following general rules are used when enhancing the message content. • Messages with new content are identified with a new three character message type identifier. All messages in the MPS Developer folders contain the first data item which
Avaya CCSS 1000/2000 Feature Documentation August 2013 213 ISUP Application Programming
identifies the data type. These messages will uniquely identify the message that is being passed. • All changes to message content is added to the end of the message. This enables a level of compatibility between the applications. • Message enhancements that are customer specific are supported through a generic mechanism that isolates the data processing to the application.
Data Items
Initial Address Message
IAM-MESSAGE-TYPE (three character numeric) is used to compare incoming messages and should always be left as 001.
001 Initial value
Note: This message provides basic support for transmitting and receiving the IAM message. See IAMX for extended capability.
Nature of Connection Indicators
All of the following Nature of Connection Indicators (NTCI) are mandatory.
IAM-NTCI-SATELLITE-IND (single character numeric) – the Satellite indicator data item.
0 Initial value 1 No Satellite 2 One Satellite 3 Two Satellite
IAM-NTCI-CONTINUITY-CHECK-IND (single character numeric) – the continuity check indicator data item.
214 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Forward Call Indicators
0 Initial value 1 Not Required 2 Required 3 Performed On Previous Circuit
IAM-NTCI-ECHO-CONTROL-IND (single character numeric) – the echo control device indicator.
0 Initial value 1 Echo Control Not Included 2 Echo Control Included
Forward Call Indicators
All of the following Forward Call Indicators (FOCI) are mandatory.
IAM-FOCI-CALL-IND (single character numeric) – national or international call indicator data item.
0 Initial value 1 national call 2 international call
IAM-FOCI-EE-METHOD-IND (single character numeric) – end-to-end method indicator data item.
0 Initial value 1 no end-to-end method available 2 pass along method available 3 SCCP method available 4 pass along and SCCP methods available
IAM-FOCI-INTERNETWORK-IND (single character numeric) – internetworking indicator data item.
0 Initial value 1 no interworking encountered 2 interworking encountered
Avaya CCSS 1000/2000 Feature Documentation August 2013 215 ISUP Application Programming
IAM-FOCI-EE-INFO-IND (single character numeric) – end-to-end information indicator data item.
0 Initial value 1 no end-to-end information available 2 end-to-end information available
IAM-FOCI-ISUP-IND (single character numeric) – ISDN user part indicator data item.
0 Initial value 1 ISDN user part not used all the way 2 ISDN user part used all the way
IAM-FOCI-ISUP-PREFER-IND (single character numeric) – ISDN user part preference indicator.
0 Initial value 1 ISDN user part preferred all the way 2 ISDN user part not required all the way 3 ISDN user part required all the way 4 spare
IAM-FOCI-ISDN-ACCESS-IND (single character numeric) – ISDN access indicator data item.
0 Initial value 1 originating access non-ISDN 2 originating access ISDN
IAM-FOCI-SCCP-METHOD-IND (single character numeric) – SCCP method indicator data item.
0 Initial value 1 no indication 2 connectionless method available 3 connection oriented method available 4 connectionless and connection oriented.
216 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Calling Party Category
Calling Party Category
All of the following Calling Party Category (CGPC) parameters are mandatory.
IAM-CGPC-CGPC (three character numeric) – Calling Party Category indicator data item.
000 Initial value 001 calling party's category unknown at this time 002 operator, language French 003 operator, language English 004 operator, language German 005 operator, language Russian 006 operator, language Spanish 007 available to administrations for 008 selecting a particular language by 009 by mutual agreement 010 reserved 011 ordinary calling subscriber 012 calling subscriber with priority 013 data call 014 test call 015 spare 016 payphone 017-256 reserved
Transmission Medium Requirement
All of the following Transmission Medium Requirement (XMR) parameters are mandatory.
IAM-XMR-REQUIREMENT (three character numeric) The transmission medium requirement data item.
Avaya CCSS 1000/2000 Feature Documentation August 2013 217 ISUP Application Programming
000 Initial value 001 speech 002 spare 003 64 kbit/s unrestricted 004 3.1 kHz audio 005 alt speech (svce 2) /64kbit/s unrsted (svce 1) 006 alt 64kbit/s unrsted (svce 1)/ speech (svce 2) 007 spare 008 reserved for 2 x 64kbit/s unrestricted 009 reserved for 384kbit/s unrestricted 010 reserved for 1536 kbit/s unrestricted 011 reserved for 1920 IAM-kbit/s unrestricted 012-255 spare
Note: This parameter is mandatory for ITU and does not exist for ANSI.
Called Party Number
All of the following Called Party Number (CDPN) parameters are mandatory and can have a variable length.
IAM-CDPN-NOA-IND (three character numeric) – the nature of address indicator data item.
000 Initial value 001 spare 002 subscriber number 003 spare, reserved for national use 004 national (significant) number 005 international number 114-25 spare 113 unknown 6 006-11 spare 2
IAM-CDPN-INN-IND (single character numeric) – the internal network number indicator data item.
218 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Calling Party Number
0 Initial value 1 routing to internal network # allowed 2 routing to internal network # not allowed
IAM-CDPN-NUMBER-PLAN (single character numeric) – the numbering plan indicator data item.
0 Initial value 1 spare 2 ISDN (Telephony) numbering plan 3 spare 4 Data numbering plan 5 Telex numbering plan 6-7 reserved for national use 8 spare
IAM-CDPN-ADDRESS (18 character alphanumeric) – the address signal data item.
Note: With the release of ccss5.4, Called Party Number has a configurable length. The minimum size that can be configured is 18 digits. The maximum size is 64 digits. The default value is 18 digits. The number of digits is set in the ss7.conf file by using the following entry: CONFIG CCME_OPTION =CDPN_LEN, VALUE=18; To transmit a Called Party Number in excess of 18 digits, use an IAM message followed by one or more SAM messages. The protocol supports a maximum of 18 digits in the IAM message. More than 18 digits results in a protocol error. If the Called Party Number digits received in IAM and SAM messages have a combined length greater than the value defined in the ss7.conf file, the received data is truncated with the leading digits discarded.
0 digit 0 1 digit 1 2 digit 2 3 digit 3 4 digit 4 5 digit 5 6 digit 6 7 digit 7 8 digit 8 9 digit 9 A spare B code 11 C code 12 D spare E spare F ST
Calling Party Number
All of the following Calling Party Number (CGPN) parameters are optional.
Avaya CCSS 1000/2000 Feature Documentation August 2013 219 ISUP Application Programming
IAM-CGPN-NOA-IND (three character numeric) – the nature of address indicator data item.
000 Initial value 001 spare 002 subscriber number 003 spare, reserved for national use 004 national (significant) number 005 international number 006-256 spare
IAM-CGPN-CGP-NI-IND (single character numeric) – the calling party number incomplete indicator data item.
0 Initial value 1 complete 2 incomplete
IAM-CGPN-NUMBER-PLAN (single character numeric) – the numbering plan indicator data item.
0 Initial value 1 spare 2 ISDN (Telephony) numbering plan 3 spare 4 Data numbering plan 5 Telex numbering plan 6-7 reserved for national use 8 spare
IAM-CGPN-ADD-PRSNT-RESTRICT-IND (single character numeric) – the address presentation restricted data item.
0 Initial value 1 presentation allowed 2 presentation restricted 3 address not available 4 spare
220 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Redirecting Number
IAM-CGPN-SCREEN-IND (single character numeric) – the screening indicator data item.
0 Initial value 1 reserved 2 user provided, verified and passed 3 reserved 4 network provided
IAM-CGPN-ADDRESS (20 character alphanumeric) – the address signal data item.
Note: For ITU99, the IAM-CGPN-ADDRESS data item is a 24 character alphanumeric.
0 digit 0 1 digit 1 2 digit 2 3 digit 3 4 digit 4 5 digit 5 6 digit 6 7 digit 7 8 digit 8 9 digit 9 A spare B code 11 C code 12 D spare E spare F spare
Redirecting Number
All of the following Redirecting Number (RDTG) parameters are optional.
IAM-RDTG-NOA-IND (three character numeric) – the nature of address indicator data item.
000 Initial value 001 spare 002 subscriber number 003 spare, reserved for national use 004 national (significant) number 005 international number 006-256 spare
IAM-RDTG-NUMBER-PLAN (single character numeric) – the numbering plan indicator data item.
Avaya CCSS 1000/2000 Feature Documentation August 2013 221 ISUP Application Programming
0 Initial value 1 spare 2 ISDN (Telephony) numbering plan 3 spare 4 Data numbering plan 5 Telex numbering plan 6-7 reserved for national use 8 spare
IAM-RDTG-ADDRESS-PRESENT-RESTRICT-IND (single character numeric) – the address present restricted indicator data item.
0 Initial value 1 presentation allowed 2 presentation restricted 3 address not available 4 spare
IAM-RDTG-ADDRESS (twenty character alphanumeric) – the address signal data item.
0 digit 0 1 digit 1 2 digit 2 3 digit 3 4 digit 4 5 digit 5 6 digit 6 7 digit 7 8 digit 8 9 digit 9 A spare B code 11 C code 12 D spare E spare F spare
Redirection Information
All of the following Redirecting Information (REDI) parameters are optional.
IAM-REDI-REDIRECT-IND (single character numeric) – the redirecting indicator data item.
0 Initial value 1 no redirection 2 call rerouted
222 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Original Called Number
3 call rerouted, redirect info pres. restricted 4 call forwarded 5 call forwarded, redirect info pres. restricted 6 call rerouted, redirect # pres. restricted 7 call forwarded, redirect # pres. restricted 8 spare
IAM-REDI-REDIRECT-REASON (two character numeric) – the original redirecting reasons data item.
00 Initial value 01 unknown/not available 02 user busy 03 no reply 04 unconditional 05-16 spare IAM-REDI-REDIRECTION-COUNTER (single character numeric) – the redirection counter data item.
Binary number between 2 and 6
IAM-REDI-REDIRECTING-REASON (two character numeric) – the redirecting reason data item.
00 Initial value 01 unknown/not available 02 user busy 03 no reply 04 unconditional 05-16 spare
Original Called Number
All of the following Original Called Number (OCDN) parameters are optional.
Avaya CCSS 1000/2000 Feature Documentation August 2013 223 ISUP Application Programming
IAM-OCDN-NOA-IND (three character numeric) – the nature of address indicator data item.
000 Initial value 001 spare 002 subscriber number 003 spare, reserved for national use 004 national (significant) number 005 international number 006-256 spare
IAM-OCDN-NUMBER-PLAN (single character numeric) – the numbering plan indicator data item.
0 Initial value 1 spare 2 ISDN (Telephony) numbering plan 3 spare 4 Data numbering plan 5 Telex numbering plan 6-7 reserved for national use 8 spare
IAM-OCDN-ADDRESS-PRESENT-RESTRICT-IND (single character numeric) – the address presentation restricted indicator data item.
0 Initial value 1 presentation allowed 2 presentation restricted 3 address not available 4 spare
IAM-OCDN-ADDRESS (twenty character alphanumeric) – the address signal data item.
0 digit 0 1 digit 1 2 digit 2 3 digit 3 4 digit 4 5 digit 5 6 digit 6 7 digit 7 8 digit 8 9 digit 9 A spare B code 11 C code 12 D spare E spare
224 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] End of Optional Parameters
F spare
End of Optional Parameters
At the end of the last optional parameter message field, there is the end of optional parameters message indicator. This parameter should not be changed, the value is always 0.
IAM-END-OF-PARAMETER (single character numeric) – end of optional parameters data item. 0 Initial value
Extended Address Message
The CCSS sends the existing IAM message type unless configured with the following in the ss7.conf file: “CONFIG CCME_OPTION = EXTENDED, VALUE=1", "CONFIG CCME_OPTION = EXTENDED, VALUE=2", "CONFIG CCME_OPTION = EXTENDED, VALUE=3", "CONFIG CCME_OPTION = EXTENDED, VALUE=4", "CONFIG CCME_OPTION = EXTENDED, VALUE=5", "CONFIG CCME_OPTION = EXTENDED, VALUE=6" "CONFIG CCME_OPTION = EXTENDED, VALUE=7” IAMX-MESSAGE-TYPE (three character numeric) – use this data item to compare incoming messages. This item should always be 029 for CCME_OPTION EXTENDED modes 1, 2 or 3. 029 Initial value
IAMX Parameters
The following table lists the parameters that are included in the IAMX message that is appended to the end of the existing IAM data folder.
Avaya CCSS 1000/2000 Feature Documentation August 2013 225 ISUP Application Programming
Parameter Name Comment Generic Number Optional Forward Call Info User Service Info Location Number Additional Parameters Includes: Access Transport Generic Name Unrecognized Parameters Parameter Compatibility Info Supplementary Line Info User to User Info
Extended Option 4 and 5
IAMX-MESSAGE-TYPE (three character numeric) – use this data item to compare incoming messages. This should always be 047 for "CONFIG CCME_OPTION = EXTENDED, VALUE=4" or 'CONFIG CCME_OPTION = EXTENDED, VALUE=5'. The following parameters have been added to the previous IAM filter list and the CCME_OPTION EXTENDED 1, 2 or 3 and Extended Option 4 and 5. • Jurisdiction Information • Carrier ID • Charge Number • Origination Line Info
Extended Option 6 and 7
IAMX-MESSAGE-TYPE (three character numeric) should always be 052 for 'CONFIG CCME_OPTION = EXTENDED, VALUE=6' or 122 for 'CONFIG CCME_OPTION = EXTENDED, VALUE=7'. The following parameters have been added to the previous IAM filter list and the CCME_OPTION EXTENDED 1, 2, 3, 4, or 5. • Correlation ID • SCF ID • Access Transport Parameter • Call Reference • Closed User Group Interlock Code
226 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Forward Call Indicators
Forward Call Indicators
Forward Call Indicators will have the addition of the following: IAM-FOCI-SPARE (two character numeric) – the additional remaining bits for FOCI item. For Telcordia variant, the M bit in FOCI represents the translated called number indicator. This bit can be set by filling the appropriate value of FOCI_SPARE of the IAM in extended mode 5 outbound application for Telcordia variant. Filling value 1 or 2 in FOCI _SPARE will set the Mbit to 0 that is, number not translated. Filling value 3 or 4 in FOCI_SPARE will set the Mbit to 1 (that is, number translated).
Generic Number
All of the following Generic Number (GNUM) parameters are optional.
IAMX-GNUM-NUM-QUAL-IND (three character numeric) – the Number Qualifier Indicator data item.
000 Initial value 001 Reserved 002 Additional Called Number 003 Reserved 004 Reserved 005 Reserved 006 Additional Connected Number 007 Additional Calling Party Number 008 Additional Original Called Number 009 Additional Redirecting Number 010 Additional Redirection Number
IAMX-GNUM-NOA-IND (single character numeric) – the Nature Of Address Indicator data item.
0 Initial value 1 Spare
Avaya CCSS 1000/2000 Feature Documentation August 2013 227 ISUP Application Programming
2 Subscriber Number 3 Unknown 4 National Significant Number 5 International Number 6-110 Spare 111-255 Reserved 256 Spare
IAMX-GNUM-NII-IND (single character numeric) – the Number Incomplete Indicator data item.
0 Initial value 1 Number Complete 2 Number Incomplete
IAMX-GNUM-NUMBER-PLAN (single character numeric) – the Numbering Plan Indicator data item.
0 Initial value 1 Spare 2 ISDN Telephony Numbering Plan 3 Spare 4 Data Numbering Plan 5 Telex Numbering Plan 6 Private Numbering Plan 7 Reserved for National Use 8 Spare
IAMX-GNUM-PRESENT-RESTRICT-IND (single character numeric) – the Address Presentation Restricted Indicator data item.
0 Initial value 1 Presentation Allowed 2 Presentation Restricted 3 Address Not Available 4 Spare
228 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Optional Forward Call Indicators
IAMX-GNUM-SCREEN-IND (single character numeric) – the Screening Indicator data item.
0 Initial value 1 User Provided, Not Verified 2 User Provided, Verified and Passed 3 User Provided, Verified and Failed 4 Network Provided
IAMX-GNUM-PRESENT-ADDRESS (20 character alphanumeric) – the Address Signal data item.
0 Digit 0 1 Digit 1 2 Digit 2 3 Digit 3 4 Digit 4 5 Digit 5 6 Digit 6 7 Digit 7 8 Digit 8 9 Digit 9
The field is left justified and the field contains spaces if address signals are not present.
Optional Forward Call Indicators
IAMX-OFCI-CUG-IND (single character numeric) – Closed User Group Call Indicator data item.
0 Initial value 1 Non-CUG Allowed 2 Spare 3 CUG, Outgoing Access Allowed 4 CUG Call, Outgoing Access Not Allowed
Avaya CCSS 1000/2000 Feature Documentation August 2013 229 ISUP Application Programming
IAMX-OFCI-SEG-IND (single character numeric) – simple segmentation Indicator data item.
0 Initial value 1 No additional information will be sent 2 Additional information will be sent in a segmentation message
Note: A value of 2 for this parameter causes the IAM that is being sent to the inbound application to be delayed.
IAMX-OFCI-CLI-REQ-IND (single character numeric) – Connected Line Identity Request Indicator data item.
0 Initial value 1 Not Requested 2 Requested
Note: There is a structural difference in this parameter for ANSI88.
User Service Info
IAMX-USI-CODE-STD (single character numeric) – Coding Standard data item.
0 Initial value 1 CCITT Standardized Coding 2 ISO/IEC Standard 3 National Standard 4 Standard on Network Side of Interface
IAMX-USI-INFO-TRANS-CAP (two character numeric) – Information Transfer Capability data item.
00 Initial value 09 Unrestricted Digital Information
230 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] User Service Info
10 Restricted Digital Information 17 3.1 Khz Audio 18 Unrestricted Digital Information with tones or announcements 25 Video
IAMX-USI-TRANS-MODE (single character numeric) – Transfer Mode data item
0 Initial value 1 Circuit mode 3 Packet mode
IAMX-USI-INFO-TRANS-RATE (two character numeric) – Information Transfer Rate data item
00 Initial value 17 64 kbit/s 18 2 x 64 kbit/s 19 384 kbit/s 22 1536 kbit/s 24 1920 kbit/s 25 Multirate (64 kbit/s base rate)
IAMX-USI-STRUCT (single character numeric) – structure data item.
00 Initial value 01-8 Network Specified
IAMX-USI-CFG (single character numeric) – configuration data item.
0 Initial value 1 Supported Value 1-4 Network Specified Range
IAMX-USI-ESTABLISH (single character numeric) – establishment data item.
0 Initial value 1 Supported Value 1-4 Network Specified Range
IAMX-USI-SYMMETRY (single character numeric) – symmetry data item.
Avaya CCSS 1000/2000 Feature Documentation August 2013 231 ISUP Application Programming
0 Initial value 1 Supported Value 1-4 Network Specified Range
IAMX-USI-INFO-DTO-TRANS-RATE (two character numeric) – Information Transfer Rate data item.
00 Initial value 17 64 kbit/s 18 2 x 64 kbit/s 19 384 kbit/s 22 1536 kbit/s 24 1920 kbit/s 25 Multirate (64 kbit/s base rate)
IAMX-USI-L1-IDENT (single character numeric) – Layer 1 Identity data item.
0 Initial value 2 Layer 1 Identity
IAMX-USI-L1-USR-INFO (two character numeric) – Layer 1 User Info data item.
00 Initial value 01-64 Network Specified
IAMX-USI-L2-IDENT (single character numeric) – Layer 2 Identity data item.
0 Initial value 3 Layer 2 Identity
IAMX-USI-L2-USR-INFO (single character numeric) – Layer 2 User Info data item.
0 Initial value 3 Supported Value - Q.921 7 Supported Value - X.25 01-64 Network Specified Range
IAMX-USI-L3-IDENT (single character numeric) – Layer 3 Identity data item.
0 Initial value
232 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Location Number
4 Layer 3 Identity
IAMX-USI-L3-USR-INFO (single character numeric) – Layer 3 User Info data item.
0 Initial value 3 Supported Value - Q.931 7 Supported Value - X.25 01-64 Network Specified Range
Note: The structure of this parameter is different for ANSI. This parameter is mandatory for ANSI88 and optional for ITU ANSI92.
Location Number
IAMX-LNUM-NOA-IND (single character numeric) – the nature of address indicator data item. 0 Initial value 1 Spare 2 Subscriber number 3 Unknown 4 National significant number 5 International number 6-110 Spare 111-255 Reversed 256 Spare
IAMX-LNUM-NII-IND (single character numeric) – the number incomplete indicator data item.
0 Initial value 1 Number complete 2 Number incomplete
Avaya CCSS 1000/2000 Feature Documentation August 2013 233 ISUP Application Programming
IAMX-LNUM-NUMBER-PLAN (single character numeric) – the numbering plan indicator data item.
0 Initial value 1 Spare 2 ISDN telephony numbering plan 3 Spare 4 Data numbering plan 5 Telex numbering plan 6 Private numbering plan 7 Reserved for national use 8 Spare
IAMX-LNUM-PRESENT-RESTRICT-IND (single character numeric) – the address presentation restricted indicator data item.
0 Initial value 1 Presentation allowed 2 Presentation restricted 3 Address not available 4 Spare
IAMX-LNUM-SCREEN-IND (single character numeric) – the screening indicator data item.
0 Initial value 1 User provided, not verified 2 User provided, verified and passed 3 User provided, verified and failed 4 Network provided
IAMX-LNUM-ADRESS (20 character numeric) – the address signal data item.
0 Digit 0 1 Digit 1 2 Digit 2 3 Digit 3 4 Digit 4 5 Digit 5 6 Digit 6 7 Digit 7 8 Digit 8 9 Digit 9 A code 1010 B code 1011 C code 1100 D code 1101 E code 1110 F code 1111
234 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Jurisdiction Info
The field will be left justified and is filled with spaces if address signals are not present.
Jurisdiction Info
The Jurisdiction Info information element is sent in the forward direction to indicate the geographical origination of the call. IAMX-JUIN-ADDRESS (Single character numeric)
Carrier ID
The carrier ID information element is sent in the forward direction to the transit network and it indicates the transit network selected by the originating subscriber. IAMX-CAID-NETWORK-ID-PLAN (Single character numeric) IAM-CAID-NETWORK-ID- TYPE (Single character numeric) IAMX-CAID-CARRIER-ID (4 character numeric)
Charge Number
The charge number parameter contains the number to be charged for a call. IAMX-CHNM-NOA-IND (3 character numeric)
000 Initial value 001 ANI of the calling party subscriber number 002 ANI not available or not provided 003 ANI of the calling party national number 005 ANI of the called party subscriber number 006 ANI of the called party no number present 007 ANI of the called party national number
IAMX-CHNM-NUMBER-PLAN – 1 character numeric IAMX-CHNM-ADDRESS – 18 character numeric
Avaya CCSS 1000/2000 Feature Documentation August 2013 235 ISUP Application Programming
Originating Line Info
The Originating Line Info information element is sent in the forward direction to indicate a toll class of service for the call. IAMX-OLI-LINEINFO – 3 character alphanumeric
000 Initial value 001 identified line - no special treatment 002 ONI (multiparty) 003 ANI failure (unavailable) 007 hotel (without room identification) 008 coinless, hospital, inmate, and the like 009 interLATA restricted 015 AIOD - listed DN sent 01C coin line 045 interLATA restricted - hotel 04F interLATA restricted - coinless, and the like 00B Test call 018 coin or non-coin 019 800 Call
SCF ID
The Service Control Function (SCF) parameter is used to assisting SSP to establish communication with the SCP. SCF ID enables the assisting SSF to identify the SCF that the Assist Request Instructions are to be sent to. IAMX-SCFID-LENGTH – 2 character numeric IAMX-SCFID-SCFID –20 character numeric
236 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Correlation ID
Correlation ID
This parameter is used by the SCF to associate the Assist Request Instructions from the assisting Service Switching Function (SSF) or the Specialized Resource Function (SRF) with the request from the initiating SSF. IAMX-SCFID-LENGTH – 2 character numeric IAMX-SCFID-SCFID – 20 character numeric
Access Transport Parameter
This parameter is used to represent multiple Q.931 information elements. IAMX-ACCESS-TRANSPORT-LENGTH – 2 character numeric IAMX-ACCESS- TRANSPORT-DATA – 36 character alphanumeric
Call Reference
IAMX-CALL-REF-ID (8 character numeric) – Call Reference ID data item.
0 Initial value IAMX-CALL-REF-POINT (8 character numeric) – Call Reference Point Code data item. 0 Initial value
1-214 decimal value of the point code
Closed User Group Interlock Code
This parameter is used to convey digits and binary code to identify the particular closed group of users. IAMX-CUG-DIGIT1 (Single character numeric) IAMX-CUG-DIGIT2 (Single character numeric) IAMX-CUG-DIGIT3 (Single character numeric) IAMX-CUG-DIGIT4 (Single character numeric) The preceding digits should be specified in BCD format.
Avaya CCSS 1000/2000 Feature Documentation August 2013 237 ISUP Application Programming
IAMX-CUG-BINCODE (5 character alphanumeric)
Additional Parameters
IAMX-ADD-PARAM (522 character numeric) For details of this structure, see Additional Parameters on page 295.
Address Complete
ACM-MESSAGE-TYPE (three character numeric) – use this data item to compare incoming messages. This should always be 002. 002 Initial value
Backward Call Indicator
All of the following Backward Call Indicator (BACI) parameters are mandatory and have a fixed length.
ACM-BACI-CHARGE-IND (single character numeric) – the charge indicator data item.
0 Initial value 1 no indication 2 no charge (N.B.) 3 charge 4 spare
ACM-BACI-CDP-STAT-IND (single character numeric) – the called party's status indicator data item.
0 Initial value 1 no indication 2 subscriber free 3 connect when free 4 spare
238 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Backward Call Indicator
ACM-BACI-CDP-CAT-IND (single character numeric) – the category indicator data item of the called party.
0 Initial value 1 no indication 2 ordinary subscriber 3 payphone 4 spare
ACM-BACI-EE-METHOD-IND (single character numeric) – the end-to-end method indicator data item.
0 Initial value 1 no end-to-end method available 2 pass along method available 3 SCCP method available 4 pass along and SCCP methods available
ACM-BACI-INTERNETWORK-IND (single character numeric) – the internetworking indicator data item.
0 Initial value 1 no interworking encountered 2 interworking encountered
ACM-BACI-EE-INFO-IND (single character numeric) – thee end-to-end information indicator data item.
0 Initial value 1 no end-to-end information available 2 end-to-end information available
ACM-BACI-ISUP-IND (single character numeric) – the ISDN user part indicator data item.
0 Initial value 1 ISDN user part not used all the way 2 ISDN user part used all the way
ACM-BACI-HOLD-IND (single character numeric) – the holding indicator data item.
0 Initial value
Avaya CCSS 1000/2000 Feature Documentation August 2013 239 ISUP Application Programming
1 holding not requested 2 holding requested
ACM-BACI-ISDN-ACCESS-IND (single character numeric) – the ISDN access indicator data item.
0 Initial value 1 terminating access non-ISDN 2 terminating access ISDN
ACM-BACI-ECHO-CONTROL-IND (single character numeric) – the echo control device indicator data item.
0 Initial value 1 Echo Control Not Included 2 Echo Control Included
ACM-BACI-SCCP-METHOD-INC (single character numeric) – the SCCP method indicator data item.
0 Initial value 1 no indication 2 connectionless method available 3 connection oriented method available 4 connectionless and connection oriented
Optional Backward Call Indicators
The Optional Backward Call Indicator (OBI) parameters are optional.
ACM-OBI-INBAND-IND (single character numeric) – the inband information indicator data item.
0 Initial value 1 no indication 2 in-band info or pattern is now available
ACM-OBI-FORWARD-IND (single character numeric) – the call forwarding may occur indicator data item.
240 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] End of Optional Parameters
0 Initial value 1 no indication 2 call forwarding may occur
End of Optional Parameters
At the end of the last optional parameter message field, there is the end of optional parameters message indicator. This should always be 0. ACM-END-OF-PARAMETER (single character numeric) – the end of optional parameters data item. 0 Initial value
Extended Address Complete Message
Extended Option 2
The CCSS sends the existing ACM message type unless CCSS is configured with the following in the ss7.conf file: CONFIG CCME_OPTION = EXTENDED, VALUE=2, 3, 4 or 5 The following parameters were added to the ACM filter list. ACMX-MESSAGE-TYPE (three character numeric) – use this data item to compare incoming messages. This data item should always be 034.
ACMX Parameters
The following table lists the parameters that are included in the ACMX message that is appended to the end of the existing ACM data folder.
Avaya CCSS 1000/2000 Feature Documentation August 2013 241 ISUP Application Programming
Parameter Name Comment Additional Parameters Includes: Access Transport Unrecognized Parameters Parameter Compatibility Info User to User Info Call Reference
Extended Option 6 and 7
ACMX-MESSAGE-TYPE (three character numeric) – use this data item to compare incoming messages. This data item should always be 051 for CONFIG CCME_OPTION = EXTENDED, VALUE= 6 and 124 for CONFIG CCME_OPTION = EXTENDED, VALUE=7. The following table lists the parameters that are included in the ACMX message that is appended to the end of the existing ACM data folder.
Parameter Name Comment Additional Parameters Includes: Call Reference Call Diversion Information Redirection Number Cause Indicator Access Delivery Information Generic Notification Indicator
Call Reference
The Call Reference is an optional and variable length parameter. ACMX-CALL-REF-ID (eight character numeric) – Call Reference ID data item. 0 Initial value ACMX-CALL-REF-POINT-CODE (eight character numeric) – Call Reference Point Code data item.
0 Initial value 1-214 decimal value of the point code
242 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Call Diversion Information
Call Diversion Information
ACMX-CDI-NOTIF-SUBSCR (single character numeric) – Notification subscription option data item.
0 initial value 1 reserved 2 presentation not allowed 3 presentation allowed with redirection number 4 presentation allowed without redirection number
ACMX-CDI-REDIR-REASON (single character numeric) – Redirecting reason data item.
0 initial value 1 reserved 2 User busy 3 no reply 4 unconditional 5 deflection during alerting 6 deflection immediate response 7 mobile subscriber not reachable
Redirection Number
ACMX-REDN-NOA-IND (3 character numeric) – nature of address indicator data item.
0 initial value 1 reserved 2 subscriber number (national use) 3 unknown (national use) 4 national (significant) number
Avaya CCSS 1000/2000 Feature Documentation August 2013 243 ISUP Application Programming
5 international number 6 reserved 7 network routing number in national (significant) number format (national use) 8 network routing number in network-specific number format (national use) 9 reserved for network routing number concatenated with Called Directory Number (national use)
ACMX-REDN-INN-IND (single character numeric) – internal network number indicator data item.
0 initial value 1 routing to internal network number allowed 2 routing to internal network number not allowed
ACMX-REDN-NUMBER-PLAN (single character numeric) – numbering plan indicator data item.
0 initial value 1 spare 2 ISDN (Telephony) numbering plan (ITU-T Recommendation E.164) 3 spare 4 Data numbering plan (ITU-T Recommendation X.121) (national use) 5 Telex numbering plan (ITU-T Recommendation F.69) (national use)
ACMX-REDN-ADDRESS (18 character alphanumeric) – redirecting address data item.
0 digit 0 1 digit 1 2 digit 2 3 digit 3 4 digit 4 5 digit 5 6 digit 6 7 digit 7 8 digit 8 9 digit 9 A spare B code 11 C code 12 D spare E spare F ST
Cause Indicator
The Cause Indicator (CAU) parameters are optional and can have a variable length. Because this parameter is similar to cause parameter in REL msg, for details see Cause Indicators on page 272.
244 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Access Delivery Information
Access Delivery Information
ACMX-ADI-DELIND (single character numeric) – access delivery indicator data item.
0 initial value 1 set-up message generated 2 no set-up message generated
Generic Notification Indicator
NOTIF-ID (3 character numeric) – notification indicator data item. 0 initial value 1 user suspended 2 user resumed 3 bearer service change 4 Discriminator for extension to ASN.1 encoded component (used in DSSI) 5 call completion delay 6-66 reserved 67 conference established 68 conference disconnected 69 other party added 70 isolated 71 reattached 72 other party isolated 73 other party reattached 74 other party split 75 other party disconnected 76 conference floating 77-96 reserved
Avaya CCSS 1000/2000 Feature Documentation August 2013 245 ISUP Application Programming
97 call is a waiting call 98-104 reserved 105 diversion activated (used in DSS1) 106 call transfer, alerting 107 call transfer, active 108-121 reserved 122 remote hold 123 remote retrieval 124 call is diverting 125-128 reserved
Answer
ANM-MESSAGE-TYPE (three character numeric) – use this data item to compare incoming messages. This data item should always be 003. This message provides basic support for transmitting and receiving the ANM message. For extended capability, see ANMX Parameters on page 250.
Backward Call Indicator
The Backward Call Indicator (BACI) parameters are optional.
ANM-BACI-CHARGE-IND (single character numeric) – the charge indicator data item.
0 Initial value 1 no indication 2 no charge (N.B.) 3 charge 4 spare
ANM-BACI-CDP-STAT-IND (single character numeric) – the called party status indicator data item.
0 Initial value
246 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Backward Call Indicator
1 no indication 2 subscriber free 3 connect when free 4 spare
ANM-BACI-CDP-CAT-IND (single character numeric) – the called party category indicator data item.
0 Initial value 1 no indication 2 ordinary subscriber 3 payphone 4 spare
ANM-BACI-EE-METHOD-INC (single character numeric) – the end-to-end method indicator data item.
0 Initial value 1 no end-to-end method available 2 pass along method available 3 SCCP method available 4 pass along and SCCP methods available
ANM-BACI-INTERNETWORK-IND (single character numeric) – the internetworking indicator data item.
0 Initial value 1 no interworking encountered 2 interworking encountered
ANM-BACI-EE-INFO-IND (single character numeric) – the end-to-end information indicator data item. 0 Initial value 1 no end-to-end information available 2 end-to-end information available
ANM-BACI-ISUP-IND (single character numeric) – the ISDN user part indicator data item.
0 Initial value
Avaya CCSS 1000/2000 Feature Documentation August 2013 247 ISUP Application Programming
1 ISDN user part not used all the way 2 ISDN user part used all the way
ANM-BACI-HOLD-IND (single character numeric) – the holding indicator data item.
0 Initial value 1 holding not requested 2 holding requested
ANM-BACI-ISDN-ACCESS-IND (single character numeric) – the ISDN access indicator data item.
0 Initial value 1 originating access non-ISDN 2 originating access ISDN
ANM-BACI-ECHO-CONTROL-IND (single character numeric) – the echo control device indicator data item.
0 Initial value 1 Echo Control Not Included 2 Echo Control Included
ANM-BACI-SCCP-METHOD-IND (single character numeric) – the SCCP method indicator data item.
0 Initial value 1 no indication 2 connectionless method available 3 connection oriented method available 4 connectionless and connection oriented
Optional Backward Call Indicators
The Optional Backward Call Indicator (OBI) parameters are optional.
ANM-OBI-INBAND-IND (single character numeric) – the in-band information indicator data item.
248 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] End of Optional Parameters
0 Initial value 1 no indication 2 in-band info or pattern is now available
ANM-OBI-FORWARD-IND (single character numeric) – the call forwarding may occur indicator data item.
0 Initial value 1 no indication 2 call forwarding may occur
End of Optional Parameters
At the end of the last optional parameter message field, there is the end of optional parameters message indicator. This indicator should always be zero. ANM-END-OF-PARAMETER (single character numeric) – end of optional parameters data item. 0 Initial value
Extended Answer
The CCSS sends the existing ANM message type unless the CCSS is configured with the following in the ss7.conf file: CONFIG CCME_OPTION = EXTENDED, VALUE=1, 2, 3, 4, or 5
Extended Option 1
ANMX-MESSAGE-TYPE (three character numeric) – use this data item to compare incoming messages. This item should always be 031 for CCME_OPTION EXTENDED 1.
Avaya CCSS 1000/2000 Feature Documentation August 2013 249 ISUP Application Programming
ANMX Parameters
The Connected Number parameter is included in the ANMX messages that are appended to the end of the existing ANM data folder.
Extended Option 2
ANMX-MESSAGE-TYPE (three character numeric) – use this data item to compare incoming messages. This data item should always be 036 for CCME_OPTION EXTENDED 2, 3, 4, or 5. The following table lists the parameters that are included in the ANMX messages and are appended to the end of the existing ANM data folder.
Parameter Name Comment Connected Number Additional Parameters Includes: Access Transport Unrecognized Parameters Parameter Compatibility Info User to User Info
Connected Number
All of the following Connected Number (CONN) parameters are optional.
ANMX-CONN-NOA-IND (three character numeric) – the nature of address indicator data item.
000 Initial value 001 spare 002 subscriber number 003 spare, reserved for national use 004 national (significant) number 005 international number
250 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Connected Number
006-256 spare
ANMX-CONN-NUMBER-PLAN (single character numeric) – the numbering plan indicator data item.
0 Initial value 1 spare 2 ISDN (Telephony) numbering plan 3 spare 4 Data numbering plan 5 Telex numbering plan 6-7 reserved for national use 8 spare
ANMX-CONN-ADD-PRSNT-RESTRICT-IND (single character numeric) – the address presentation restricted data item.
0 Initial value 1 presentation allowed 2 presentation restricted 3 address not available 4 spare
ANMX-CONN-SCREEN-IND (single character numeric) – the screening indicator data item.
0 Initial value 1 reserved 2 user provided, verified and passed 3 reserved 4 network provided
ANMX-CONN-ADDRESS (20 character alphanumeric) – the address signal data item.
0 digit 0 1 digit 1 2 digit 2 3 digit 3
Avaya CCSS 1000/2000 Feature Documentation August 2013 251 ISUP Application Programming
4 digit 4 5 digit 5 6 digit 6 7 digit 7 8 digit 8 9 digit 9 A spare B code 11 C code 12 D spare E spare F spare
Additional Parameters
ANMX-ADD-PARAM (522 character numeric) – for more about this structure, see Additional Parameters on page 295.
End of Optional Parameters
At the end of the last optional parameter message field there is an end of optional parameters message indicator. This indicator should always be zero. ANMX-END-OF-PARAMETER (single character numeric) – end of optional parameters data item. 0 Initial value
Call Progress
CPG-MESSAGE-TYPE (three character numeric) – use this data item to compare incoming messages. This data item should always be 004.
252 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Event Information
Event Information
The Event Information (EVI) parameters are mandatory and have a fixed length.
CPG-EVI-EVI-IND (three character numeric) – the event indicator data item.
000 Initial value 001 spare 002 ALERTING 003 PROGRESS 004 in-band info or pattern is now available 005 call forwarded on busy 006 call forwarded on no reply 007 call forwarded unconditional 008 spare
CPG-EVI-EVENT-PRESENT-RESTRICT-IND (single character numeric) – the event presentation restricted indicator data item.
0 Initial value 1 no indication 2 presentation restricted
Backward Call Indicator
The Backward Call Indicator (BACI) parameters are optional.
CPG-BACI-CHARGE-IND (single character numeric) – the charge indicator data item.
0 Initial value 1 no indication 2 no charge (N.B.) 3 charge
Avaya CCSS 1000/2000 Feature Documentation August 2013 253 ISUP Application Programming
4 spare
CPG-BACI-CDP-STAT-IND (single character numeric) – the called party status indicator data item.
0 Initial value 1 no indication 2 subscriber free 3 connect when free 4 spare
CPG-BACI-CDP-CAT-IND (single character numeric) – the called party category indicator data item.
0 Initial value 1 no indication 2 ordinary subscriber 3 payphone 4 spare
CPG-BACI-EE-METHOD-IND (single character numeric) – the end-to-end method indicator data item.
0 Initial value 1 no end-to-end method available 2 pass along method available 3 SCCP method available 4 pass along and SCCP methods available
CPG-BACI-INTERNETWORK-IND (single character numeric) – the internetworking indicator data item.
0 Initial value 1 no interworking encountered 2 interworking encountered
CPG-BACI-EE-INFO-IND (single character numeric) – the end-to-end information indicator data item.
0 Initial value
254 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Backward Call Indicator
1 no end-to-end information available 2 end-to-end information available
CPG-BACI-ISUP-IND (single character numeric) – the ISDN user part indicator data item.
0 Initial value 1 ISDN user part not used all the way 2 ISDN user part used all the way
CPG-BACI-HOLD-IND (single character numeric) – the holding indicator data item.
0 Initial value 1 holding not requested 2 holding requested
CPG-BACI-ISDN-ACCESS-IND (single character numeric) – the ISDN access indicator data item.
0 Initial value 1 originating access non-ISDN 2 originating access ISDN
CPG-BACI-ECHO-CONTROL-IND (single character numeric) – the echo control device indicator data item.
0 Initial value 1 Echo Control Not Included 2 Echo Control Included
CPG-BACI-SCCP-METHOD-IND (single character numeric) – the SCCP method indicator data item.
0 Initial value 1 no indication 2 connectionless method available 3 connection oriented method available 4 connectionless and connection oriented
Avaya CCSS 1000/2000 Feature Documentation August 2013 255 ISUP Application Programming
Optional Backward Call Indicators
The Optional Backward Call Indicator (OBI) parameters are optional.
CPG-OBI-INBAND-IND (single character numeric) – the in-band information indicator data item.
0 Initial value 1 no indication 2 in-band info or pattern is now available
CPG-OBI-FORWARD-IND (single character numeric) – the call forwarding may occur indicator data item.
0 Initial value 1 no indication 2 call forwarding may occur
End of Optional Parameters
At the end of the last optional parameter message field there is an end of optional parameters message indicator. This indicator should always be zero. CPG-END-OF-PARAMETER (single character numeric) – end of optional parameters data item. 0 Initial value
Extended Call Progress
The CCSS sends this message type when it is configured with 'CONFIG CCME_OPTION = EXTENDED, VALUE=1, 2, 3, 4, or 5' in the ss7.conf file.
256 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Extended Option 2
Extended Option 2
CPGX-MESSAGE-TYPE (three character numeric) – use this data item to compare incoming messages. This data item should always be 032 for CCME_OPTION EXTENDED 2 or 3. The following table lists the parameters that are included in the CPG messages that are appended to the end of the existing CPG data folder.
Parameter Name Comment Additional Parameters Includes: Generic Notification Access Transport Unrecognized Parameters Parameter Compatibility Info User to User Info
Extended Option 4
CPGX-MESSAGE-TYPE (three character numeric) – use this data item to compare incoming messages. This data item should always be 046 for CCME_OPTION EXTENDED 4, 5 or 6. The following table lists the parameters that are included in the CPG messages that are appended to the end of the existing CPG data folder.
Parameter Name Comment Cause Indicator Additional Parameters Includes: Generic Notification Access Transport Unrecognized Parameters Parameter Compatibility Info User to User Info
Extended Option 5
CPGX-MESSAGE-TYPE (three character numeric) – use this data item to compare incoming messages. This data item should always be 123 for CCME_OPTION EXTENDED 7.
Avaya CCSS 1000/2000 Feature Documentation August 2013 257 ISUP Application Programming
The following table lists the parameters that are included in the CPG messages that are appended to the end of the existing CPG data folder.
Parameter Name Comment Cause Indicator Additional Parameters Includes: Call Diversion Information Generic Notification Redirection Number Unrecognized Parameters Parameter Compatibility Info User to User Info
Cause Indicator
The Cause Indicator (CAU) parameters are optional and can have a variable length. This parameter is similar to the cause parameter in Rel msg. For more information, see Cause Indicators on page 272.
Call Diversion Information
CPGX-CDI-NOTIF-SUBSCR (single character numeric) – notification subscription options data item.
0 initial value 1 reserved 2 presentation not allowed 3 presentation allowed with redirection number 4 presentation allowed without redirection number
CPGX-CDI-REDIR-REASON (single character numeric) – redirecting reason data item.
0 initial value 1 reserved 2 User busy 3 no reply
258 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Redirection Number
4 unconditional 5 deflection during alerting 6 deflection immediate response 7 mobile subscriber not reachable
Redirection Number
CPGX-REDN-NOA-IND (3 character numeric) – nature of address indicator data item.
0 initial value 1 reserved 2 subscriber number (national use) 3 unknown (national use) 4 national (significant) number 5 international number 6 reserved 7 network routing number in national (significant) number format (national use) 8 network routing number in network-specific number format (national use) 9 reserved for network routing number concatenated with Called Directory Number (national use)
CPGX-REDN-INN-IND (single character numeric) – internal network number indicator data item.
0 initial value 1 routing to internal network number allowed 2 routing to internal network number not allowed
CPGX-REDN-NUMBER-PLAN (single character numeric) – numbering plan indicator data item.
0 initial value 1 spare 2 ISDN (Telephony) numbering plan (ITU-T Recommendation E.164) 3 spare
Avaya CCSS 1000/2000 Feature Documentation August 2013 259 ISUP Application Programming
4 Data numbering plan (ITU-T Recommendation X.121) (national use) 5 Telex numbering plan (ITU-T Recommendation F.69) (national use)
CPGX-REDN-ADDRESS (18 character alphanumeric) – redirecting address data item.
0 digit 0 1 digit 1 2 digit 2 3 digit 3 4 digit 4 5 digit 5 6 digit 6 7 digit 7 8 digit 8 9 digit 9 A spare B code 11 C code 12 D spare E spare F ST
Generic Notification Indicator
NOTIF-ID (3 character numeric) – notification indicator data item.
0 initial value 1 user suspended 2 user resumed 3 bearer service change 4 Discriminator for extension to ASN.1 encoded component (used in DSSI) 5 call completion delay 6-66 reserved 67 conference established 68 conference disconnected 69 other party added 70 isolated 71 reattached 72 other party isolated 73 other party reattached 74 other party split 75 other party disconnected 76 conference floating 77-96 reserved 97 call is a waiting call
260 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Additional Parameters
98-104 reserved 105 diversion activated (used in DSS1) 106 call transfer, alerting 107 call transfer, active 108 reserved 122 remote hold 123 remote retrieval 124 call is diverting 125-128 reserved
Additional Parameters
CPGX-ADD-PARAM (522 character numeric) – for more information about this structure, see Additional Parameters on page 295.
Connect
CONN-MESSAGE-TYPE (three character numeric) – use this data item to compare incoming messages. This should always be 007. This message provides basic support for transmitting and receiving of the CONN message. For extended capabilities, see Extended Connect on page 265.
Backward Call Indicator
The Backward Call Indicator (BACI) parameters are mandatory and have a fixed length.
CONN-BACI-CHARGE-IND (single character numeric) – the charge indicator data item.
0 Initial value 1 no indication 2 no charge (N.B.) 3 charge
Avaya CCSS 1000/2000 Feature Documentation August 2013 261 ISUP Application Programming
4 spare
CONN-BACI-CDP-STAT-IND (single character numeric) – the status indicator data item of the called party.
0 Initial value 1 no indication 2 subscriber free 3 connect when free 4 spare
CONN-BACI-CDP-CAT-IND (single character numeric) – the category indicator of the called party.
0 Initial value 1 no indication 2 ordinary subscriber 3 payphone 4 spare
CONN-BACI-EE-METHOD-IND (single character numeric) – the end-to-end method indicator data item.
0 Initial value 1 no end-to-end method available 2 pass along method available 3 SCCP method available 4 pass along and SCCP methods available
CONN-BACI-INTERNETWORK-IND (single character numeric) – the internetworking indicator data item.
0 Initial value 1 no interworking encountered 2 interworking encountered
CONN-BACI-EE-INFO-IND (single character numeric) – the end-to-end information indicator data item.
0 Initial value
262 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Backward Call Indicator
1 no end-to-end information available 2 end-to-end information available
CONN-BACI-ISUP-IND (single character numeric) – the ISDN user part indicator data item.
0 Initial value 1 ISDN user part not used all the way 2 ISDN user part used all the way
CONN-BACI-HOLD-IND (single character numeric) – the holding indicator data item.
0 Initial value 1 holding not requested 2 holding requested
CONN-BACI-ISDN-ACCESS-IND (single character numeric) – the ISDN access indicator data item.
0 Initial value 1 originating access non-ISDN 2 originating access ISDN
CONN-BACI-ECHO-CONTROL-IND (single character numeric) – the echo control device indicator data item.
0 Initial value 1 Echo Control Not Included 2 Echo Control Included
CONN-BACI-SCCP-METHOD-IND (single character numeric) – the SCCP method indicator data item.
0 Initial value 1 no indication 2 connectionless method available 3 connection oriented method available 4 connectionless and connection oriented
Avaya CCSS 1000/2000 Feature Documentation August 2013 263 ISUP Application Programming
Optional Backward Call Indicators
The Optional Backward Call Indicator (OBI) parameters are optional.
CONN-OBI-INBAND-IND (single character numeric) – the in-band information indicator data item.
0 Initial value 1 no indication 2 in-band info or pattern is now available
CONN-OBI-FORWARD-IND (single character numeric) – the call forwarding may occur indicator data item.
0 Initial value 1 no indication 2 call forwarding may occur
End of Optional Parameters
At the end of the last optional parameter message field there is the end of optional parameters message indicator. This indicator should always be zero.
CONN-END-OF-PARAMETER (single character numeric) – end of optional parameters data item.
0 Initial value
264 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Extended Connect
Extended Connect
Extended Option 2
CONN-MESSAGE-TYPE (three character numeric) – use this data item to compare incoming messages. This data item should always be 033. The CCSS sends this message type when it is configured with the 'CONFIG CCME_OPTION = EXTENDED, VALUE=2, 3, 4 or 5' in the ss7.conf file. The following table lists the parameters that are included in the CONN message that is appended to the end of the existing CONN data folder.
Parameter Name Comment
Additional Parameters • Includes: • Access Transport • Unrecognized Parameters • Parameter Compatibility Info • User to User Info
Additional Parameters
CONNX-ADD-PARAM (522 character numeric) – for information about this structure, see Additional Parameters on page 295.
Information
INF-MESSAGE-TYPE (three character numeric) – use this data item to compare incoming messages. This data item should always be 009.
Avaya CCSS 1000/2000 Feature Documentation August 2013 265 ISUP Application Programming
Information Indicators
The Information Indicator (INI) parameters are mandatory and have a fixed length.
INF-INI-CGP-ADDRESS-RESP-IND (single character numeric) – the calling party address response indicator data item.
0 Initial value 1 Calling party address not included 2 Calling party address not available 4 Calling party address included
INF-INI-HOLD-PROVIDE-IND (single character numeric) – the hold provided indicator data item.
0 Initial value 1 hold not provided 2 hold provided
INF-INI-CGP-CAT-RESP-IND (single character numeric) – the category response indicator of the calling party.
0 Initial value 1 calling party's category not included 2 calling party's category included
INF-INI-CHARGE-INFO-RESP-IND (single character numeric) – the charge information response indicator data item.
0 Initial value 1 charge information not included 2 charge information included
INF-INI-SOLICITED-INFO-IND (single character numeric) – the solicited information indicator.
0 Initial value 1 solicited 2 unsolicited
266 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Calling Party Category
Calling Party Category
The Calling Party's Category (CGPC) parameter is optional.
INF-CGPC-CGPC (three character numeric) – the category data item of the calling party.
000 Initial value 001 calling party's category unknown 002 operator, language French 003 operator, language English 004 operator, language German 005 operator, language Russian 006 operator, language Spanish 007 available to administrations for 008 selecting a particular language by 009 by mutual agreement 010 reserved 011 ordinary calling subscriber 012 calling subscriber with priority 013 data call 014 test call 015 spare 016 pay phone 017-256 reserved
Calling Party Number
The Calling Party Number (CGPN) parameters are optional and are not sent by the network.
INF-CGPN-NOA-IND (three character numeric) – the nature of address indicator data item.
Avaya CCSS 1000/2000 Feature Documentation August 2013 267 ISUP Application Programming
000 initial value 001 spare 002 subscriber number 003 spare, reserved for national use 004 national (significant) number 005 international number 006–256 spare
INF-CGPN-CGP-NI-IND (single character numeric) – the calling party number incomplete indicator data item.
0 Initial value 1 complete 2 incomplete
INF-CGPN-NUMBER-PLAN (single character numeric) – the numbering plan indicator data item.
1 spare 2 ISDN (Telephony) numbering plan 3 spare 4 Data numbering plan 5 Telex numbering plan 6-7 reserved for national use 8 spare
INF-CGPN-ADD-PRESENT-RESTRICT-IND (single character numeric) – the address presentation restricted indicator data item.
0 Initial value 1 presentation allowed 2 presentation restricted 3 address not available 4 spare
INF-CGPN-SCREEN-IND (single character numeric) – the screening indicator data item.
0 Initial value
268 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] End of Optional Parameters
1 reserved 2 user provided, verified and passed 3 reserved 4 network provided
INF-CGPN-ADDRESS (20 character alphanumeric) – the address signal data item.
0 digit 0 1 digit 1 2 digit 2 3 digit 3 4 digit 4 5 digit 5 6 digit 6 7 digit 7 8 digit 8 9 digit 9 A spare B code 11 C code 12 D spare E spare F spare
End of Optional Parameters
At the end of the last optional parameter message field there is the end of optional parameters message indicator. This indicator should always be zero.
INF-END-OF-PARAMETER (single character numeric) – end of optional parameters data item.
0 Initial value
Avaya CCSS 1000/2000 Feature Documentation August 2013 269 ISUP Application Programming
Information Request
INR-MESSAGE-TYPE (three character numeric) – use this data item to compare incoming messages. This data item should always be 010.
Information Request Indicators
The Information Request Indicators are mandatory and have a fixed length.
INR-INRI-CALLING-PTY-ADD-REQ-IND (single character numeric) – the calling party address request indicator data item.
0 Initial value 1 calling party address not requested 2 calling party address requested
INR-INRI-HOLD-IND (single character numeric) – the holding indicator data item.
0 Initial value 1 holding not requested 2 hold requested
INR-INRI-CALLING-PTY-CAT-REQ-IND (single character numeric) – the calling party category request indicator data item.
0 Initial value 1 calling party's category not requested 2 calling party's category requested
INR-INRI-CHG-INF-REQ-IND (single character numeric) – the charge information request indicator data item.
0 Initial value 1 charge Information not requested 2 charge Information requested
INR-INRI-MAL-CALL-IDENT-REQ-IND (single character numeric) – the malicious call identification request indicator data item.
270 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] End of Optional Parameters
0 Initial value 1 malicious call identification not requested 2 malicious call identification requested
End of Optional Parameters
At the end of the last optional parameter message field there is the end of optional parameters message indicator. This parameter should always be zero.
INR-END-OF-PARAMETER (single character numeric) – end of optional parameters data item.
0 Initial value
Cause Diagnostics
RELX-CAU-DIAGNOSTIC-LEN (2 character The length of the diagnostics field data numeric) item. RELX-CAU-DIAGNOSTIC-DIAG (32 The diagnostics field data item. character alphanumeric)
Release
REL-MESSAGE-TYPE (three character numeric) – use this data item to compare incoming messages. This data item should always be. This message provides basic support for transmitting and receiving of the REL message. For extended capabilities Extended Release on page 276
Avaya CCSS 1000/2000 Feature Documentation August 2013 271 ISUP Application Programming
Cause Indicators
The Cause Indicator (CAU) parameters are mandatory and can have a variable length.
REL-CAU-EXT-INDL (single character numeric) – the extension indicator data item.
0 Initial value 1 octet continues through the next octet 2 last octet
REL-CAU-CODING-STANDARD (single character numeric) – the coding standard data item.
0 Initial value 1 CCITT standard 2 reserved for other international standard 3 national standard 4 standard specific to identified location
REL-CAU-LOCATION (two character numeric) – the location data item.
00 Initial value 01 user 02 private network serving the local user 03 public network serving the local user 04 transit network 05 public network serving the remote user 06 private network serving the remote user 07 international network 08 beyond an interworking point 09-16 all others reserved
REL-CAU-EXT-IND1A (single character numeric) – an extension indicator data item.
0 Initial value 1 octet continues through the next octet
272 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Cause Indicators
2 last octet
REL-CAU-RECOMMENDATION (three character numeric) – the recommendation data item.
001 Q7.63 004 X.21 005 X.25 006 public land mobile networks, q.1000
REL-CAU-EXT-IND2 (single character numeric) – an extension indicator data item.
1 octet Continues through the next octet 2 last octet (Initial value)
REL-CAU-CAUSE-VAL (three character numeric) – the cause value data item.
000 Initial value 002 unallocated (unassigned) number 003 no route to transit network (natl use) 004 no route to destination 005 send special Information tone 006 misdialled trunk prefix 017 normal call clearing 018 user busy 019 no user responding 020 no answer from user (user alerted) 022 call rejected 023 number changed 028 destination out of order 029 address incomplete 030 facility rejected 032 normal - unspecified 035 no circuit available 039 network out of order 042 temporary failure
Avaya CCSS 1000/2000 Feature Documentation August 2013 273 ISUP Application Programming
043 switching equipment Congestion 045 requested channel not available 048 resource unavailable - unspecified 051 requested facility not subscribed 056 incoming calls barred within CUG 058 bearer capability not authorized 059 bearer capability not presently available 064 service/option not available - unspecified 066 bearer capability not implemented 070 requested facility not implemented 071 only restored digital info bearer capacity avble 080 svce or option not implemented - unspecified 088 called user not member of CUG 089 incompatible destination 092 invalid transit network selection (natl use) 096 invalid message, unspecified 098 message type non-existent or not implemented 100 parameter non-existent/not implemented-discarded 104 parameter non-existent/not implemented-passed on 112 protocol error, unspecified 128 interworking, unspecified
REL-CAU-COND-COND (single character numeric) – the condition diagnostic data item.
0 Initial value 1 unknown 2 permanent 3 transient REL-CAU-COND-EXT-IND3 (single character numeric) – an extension indicator data item.
0 Initial value 1 octet continues through next octet 2 last octet
274 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] End of Optional Parameters
REL-CAU-COND-ATT-NUM (three character numeric) – the attribute number data item.
000 Initial value
REL-CAU-COND-EXT-IND3A (single character numeric) – an extension indicator data item.
0 Initial value 1 octet continues through next octet 2 last octet
REL-CAU-COND-REJ-ATTRIB (three character numeric) – the rejected attribute data item.
000 Initial value
REL-CAU-COND-EXT-IND3B (single character numeric) – an extension indicator data item.
0 Initial value 1 octet continues through next octet 2 last octet
REL-CAU-COND-AVAIL-ATTRIB (three character numeric) – the available attribute data item.
000 Initial value
REL-CAU-COND-PARM-NAM (eight character numeric) – the parameter name data item.
0 Initial value
End of Optional Parameters
At the end of the last Optional Parameter field there is the end of Optional Parameters Message Indicator. This indicator should always be zero.
REL-END-OF-PARAMETER (single character numeric) – end of optional parameters data item.
0 Initial value
Avaya CCSS 1000/2000 Feature Documentation August 2013 275 ISUP Application Programming
Extended Release
Extended Option 1
RELX-MESSAGE-TYPE (three character numeric) – use this data item to compare incoming messages. This data item should always be 030.
030 Initial value
The CCSS sends this message type when it is configured with "CONFIG CCME_OPTION = EXTENDED, VALUE=1" in the ss7.conf file. The following parameters are included in the RELX message that is appended to the end of the existing REL data folder. Example • Called Party Number • Signaling Point Code
Extended Option 2
RELX-MESSAGE-TYPE (three character numeric) – use this data item to compare incoming messages. This data item should always be 037.
037 Initial value
The CCSS sends this message type when it is configured with "CONFIG CCME_OPTION = EXTENDED, VALUE= 2" in the ss7.conf file.
276 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Extended Option 4
The following parameters are included in the RELX message that is appended to the end of the existing REL data folder. Example • Called Party Number • Signaling Point Code • Automatic Congestion Level
Extended Option 4
RELX-MESSAGE-TYPE (three character numeric) – use this item to compare incoming messages. This data item should always be 040.
040 Initial value
The CCSS sends this message type when it is configured with "CONFIG CCME_OPTION = EXTENDED, VALUE= 3, 4, 5 or 6" in the ss7.conf file. The following parameters are included in the RELX message that is appended to the end of the existing REL data folder. Example • Called Party Number • Signaling Point Code • Automatic Congestion Level
Extended Option 5
RELX-MESSAGE-TYPE (three character numeric) – use this item to compare incoming messages. This data item should always be 125.
125 Initial value
The CCSS sends this message type when it is configured with 'CONFIG CCME_OPTION = EXTENDED, VALUE= 7' in the ss7.conf file. The following table lists the parameters that are included in the RELX message that is appended to the end of the existing REL data folder.
Avaya CCSS 1000/2000 Feature Documentation August 2013 277 ISUP Application Programming
Parameter Name Comment Called Party Number Signaling Point Code Automatic Congestion Level Redirection Number Redirection Information
Extended Option 8
RELX-MESSAGE-TYPE (three character numeric) – use this item to compare incoming messages. This data item should always be 126. 126 Initial value
The CCSS sends this message type when it is configured with CONFIG CCME_OPTION = EXTENDED, VALUE= 8 in the ss7.conf file. The following table lists the parameter that is included in the RELX message that is added after RELX-CAU-PARM-NAM. The diagnostics parameter is optional.
Parameter Name Comment Cause Diagnostics RELX-CAU-DIAGNOSTIC-LEN (2 character numeric) - The length of the diagnostics field data item. RELX-CAU-DIAGNOSTIC-DIAG (32 character alphanumeric) - The diagnostics field data item.
Called Party Number
The Called Party Number (CDPN) parameters are mandatory.
RELX-CDPN-NOA-IND (three character numeric) – the nature of address indicator data item.
000 Initial value 001 spare 002 subscriber number
278 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Called Party Number
003 spare, reserved for national use 004 national (significant) number 005 international number 006-112 spare 113 unknown 114-256 spare
RELX-CDPN-INN-IND (single character numeric) – the internal network number indicator data item.
0 Initial value 1 route to internal net # ok 2 route to internal net # not ok
RELX-CDPN-NUMBER-PLAN (single character numeric) –the numbering plan indicator data item.
0 Initial value 1 spare 2 ISDN (Telephony) numbering plan 3 spare 4 Data numbering plan 5 Telex numbering plan 6-7 reserved for national use 8 spare
RELX-CDPN-ADDRESS (18 character alphanumeric) – redirecting address data item.
0 digit 0 1 digit 1 2 digit 2 3 digit 3 4 digit 4 5 digit 5 6 digit 6 7 digit 7 8 digit 8 9 digit 9 A spare B code 11 C code 12 D spare E spare F ST
Avaya CCSS 1000/2000 Feature Documentation August 2013 279 ISUP Application Programming
Signaling Point Code
RELX-SPC (five character numeric) – Signaling Point Code data item. 0 Initial value
1-214 decimal value of the point code
Automatic Congestion Level
RELX-ACL (three character numeric) – Automatic Congestion Level data item.
001 spare 002 congestion level 1 exceeded 003 congestion level 2 exceeded 004 -256 spare
Redirection Number
RELX-REDN-NOA-IND (3 character numeric) – Nature of Address indicator data item.
0 initial value 1 reserved 2 subscriber number (national use) 3 unknown (national use) 4 national (significant) number 5 international number 6 reserved 7 network routing number in national (significant) number format (national use) 8 network routing number in network-specific number format (national use)
280 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Redirection Information
9 reserved for network routing number concatenated with Called Directory Number (national use) RELX-REDN-INN-IND (single character numeric) – internal network number indicator data item.
0 initial value 1 routing to internal network number allowed 2 routing to internal network number not allowed
RELX-REDN-NUMBER-PLAN (single character numeric) – numbering plan indicator data item.
0 initial value 1 spare 2 ISDN (Telephony) numbering plan (ITU-T Recommendation E.164) 3 spare 4 Data numbering plan (ITU-T Recommendation X.121) (national use) 5 Telex numbering plan (ITU-T Recommendation F.69) (national use)
RELX-REDN-ADDRESS (18 character alphanumeric) – redirecting address data item.
0 digit 0 1 digit 1 2 digit 2 3 digit 3 4 digit 4 5 digit 5 6 digit 6 7 digit 7 8 digit 8 9 digit 9 A spare B code 11 C code 12 D spare E spare F ST
Redirection Information
The following Redirecting Information (REDI) parameters are optional.
RELX-REDI-REDIRECT-IND (single character numeric) – the redirecting indicator data item.
0 Initial value 1 no redirection 2 call rerouted 3 call rerouted, redirect info pres. restricted
Avaya CCSS 1000/2000 Feature Documentation August 2013 281 ISUP Application Programming
4 call forwarded 5 call forwarded, redirect info pres. restricted 6 call rerouted, redirect # pres. restricted 7 call forwarded, redirect # pres. restricted 8 spare
RELX-REDI-REDIRECT-REASON (two character numeric) – the original redirecting reasons data item.
00 Initial value 01 unknown/not available 02 user busy 03 no reply 04 unconditional 05-16 spare RELX-REDI-REDIRECTION-COUNTER (single character numeric) – the redirection counter data item.
This data item is a binary number between 2 and 6.
RELX-REDI-REDIRECTING-REASON (two character numeric) – the redirecting reason data item.
00 Initial value 01 unknown/not available 02 user busy 03 no reply 04 unconditional 05-16 spare
Release Complete
RLC-MESSAGE-TYPE (three character numeric) – use this data item to compare incoming messages. This data item should always be 012.
282 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Cause Indicators
Cause Indicators
The Cause Indicator (CAU) parameters are optional.
RLC-CAU-EXT-IND1 (single character numeric) – the extension indicator data item.
0 Initial value 1 octet continues through the next octet 2 last octet
RLC-CAU-CODING-STANDARD (single character numeric) – the coding standard data item.
0 Initial value 1 CCITT standard 2 reserved for other international standard 3 national standard 4 standard specific to identified location
RLC-CAU-LOCATION (two character numeric) – the location data item.
00 Initial value 01 user 02 private network serving the local user 03 public network serving the local user 04 transit network 05 public network serving the remote user 06 private network serving the remote user 07 international network 08 beyond an interworking point 09-16 all others reserved
RLC-CAU-EXT-IND1A (single character numeric) – an extension indicator data item.
0 Initial value 1 octet continues through the next octet
Avaya CCSS 1000/2000 Feature Documentation August 2013 283 ISUP Application Programming
2 last octet
RLC-CAU-RECOMMENDATION (three character numeric) – the recommendation data item.
000 Initial value 001 Q7.63 004 X.21 005 X.25 006 public land mobile networks, q.1000
RLC-CAU-EXT-IND2 (single character numeric) – an extension indicator data item.
0 Initial value 1 octet continues through the next octet 2 last octet (Initial value)
RLC-CAU-CAUSE-VAL (three character numeric) – the cause value data item. 000 Initial value 002 unallocated (unassigned) number 003 no route to specified transit net (natl use) 004 no route to destination 005 send special information tone 006 misdialled trunk prefix 017 normal call clearing 018 user busy 019 no user responding 020 no answer from user (user alerted) 022 call rejected 023 number changed 028 destination out of order 029 address incomplete 030 facility rejected 032 normal - unspecified 035 no circuit available 039 network out of order
284 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Cause Indicators
042 temporary failure 043 switching equipment congestion 045 requested channel not available 048 resource unavailable - unspecified 051 requested facility not subscribed 056 incoming calls barred within CUG 058 bearer capability not authorized 059 bearer capability not presently available 064 service/option not available - unspecified 066 bearer capability not implemented 070 requested facility not implemented 071 only restricted digital info bearer cap. avail. 080 service/option not implemented - unspecified 088 called user not member of CUG 089 incompatible destination 092 invalid transit network selection (natl use) 096 invalid message, unspecified 098 message type non-existent or not implemented 100 parameter non-existent/not implemented-discarded 104 parameter non-existent/not implemented-passed on 112 protocol error, unspecified 128 interworking, unspecified
RLC-CAU-COND-COND (single character numeric) – the condition diagnostic data item.
0 Initial value 1 unknown 2 permanent 3 transient
RLC-CAU-COND-EXT-IND3 (single character numeric) – an extension indicator data item.
0 Initial value 1 octet continues through the next octet
Avaya CCSS 1000/2000 Feature Documentation August 2013 285 ISUP Application Programming
2 last octet
RLC-CAU-COND-ATT-NUM (three character numeric) – the attribute number data item.
000 Initial value
RLC-CAU-COND-EXT-IND3A (single character numeric) – an extension indicator data item.
0 Initial value 1 octet continues through the next octet 2 last octet
RLC-CAU-COND-REJ-ATTRIB (three character numeric) – the reject attribute data item.
000 Initial value
RLC-CAU-COND-EXT-IND3B (single character numeric) – an extension indicator data item.
0 Initial value 1 octet continues through the next octet 2 last octet
RLC-CAU-COND-AVAIL-ATTRIB (three character numeric) – the available attribute data item.
000 Initial value
RLC-CAU-COND-PARM-NAM (eight character numeric) – the parameter name data item.
0 Initial value
User to User Information
UUI-Message-Type (three character numeric) – use this data item to compare incoming messages. This data item should always be 053. 053 Initial value This parameter is used to convey information between ISDN users.
286 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Access Transport Parameter
UUI-USER-2-USER-LENGTH (3 character numeric) UUI-USER-2-USER-PARAMETER (131 character alphanumeric) 0 Initial value
Access Transport Parameter
This parameter is used to represent multiple Q.931 information elements. UUI-AXP-TRANS-LENGTH (3 character numeric) UUI-AXP-TRANS-PARAMETER (256 character alphanumeric)
Continuity Message
COT-MESSAGE-TYPE (three character numeric) – use this data item to compare incoming messages. This data item should always be 008. 008 Initial value This message provides basic support for transmitting a Continuity (COT) message.
Continuity Indicators
The Continuity Indicator (COT) parameters are mandatory.
COT-STATUS-IND (single character numeric) – the Status indicator data item.
0 Initial value 1 Continuity check failed 2 Continuity check successful
At the end of the last optional parameter message field, there is the end of optional parameters message indicator. This parameter should always be zero. COT-END-OF-PARAMETER (single character numeric) – end of optional parameters data item. 0 Initial value
Avaya CCSS 1000/2000 Feature Documentation August 2013 287 ISUP Application Programming
Continuity Check Request
CCR-MESSAGE-TYPE (three character numeric) – use this data item to compare incoming messages. This data item should always be 038. 038 Initial value This message provides basic support for transmitting and receiving a Continuity Check Request (CCR) message. There are no parameters for the Continuity Check Request. There is the end of optional parameters message indicator that should always have a value of zero. COT-END-OF-PARAMETER (single character numeric) – end of optional parameters data item. 0 Initial value
Continuity Processing (Proxy Mode)
Continuity Processing is divided into two halves. Example • Inbound Continuity Processing • Outbound Continuity Processing
288 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Inbound Continuity Processing
Inbound Continuity Processing
The application handling Continuity Processing on the inbound side must do the following: Example • Handle the request to loopback the inbound and outbound voice circuits. When a CCR condition is received, the application must issue a PLM Copy Command to connect the inbound and outbound voice circuits. • Handle the termination of loopback request. When a COT condition is received, the application must issue a PLM Copy Command to terminate the looping of the inbound and outbound voice circuits. • When a REL condition is received and the inbound and outbound circuits are in loopback, the application must issue a PLM Copy Command to terminate the loopback. For Application programming, see PLM Copy for Continuity Handling on page 370.
Outbound Continuity Processing
The application handling Continuity Check Requests on the outbound side must do the following: Example • Generate an IAM message with Continuity Check Indication set to Continuity Check Requested on this circuit. • Play a 2000 +/30 Hz tone. • Generate a COT with status of Success if the tone played is received on the inbound voice circuit. The received tone must be within the limits defined in Section 7.2.3 of Q.724. • Generate a COT with status of Failed if the tone is not received correctly. If the continuity test fails, the application must generate a CCR and repeat the test until the test passes.
Note: The sample applications supplied play the DTMF Tone 1. If the tone is received on the inbound circuit while being played, the applications determine that the continuity test is successful. If no tone is received then the applications send a COT message with the status of failure. If a COT with the status of success is sent, normal processing of the call continues.
Avaya CCSS 1000/2000 Feature Documentation August 2013 289 ISUP Application Programming
The following Sample Inbound and Outbound Continuity Testing Applications are provided in the samples directory: • rel5.inbound_cot_ext_1.ppr, rel5.outbound_cot_ext_1.ppr • rel5.outbound_cot_pre_ext_1.ppr • rel5.outbound_cot_pre_f_ext_1.ppr • rel5.outbound_ccr_ext_1.ppr
Facility Request
FACR-MESSAGE-TYPE (three character numeric) – use this data item to compare incoming messages. This data item should always be 048.
Facility Indicator
The Facility Indicator parameter is mandatory and has a fixed length. FACR-FACIND (three character numeric) – facility indicator data item. 016 Dual Port RLT 017 Single Port RLT (initial value)
Called Party Number
The Called Party Number is an optional parameter and has a variable length.
FACR-CDPN-NOA-IND (three character numeric) – the nature of address indicator data item.
000 initial value 001 spare 002 subscriber number 003 spare, reserved for national use 004 national (significant) number 005 international number 006-112 spare 113 unknown 114-256 spare
FACR-CDPN-INN-IND (single character numeric) – the internal network number indicator data item.
290 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Subsequent Number
0 Initial value 1 routing to internal network # allowed 2 routing to internal network # not allowed
FACR-CDPN-NUMBER-PLAN (single character numeric) – the numbering plan indicator data item.
0 Initial value 1 spare 2 ISDN (Telephony) numbering 3 spare plan 4 Data numbering plan 5 Telex numbering plan 6-7 reserved for national use 8 spare
FACR-CDPN-ADDRESS (18 character alphanumeric) – the address signal data item.
Note: With the release of ccss5.4, Called Party Number has a configurable length. The minimum size that can be configured is 18 digits. The maximum size is 64 digits. The default value is 18 digits. The number of digits is set in the ss7.conf file by using the following entry:
CONFIG CCME_OPTION = CDPN_LEN, VALUE=18 To transmit a Called Party Number with a length greater than 18 digits, use an IAM message followed by one or more SAM messages. The protocol supports a maximum of 18 digits in the IAM message. More than 18 digits results in a protocol error. The Called Party Number digits received with a combined length greater than that defined in the ss7.conf file, in IAM and SAM messages, will be truncated with the leading digits discarded.
Subsequent Number
The Subsequent Number is an optional parameter that has a variable length. If the application wants the pullback feature, the application must complete the subsequent number field. FACR-SUBSEQUENT-NUM (twenty-four character numeric) – Subsequent Number data item.
Avaya CCSS 1000/2000 Feature Documentation August 2013 291 ISUP Application Programming
Call Reference
Call Reference is an optional parameter that has a variable length. The Call Reference field is used for Single FAR Dual Port RLT only. The application must copy the "Call Reference" parameter that was received in the incoming ACM message to the outgoing FAR message. FACR-CALL-REF-ID (eight character numeric) – Call Reference ID data item. 0 Initial value FACR-CALL-REF-POINT-CODE (eight character numeric) – Call Reference Point Code data item.
0 Initial value
1-214 decimal value of the point code
Signalling Point Code
FACR-SPC (eight character numeric) – Signalling Point Code data item
0 Initial value
1-214 decimal value of the point code
User to User Information
FACR-UTU-SEND-ACK (single character numeric) – Send Acknowledgement data item
0 no response required for this request 1 send response for this request
FACR-UTU-CALL-BRIDGE-ID (five character numeric) – Call Bridge ID data item
0 Initial value 0-65535 decimal value of the bridge ID
292 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Facility Accept
Facility Accept
FAA-MSG-TYPE (three character numeric) – use this data item to compare incoming messages. This data item should always be 049.
Facility Indicator
The Facility Indicator parameter is mandatory and has a fixed length. FAA-FACIND (three character numeric) – Facility indicator data item.
016 Dual Port RLT 017 Single Port RLT (initial value)
Facility Reject
FRJ-MSG-TYPE (three character numeric) – use this data item to compare incoming messages. This data item should always be 050.
Facility Indicator
The Facility Indicator parameter is mandatory and of fixed length. FRJ-FACIND (three character numeric) – Facility indicator data item.
016 Dual Port RLT 017 Single Port RLT (initial value)
Cause Indicators
The Cause Indicators parameters are mandatory and and have variable lengths.
Avaya CCSS 1000/2000 Feature Documentation August 2013 293 ISUP Application Programming
FRJ-CAU-EXT-IND1 (single character numeric) – the extension indicator data item.
0 Initial value 1 octet continues through the next octet 2 last octet
FRJ-CAU-CODING-STANDARD (single character numeric) – the coding standard data item.
0 Initial value 1 CCITT standard 2 reserved for other international standard 3 national standard 4 standard specific to identified location
FRJ-CAU-LOCATION (two character numeric) – the location data item.
00 Initial value 01 user 02 private network serving the local user 03 public network serving the local user 04 transit network 05 public network serving the remote user 06 private network serving the remote user 07 international network 08 beyond an interworking point 09-16 all others reserved
FRJ-CAU-EXT-IND1A (single character numeric) – an extension indicator data item.
0 Initial value
FRJ-CAU-RECOMMENDATION (three character numeric) – the cause recommendation data item.
0 Initial value
FRJ-CAU-EXT-IND2 (single character numeric) – an extension indicator data item.
1 octet Continues through the next octet
294 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Cause Diagnostic
2 last octet (Initial value)
FRJ-CAU-CAUSE-VAL (three character numeric) – the cause value data item.
000 initial value 063 service or option not yet available 100 invalid parameter contents 031 normal - unspecified 041 temporary failure 079 service or option not implemented 081 invalid Call Reference Value 101 message not compatible with call state 102 recovery on timer expiry
Cause Diagnostic
FRJ-CAU-DIAGNOSTIC (single character numeric) – the cause diagnostic data item.
Additional Parameters
Parameters that are not included in the ISUP data folders can be accessed by using a C call function from the MPS Developer application. The call function provides a general mechanism for handling multiple occurrences, unrecognized and country specific parameters and for handling parameters that have a variable length and must be known in advance to define the data folder. This mechanism does not require changes in the CCSS software if support for additional parameters is required by the network because the parameters are passed as unrecognized to the application for processing. The initial implementation addresses application access to the following parameters: Example • Access Transport • Generic Name • Unrecognized Parameters • Parameter Compatibility Info
Avaya CCSS 1000/2000 Feature Documentation August 2013 295 ISUP Application Programming
• Supplementary Line Info • User to User Info The format of the data structure passed to the MPS Developer application is as follows:
Decoding/Encoding
Only parameters that have no data structure are included in this data structure. The data structure is defined as a series of characters of varying length that are the last elements of the IAMX. This mechanism can be used for both DECODING incoming messages and ENCODING outgoing messages, this enables the system to function as a transit exchange if required. Example call functions demonstrate sending and receiving additional parameters. The parameters are in the order that they were received from the network. When sending, the parameters are included in the order specified after all the parameters defined in the data folder. DECODE The DECODE function uses ID to search for a message in the network message. After the ID is found, DECODE returns the ID, Len, and Data parameters to the MPS Developer application.
296 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Decoding/Encoding
Input Parameter Description NetMsg The network message from which ID, Len, and Data can be DECODED from. ID The ID of the data in the network message. Len A return data length. Data A returning data. WhichID Enables the DECODE routine to know what data needs to return to the application. Sometimes there is more than one block of data which has the same ID.
Returns Description 0 Successfully decoded data -1 Error. Possible errors are: • Input arguments are greater than 5. • ID is not found in the network message or it can not find the specified ID passed in the WhichID parameter.
The input parameters for the external call function cf_CCSS_Decode_Param must be in the following order. If they are not in the specified order, the behavior of this function is unpredictable.
cf_CCSS_Decode_Param (char *NetMsg, char *ID, char *Len, char *Data, char *WhichID) { ... } ENCODE The ENCODE function uses the ID, Len, and Data parameters that are passed from the MPS Developer application and appended to the end of the network message. The network message is also passed in from the MPS Developer application.
Input Parameter Description NetMsg The first parameter which will be returned back to the application after the data is appended. ID The second parameter, representing massage ID, which will be appended to the network message. Len The third parameter, representing data length, which will be appended to the network message. Data The fourth parameter, and is the actual data needed to be appended to the network massage.
Avaya CCSS 1000/2000 Feature Documentation August 2013 297 ISUP Application Programming
Returns Description 0 Successfully encoded data -1 Error. Possible errors are: • Total number of arguments passed in this function is greater than 4. • Data length is greater than the available space for the network message.
The input parameters for the external call function cf_CCSS_Encode_Param must be in the following order. If they are not in this order, the behavior of this function is unpredictable.
cf_CCSS_Encode_Param (char *NetMsg, char *ID, char *Len, char *Data) { ... }
Remove
The REMOVE function searches for an ISUP parameter in the additional parameters folder of an SS7 ISUP message received from the network. If the parameter is found this function returns a copy of the input folder with the requested information element removed. With this function, the combination of call functions for handling additional parameters (cf_CCSS_Encode_Param, cf_CCSS_Decode_Param, and cf_CCSS_Remove_Param) can be used to edit parameters from an incoming message and pass them through to an outgoing message, adding or removing some parameters while leaving other parameters unchanged.
Parameter Description NetMsg The input network message from which the information element of type ID is to be removed. The function will not modify this value. ID The ID of the information element that is to be removed from NetMsg. This is a single byte and must be passed into the function converted to hexadecimal. Count A return value indicating the number of parameters removed by the function, also a hexadecimal byte. 0 = Parameter not found, and not removed. RetMsg will be the same as NetMsg. 1 = Parameter found and removed, RetMsg is NetMsg minus the parameter removed. -1 = A data error
298 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Printing a Network Message
Parameter Description occurred. RetMsg returned to the application is undefined. RetMsg An application folder of the same type as NetMsg, and at least as large. This holds the returned message, with the indicated information element removed if present. WhichID If an information element of type ID occurs more than once in NetMsg, this input parameter indicates which instance is to be removed. The function supports instances 1 to 5. If removing the first instance this argument is optional and does not have to be provided. This is a single byte and must be passed into the function converted to hexadecimal.
Returns Description 0 0 = Parameter not found, and not removed. 1 1 = Parameter found and removed -1 Error. Possible errors are: • Total number of arguments passed in this function is greater than 5. • Data errors in the input prevent locating the parameter identified and removing it.
The input parameters for the external call function cf_CCSS_Remove_Param must be provided in the following order. If they are not, the behavior of this function is unpredictable. cf_CCSS_Remove_Param (char *NetMsg, char *ID, char *Count, char *Data, char *WhichID) { ... }
Printing a Network Message
The parameters required to print an entire network message in hexadecimal format are described in the following table.
Parameter Description Input parameter NetMsg: network message Return none
Avaya CCSS 1000/2000 Feature Documentation August 2013 299 ISUP Application Programming
Parameter Description Note Not callable from application.
Note: This function is currently commented out in the callfunction file. To uncomment, edit the app_call_func.h file and set PRINT_ON to 1
void CCSS_PRINT_Msg(unsigned char *Buffer) { ... }
Sample Call Functions
The sample call functions are in $CCSSHOME/sample/call_func. The app_call_func_.h file contains the function prototypes that are implemented in app_call_func.c. The app_call_func.c file contains the source code for the ENCODE and DECODE call functions. Use the following instructions for compiling the call functions: Example • Change directory to the directory that contains app_call_func.h and app_call_func.c. For example:
cd $CCSSHOME/sample/call_func • Transfer app_call_func.h and app_call_func.c to a directory on the MPS. For example, / home/peri/call_func. • Execute the makecall script from the directory on the MPS, using the following command: makecall -C
300 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] ISUP Application Programming using the SS7 Toolkit
Note: The makecall script is a part of the PERIase package. This script is located in the $MPSHOME/bin directory after the PERIase package installation. • After the successful execution of the makecall script, the archive file and the corresponding shared object (libname.so) will be placed in the path. For example: libcall.a and libcall.so will be placed in /opt/vps/lib.
ISUP Application Programming using the SS7 Toolkit
For information about application programming using the SS7 toolkit, see ISUP Application Programming Using the SS7 Toolkit on page 304.
Dynamic Provisioning of Extended Mode
You can override the extended mode that is configured in ss7.conf file as a CCME option. Each line can run an application of a different extended mode instead of configuring a common extended mode for all lines in all trunk groups in the ss7.conf file. Dynamic provisioning of extended mode is available for PROXY and DSSI modes.
Dynamic Provisioning of Extended Mode in PROXY Mode
In PROXY mode, the dynamic provisioning of extended mode is shown in the following diagram.
Avaya CCSS 1000/2000 Feature Documentation August 2013 301 ISUP Application Programming
The CCSS resource must be acquired as shown in the previous diagram with the extended mode passed as part of the mode entry. To the mode string "isup, cond_msg" add a comma, a space, and "extxx" where xx is a two-digit number for the extended mode. Example: "isup, cond_msg, ext06" for extended mode 6.
302 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Chapter 7: ISUP Programming in TMS Integrated Mode for MPS
This chapter covers: 1. Introduction 2. Application Programming using SS7 Toolkit 3. Application Flow 4. Data Items
This chapter describes ISUP Application Programming in TMS Integrated Mode for MPS environment. TMS Integrated Mode is a CCSS configuration in which SS7 call control (CCME) interacts with the call control in the Telephony Media Server (TMS) to setup up phone calls. In TMS integrated mode, the signalling data and SS7 lines status information is passed between the application and CCSS server through a LAN connection to the TMS. In TMS mode, the TMS will use the 'CCext' interface to communicate with CCME, rather than the proxy API. CCext is an extension of CCME. The CCext defines a set of message primitives that allows the CCSS to communicate with the DSSI task (call control task) resident in the TMS. TMS integrated mode MPS Developer applications use the SS7 application programming toolkit to setup and clear down calls whereas in the Proxy Mode the applications are required to process SS7 ISUP messages and data content directly through the handling of ccs7cc conditions and the performance of send operations to the CCSS resource.
The applications in TMS (DSSI)1 Integrated Mode have an option not to handle the SS7 protocol data directly. For those applications that need to do so, there is capability to specify the data content of IAM and REL messages sent to the network.
Avaya CCSS 1000/2000 Feature Documentation August 2013 303 ISUP Programming in TMS Integrated Mode for MPS
ISUP Application Programming Using the SS7 Toolkit
SS7 Toolkit
The SS7 toolkit provides the MPS Developer application with a set of blocks and folder required to populate data pertaining to ISUP for sending/receiving to/from the CCSS using the Proxy resource, or the TMS mode of operation on the MPS.
SS7 Toolkit Blocks
The SS7 toolkit blocks for sending and receiving protocol data are identified in the following table.
SS7 Toolkit Block Description SS7Startup Block The SS7Startup block is used to determine the mode of operation the ISUP protocol variant to be used and the extended mode to be employed in the MPS Developer application. The mode of operation, the ISUP protocol variant and the extended mode can be specified through a command line option (or through the Parameter to Pass to Application option in the Application Configuration option of the Properties menu of MPS Developer). The acceptable command line options are: PROXYANSI, PROXYETSIEXT, PROXYITU, PROXYTELCORDIA, DSSIANSI, DSSIETSI, DSSIITU, DSSITELCORDIA. For these options, the extended mode is set to default value of 8. The extended mode may also be specified as a command line option in the format: PROXYITUEXT** or DSSIETSIEXT**, where ** specifies extended mode as EXT7 or EXT07 . Valid values for extended mode range from 0 to 8. SS7InitProto Block This block is used to initialize any one of the following ISUP messages with default values: IAMX, CPGX, ANMX, RELX, FACR and UUIX. This block is also used to indicate whether "Additional parameters" are in the message.
304 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] SS7 Toolkit Folders
SS7 Toolkit Block Description SS7SetProto Block The SS7SetProto block is used to fill the GSS7.ISUP- Send-Buf character data card with the ISUP message to send to the CCSS. The ISUP message type used is the same as the one specified in the SS7InitProto block. In TMS mode of operation, the GnHeader folder automatically precedes the GSS7.ISUP-Send-Buf.
SS7GetProto Block Prior to using the SS7GetProto block, the relevant ISUP message must be received in the GSS7.ISUP-Recv-Buf character data card. (The GSS7.ISUP-Recv-Buf-Length is used to receive the protocol data length). After executing this block, the received ISUP message is placed in the GSS7.ISUP-Message-In folder and can be extracted through the GSS7.ISUP-Message-In folder. This block also indicates whether Additional ISUP parameters are to be decoded.
SS7 Toolkit Folders
The toolkit folders specify data structures used to send or receive SS7 data in Proxy mode (data received as condition data) and TMS Integrated/DSSI mode (data received as VAR data).
Toolkit Folder File Use GSS7 ISS7.folder Used by applications to format, send, receive, and decode SS7 protocol data in the Proxy/DSSI mode. GSS7Common ISS7Common.folder Used by applications to get the mode and ISUP variant.
ISUP Protocol Folders
The ISUP Protocol Call Info folder definitions for formatting and retrieving protocol data are the same as defined in the section Data Items on page 214.
Avaya CCSS 1000/2000 Feature Documentation August 2013 305 ISUP Programming in TMS Integrated Mode for MPS
ISUP Parameter Value Specification in TMS Integrated Mode
The default ISUP parameter values are set when the PERIccss package is installed. The interworking with various SS7 ISUP variants and features at the customer site might require changes to the default ISUP parameter values to be sent to the network. In TMS Integrated Mode, the default ISUP parameter values can be overridden in the following two ways: 1. Server configuration in the $CCSSHOME/etc/ss7.conf file is for specification of default SS7 ISUP data parameters to be used in ISUP messages sent from the server to the network. The parameter values are specified by adding the following line in the ss7.conf file:
CONFIG CCME_DEFAULT=parameter_name, VALUE=value; For example: The Forward Call Indicator parameter in IAM messages has a default value of zero that specifies a national call. To have a default of International, the value must be set to one. The addition of the following line in the ss7.conf file changes the default to International:
CONFIG CCME_DEFAULT=FOCI_C_CALL_IND,VALUE=1;
Note: The default parameter value set in the ss7.conf file is the value that is sent on to the network unless it is overridden by the application on a per call basis. The default values are used every time the CCSS transmits the configured parameters. 2. To override the server configured parameter values, the application must specify the ISUP parameter values in the message folder. The application uses a Compute block (FILL_IAMX) after the SS7InitProto block that initializes default parameters for IAMX. The ISUP parameter values are overridden in the FILL_IAMX compute block. The application invokes the SS7SetProto block to send this new parameter value in GSS7.ISUP-Send-Buf. For example: If the application wants to override the initial default value FOCI-CALL-IND = 0 in the IAM message with FOCI-CALL-IND=1. This value indicates an international call to be sent on the network, the application sets the following value: GSS7.ISUP-Message-Out.IAMX.IAMX.IAM-FOCI.IAM-FOCI-CALL-IND = 2.
306 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Message Types
It is necessary to set FOCI-CALL-IND =2 for the network to receive FOCI_CALL- IND=1.
Note: As a general rule, one is added by the CCSS to the parameter value received from the network and passed on to the application. The application receives a parameter value that is equal to network parameter value plus one. Similarly, the application must set a parameter value to one more than the actual parameter value to be sent to the network. As stated in the preceding example, for the network to receive FOCI-CALL-IND =1, the application must set the following: GSS7.ISUP-Message-Out.IAMX.IAMX.IAM-FOCI.IAM-FOCI-CALL-IND =2. For more information on all the supported parameter values that can be set in the application, see Data Items on page 214. Any data item that is set to zero means that the network did not deliver that data to the server. If a data variable accepts characters, a blank string indicates that the message was not delivered. The application can set a data item to zeros or blanks and the information is not get transmitted to the network. The use of overriding parameter values through the application is an option available to the application programmer. Using overriding parameter values, the programmer has the flexibility to vary certain message items on a per call basis whenever variations from the default values are needed. Any calls made on the same line at a later time revert to the default values.
Message Types
The message type used for SS7 toolkit application folders is matched to support Proxy and TMS Integrated mode data item message types. For additional information, see Data Items on page 214.
Starting ISUP Applications
Use the SS7 Startup toolkit block before using any other toolkit block in an application. The Startup toolkit block is used to determine the mode of operation and the ISUP variant from the specified command line option. If nothing is specified on the command line, the default mode
Avaya CCSS 1000/2000 Feature Documentation August 2013 307 ISUP Programming in TMS Integrated Mode for MPS
of operation is Proxy and the default ISUP variant is ITU. An MPS Developer application can be started in the following ways from the command line: • vengine -vN -pN
Application Flow
Outbound ISUP Call
This section describes the procedure for an outgoing call in TMS Integrated mode.
308 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Call Origination
Figure 2: Sample Outbound TMS mode Application
Call Origination
An application can originate a call as follows: 1. A Handle block is used in the beginning of the outbound application to handle exceptions and error conditions. 2. The SS7Startup block is used determine the mode of operation (proxy./tms) and the ISUP protocol variant.
Avaya CCSS 1000/2000 Feature Documentation August 2013 309 ISUP Programming in TMS Integrated Mode for MPS
3. SS7InitProto block is used to initialize the IAMX parameters to default values. The SS7InitProto block indicates whether ISUP additional parameters are to be encoded in the message.
4. To override any default ISUP parameters, the application uses the Fill_IAMX compute block. Parameter values assigned here in the application overrides any server configured parameter value.
310 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Call Origination
The following graphic describes filling the ISUP parameter values in the Fill_IAMX compute block.
5. After the ISUP parameters for IAMX are filled, the application invokes SS7SetProto block to fill the GSS7.ISUP-Send-Buf character data card with the ISUP message (IAMX) to be sent to the CCSS.
6. The Originate block is used in the MPS Developer ISUP application to outdial a number and connect with the called party. The following steps are performed in the originate block. 1. Set the Call Type to Originate. 2. Use System.DefaultCID in the CID (Connection ID of the outdial line) field. 3. Fill the Dial Number. The Dial number in originate block is copied automatically from GSS7.dial-number. Alternatively, it can be set in the originate block by the user. In Originate Block, Send Protocol Data and Data Length fields are set to GSS7.ISUP-Send- Buf and GSS7.ISUP-Send-Buf-Length respectively to send the IAMX data the CCSS.
Avaya CCSS 1000/2000 Feature Documentation August 2013 311 ISUP Programming in TMS Integrated Mode for MPS
Originate Block
Sending UUI message
The following is the procedure for sending a UUI message. 1. The SS7InitProto block is used to initialize the UUIX parameters to default values. Set ISUP Msg To Initialize to UUIX. 2. Invoke SS7SetProto block to fill the GSS7.ISUP-Send-Buf character data card with the ISUP message (UUIX) to be sent to the CCSS.
3. Use the Call Control (protocol specific) block to send the message to the CCSS. • Set the Control Operation to Send Protocol Data. • Set Length to GSS7.ISUP-Send-Buf-Length.
Note: FACR, SUS and RES messages can also be sent in the same way as sending UUII messages.
312 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Releasing a Call
Releasing a Call
The following is the procedure for releasing a call. 1. The application invokes SS7InitProto block to initialize the RELX parameters to default values. The ISUP parameters for RELX can then be overridden using a Fill_RELX compute block. SS7SetProto block is then invoked to fill the GSS7.ISUP- Send-Buf character datacard with the ISUP message (RELX) to send to the CCSS.
2. The Disconnect block, shown in the following diagram, is used by the application to disconnect the call. The Send Protocol Data and Data Length fields in Disconnect block are set to GSS7.ISUP-Send-Buf and GSS7.ISUP-Send-Buf-Length respectively to send the RELX data to the CCSS. Set CID to System.DefaultCID.
Avaya CCSS 1000/2000 Feature Documentation August 2013 313 ISUP Programming in TMS Integrated Mode for MPS
Inbound ISUP Call
This section describes the procedure for an incoming call in TMS Integrated Mode.
Figure 3: Sample Inbound TMS mode Application
314 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Call Reception
Call Reception
The following steps identify how a call is received in TMS Integrated mode. 1. The Handle block is used in the beginning of the outbound application to handle exceptions and error conditions. 2. The SS7Startup block is used determine the mode of operation (proxy./tms) and the ISUP protocol variant.
3. The Answer block is used to determine how the incoming call is handled. The following are options available for handling a call: • Get Call action — causes the Answer block to wait until a call is presented. The IAM data received is also copied to an ISUP Receive Buffer. • Proceed Call action — follows a Get Call, and then the application puts the call into a state where it can read data about the call. The call is put into the proceeding state. • Alert Call action — then puts the call into a state where it can read data about the call but the caller continues to hear ringback. The application can then decide what to do with the call according to the data received. The call is put into the Alerting state. • Answer Call action — causes the Answer block to wait for the specified number of rings, and then connect the phone and speak the greeting phrases, if any, specified in the Prompt field. Application execution then immediately continues at the next block.
Avaya CCSS 1000/2000 Feature Documentation August 2013 315 ISUP Programming in TMS Integrated Mode for MPS
Figure 4: Answer Block
4. After the application invokes SS7GetProto block, the data received in the network message (such as IAM), present in GSS7.ISUP-Recv-Buf, is copied to the GSS7.ISUP-Message-In folder and can be accessed.
316 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Releasing a Call
Releasing a Call
The following steps identify how release a call in TMS Integrated mode. 1. To release a call, the application invokes SS7InitProto block to initialize the RELX parameters to default values. The ISUP parameters values for RELX can then be overridden using a Fill_RELX compute block. SS7SetProto block is subsequently invoked to fill the GSS7.ISUP-Send-Buf character data card with the ISUP message (RELX) to send to the CCSS.
Avaya CCSS 1000/2000 Feature Documentation August 2013 317 ISUP Programming in TMS Integrated Mode for MPS
2. The Disconnect block is used by the application to disconnect the call. Send Protocol Data and Data Length fields in Disconnect block are set to GSS7.ISUP- Send-Buf and GSS7.ISUP-Send-Buf-Length respectively to send the RELX data to the CCSS.
318 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Sample TMS Integrated mode applications
Sample TMS Integrated mode applications
The sample MPS Developer applications are available at the following path:
$CCSSHOME/samples/ppro/*. For TMS Integrated mode, the following sample MPS Developer application files are used: 1. mps.tms_ansi_inbound.ppr 2. mps.tms_ansi_outbound.ppr 3. mps.tms_Telcordia_inbound.ppr 4. mps.tms_Telcordia_outbound.ppr 5. mps.tms_itu_inbound.ppr 6. mps.tms_itu_outbound.ppr
Installation Procedure for SS7 Toolkit
Installation of MPS Developer is a prerequisite for the SS7 toolkit to work. The Toolkit must be in the PPROPATH to access the toolkit definitions and include folders. Assuming a c-shell environment and the SS7 toolkit to be installed in /opt/vps/PERItlkt/ss7, the following should be added to the .cshrc file: setenv PPROPATH ${MPSHOME}/PERIppro:/opt/vps/PERItlkt/ss7
Avaya CCSS 1000/2000 Feature Documentation August 2013 319 ISUP Programming in TMS Integrated Mode for MPS
Performing Referral in TMS mode
In TMS mode, referral is performed using the Bridge block in the MPS Developer application for MPS. The Bridge block can bridge two calls or unbridge a previously created bridge. This is typically used to connect a caller to an outside party. The Bridge block specifies the CID of the first (master) and the second (slave) line. The operation in the Bridge block is specified as Bridge.
Figure 5: Referral using Bridge Block
320 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Performing Referral in TMS mode
Figure 6: CallFlow for Referral in TMS mode
The Originate block makes the second (slave) line available before performing a bridge by specifying the CID of the second (referral) line. The originate block also specifies the outdial number for referral.
Avaya CCSS 1000/2000 Feature Documentation August 2013 321 ISUP Programming in TMS Integrated Mode for MPS
The Line Operation block provides access to the resource pool to get an outbound line for referral. The pool specified in the Line operation block is the same as in the pmgr.cfg file of the MPS system.
322 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Performing Referral in TMS mode
Figure 7: Line Operations Block
The Bridge block is used to unbridge the call before the application issues a disconnect to both the lines such as the master and the slave line. The operation in the Bridge block is specified as Unbridge. The break type sets the type of unbridge used for the unbridge operation. For example: destroy in the break type field means break the bridge in both directions and destroy it. It is used only if the bridge is never used again.
Avaya CCSS 1000/2000 Feature Documentation August 2013 323 ISUP Programming in TMS Integrated Mode for MPS
Figure 8: Unbridging the call using the Bridge block
If the application receives a disconnect, it unbridges the calls using the Bridge block.
Sample Referral Application for TMS mode
The sample MPS Developer applications are available at the following path:
$CCSSHOME/samples/ppro/. mps.tms_referral.ppr is a sample referral application for TMS mode is part of the ccss6.3 software.
CCSS Configuration for TMS integrated Mode
See TMS Integrated Mode Configuration on page 94.
324 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Configurable Default ISUP Parameter Values
Configurable Default ISUP Parameter Values
The following table lists the configurable default values used in the CCSS version. If a user wants to override any of these values they can do so by either setting the new value from the application or in the ss7.conf file.
Note: The default ISUP parameter values are the values which will be sent to the network. If we need to send any Parameter values other than the default value in the ISUP message then we have to set this value in ss7.conf file or set the parameter field in the application. For example: The Forward Call Indicator parameter in IAM messages has a default value of 0 that specifies a National Call. To have a default of International then the value needs to be set to 1. To set a new value to any of the parameters using the ss7.conf file, an entry must be added for each parameter which is to be overridden. The syntax for adding an entry is as follows:
CONFIG CCME_DEFAULT=parameter_name, VALUE=
CONFIG CCME_DEFAULT=NTCI_SATELLITE_IND, VALUE=1;
Parameter (default) Parameter (default)
BACI_CDP_CAT_IND (0) GNUM_NII_IND (0) BACI_CDP_STAT_IND (0) GNUM_NOA_IND (1) BACI_CHARGE_IND (0) GNUM_NUM_QUAL_IND (1) BACI_ECHO_CONTROL_IND (0) GNUM_NUMBER_PLAN (1) BACI_EE_INFO_IND (0) GNUM_PRESENT_RESTRICT_IND (0) BACI_EE_METHOD_IND (0) GNUM_SCREEN_IND (0) BACI_HOLD_IND (0) LNUM_NII_IND (0) BACI_INTERNETWORK_IND (0) LNUM_NOA_IND (1) BACI_ISDN_ACCESS_IND (0) LNUM_NUMBER_PLAN (1) BACI_ISUP_IND (0) LNUM_PRESENT_RESTRICT_IND (0) BACI_SCCP_METHOD_IND (0) LNUM_SCREEN_IND (0) CAID_NETWORK_ID_PLAN (0) NTCI_CONTINUITY_CHECK_IND (0) CAID_NETWORK_ID_TYPE (0) NTCI_ECHO_CONTROL_IND (0) CAU_CAUSE_VAL (16) NTCI_SATELLITE_IND (0) CAU_CODING_STANDARD (0) OBI_FORWARD_IND (0) CAU_EXT_IND1 (0) OBI_INBAND_IND (0) CAU_EXT_IND1A (0) OCDN_ADDRESS_PRESENT_RESTRICT_IND CAU_EXT_IND2 (2) (0) CAU_LOCATION (0) OCDN_NOA_IND (0) CAU_RECOMMENDATION (0) OCDN_NUMBER_PLAN (0) CDPN_INN_IND (0) OFCI_CLI_REQ_IND (0) CDPN_NOA_IND (1) OFCI_CUG_IND (0)
Avaya CCSS 1000/2000 Feature Documentation August 2013 325 ISUP Programming in TMS Integrated Mode for MPS
Parameter (default) Parameter (default) CDPN_NUMBER_PLAN (1) OFCI_SEG_IND (0) CGPC_CGPC (10) OLI_LINEINFO (0) CGPN_ADD_PRESENT_RESTRICT_IND (0) RDTG_ADDRESS_PRESENT_RESTRICT_IND CGPN_CGP_NI_IND (0) (0) CGPN_NOA_IND (1) RDTG_NOA_IND (0) CGPN_NUMBER_PLAN (1) RDTG_NUMBER_PLAN (0) CGPN_SCREEN_IND (1) REDI_REDIRECT_IND (3) CHNM_NOA_IND (0) REDI_REDIRECT_REASON (0) CHNM_NUMBER_PLAN (0) REDI_REDIRECTION_COUNTER (4) CONN_ADD_PRSNT_RESTRICT_IND (0) REDI_REDIRECTION_REASON (0) CONN_NOA_IND (0) USI_CFG (0) CONN_NUMBER_PLAN (0) USI_CODE_STD (0) CONN_SCREEN_IND (0) USI_ESTABLISH (0) EVI_EVENT_PRESENT_RESTRICT_IND (0) USI_INFO_DTO_TRANS_RATE (16) EVI_EVI_IND (0) USI_INFO_TRANS_CAP (16) FOCI_CALL_IND (0) USI_INFO_TRANS_RATE (16) FOCI_EE_INFO_IND (0) USI_L1_IDENT (1) FOCI_EE_METHOD_IND (0) USI_L1_USR_INFO (11) FOCI_INTERNETWORK_IND (0) USI_L2_IDENT (2) FOCI_ISDN_ACCESS_IND (1) USI_L2_USR_INFO (2) FOCI_ISUP_IND (1) USI_L3_IDENT (3) FOCI_ISUP_PREFER_IND (0) USI_L3_USR_INFO (6) FOCI_SCCP_METHOD_IND (0) USI_STRUCT (0) FOCI_SPARE (0) USI_SYMMETRY (0) USI_TRANS_MODE (0) XMR_REQUIREMENT (0)
326 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Chapter 8: ISUP Programming in LineID Mode
This chapter covers: 1. Introduction to LineID Mode 2. Application Programming in LineID Mode 3. Application Flow 4. Data Items
ISUP Application Programming in LineID Mode (MPS Mode)
This chapter describes ISUP Application Programming in LineID Mode. LineID mode incorporates the ability to define a mapping between Line Identifiers (LineIDs) and ISUP Circuit Identification Codes (CICs) for voice channels. Mapping LineIDs to CICs extends the capability of ISUP condition applications using the MPS Developer toolkit to signal on behalf of multiple CICs by using the MPS LineID that is associated with those CICs. The ISUP condition applications can use the Line Operations block (Line OPS) to signal on behalf of multiple CICs by using the MPS LineID that is associated with the CICs. Using this capability for ISUP condition applications overrides the static binding of a single CIC to each application that existed in previous releases for PROXY mode application programming. In LineID mode, if the CallProtectStart flag is checked, the application can start in Call Protect mode and Line OPS can be used to acquire lines from a pool of lines on an MPS system. If the CallProtectStart flag is not checked, the application can start in normal mode. LineID (MPS) mode uses the ccs7cc conditions and the proxy resource to set up phone calls. The SS7 protocol data can be manipulated using the SS7 data folders and can be transmitted between the applications and the CCSS server using the CCSS resource proxy. LineID mode uses the MPS Developer toolkit operations to bridge lines and speak to callers. Dynamic provisioning of extended mode can be done by dynamic provisioning of extended mode in PROXY mode also. See Dynamic Provisioning of Extended Mode in PROXY Mode on page 301.
Avaya CCSS 1000/2000 Feature Documentation August 2013 327 ISUP Programming in LineID Mode
For additional information on Call Protect configuration in an N+1 AP cluster, refer to the MPS System Reference Manual.
MPSMODE Parameters
In addition to the isup and cond_msg tokens, the Resource allocation step requires an additional parameter called mpsmode in the mode field. The following is a typical mode string parameter for ISUP applications.
isup, cond_msg, mpsmode The application must get and free the CCSS resource only once for each run, regardless of the number of calls it handles.
Bind and Unbind
The CCSS server uses the Line ID to identify an SS7 circuit before initiating or accepting an SS7 call. Applications call the external function start-info to get the Default CID and Line ID for binding or use the MPS Developer LineOPS (Line Operation) block to acquire a line to retrieve the LineID. When the call is complete, the application must use another SEND RESOURCE command to the CCSS to unbind itself from the SS7 circuit. Bind and Unbind are similar to the Get and Free CCSS resource steps used in applications that are not written for LineID/MPS mode. The resource allocation and deallocation steps must be performed to inform the CCSS server that the application can run in LineID mode. The Bind and Unbind steps are used exactly as the Get and Free steps in non-MPS (LineID) applications to enable the application to send and receive SS7 messages that are related to a particular voice circuit. The application must Bind and Unbind each LineID that is acquired from the MPS each time it handles a new call on that LineID. An application that handles multiple calls must be written to handle ccs7cc conditions simultaneously for as many calls as it is handling and should not recycle or free the CCSS resource until all calls in progress are torn down and all LineIDs are unbound.
328 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Acquiring the CCSS Resource in LineID Mode
Acquiring the CCSS Resource in LineID Mode
To acquire the CCSS resource, MPS 3.0 CCSS applications must execute a RESOURCE block with the following parameters. • Resource: ccss • Mode: isup,cond_msg,mpsmode
Folder Structure
Following the message type, there is a 24-character LineID field.
Send Resource
SEND RESOURCE operations to the CCSS server return success and failure through the output complete (oc) and output failure (of) conditions like other CCSS or MPS applications. In the new CCSS release with MPS, these conditions carry the LineID contained in the SEND RESOURCE request also so the condition can be associated with the request operation.
Message Types
The message type values used by LineID mode applications to identify ISUP messages in SS7 data folders are different from the message type values by proxy mode applications. See the Data Items on page 335 section below for message types used in LineID mode.
Avaya CCSS 1000/2000 Feature Documentation August 2013 329 ISUP Programming in LineID Mode
Application Flow
Get CCSS Resource
To acquire a CCSS resource, the Resource block should be used with the following parameters: • isup • cond_msg • mpsmode Get CCSS Resource once per execution.
330 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Check Call Protect
Check Call Protect
Applications should check for the CallProtectStart data card. If the data card is true, the application should proceed with the DoCP container block, else normal call flow will be carried out.
Avaya CCSS 1000/2000 Feature Documentation August 2013 331 ISUP Programming in LineID Mode
Binding the LineID
Applications should bind the LineID obtained by calling the external function start-info. Bind the LineID by using the Resource block as shown in the following diagram.
Call Protect Outbound
Applications use the external function start-info to get the information about the failed call. The CPStartInfo application folder is updated by the start-info call function. The following diagram
332 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Call Protect Outbound
is an example of the Do CallProtect (DoCP) container block that is part of outbound application flow.
Applications should rebind the LineID with the updated LineID that is available in CPStartInfo on Primary MPS fail over or failback. The state of the call should then be checked and the flow continues from that state.
If the call state is connected, the applications should proceed with normal call flow after the call setup is done.
Avaya CCSS 1000/2000 Feature Documentation August 2013 333 ISUP Programming in LineID Mode
Call Protect Inbound
Applications use the external function start-info to get the information about the failed call. The CPStartInfo application folder is updated by the start-info call function. The following diagram is an example of a DoCP (Do CallProtect) container block. On Primary AP failover or Secondary failback, the CallProtectStart flag is set to 1 and the DoCP container block is executed.
If the state of the call is in the connected state, the LineID obtained from start-info should be rebinded and normal call flow should be continued.
Releasing the Call
Once the normal call flow is completed, the applications should unbind the LineID using the Resource block as shown in the following diagram.
334 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Data Items
The CCSS resource should also be released after unbinding the LineID.
Data Items
The data items for the messages and message types used for Line ID applications is similar to Proxy mode applications. The following table lists the new message types used in LineID Mode, as well as the Proxy Mode message types that they replace.
SS7 Message LineID Mode Message Proxy Mode Message Type Type IAM 81 = IAM_CN 1 = IAM IAM2 82 = IAM2_CN 29 = IAM2 IAM4 105 = IAM4_CN 47 = IAM4 IAM6 110 = IAM5_CN 52 = IAM6 IAM7 112 = IAM7_CN 122 = IAM7 REL 83 = REL_CN 11 = REL REL2 84 = REL2_CN 30 = REL2 REL3 85 = REL3_CN 37 = REL3 REL4 86 = REL4_CN 40 = REL4 REL5 115 = REL5_CN 125 = REL5 ANM 87 = ANM_CN 3 = ANM ANM2 88 = ANM2_CN 31 = ANM2 ANM3 89 = ANM3_CN 36 = ANM3 DRS 90 = DRS_CN 13 = DRS
Avaya CCSS 1000/2000 Feature Documentation August 2013 335 ISUP Programming in LineID Mode
SS7 Message LineID Mode Message Proxy Mode Message Type Type CPG 91 = CPG_CN 4 = CPG CPG2 92 = CPG2_CN 32 = CPG2 CPG4 104 = CPG4_CN 46=CPG4 CPG5 113 = CPG5_CN 123 = CPG5 CON 93 = CON_CN 7 = CON CON2 94 = CON2_CN 33 = CON2 SAM 95 = SAM_CN 27 = SAM SUS 96 = SUS_CN 14 = SUS RES 97 = RES_CN 15 = RES COT 98 = COT_CN 8 = COT CCR 99 = CCR_CN 38 = CCR ACM 100 = ACM_CN 2 = ACM ACM2 101 = ACM2_CN 34 = ACM2 ACM5 109 = ACM5_CN 51 = ACM5 ACM6 114 = ACM6_CN 124 = ACM6 UUI 111 = UUI_CN 53 = UUI RLC 102 = RLC_CN 12 = RLC RSC 103 = RSC_CN 18 = RSC BIND 28 = BIND_CN Not used UNBIND 43 = UNBIND_CN Not used REBIND 44 = REBIND_CN Not used
336 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Chapter 9: TCAP Application Programming
This chapter covers: 1. System Overview and Architecture 2. SCCP Functionality 3. TCAP Functionality 4. TCAP Folders
System Overview and Architecture
The CCSS TCAP programming API described in this chapter enables the deployment of data transaction services by supporting non circuit related information exchange between signaling points using the Signaling Connection Control Part (SCCP) connectionless service.
Avaya CCSS 1000/2000 Feature Documentation August 2013 337 TCAP Application Programming
SCCP
Functionality
The Signaling Connection Control Part (SCCP) provides additional functions to the Message Transfer Part (MTP) to cater for both connectionless, as well as connection-oriented network services to transfer circuit related and non-circuit related signaling information using a
338 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Routing and Addressing
Signaling System No. 7 (SS7) network. The combination of the MTP and the SCCP is called Network Service Part (NSP). The overall objectives of the SCCP are to provide the means for: Example • Logical signaling connections within the SS7 network • A transfer capability for network service data units with or without the use of logical signaling connections The protocol used by the SCCP to provide network services is subdivided into four protocol classes defined as follows: Example • Class 0: Basic Connectionless class • Class 1: Sequenced Connectionless class • Class 2: Basic connection-oriented class • Class 3: Flow control connection-oriented class
Note: CCSS implementation of Transaction Capability Application Part (TCAP), as the service user of SCCP, uses the protocol class 1 of SCCP connectionless services to facilitate the operation of dialogues and remote nodes. The in-sequence delivery of connectionless class with guaranteed in-sequence delivery of SCCP-SDUs.
Routing and Addressing
The SCCP routing provides a powerful addressing information translation function on behalf of its users. This function makes it unnecessary for SCCP users to store knowledge of SCCP signaling routing information. To reach the goal, the SCCP parameters "called address/calling address" are used to convey addresses identifying the destination/source of a communication. The addressing capabilities of SCCP extend those found in Message Transfer Part (MTP), which is limited to delivering a message to a specified node and using a four-bit service indicator to distribute messages within a node. SCCP supplements this capability by providing its own Calling and Called Party addresses. Both Calling and Called Party addresses include an address indicator that describes the type of address information contained in the address field. The address consists of one or any combination of the following elements: • Signaling Point Code • Subsystem Number • Global Title
Avaya CCSS 1000/2000 Feature Documentation August 2013 339 TCAP Application Programming
Information about TCAP/SCCP configurations are explained in detail in the section SCCP/ TCAP Configuration on page 103.
TCAP
Functionality
TCAP uses the connectionless services of SCCP to facilitate the operation of dialogues with remote nodes for the facilitation of complex operations and information retrieval. The basic elements of communication between two TCAP users are known as components. A component has an ID associated with it and may be in the form of either an operation or a reply. Several components may be sent in the same message and will arrive in the same order as they were sent. The exchange of components between two TCAP users to perform an application constitutes a dialogue. Several dialogues may take place concurrently. There are two possible types of dialogue, structured and unstructured. Unstructured dialogue This type of dialogue consists of unidirectional messages sent between peers. Structured dialogue This involves the formation of an association between the peer layers and the message types sent between the layers may indicate dialogue begin, dialogue continue and dialogue end. Several dialogues may take place simultaneously each of which must have an associated dialogue ID. The components may either invoke operations or convey the results of operations. Each invoking component has an invoke ID and the same ID value is returned in the return value component. There are four possible classes of operation in TCAP: • Class 1: Both success and failure are reported. • Class 2: Only failure is reported. • Class 3: Only success is reported. • Class 4: Neither success nor failure is reported. Replies to operations may be segmented. Components may be rejected. Invoked operations may be cancelled. The TCAP user will be informed of malformed or unexpected components. The TCAP user will also be informed if the time period allowed for receiving a result to a Class 1-3 operation expires.
340 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] TCAP USER
In the case of an unstructured dialogue many unidirectional messages may be sent in the same transaction under the same dialogue ID without having any transaction ID. The TR-UNI primitive in the transaction layer is used to send these components. Within a transaction two TR-users may perform operations for transaction begin, continue, which allows full duplex exchange of messages between TR-users and transaction end. Transaction end may be one of the following types: Example: • Prearranged end: Each TR-USER has a convention to end the transaction independently. • Basic end: Terminating TR_USER informs peer. • Basic end: Terminating TR_USER informs peer. • Transaction abort: Transaction aborted, messages discarded and reason for abort sent to peer.
Messages between users may contain one or more components.
Note: When the component sub-layer is the TR-user there is a one to one mapping between transactions and dialogues. This will always be the case in the context of this system.
TCAP USER
Dialog Management
One of the major functions of the tcuser software will be to manage the various dialog ID numbers which are required. The following dialog ID numbers are required • Application dialog ID The application specifies a dialog number in all transaction and component messages which it transmits and receives with the TC User. The application dialog ID is intended to be a simple integer identification which ties the messages within a dialog together. When initiating dialogs the application may specify any integer which it chooses. When a network initiated dialog is received, the application will receive a dialog number, which is 0. • TC User dialog ID - sudlgid
Avaya CCSS 1000/2000 Feature Documentation August 2013 341 TCAP Application Programming
The TC User software will maintain a sudlgid (Service User dialog id) for all dialogs which it manipulates. • TCAP layer dialog ID - spdlgid The TCAP layer will allocate its spgldid (Service Provider dialog id) for all transactions. For outbound transactions the spdlgid will be delivered in a backwards component confirmation (CmpCfm). For all inbound dialogs the spdlgid will be received with the BEGIN.
Resource Operations
CCSS TCAP applications, running in an SS7 environment, are allowed access to network signaling messages. The signaling messages are passed from the CCSS server to the application server. The application server (MPS) views the signaling server as a shared resource. An application can obtain the resource when it is ready to handle a transaction, process the transaction information, and free the resource when the transaction is completed.
Application Setup - Resource Allocation
To start the application, allocate the TCAP resource using an ISSUE GET tcap. A set of parameters should be specified in the mode folder getting tcap resource. An application can register itself for inbound or outbound mode. For more information about the Mode folder, see Mode Folder on page 351. For an outbound type application, the destination field is used to specify the far-end subsystem name, configured in the SCCP_NETWORK or the global title translation node (if global title is to be used in the called party address), configured in SCCP_GTTNODE. In addition, the application context name and/or user data can optionally also be specified in the mode folder, which will be built in the dialogue portion of a TCAP package. For an inbound type application, the origination field may use the local subsystem name specified in SCCP_LOCAL_SS if the application is to use point code and subsystem number as its calling party address. An application can also use a global title address as its calling party address configured in SCCP_LOCAL_GT. Optionally, the application can specify the application context name it is expecting. This application context name should be specified in the ACN_GRP configuration, which defines the rules for TCU handling the inbound transaction requests. TCU maintains pools for each application group defined in ACP_GRP and a default pool for an application registering itself without application context name specified. For more information on ACN_GRP configuration in CCSS, see CONFIG SCCP_NETWORK on page 46.
342 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Application Termination- Resource Deallocation
Application Termination- Resource Deallocation
After the dialogue is completed, the application should issue a FREE to free the tcap resources.
Sending TCAP Messages
Sending TCAP messages to CCSS can be done through the Resource Block SEND operation. The parameters for this are: • Resource name: tcap • From: TCAP folder • Length: TCAP folder length • Exceptions: TRUE
Note: The folder version should remain consistent throughout the dialogue. A TCAP message is composed at the TCAP interface. The application can send none, single or multiple component type messages queued at the TCAP component sub-layer and a transaction type message that would flush all queued component messages, sending them out on the wire.
Avaya CCSS 1000/2000 Feature Documentation August 2013 343 TCAP Application Programming
Receiving TCAP Messages
TCAP messages can be received from condition data under condition tcapcc. A TCAP message is decomposed at the TCAP interface. A received TCAP message is divided into several pieces at the TCAP interface before sending to the application. At least one transaction type message and none, single or multiple component type messages are delivered to the application sequentially.
344 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Message Flow Diagrams
Message Flow Diagrams
ISSUE GET Succeeds
If the SSN and application context are found to be acceptable then the server will accept the ISSUE GET. The SSN specified by the application must be configured and ready in order for success to be indicated.
Avaya CCSS 1000/2000 Feature Documentation August 2013 345 TCAP Application Programming
ISSUE GET Fails
If the TC User cannot accept the applications request for service it will reply with condition REGFAIL. The condition data will show the reason for failure. The following reasons are expected: • Local Subsystem Out of Service • Remote Subsystem Out of Service • SCCP Congested • SCCP Unavailable • Invalid Origination Name • Invalid Destination Name • Previous dialogue not cleared • Invalid application state • Invalid Inbound ACN • Invalid user buffer
346 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Dialog Initiated By The Application
Dialog Initiated By The Application
The message flow is intended to show the normal sequence of messages for a dialog which is initiated by an application. In ISSUE GET, Mode = Outbound
Avaya CCSS 1000/2000 Feature Documentation August 2013 347 TCAP Application Programming
Dialog Initiated By The Network
Some protocols may require a dialog to be initiated from the network onto our system. The MPS Developer applications will need to respond to the following message sequence. In ISSUE GET, Mode = Inbound
348 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Application Free During Dialog
Application Free During Dialog
In the event that an application performs an ISSUE FREE in the middle of a dialog, the TC User software must terminate any dialogs which are in progress. Each dialog which is in progress will be
Avaya CCSS 1000/2000 Feature Documentation August 2013 349 TCAP Application Programming
Proxy/TCAP Resource
The TCAP user software will interface to the MPS Developer applications using the tcapproxy resource. The tcapproxy executable allows external resources to interface into the vengine/MPS Developer environment. (Support for multiple redundant LANS is not yet supported). The tcapproxy will be used to provide access to a resource named TCAP. In addition the TCAP User software in communicate with the application using a condition named TCAPCC.
MPS Developer Interface
MPS Developer applications will have control over the data which will be transmitted in the SS7 network. To fit with the TCAP interface, the application will be able to specify both component oriented data as well as transaction oriented data.
350 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Issue Get
Issue Get
The ISSUE GET which is performed by the application needs to inform the TCU of several pieces of information. These include the following Example • The Local Sub-system Name this application is associated with • The Destination SSN • The Application Context to which the application is binding • The Inbound/Outbound mode. • User Data/Len The Application context will be used by the TCU software to route dialogs to the application correctly. It will also allow the system to pass multiple application contexts across a single SSN.
TCAP Folders
Mode Folder
Item ITU ITU ITU ITU ANSI ANSI ANSI Size MPS V1 V2 V3 V4 V2 V3 V4 (bytes Developer ) Data Type Version X X X X X X 3 number Origination X X X X X X X 16 characters Destination X X X X X X 16 characters Inbound/Outbound X X X X X X 1 number Mode Application Context X X X X X X X 160 characters user buffer length X X X X X X 5 number user buffer X X X X X X 128 characters
Avaya CCSS 1000/2000 Feature Documentation August 2013 351 TCAP Application Programming
• Version: Folder version - This field is used to determine the folder version used for TCAP including transaction folder and component folder. If this field does not exist, version 1 is assumed. - Version 0 and 1 are identical and reserved for ITU only. It assumes the outbound transaction. - Version 2, version 3 and version 4 are available for ITU and ANSI. - Global title is not supported in the version 1 folder. • Origination: The organization name associated with the local sub-system. The origination name should be configured in ss7.conf/SCCP_LOCAL_SS or SCCP_LOCAL_GT if using global title address as the sending address. • Destination- Specifies the peer entity the application intended to communicate with. The destination is supported in version 2, version 3 and version 4 folders. If using version 2 or version 3 or version 4 folder, the destination is Out Of Service, GET FAIL will be received with condition data SSN out of service. - The destination name should match SCCP_NETWORK as configured in ss7.conf, if the routing is based on SSN. - For global title transmission, specify GTTNODE name as in ss7.conf. • Inbound/Outbound Mode - 0 = outbound - 1 = inbound • Application Context: The application context string is in the ASCII string format. For an inbound mode application, the application context name specified here should match the ACN_GRP configuration in the ss7.conf file. For an outbound mode application, this application context name will be built into the dialogue portion in the BEGIN package • User Buffer Length: Specifies the length of the User Data • User buffer is used to specify user specific information registering to an application context group. User buffer length and data are used to provide additional user information for an inbound application pool registration. This is currently used by "Internal IP" application context group, which uses this field to specify the 18 digits correlation ID.
352 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Transaction/Component Message Header
Transaction/Component Message Header
Item ITU ITU ITU ITU ANSI ANSI ANSI Size MPS V1 V2 V3 V4 V2 V3 V4 (bytes Developer ) Data Type Version X X X X X X X 3 number Dialog ID X X X X X X X 3 number Message Type X X X X X X X 3 number
• Version: specified in the Mode Folder • Dialog ID: allows the application to specify multiple dialog numbers. This is a simple integer, which identifies one of multiple concurrent dialogs in progress. The current implementation only allows one dialog per application. The application values are ranged from 0 to 255. • Message Type: specifies the message primitive IDs. The message primitive IDs are defined in the following table
ID ITU ANSI Description 0 Notice Indication Notice Indication Abnormal situation detected indicator. Application should abort and free TCAP resource. 1 TC_INVOKE Invocation of an ITU operation, which may be linked to another operation 2 TC_RESULT-L Only result, or last part, of a segmented result of a successfully executed ITU operation 3 TC_RESULT-NL Non-final part of the segmented result of a successfully executed ITU operation 4 TC_ERROR Reply to a previously invoked operation, indicating that the ITU operation execution failed 5 TC_L_REJECT Informs the local TC-User that a component sub-layer detected invalid ITU component was received
Avaya CCSS 1000/2000 Feature Documentation August 2013 353 TCAP Application Programming
ID ITU ANSI Description 6 TC_R_REJECT Informs the local TC-User that an ITU component was rejected by the peer 7 TC_CANCEL Informs the local TC-User that an ITU operation invocation is terminated due to a time out condition 8 TC_UNI Unstructured Dialog 9 TC_BEGIN Begin a Dialog 10 TC_CONTINUE Continue the exchange of messages in a Dialog 11 TC_END End the Dialog 12 TC_ABORT Abort the Dialog 13 Reserved 14 Reserved 15 Reserved 16 Reserved 17 TC_ANSI_INVOKE_L The only, or the last, part of the segmented invocation of an ANSI operation, which may be linked to another operation invocation 18 TC_ANSI_INVOKE_N The non-final part of the L segmented invocation of an ANSI operation, which may be linked to another operation invocation 19 TC_ANSI_RESULT-L The only result, or the last part, of the segmented result of a successfully executed ANSI operation 20 TC_ANSI_RESULT- The non-final part of the NL segmented result of a successfully executed ANSI operation 21 TC_ANSI_ERROR Reply to a previously invoked operation, indicating that the ANSI operation execution failed 22 TC_ANSI_L_REJECT Informs the local TC-User that a component sub-layer detected invalid ANSI component was received
354 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Transaction Type Message Folder
ID ITU ANSI Description 23 TC_ANSI_R_REJECT Informs the local TC-User that an ANSI component was rejected by the peer 24 TC_ANSI_CANCEL Informs the local TC-User that an ANSI operation invocation is terminated due to a time out condition 25 TC_ANSI_UNI Unstructured Dialog 26 TC_ANSI_QWP Query With Permission message 27 TC_ANSI_QWOP Query Without Permission message 28 TC_ANSI_RESPONS ANSI Response E 29 TC_ANSI_CWP Conversation With Permission 30 TC_ANSI_CWOP Conversation Without Permission 31 TC_ANSI_ABORT Abort Dialog
Transaction Type Message Folder
Item ITU ITU ITU ITU ANSI ANSI ANSI Size MPS V1 V2 V3 V4 V2 V3 V4 (bytes Developer ) Data Type Header X X X X X X X 9 folder Address Option X X X X X X 1 number Routing Indicator X X X X 1 number SCCP Network X X X X 20 characters Name DPC X X X X 8 number Destination X X X X X X X 16 characters End X X X X X X X 1 number Components X X X X X X X 1 number Present GT Format X X X X X X 1 number Translation Type X X X X X X 3 number
Avaya CCSS 1000/2000 Feature Documentation August 2013 355 TCAP Application Programming
Item ITU ITU ITU ITU ANSI ANSI ANSI Size MPS V1 V2 V3 V4 V2 V3 V4 (bytes Developer ) Data Type Nature X X X X X X 3 number Plan X X X X X X 2 number Encoding Scheme X X X X X X 1 number Address X X X X X X 64 number UserBuffer Length X X X X X X 5 number UserBuffer X X X X X X 128 characters
• Header - Header folder defined in the following tables • Address Option - Version 2, version 3 and version 4 folders provide an option to determine the inclusion of Point Code in the Called/Calling address - Allowable values are: • 0 - Both SCCP Called/Calling party address INCLUDE Point Code • 1 - Only SCCP calling party address INCLUDE Point Code • 2 - Only SCCP Called party address INCLUDE Point Code • 3 - Both SCCP Called/Calling party address EXCLUDE Point Code • Routing Indicator - Version 3 and version 4 folder provides the routing indicator of the calling party address - 0- routing based on GT - 1- routing based on DPC+SSN - This field is updated only when the Inbound Begin message is received • SCCP network name - Version 3 and version 4 folder provides the SCCP network name associated with the calling party address when routing is based on DPC+SSN - This field is updated only when the Inbound Begin message is received • DPC - In case the routing is based on GT, version 3 and version 4 folder provides the PC of the calling party address
356 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Transaction Type Message Folder
- In case of routing based on SSN, version 3 and version 4 folder provides the PC of the calling party address, provided the SCCP network name is not associated with the SS7 node - This field is updated only when the Inbound Begin message is received • Destination - Version 1 routing based on DPC+SSN: Specify destination name configured in ss7.conf SCCP_NETWORK - Version 2, version 3 and version 4 routing based on DPC+SSN is specified in Mode Folder - Version 2, version 3 and version 4 routing based on Global Title transmission: Specify GTTNODE name in ss7.conf • End - This flag decides the mode (pre-arranged or basic) of dialogue termination • If flag is set to 1, then the pre-arranged mode of dialogue termination is assumed. The dialogue is locally terminated, and no END or RESPONSE message is sent; the pending components for this dialogue are discarded in this case. • If flag is set to 0, then the basic mode of dialogue termination is assumed. The dialogue is locally terminated and an END or RESPONSE message is sent with the pending components for this dialogue. - This flag is significant only when the message type is set to TC_END for ITU or TC_ANSI_RESPONSE for ANSI • Component Present - An indication of component type message to follow this primitive • If this flag is set to 1, it signifies the presence of the component portion in the received message; the application should expect component type message to follow this primitive • If this flag is set to 0, then a component was not present in the received message; the application should not expect any component type message to follow this primitive • GTformat - Global Title format - The format is encoded in the global title indicator (within the address indicator octet of the address parameter) in an SCCP message - ITU allowed values are • 0: No Global Title • 1: Nature of address + Odd/Event indicator (generated automatically) • 2: Translation Type
Avaya CCSS 1000/2000 Feature Documentation August 2013 357 TCAP Application Programming
• 3: Translation Type + Numbering Plan + Encoding Scheme (generated automatically) • 4: Translation Type + Numbering Plan + Encoding Scheme (generated automatically) + Nature of address The applicability of each item in each format (for ITU)
Data Item Size and Format Description Format 1 2 3 4 GT_Format 1 char. X X X X Global Title Format: For ANSI, only numeric format 2 and 3 are supported Translation 3 char. X X X Used to specify the Transaction Type numeric type octet within GT type =2 Nature of 3 char. X X Used to specify the 7 bits for the Address numeric Nature of Address Indicators. This Indicator field is used for format 1 GT Numbering 2 char. X X Used to code the 4 bits of the Plan numeric Number plan. This field is used for GT types 3 and 4. Encoding 1 char. X X Used to specify the 4 bits for the Scheme numeric encoding scheme. Used for GT types 3 and 4. Global Title 64 char. X X X X Contains the address data in ASCII. Address alpha- The length of the data will be numeric determined by searching for the first blank. Used for all GT types.
• ANSI allowed values are: - 0: No Global Title - 1: Translation Type + Numbering Plan + Encoding Scheme (generated automatically) - 2: Translation Type
Data Item Size and Format Description Format 1 2 3 4 GT_Format 1 char. X X Global Title Format numeric Translation 3 char. X X Used to specify the Transaction Type numeric type octet. Nature of 3 char. ITU only Address numeric Indicator
358 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Transaction Type Message Folder
Data Item Size and Format Description Format 1 2 3 4 Numbering 2 char. X Used to code the 4 bits of the Plan numeric Number plan. This field is used for GT type 1 Encoding 1 char. X Used to specify the 4 bits for the Scheme numeric encoding scheme. Used for GT type 1 Global Title 64 char. X X Contains the address data in ASCII. Address alpha- The length of the data will be numeric determined by searching for the first blank. Used for all GT types.
• Translation Type The translation type is used to direct the message to the appropriate global title translation function. A translation type may for instance imply a specific service to be provided by the SCCP user, such as 800 number translation. It may also identify the category of service to be provided. For example, dialed number screening, password validation or translation of digits to telephone network address. - Used to encode the 8-bit translation type field in the address parameter of an SCCP message • Nature The Nature of Address Indicator (NAI) identifies the scope (a network, geographical region or other) in which a number is valid (such as the local area, country). This allows shortening the number (and hence the translation process) to the digits that are actually relevant in that particular scope. The different scopes are defined together with a numbering plan. SCCP provides only a coding for the different scopes necessary for SCCP message routing purposes. - Used to encode the 7-bit Nature of Address Indicator (NAI) bit in the address parameter of an SCCP message. • 1: Subscriber number • 3: National Significant Number • 4: International Number • Encoding Scheme (ES) - Used to encode the encoding scheme in the address parameter of an SCCP message. • 0: ES_Unknown • 1: BCD Odd/Even • Plan The Numbering Plan (NP) represents a numbering scheme for users of telecommunications services in different telecommunication networks. For example, E.164 for ISDN allocates numbers for telephony subscribers, E.212 for mobile, and so
Avaya CCSS 1000/2000 Feature Documentation August 2013 359 TCAP Application Programming
on. One specific numbering plan ("generic numbering plan") is defined by SCCP to allow nodes or SCCP subsystems in the SS7 network to be numbered unambiguously. - Used to encode the plan nibble in the address parameter of an SCCP message • 0: Unknown • 1: ISDN • 2: Telephony • 3: Data • 4: Telex • 5: Maritime Mobile • 6: Land Mobile • 7: ISDN Mobile • Address - Specify the ASCII string of the Global Title Address to be sent. TCU is responsible for encoding the address into BCD format. • User Buffer Length - The length of the User Buffer • User Buffer - Used to pass the user abort information of the ITU and ANSI abort messages. When there is no user information to be passed, the length should be set to 0. - User information must be encoded by the service user in ASN.1 format, including the external tag and length. TCAP will only insert the tag and length of user information.
Component Type Message Folder
Item ITU ITU ITU ITU ANSI ANSI ANSI Size MPS V1 V2 V3 V4 V2 V3 V4 (bytes) Developer Data Type Header X X X X X X X 9 folder Invoke ID Present X X X X X X X 1 number Invoke ID X X X X X X X 4 number Linked/Correlation X X X X X X X 1 number ID Present
360 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Component Type Message Folder
Item ITU ITU ITU ITU ANSI ANSI ANSI Size MPS V1 V2 V3 V4 V2 V3 V4 (bytes) Developer Data Type Linked/Correlation X X X X X X X 4 number ID Class X X X X X X X 1 number Invoke Timer X X X X X X X 5 number Op Code Flag X X X X X X 1 number Op Code Type X X X X X X 3 number Op Code X X X X X X X 3 number Error Code Flag X X X X X X 1 number Error Code X X X X X X X 3 number Problem Flag X X X X X X X 1 number Problem Code X X X X X X X 3 number Parameter Flag X X X X X X 1 number Last Component X X X X X X X 1 number Flag Length X X X X X X X 5 number Data X X X X X X X 256* characters Global Op Code X 32 characters Global Error Code X 32 characters
• Header - Header folder defined in the previous section. • Invoke ID Present - Used to represent whether Invoke ID is present. It is set to 1 if Invoke ID is present, otherwise it is set to 0. • Invoke ID - Used to represent the Invoke ID value • Linked/Correlation ID Present - Used to represent whether Linked ID for ITU, or Correlation ID for ANSI, is present. It is set to 1 if Linked/Correlation ID is present, otherwise it is set to FALSE. • Linked/Correlation ID - Used to represent the ITU Linked ID or ANSI Correlation ID.
Avaya CCSS 1000/2000 Feature Documentation August 2013 361 TCAP Application Programming
• Class - Represents the class of an operation. The allowable value is in the range of 1-4. • Class 1: Both success and failure are reported • Class 2: Only failure is reported • Class 3: Only success is reporter • Class 4: Neither success nor failure are reported • Invoke Timer - Used to represent the Invoke Timer value in seconds. - If the value is zero, then a default Invoke Timer value of 10 seconds is used. • Op Code Flag - Used to specify the Operation Code type. - The allowable values for ITU TCAP are: • 0: No Operation Code flag • 1: Local code; default for version 1 folder • 2: Global code (supported in folder version 4) - The allowable values for ANSI TCAP are: • 0: No Operation Code flag • 3: National TCAP • 4: Private TCAP • Op Code Type - ANSI only: Specifies the type of Operation Code, the operation family. • Op Code - ITU: Used to represent the Operation Code used in the Invoke Component type - ANSI: Specifies the specific Operation Code for a given operation type • Error Code Flag - Used to specify the Error Code - The allowable values for ITU TCAP are: • 0: No Operation Code flag • 1: Local code; default for version 1 folder • 2: Global code (supported in folder version 4)
362 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Component Type Message Folder
- The allowable values for ANSI TCAP are: • 0: No Operation Code flag • 3: National TCAP • 4: Private TCAP • Error Code - Used to represent the error code used in the Return-Error component. • Problem Flag - Used to represent the Problem type. Allowable values are: • 0: Problem type General • 1: Problem type Invoke • 2: Problem type Return Result • 3: Problem type Return Error • 4: Problem type Unknown • Problem Code - Used to represent the Problem code used in the reject component • Parameter Flag - Used to represent the ID used for operation parameters. Used only by ANSI - Allowable values are: • 0: No set or sequence flag • 1: Sequence flag desired • 2: Set flag desired • Last Component Flag - Used to represent the last component. It is set to 1 if it is the last component in the received message. • Length - The length of the component parameter data • Data - Component parameter data. Used to pass the parameters of components. It should be 128 bytes for version V1 and V4. But for version V2 and V3 the latest component parameter data size is 256* bytes.
Avaya CCSS 1000/2000 Feature Documentation August 2013 363 TCAP Application Programming
• Global Op Code - Used to represent the global operation code in OID(ASN.1) format. Supported in ITU only. • Global Error Code - Used to represent the global error code in OID(ASN.1) format. Supported in ITU only.
Notice Message folder
Item Size (bytes) MPS Developer Data Type Header 9 folder Return Value 3 number Return Value Description 50 characters
• Header - Version: 000 - Dialogue ID: 000 - MsgType: 000 • Return Value/Return Value Description
Value ITU ANSI 000 No Translation, address of such a No Translation, address of such a nature nature 001 No Translation, specific address No Translation, specific address 002 Sub-system congestion Sub-system congestion 003 Sub-system Failure Sub-system Failure 004 Unequipped User Unequipped User 005 Network Failure Network Failure 006 Network Congestion Network Congestion 007 Unqualified Unqualified 008 Error in message transport Hop counter violation 009 Error in local processing Invalid 010 Destination cannot perform Invalid reassembly
364 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Notice Message folder
Value ITU ANSI 011 SCCP failure Invalid 012 TCU APP State violation SCCP failure 013 Dialogue Reset Dialogue Reset 014 MTI Connection Closed MTI Connection Closed 015 Local Subsystem Out of Service Local Subsystem Out of Service
Avaya CCSS 1000/2000 Feature Documentation August 2013 365 TCAP Application Programming
Application State Machine Transition Diagram
366 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] TCU Dialogue State Transition Diagram
TCU Dialogue State Transition Diagram
Avaya CCSS 1000/2000 Feature Documentation August 2013 367 TCAP Application Programming
368 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Appendix A: Application Bridging Techniques
This chapter covers: 1. Interprocess Communications (IPC) Mechanisms 2. Using PLM Copy for Continuity Testing (Non TMS Integrated Mode)
Interprocess Communications
In SS7/C7 referral, the master application and slave application must communicate to remain synchronized and notify each other of line events. One way is to use shared memory variables (that is, use one variable as a flag and another for data). Another is to use POST and WAIT events. The sample applications use new Interprocess Communications (IPC) mechanism supported by VENGINE. IPC is implemented by the "phone" resource. The source application sends a message to the destination application by specifying the phone resource, the destination line, and the message to send.
The destination application can receive an IPC message in one of two ways: 1. Use RECEIVE. The destination application can wait on a RECEIVE from the phone resource (the fromphone condition must have default handling). The message is brought into the specified variable:
Avaya CCSS 1000/2000 Feature Documentation August 2013 369 Application Bridging Techniques
2. Handle fromphone. If the destination application is not waiting on a RECEIVE, it receives the fromphone condition. The message from the source application is contained in the ConditionData folder. Do not ignore the fromphone condition, though it is not handled by default.
Note: The programmer must design the applications to remain in sync (that is, there is no inherent synchronizing mechanism for two applications communicating with IPC).
PLM Copy for Continuity Handling
The PLM copy is used for Continuity testing in proxy mode. The Application handling of Inbound Continuity Processing. 1. Handle the request to loopback the inbound and outbound voice circuits. When a CCR condition is received, the application must issue a PLM Copy Command to connect the inbound and outbound voice circuits.
370 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] PLM Copy for Continuity Handling
2. Handle the termination of loopback request. When a COT condition is received, the application must issue a PLM Copy command to terminate the looping of the inbound and outbound voice circuits.
Avaya CCSS 1000/2000 Feature Documentation August 2013 371 Application Bridging Techniques
3. When a REL condition is received, and the inbound and outbound circuits are in loopback, the application must issue a PLM Copy Command to terminate the loopback.
372 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] PLM Copy for Continuity Handling
Avaya CCSS 1000/2000 Feature Documentation August 2013 373 Application Bridging Techniques
374 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Appendix B: Configuration Information Worksheets
Network Information
Note: For ITU Originating Signaling Point Code [Zone:Network:SPid]:______STP Signaling Point Code(s) [Zone:Network:SPid]:______For ANSI Originating Signaling Point Code [Network:Cluster:Member Octet]: STP Signaling Point Code(s) [Network:Cluster:Member Octet] Network Type: National or International Link Baud Rate: 56000 64000 Span Type: T1 ESF , T1 SF, E1 MF
Circuit Group Information
Switch Information IVR Information Trunk DPC Circuit MPS MPS MPS Starting Line Group Hostname / [Optional] Number Number / TMS (Proxy TMS Span Hostname Mode) Number
Avaya CCSS 1000/2000 Feature Documentation August 2013 375 Configuration Information Worksheets
Switch Information IVR Information Trunk DPC Circuit MPS MPS MPS Starting Line Group Hostname / [Optional] Number Number / TMS (Proxy TMS Span Hostname Mode) Number
376 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Appendix C: CCSS Configuration Files
Note: Unless otherwise instructed in this document, the configuration files should not be modified without consulting Avaya personnel.
Note: A pair of fault tolerant servers CCSS A and CCSS B should have similar configuration files. The only difference should be in the CONFIG REDUNDANT_SERVER command, where each server would identify the remote server as its FT peer.
The ss7.conf File (Proxy Mode)
ss7.conf is the configuration file for configuring the CCSS system. MGMT reads this file when the process starts (or is restarted). A sample file is shown in the following example. ss7.conf File (Proxy Mode)
# The MTP configuration CONFIG NODE=A1, OPC=2068, TYPE=SEP; CONFIG LINK=link1, SLC=0, TYPE=DTE, HOST=link3, BR=64000, TIMER_MAC=10, PRIORITY=0; CONFIG DCCHOST=dccl1, HOST=dcclink1b; CONFIG DCCLINK=link2, SLC=1, DCCHOST=dccl1, PRIORITY=0, CHASSIS = 2, BPS=2, SLOT=4, SPAN=2, CHANNEL=24,SS7SPAN=1,SS7CHAN=2,BR=64000; CONFIG LINKSET=ls1, DPC=2067, TYPE=FLINK, ACTIVELINK=2, LINKS=link1, link2; CONFIG CMB_LINKSET=cs1, LSETS=ls1; CONFIG ROUTE=rt1, DPC=2067, LSETS=cs1; # The local SCCP point code CONFIG SCCP_LOCAL=A1, OPC=2068; # The network SCCP point code and SSN CONFIG SCCP_NETWORK=periSCP, DPC=2067, SSN=252; # ISUP trunk groups CONFIG TRK_GRP=1, CIR_GRP=0, GRP_TYPE=T1, DPC=2067; CONFIG TRK_GRP=2, CIR_GRP=1, GRP_TYPE=T1, DPC=2067; CONFIG TRK_GRP=3, CIR_GRP=2, GRP_TYPE=T1, DPC=2067; CONFIG TRK_GRP=4, CIR_GRP=3, GRP_TYPE=T1, DPC=2067; # Host MCP1 will need TCAP access CONFIG TCUSER_HOST=MCP1, VAS=VAS2; # MCP1 has one cps #20 which has 2 T1 CONFIG TCUSER_CLIENT=VAS2, GROUP=1, TYPE=T1, VPS=20, LINE=1; CONFIG TCUSER_CLIENT=VAS2, GROUP=2, TYPE=T1, VPS=20, LINE=25; # ccss_remote identifies the redundant pair for an FT configuration.
Avaya CCSS 1000/2000 Feature Documentation August 2013 377 CCSS Configuration Files
CONFIG REDUNDANT_SERVER=ccss_remote, HOSTNAMES=tcccss12_1, tcccss12_2, PINGHOSTS=tcccss12_3;
#configure signaling point CONFIG NODE=CCSSA, OPC=2065, TYPE=SEP;
# DCCSS7 hosts CONFIG DCCHOST=dccl1, HOST=dcclink1; CONFIG DCCHOST=dccl2, HOST=dcclink2;
# SS7 links CONFIG DCCLINK=link1, SLC=0, DCCHOST=dccl1, PRIORITY=0, CHASSIS=2, BPS=1, SLOT=4, SPAN=1, CHANNEL=24, SS7SPAN=1, SS7CHAN=1, BR=64000; CONFIG DCCLINK=link2, SLC=1, DCCHOST=dccl1, PRIORITY=0, CHASSIS=2, BPS=1, SLOT=4, SPAN=2, CHANNEL=24, SS7SPAN=1, SS7CHAN=2, BR=64000; CONFIG DCCLINK=link3, SLC=2, DCCHOST=dccl2, PRIORITY=0, CHASSIS=2, BPS=2, SLOT=4, SPAN=1, CHANNEL=24, SS7SPAN=1, SS7CHAN=1, BR=64000; CONFIG DCCLINK=link4, SLC=3, DCCHOST=dccl2, PRIORITY=0, CHASSIS=2, BPS=2, SLOT=4, SPAN=2, CHANNEL=24, SS7SPAN=1, SS7CHAN=2, BR=64000;
# link sets CONFIG LINKSET=ls1, DPC=2066, TYPE=ALINK, ACTIVELINK=2, LINKS=link1,link2; CONFIG LINKSET=ls2, DPC=2067, TYPE=ALINK, ACTIVELINK=2, LINKS=link3,link4;
# combined linksets for the STP routes CONFIG CMB_LINKSET=stpcls1, LSETS=ls1, ls2; CONFIG CMB_LINKSET=stpcls2, LSETS=ls2, ls1;
# routes for the STP CONFIG ROUTE=stpr1, DPC=2066, LSETS=stpcls1; CONFIG ROUTE=stpr2, DPC=2067, LSETS=stpcls2;
# combined linksets for the ISUP DPCs CONFIG CMB_LINKSET=cs1, LSETS=ls1, ls2; CONFIG CMB_LINKSET=cs2, LSETS=ls2, ls1;
# routes for the ISUP DPCs CONFIG ROUTE=rt1, DPC=2068, LSETS=cs1; CONFIG ROUTE=rt2, DPC=2069, LSETS=cs2;
# trunk groups CONFIG TRK_GRP=1, CIR_GRP=0, GRP_TYPE=T1, DPC=2068; CONFIG TRK_GRP=2, CIR_GRP=1, GRP_TYPE=T1, DPC=2068; CONFIG TRK_GRP=3, CIR_GRP=2, GRP_TYPE=T1, DPC=2069; CONFIG TRK_GRP=4, CIR_GRP=3, GRP_TYPE=T1, DPC=2069;
# proxy mode host and application lines CONFIG CCME_PROXY_HOST=SCN1, HOSTNAMES=localhost; CONFIG CCME_PROXY_GRP=1, CCME_PROXY_HOST=SCN1, VPS=1, LINE=1; CONFIG CCME_PROXY_GRP=2, CCME_PROXY_HOST=SCN1, VPS=1, LINE=25; CONFIG CCME_PROXY_GRP=3, CCME_PROXY_HOST=SCN1, VPS=2, LINE=1; CONFIG CCME_PROXY_GRP=4, CCME_PROXY_HOST=SCN1, VPS=2, LINE=25;
# This sets up call control for extended mode 4 application folders # This can be adjusted to match older revisions of the CCSS CONFIG CCME_OPTION=EXTENDED, VALUE=4;
378 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Sample ss7.conf File for TMS Integrated Mode
Sample ss7.conf File for TMS Integrated Mode
ss7.conf File (TMS Integrated Mode)
# CCSS node CONFIG NODE=A1, OPC=2068, TYPE=SEP;
# MTP configuration CONFIG DCCHOST=dccl1, HOST=dcclink1; CONFIG DCCLINK=link1, SLC=0, DCCHOST=dccl1, PRIORITY=0, CHASSIS=2, BPS=2, SLOT=4, SPAN=1, CHANNEL=24, SS7SPAN=1, SS7CHAN=1, BR=64000; CONFIG DCCLINK=link2, SLC=1, DCCHOST=dccl1, PRIORITY=0, CHASSIS=2, BPS=2, SLOT=4, SPAN=2, CHANNEL=24, SS7SPAN=1, SS7CHAN=2, BR=64000; CONFIG LINKSET=ls1, DPC=2067, TYPE=FLINK, ACTIVELINK=2, LINKS=link1,link2; CONFIG CMB_LINKSET=cs1, LSETS=ls1; CONFIG ROUTE=rt1, DPC=2067, LSETS=cs1;
# ISUP trunk groups CONFIG TRK_GRP=1, CIR_GRP=0, GRP_TYPE=E1, DPC=2067; CONFIG TRK_GRP=2, CIR_GRP=1, GRP_TYPE=E1, DPC=2067; CONFIG TRK_GRP=3, CIR_GRP=2, GRP_TYPE=E1, DPC=2067; CONFIG TRK_GRP=4, CIR_GRP=3, GRP_TYPE=E1, DPC=2067;
# TMS host for TMS-Integrated Mode # Map TMS-Integrated Mode trunkgroups (1-4) to TMS2 spans 1 through 4 CONFIG CCME_TMS_HOST=TMS2, HOSTNAMES=tms2a; CONFIG CCME_TMS_GRP=1, CCME_TMS_HOST=TMS2, TMS_SPAN=1; CONFIG CCME_TMS_GRP=2, CCME_TMS_HOST=TMS2, TMS_SPAN=2; CONFIG CCME_TMS_GRP=3, CCME_TMS_HOST=TMS2, TMS_SPAN=3; CONFIG CCME_TMS_GRP=4, CCME_TMS_HOST=TMS2, TMS_SPAN=4;
# Local SCCP point code CONFIG SCCP_LOCAL=A1, OPC=2068;
# Network SCCP point code and SSN CONFIG SCCP_NETWORK=periSCP, DPC=2067, SSN=252;
# MPS AP MCP1 will run TCAP aplications # Map TCAP applications for two T1s to MCP1, MPS component #20, lines 1-48 CONFIG TCUSER_HOST=MCP1, VAS=VAS2; CONFIG TCUSER_CLIENT=VAS2, GROUP=1, TYPE=T1, VPS=20, LINE=1; CONFIG TCUSER_CLIENT=VAS2, GROUP=2, TYPE=T1, VPS=20, LINE=25;
#Override ISUP default parameter values CONFIG CCME_DEFAULT=FOCI_CALL-IND, VALUE=1;
#Define call control optional values CONFIG CCME_OPTION=OVERLAP, VALUE=y;
# Identify the other CCSS host in a redundant pair (for fault-tolerant configuration) CONFIG REDUNDANT_SERVER=ccss_remote, SERVER_ID=A, HOSTNAMES=tcccss12_1, PINGHOSTS=tcccss12_2;
Avaya CCSS 1000/2000 Feature Documentation August 2013 379 CCSS Configuration Files
TMS Configuration File
tms.cfg File (TMS Integrated Mode)
[DTCMAP] ;------; TMS PLI Span SRV Mps ; Num Slot Num type Num ;------LOAD 2 4 1 SS7 - LOAD 2 4 2 SS7 - LOAD 2 4 3 SS7 - LOAD 2 4 4 SS7 - [DTCMAP] ;------; Out Pool Protocol ; Pkg ;------e1_mf_ss7_proto.cfg B=1-15:17-31 D=16 - - e1_mf_ss7_proto.cfg B=1-15:17-31 D=16 - - e1_mf_ss7_proto.cfg B=1-15:17-31 D=16 - - e1_mf_ss7_proto.cfg B=1-15:17-31 D=16
[SS7] ;------; TMS PLI Span Chan SS7 Span Chan ; Num Slot Num Num Slot Num Num ;------SS7MAP 2 4 1 16 2 1 1 SS7MAP 2 4 2 16 2 1 2 SS7MAP 2 4 3 16 2 1 3 SS7MAP 2 4 4 16 2 1 4
For configuration options, see tms.cfg configuration parameters on page 67.
380 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Appendix D: Alarms
CCME Alarms
The following is a listing of alarms that the CCME process may generate on the CCSS console. Where appropriate, perform the suggested resolution.
Note: The alarms field '%s' in the alarm message displayed, represents a character string The alarms field '%d' in the alarm message displayed, represents a decimal value The alarms field '%x' in the alarm message displayed, represents a hexadecimal value For example: If the alarm message displayed is (%d,%d,%d) T5 expired, circuit down, a possible display would be (0,44,3). (0,44,3) corresponds to (point code # always 0, trunk group number 44, channel 3
Alarm Alarm Message Description Resolution Level Code Displayed Required INFO 0x010100 ccme startup Call control has None complete on sp %d completed startup. Call control is ready to service calls. CRITICAL 0x010101 Connection check Internal timer to None timer not running, check for new VAS restarting connections has stopped running and was restarted CRITICAL 0x010101 Could not allocate An error was None EBS reported while timer(%d,%d,%d) attempting to start a timer associated with circuit CRITICAL 0x010101 Could not allocate Could not start the None KeepAlive EBS timer used to check timer sp %d VAS network availability %s for the VAS listed CRITICAL 0x010101 Could not allocate Could not start the None must reset EBS timer used to pace
Avaya CCSS 1000/2000 Feature Documentation August 2013 381 Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required timer sp %d group the transmission of %d a Group Reset message CRITICAL 0x010101 1 Second timer not Call control has None running, restarting detected that its internal 1 second timer is not running CRITICAL 0x010101 Could not allocate Could not start the None Connection check timer used for EBS timer sp %d checking VAS connections CRITICAL 0x010101 Could not allocate Unable to allocate None KeepAlive timer sp the Keep Alive %d VAS %s timer CRITICAL 0x010101 Could not allocate Unable to allocate None mustreset timer sp Reset timer %d group %d MINOR 0x010102 (%d,%d,%d) A message has Report to Avaya Unexpected ISUP been received state %d message which is %s unexpected given the current state of the circuit. MINOR 0x010102 (%d,%d,%d) Unexpected Report to Avaya Unexpected message state message state %d message %s MINOR 0x010102 (%d,%d,%d) Report to Avaya Unexpected ISUP state %d messag e %s, transition negated, line state = %x MINOR 0x010103 (%d,%d,%d) Notification Report to Avaya Unexpected Timer received about state %d message expiration of an %s ISUP timer which was unexpected given the current state of the circuit MINOR 0x010103 (%d,%d,%d) Notification Report to Avaya Unexpected T received about invalid timer state
382 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] CCME Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required Timer state %d which was message %s unexpected given the current state of the circuit. MINOR 0x010104 (%d,%d,%d) A call control Report to Avaya Unexpected P timer(P) has Timer state %d expired which was message %s unexpected given the current state of the circuit MINOR 0x010105 (%d,%d,%d) An application Check application Unexpected message was for error Application received which is message state %d not valid for the message %s current state of the circuit MINOR 0x010105 (%d,%d,%d) Error Message from Check application generating Application for error. parameter %d, contains invalid status returned: %s values in %s message MINOR 0x010105 Unknown message Message from Check the type index = %d Application application and fix contains invalid the message type. message type MINOR 0x010105 Received NULL Call Control Report to Avaya. ccext primitive received invalid message from application MINOR 0x010105 Unknown ccext Call Control Report to Avaya. primitive..%d received unknown message. MAJOR 0x010105 Invalid Protocol ID Message from Check the %s received on application application and fix span %d circuit %d contains invalid the protocol ID. from Application protocol ID CRITICAL 0x010106 Unsupported ISUP has Report to Avaya TIMER T%d transmitted a timer occurred expiration which is not supported in call control
Avaya CCSS 1000/2000 Feature Documentation August 2013 383 Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 0x010107 (%d,%d,%d) T5 ISUP T5 expired, Verify signaling links expired, circuit release has not are available. down been Determine reason acknowledged for lack of network response. CRITICAL 0x010108 (%d,%d,%d) T1 ISUP T1 has None expired, REL retry expired, release is being retransmitted FATAL 0x010109 Error in command An error was Verify CCSS line sp %d encountered while installed correctly. parsing the parameters which were passed on the command line MAJOR 0x01010a (%d,%d,%d) P5 Circuit reset is in None expired, circuit progress and has down - resetting not been acknowledged MAJOR 0x01010a (%d,%d,%d) T16 ISUP timer T16 None Stopped, Reset was stopped. complete Circuit RESET has completed MAJOR 0x01010a (%d,%d,%d) P6 An application is Verify that the expired Application slow in doing an application not slow response = ISSUE GET. The taking too much Blocking release of the last time between doing call will be ISSUE FREE and completed, the the ISSUE GET circuit will be blocked. MAJOR 0x01010b (%d,%d,%d) T22 Group Reset has None. expired not been acknowledged. MAJOR 0x01010b (%d,%d,%d) T17 A circuit reset has None expired, circuit not been down - resetting acknowledged MAJOR 0x01010b (%d,%d,%d) T23 Group Reset has None expired, circuit not been down - resetting acknowledged MAJOR 0x010110 (%d,%d,%d) ccme was notified Fix configuration Configuration error, that it has sent mismatch between Unequipped CIC message traffic ccme and ISUP relating to a circuit
384 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] CCME Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required which is not configured under ISUP. MAJOR 0x010110 Message %d '%s' ccme received a Fix configuration Received for message from the mismatch between unconfigured trunk network for a circuit ccme and ISUP %d, check which it is not configuration configured MAJOR 0x010110 Message Received Call Control Check configuration for unconfigured received message files trunk %d, check from ISUP on a configuration trunk group which is not configured. MAJOR 0x010110 ISUP Message ISUP message Verify that the Received for trunk received on a trunk configuration is %d circuit %d, of the standby correct. CCME in Standby system. Mode.\n MAJOR 0x010110 APP Message Application Check application received in message received for error Standby Mode.\n on standby server FATAL 0x010111 Environment The CCSSHOME Verify CCSS is variable environment installed correctly. CCSSHOME not variable must be Verify that set set. CCSSHOME is set. INFO 0x010112 (%s/%d/%d) A message was Correct the Unsupported App received from the application message %s application which is not supported. MAJOR 0x010112 (%d,%d,%d) Call Control If CON message Application Received CON need to be sent out transmitted CON from application, instead of ACM/ with AUTO_ACM when option AUTO ANM, set the option option = true ACM is on. parameter AUTO ACM in the configuration file to false (0). INFO 0x010113 (%d,%d,%d) SAM Call control Reconfigure message received a network connection unsupported, Subsequent for Enbloc Enbloc operation Address Message operation. supported (SAM) from the network. SAM is not supported.
Avaya CCSS 1000/2000 Feature Documentation August 2013 385 Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required INFO 0x010113 (%d,%d,%d) A network None Unsupported ISUP message was message %d received which is not supported. INFO 0x010113 Application Application None message without message received CN, in CN mode without connection identifier in CN mode INFO 0x010113 Application Application Check application message with message received for error unknown CN with unknown CN INFO 0x010113 Application Application Check application message with CN, message received for error in non-CN mode with connection identifier in non - CN mode INFO 0x010113 Application invalid Invalid Application Check application message type, in message received for error non-CN mode in non-CN mode. INFO 0x010113 IAMX (extended 4) Extended IAM None Rx from app in %s message received from application with 'OPTION Extended 4' configuration INFO 0x010113 IAM (non- Non-extended IAM None extended) Rx from message received app in %s from application. INFO 0x010113 RELX (extended 1) Extended REL None Rx from app in %s message received from application with 'OPTION EXTENDED 1' configuration INFO 0x010113 RELX (extended 2) Extended REL None Rx from app in %s message received from application with 'OPTION EXTENDED 2' configuration
386 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] CCME Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required INFO 0x010113 RELX (extended Extended REL None 3,4) Rx from app in message received %s from application with 'OPTION EXTENDED 3'or ' OPTION EXTENDED 4' configuration INFO 0x010113 ANM (non- Non-extended None extended) Rx from ANM message app in received from application. INFO 0x010113 CPG (non- Non-extended None extended) Rx from CPG message app in %s received from application INFO 0x010113 CPGX (extended Extended CPG None 2,3) Rx from app in message received %s from application with 'OPTION EXTENDED 2or' OPTION EXTENDED 3' configuration INFO 0x010113 CPGX (extended Extended CPG None 4) Rx from app in message received %s from application with 'OPTION EXTENDED 4' configuration INFO 0x010113 CON (non- Non-extended None extended) Rx from CON message app in %s received from application INFO 0x010113 CONX (extended Extended CON None 2,3,4) Rx from app message received in %s from application with 'OPTION EXTENDED 2',' OPTION EXTENDED 3' or 'OPTION EXTENDED 4' configuration
Avaya CCSS 1000/2000 Feature Documentation August 2013 387 Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required INFO 0x010113 REBIND of CN by Call Control Check the app other than call- received message application / protect redundant REBIND of CN configuration file for app from application error other than call- protect redundant app. INFO 0x010113 IAMX (extended Extended IAM None 2,3) Rx from app in message received %s from application with 'OPTION EXTENDED 2'or' OPTION EXTENDED 3' configuration INFO 0x010113 REL Rx from app in REL is received Check application %s\n from application for error when not expected. INFO 0x010113 ANMX (extended ANM received from Check application 1) Rx from app in the application for error %s\n INFO 0x010113 ANMX (extended ANM received from Check application 2,3,4) Rx from app the application. for error in %s\n CRITICAL 0x010114 CCME: OPTION The ccme Fix the configuration registration failure configuration file file and restart the contains a line with CCSS an OPTION keyword which contains an error CRITICAL 0x010114 CCME: SERVER The ccme Fix the configuration registration failure configuration file file and restart the contains a line with CCSS a SERVER keyword which contains an error CRITICAL 0x010114 CCME: TIMER The ccme Fix the configuration registration failure configuration file file and restart the contains a line with CCSS a TIMER keyword which contains an error
388 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] CCME Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required CRITICAL 0x010114 CCME: VAS The ccme Fix the configuration registration failure configuration file file and restart the contains a line with CCSS a TIMER keyword which contains an error CRITICAL 0x010114 CCME: Using old Option to use Old None alarm date format alarm date format is set in the configuration file CRITICAL 0x010114 CCME: Default Invalid DEFAULT Check configuration registration failure parameter /value in file for error for the configuration CCME_DEFAULT file. =%s, VALUE=%d CRITICAL 0x010114 CCME: Overlap Invalid Overlap Check configuration option registration option specified in file for error. failure for the configuration CCME_OPTION= file. %s, VALUE=%d\n FATAL 0x010115 CCME: Internal error Report to Avaya and communication reported from restart the CCSS failure, bad file select description FATAL 0x010115 Communication Report to Avaya and failure restart the CCSS Server_Info.serv_s ock (fd# %d) closed FATAL 0x010115 Communication Failure in Report to Avaya and failure Vas %d communication is restart the CCSS connection # %d noticed between (fd# %d) closed Call Control and proxy. FATAL 0x010115 Communication Report to Avaya and failure timerd_fd restart the CCSS (fd# %d) closed FATAL 0x010115 Communication Report to Avaya and failure uifd # %d restart the CCSS (fd# %d) closed FATAL 0x010115 Communication Report to Avaya and failure ccfd (fd# restart the CCSS %d) closed
Avaya CCSS 1000/2000 Feature Documentation August 2013 389 Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required FATAL 0x010115 CCME: select Invalid error code. Report to Avaya. failed errno %d MAJOR 0x010116 CcExt: Failed to transmit Check LAN T_CliDiscrimInd Discrim to DSSI connection and failed, DCC %s, inspect the log file. span %d MAJOR 0x010116 CcExt: Discrim Failed to transmit Check LAN failed, bad perm Discrim to DSSI. connection and sock, DCC %s, inspect the log file span %d MAJOR 0x010116 CcExt: T_CliGoInd Failed to transmit Check LAN failed, DCC %s send go to DSSI. connection and inspect the log file. MAJOR 0x010116 CcExt: Go failed, Failed to transmit Check LAN bad perm sock, send go to DSSI. connection and DCC %s inspect the log file MAJOR 0x010116 CcExt: Failed to transmit Check LAN T_CliStopInd stop to DSSI. connection and failed, DCC %s inspect the log file. MAJOR 0x010116 CcExt: Stop failed, Failed to transmit Check LAN bad perm sock, stop to DSSI. connection and DCC inspect the log file. MAJOR 0x010116 CCME: unknown An error has None read error from occurred reading VAS %d data from a VAS MAJOR 0x010116 CCME: connection One of the Verify the VAS is up. partially lost VAS redundant LANs Check Ethernet. %s between the CCSS and the VAS has gone down. MAJOR 0x010116 CCME: connection All LANs between Verify the VAS is up. totally lost VAS %s the CCSS and the Check Ethernet VAS listed are down. MAJOR 0x010116 CcExt: Discrim Check LAN failed %s, span %d connection and inspect the log file. MAJOR 0x010116 CcExt: Send go Check LAN failed, host %s connection and inspect the log file.
390 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] CCME Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 0x010116 CcExt: Send stop Check LAN failed, host %s connection and inspect the log file. MAJOR 0x010116 CcExt: Send pause Check LAN failed, host %s connection and inspect the log file. FATAL 0x010117 ccme/proxy version There is a version Verify installation. mismatch cannot mismatch between start ccme and proxy. FATAL 0x010118 (%d,%d,%d) A network Verify the VAS is up. Cannot deliver message could not Check Ethernet. network message, be delivered to an VAS down application due to the LAN connection being down. FATAL 0x010118 (%d,%d,%d) Error was Report to Avaya cond_cpg encountered p_crt_msg failed during creation of a condition containing a CPG FATAL 0x010118 (%d,%d,%d) Error was Report to Avaya cond_rel encountered p_crt_msg failed during creation of a condition containing a REL FATAL 0x010118 (%d,%d,%d) Error was Report to Avaya cond_res encountered p_crt_msg failed during creation of a condition containing a RES FATAL 0x010118 (%d,%d,%d) Error was Report to Avaya cond_sus encountered p_crt_msg failed during creation of a condition containing a SUS FATAL 0x010118 (%d,%d,%d) Error was Report to Avaya send_appmsg encountered p_crt_msg failed during the creation of an application message
Avaya CCSS 1000/2000 Feature Documentation August 2013 391 Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 0x010118 (%d,%d,%d) Error was Report to Avaya cond_ccr encountered p_crt_msg failed during creation of a condition containing a CCR MAJOR 0x010118 (%d,%d,%d) Error was Report to Avaya cond_clr encountered p_crt_msg failed during creation of a condition containing a CLR MAJOR 0x010118 (%d,%d,%d) Error was Report to Avaya cond_ran encountered p_crt_msg failed during creation of a condition containing a RAN (Re-Answer) MAJOR 0x010118 (%d,%d,%d) Error was Report to Avaya cond_anm encountered p_crt_msg failed during creation of a condition containing a ANM MAJOR 0x010119 (%d %d %d) Call setup failed Verify that the Application did not because the application answers answer before application did not calls in time. network release answer the call. MAJOR 0x010119 (%d,%d,%d) Network released Verify that the Application did not the call before the application answers answer before application calls in time. network release answered. MAJOR 0x010119 P1 expired, Call setup failed Verify that the Application did not because the application answers answer application did not the call. answer the call. MAJOR 0x01011a (%d,%d,%d) A call was lost Verify that the Application did not because the application is fast issue get in time to application did not enough when it take call perform an ISSUE cycles. GET in time. MAJOR 0x01011A (%d,%d,%d) P3 A call was lost Verify that the expired, because the application is fast Application did not application did not enough when it iss ue get in time to perform an ISSUE recycles. take call GET in time.
392 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] CCME Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required INFO 0x01011b (%d,%d,%d) P4 Call control was None expired, Line informed of dual seized but no IAM seizure, but no received, inbound call was reattempting received. Outbound call will be reattempted. INFO 0x01011b (%d,%d,%d) P4 Call control was None expired, Line informed of dual blocked, reattempt seizure, no cancelled inbound call was received but circuit got blocked. Reattempt of outbound call cancelled. FATAL 0x01011c CCME terminating Call control is None on sp %d terminating due to operator request FATAL 0x01011c CCME: terminating Call control is None on signal %d terminating due to receipt of a signal. FATAL 0x01011c CCME: server Failure to create Report to Avaya. socket is %d, socket connection restarting ccme to peer server in redundant configuration. FATAL 0x01011c CCME on sp %d: Call control is None terminating on terminating due to signal %d receipt of a signal. CRITICAL 0x01011c CCME soft Soft termination of None termination on sp Call Control %d requested by operator. MAJOR 0x01011d (%d,%d,%d) The network has None Network Blocked blocked this circuit. circuit, Out of service MAJOR 0x01011d (%d,%d) Group Group Block None block request - ckts Message has been (%d - %d) out of received from service Network
Avaya CCSS 1000/2000 Feature Documentation August 2013 393 Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 0x01011e (%d,%d) Group A group blocking None Block applied - message has been circuits Out of transmitted. service MAJOR 0x01011e (%d,%d) Group A group unblocking None Unblock applied - message has been circuits Out of transmitted. service\n MAJOR 0x01011e (%d,%d,%d) Local A block has been Verify application. Block applied - Out transmitted for this of service, App not circuit because the ready application has not responded to a call. MAJOR 0x01011e (%d,%d,%d) Local A block has been None Block applied - on the circuit. circuit Out of service MAJOR 0x010120 (%d,%d,%d) Call Control None Network unblocked received unblock circuit (IAM UBL message from received), In ISUP service MAJOR 0x010120 (%d,%d,%d) The network has None Network unblocked removed the block circuit, In service which was on this circuit. MAJOR 0x010120 (%d,%d) Group Call control None unblock request - received Group ckts (%d - %d) in Unblock message. service MAJOR 0x010120 (%d,%d,%d) Call Control None Network IAM/IFAM received IFAM implicitly unblocks message from circuit, In service network and unblocks that circuit if remotely blocked. MAJOR 0x010121 (%d,%d) Group A group unblocking None Block removed message has been transmitted
394 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] CCME Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 0x010121 (%d,%d,%d) Local A block which was None Block Removed - In placed on this service, App ready circuit was removed because the application performed ISSUE GET MAJOR 0x010121 (%d,%d,%d) Local The block on a None Block removed circuit has been removed MINOR 0x010122 (%d,%d,%d) Multiple releases Check application Network have been performance. reattempted received on this release, still waiting circuit. Application for slow application is not ready for next call MAJOR 0x010123 (%d,%d,%d) Call control has Check application Inbound Call released a call performance. released, because the Application not application is not ready, Circuit will ready. Circuit will block block once idle MAJOR 0x010126 (%d,%d,%d) P7 An outbound call None expired, Circuit did attempt by an not clear for application is failing outbound call because a reset of release sequence has not completed. MINOR 0x010127 MTP Pause - The MTP layer has Verify signaling links Circuit group %d paused traffic on are available. this circuit group. Signaling links may be down. MINOR 0x010128 MTP resume - The MTP layer has None Circuit group %d resumed activity for this circuit group. MAJOR 0x010129 (%d,%d,%d) A call is being Application should Application released because release an active ISSUE_FREE, and application has call prior to ISSUE terminating call in done ISSUE FREE FREE progress MAJOR 0x010129 (%d,%d,%d) A call is being Check the reason Application released due to an that the application ISSUE_GET, has recycled without
Avaya CCSS 1000/2000 Feature Documentation August 2013 395 Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required terminating call in ISSUE GET being releasing the last progress received call. MAJOR 0x010129 (%d,%d,%d) Received ISSUE Check application Application FREE/ FREE from for error. UNBIND Application when terminating call in call is in progress. progress MAJOR 0x01012a (%d,%d,%d) Inbound call setup Determine if the Inbound Call has failed and is application is Rejected in state being counted as a causing the '%s' input '%s' rejected call. rejection MAJOR 0x01012a (%d,%d,%d) Inbound call setup Determine if the Inbound Call has failed and is application is Rejected in state being counted as a causing the '%s' input '%s' rejected call. rejection release cause %d \n MAJOR 0x01012b (%d,%d,%d) Inbound call setup Determine if the Inbound Call failed has failed and is application is in state '%s' input being counted as a causing the failure. '%s' failed call. MAJOR 0x01012b (%d,%d,%d) Outbound call Determine if the Outbound call setup has failed application is ejected in state '%s' and is being causing the failure. input '%s' release counted as a cause %d rejected call. MAJOR 0x01012c (%d,%d,%d) Outbound call Determine if the Outbound call setup has failed application is rejected in state and is being causing the failure. '%s' input '%s counted as a failed call. MAJOR 0x01012d (%d,%d,%d) Inbound call setup Determine if the Outbound Call has failed and is application is failed in state '%s' being counted as a causing the failure. input '%s' failed call. MAJOR 0x01012e (%d,%d,%d) An application has Verify that the Outbound Call sent IAM while the application is Rejected, Wrong circuit is not in the sending IAM State '%s' state where IAM correctly can be transmitted. MAJOR 0x01012f Commanding In redundant Check LAN COMMAND_ACTI configuration, call connection/ report to VE failed - control failed to get Avaya.
396 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] CCME Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required CRITICAL response from l2if ATTENTION for the command REQUIRED command_active. MAJOR 0x010130 (%s) Communication None Communication with the VAS has with VAS restored been restored MAJOR 0x010131 (%s) CcExt Communication Check the LAN connection down with TMS host lost connection to DSSI/ TMS. MAJOR 0x010131 (%s) Communication Verify that the VAS Communication with the VAS has is up with VAS lost been lost MAJOR 0x010131 (%s) Communication Check the LAN Communication with VAS is lost connection to with VAS totally lost proxy. MAJOR 0x010132 (%d,%d,%d) Call Control Check configuration ErrorInd cause %d received error file and report to indication in ISUP Avaya. configuration. MAJOR 0x010132 ebstoapp Received Check the message msg_index = -1 Unsupported received from message from network. Report to Network. Avaya. CRITICAL 0x010133 CCME: DCC Error in DCCHOST Check configuration registration failure entry in the file for error. configuration file. INFO 0x010133 (%d,%d,%d) All Control Check the Reattempt informed of dual application for error. indication, P4 seizure. Started P4 started timer CRITICAL 0x010134 CCME: CIC Error in registering Check configuration registration failed: CIC from CIC entry file for error. wrong number of line in configuration arguments file. CRITICAL 0x010134 CCME: CIC Error in registering Check configuration registration failed: CIC from CIC entry file for error. circuit number line in configuration must be * file. CRITICAL 0x010134 CCME: CIC Span type entered Verify and modify registration failed: in CIC line in the the configuration invalid span type configuration file is file. invalid
Avaya CCSS 1000/2000 Feature Documentation August 2013 397 Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required CRITICAL 0x010134 CCME: CIC Host Name entered Verify and modify registration failed: in CIC line in the the configuration unknown VAS, configuration file is file. TMS or DCC invalid. hostname CRITICAL 0x010134 CCME: CIC In TMS integrated Verify and modify registration failed: mode, vps number the configuration VPS number must assigned in CIC file. be 1 entry must be 1 CRITICAL 0x010134 CCME: CIC TMS span number Verify the registration failed: configured is configuration file. invalid TMS span invalid. number CRITICAL 0x10101 Could not allocate Could not start 1 Report to Avaya. activate_1sec_tim sec. timer. er sp %d CRITICAL 0x10101 Could not allocate Could not start Report to Avaya. Connection check timer used to check activate_connect_t and start proxy imer sp %d connection. CRITICAL 0x10101 Could not allocate Could not start Report to Avaya. CN mode issue timer used in CN free timer. (%d,%d) mode call protect applications to wait for REBIND when issue free comes from app. MAJOR 0x10105 Invalid Variant ID Message from Check the %s received on application application and fix span %d circuit %d contains invalid the variant ID. from Application variant ID FATAL 0x10115 Communication Failure in Check LAN failure CCEXT %d communication is connection and connection # %d noticed between report to Avaya. (fd# %d) closed Call Control and DSSI. MAJOR 0x10116 CcExt: Discrim Failed to send Check LAN failed %s, span % discrim message to connection, DSSI. configuration file and inspect the log file.
398 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] MGMT Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 0x10116 CcExt: Send go Failed to transmit Check LAN failed, host %s send go to DSSI. connection and inspect the log file. MAJOR 0x10123 (%d,%d,%d) Call control None Incompatible call received a BAD rejected with CNA IFAM from the Network. MINOR 0x10123 (%d,%d,%d) Received inbound Check configuration Incoming call on call on trunk file. outgoing trunk configured for rejected with CNA outbound. MAJOR 0x10123 (%d,%d,%d) Received call from Check application Inbound Call Network, while available. Released, application is not Application not ready to Handle. ready, Circuit resetting MAJOR 0x10123 (%d,%d,%d) Call Control Check application Inbound CCR received CCR from ready. released, Network, but Application not application were ready, Circuit will not attached or block ready. MAJOR 0x10129 (%d,%d,%d) Received ISSUE Check application Application FREE from for error. ISSUE_FREE, Application when outbound call setup call is in progress. aborted MAJOR 0x10130 (%s) CcExt Connection with None connection DSSI/TMS restored established. MAJOR 0x10131 (%s) CcExt Communication Verify that DSSI connection lost with TMS host lost. connection is up.
MGMT Alarms
The following is a listing of alarms that the MGMT process may generate on the CCSS console. Where appropriate, perform the suggested resolution.
Avaya CCSS 1000/2000 Feature Documentation August 2013 399 Alarms
Note: The alarms field '%s' in the alarm message displayed, represents a character string The alarms field '%d' in the alarm message displayed, represents a decimal value The alarms field '%x' in the alarm message displayed, represents a hexadecimal value
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 0 L4 config rout ISUP configuration Check out the failed, mismatch failed due to the ss7.conf file. between Node and mismatch between Route Variant node and route variant. MAJOR 0 ERROR %s wring Layer sent to timer None layer table is neither MTP3 nor MTP2 which is incorrect. MAJOR 0 mgmt: cfg_l4 for fd Configuring ISUP None %d using the mentioned fd. MAJOR 0 mgmt: Configured MTP2 None cfg_l2_routerif for for the mentioned %s link. MAJOR 0 mgmt: Invalid hostname cfg_l2_routerif for the com1000 invalid hostname: card. '%s' MAJOR 0 mgmt: Configuring MTP2 None cfg_l2_routerif host for the mentioned '%s' host. MAJOR 0 mgmt: Error in sending the None cfg_l2_routerif message. perm_send failed MAJOR 0 mgmt: Configuring the None cfg_l2_sysagt for fd system agent with %d the mentioned fd MAJOR 0 mgmt: init_sysagt Initializing the None for type %d system agent for the requested type. MAJOR 0 mgmt: Configuring the None form_l2_sysagt for system agent for link %d data link layer.
400 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] MGMT Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 0 l2 sysagent gen Configuration for None failed MTP2 system agent for general element type failed. MAJOR 0 invalid Configuration for None configuration for L2 MTP2 system System Agent agent is invalid. MAJOR 0 mgmt: Configuring MTP2 None cfg_l2_msgrtr for fd message router %d with the mentioned fd. MAJOR 0 mgmt: init_msgrtr Initializing the None for type %d message router for the requested type. MAJOR 0 invalid Configuration for None configuration for the system agent is MTI System Agent invalid. MAJOR 0 mgmt: Configuring the None form_l2_msgrtr for message router for link %d MTP2 MAJOR 0 l2 router gen failed Configuring the None MTP2 router for gen type failed. MAJOR 0 invalid configuration for None configuration for L2 MTP2 router is Router invalid. MAJOR 0 mgmt: Configuring the None cfg_mti_routerif for routerif. %s MAJOR 0 mgmt: Invalid host name None cfg_mti_routerif of the for invalid hostname: configuring the '%s' routerif. MAJOR 0 mgmt: Configuring routerif None cfg_mti_routerif on the com card com-1000 ip '%s' with the mentioned IP. MAJOR 0 mgmt: Sending routerif None cfg_mti_routerif configuration msg perm_send failed to the server failed.
Avaya CCSS 1000/2000 Feature Documentation August 2013 401 Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 0 mgmt: Invalid redundant Check for the cfg_mti_routerif server redundant invalid configuration. configuration in redundant_server ss7.comf file. cfg MAJOR 0 mgmt: Configuring psf None cfg_mti_psf_mtp3 mtp3 with the for fd %d mentioned fd. MAJOR 0 mgmt: init_psfmtp3 Initialising psf mtp3 None for type %d with the mentioned type. MAJOR 0 type != STZNGEN Invalid type in the None for PSFMTP3 configuration of configuration PSF MTP3 MAJOR 0 mgmt: Configuring psf None form_psfmtp3 for mtp3 for the type %d requested type. MAJOR 0 mti psfmtp3 gen Configuring psf None failed mtp3 for general type failed. MAJOR 0 invalid Configuration for None configuration for PSF MTP3 is PSF MTP3 invalid. MAJOR 0 mgmt: Configuring psf None cfg_mti_psf_isup ISUP with the for fd %d mentioned fd. MAJOR 0 mgmt: init_psfisup Initialising psf isup None for type %d with the mentioned type. MAJOR 0 type != STZNGEN Invalid type in the None for PSFISUP configuration of configuration PSF ISUP MAJOR 0 mgmt: Configuring PSF None form_psfisup for ISUP for the type %d requested type. MAJOR 0 mti psf isup gen PSF ISUP None failed configuration for general type failed. MAJOR 0 invalid Configuration for None configuration for PSF ISUp is invalid MTI PSF ISUP
402 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] MGMT Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 0 mgmt: Configuring None cfg_mti_msgrtr for message router fd %d with the mentioned fd. MAJOR 0 mgmt: Configuring None form_mti_msgrtr message router for for type %d the mentioned type. MAJOR 0 mti router gen Configuring the None failed router for general type failed. MAJOR 0 invalid Invalid None configuration for configuration for MTI Router MTI message router. MAJOR 0 mgmt: Configuring system None cfg_mti_sysagt for agent with the fd %d mentioned fd. MAJOR 0 mgmt: Configuring system None form_mti_sysagt agent for the for type %d mentioned type. MAJOR 0 mti sysagent gen Configuring for None failed general type failed for the system agent. MAJOR 0 mgmt: Configuring the None cfg_mti_sysmgr for system manager fd %d with the fd. MAJOR 0 mgmt: init_sysmgr Initialising the None for type %d system manager for the mentioned type. MAJOR 0 invalid Configuration for None configuration for the MTI system MTI System manager is invalid. Manager MAJOR 0 mgmt: Configuring the None form_mti_sysmgr system manager type %d, ent %d, with the mentioned link %d type and entity. MAJOR 0 form_mti_sysmgr: Invalid None invalid redundant configuration for
Avaya CCSS 1000/2000 Feature Documentation August 2013 403 Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required server or link the system configuration manager. MAJOR 0 invalid entity in mti Invalid entity in the None System Manager configuration of cfg system manager MAJOR 0 MTI Sysgem Failure in None Manager general configuring the MTI configuration failed system manager. MAJOR 0 invalid Configuration None configuration for invalid for the MTI mti System system manager. Manager MAJOR 0 mgmt: cfg_l1 for fd Configuring the None %d layer one with the mentioned fd. MAJOR 0 mgmt: init_l1 for Initialising layer None type %d one for the given type. MAJOR 0 invalid l1 config Configuration None MTP1 is invalid. MAJOR 0 mgmt: form_l1 for Configuring MTP1 None type %d for the mentioned type. MAJOR 0 L1 gen failed Configuring MTP1 None for general element type failed. MAJOR 0 L1 msap failed Configuring MTP1 None for the type MAC SAP failed. MAJOR 0 invalid l1 config Invalid None configuration for MTP1 MAJOR 0 mgmt: cfg_l2 for fd Configuring MTP2 None %d with the mentioned fd. MAJOR 0 mgmt: init_l2 for Initialising MTP2 None type %d for the given type. MAJOR 0 invalid Configuration for None configuration for L2 MTP2 is invalid.
404 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] MGMT Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 0 mgmt: form_l2 for Configuring MTP2 None type %d for the mentioned type MAJOR 0 l2 gen failed general element None type configuration for MTP2 failed. MAJOR 0 mgmt: form_l2 for Configuring MTp2 None STDLSAP link for data link SAP. number %d MAJOR 0 l2 dlsap failed\n Configuring MTP2 None for data link SAP failed. MAJOR 0 invalid Invalid None configuration for L2 configuration for MTP2 MAJOR 0 mgmt: cfg_l3 for fd Configuring MTP3 None %d for the mentioned fd. MAJOR 0 mgmt: init_l3 for Initialising MTP3 None type %d for the mentioned type. MAJOR 0 invalid MTP3 None configuration of L3 configuration is invalid. MAJOR 0 mgmt ERROR: %s Configuration of None layer is not yet the mentioned supported %d layer is not yet supported. MAJOR 0 mgmt ERROR: %s Mentioned layer is None layer is not valid for not valid for restart RESTART_REQD request. %d MAJOR 0 sending l3 gen Configuring MTP3 None failed for general type failed. MAJOR 0 sending l3 dlsap Configuring data None failed link sap failed for MTp3. MAJOR 0 invalid invalid None configuration for L3 configuration for MTP3
Avaya CCSS 1000/2000 Feature Documentation August 2013 405 Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 0 sending sccp gen Failure in sending None failed the SCCP configuration details. MAJOR 0 mgmt: form sccp Configuring SCCP None network network. MAJOR 0 sending sccp Configuring SCCP None NSAP failed for network SAP failed. MAJOR 0 mgmt: form_sccp Configuring the None USAP upper layer SAP for SCCP. MAJOR 0 sending sccp Configuring SCCP None USAP failed for upper layer SAP failed. MAJOR 0 sending sccp Failure in sending None address mapping the sccp address failed mapping for the given configuration. MAJOR 0 sending sccp route Configuration of None failed routes for the SCCP network failed. MAJOR 0 sending tcap gen Configuring TCAP None failed for general element type failed. MAJOR 0 mgmt: Configuring the None form_tcap_usap upper layer SAP for TCAP. MAJOR 0 sending tcap usap Failure in None failed configuring the upper layer SAP for TCAP. MAJOR 0 mgmt: Configuring the None form_tcap_lsap lower layer SAP for TCAP. MAJOR 0 sending tcap lsap Failure in None failed configuring the lower layer SAP for TCAP.
406 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] MGMT Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 0 mgmt: tcuser for fd Configuring tcuser. None %d MAJOR 0 No configuration Configuration for None for tcuser TCUSER is not available. MAJOR 0 sending tcuser Unable to send the None SUBSYSTEM TCUSER failed configuration details to CCME MAJOR 0 sending tcuser Unable to get the None DEST failed TCUSER configuration details to CCME. MAJOR 0 Failed to get DPC Unable to get the None and SSN TCUSER details from the configuration. MAJOR 0 sending tcuser Unable to send the None CLIENT failed TCUSER client details in the configuration. MAJOR 0 sending tcuser Unable to send the None GTTNODE failed GTTNODE configuration. MAJOR 0 unknown gt format Unknown GT None format for TCU. MAJOR 0 mgmt: cfg_sccp for Started configuring None fd %d SCCP MAJOR 0 mgmt: cfg_tcap for Started configuring None fd TCAP MAJOR 0 This route is for an The configuration None STP!!!!!! tells that this system is connected to an STP. MAJOR 0 mgmt ERROR: Wrong message/ None Wrong priority congestion priority range 0-3 for MTP3 MAJOR 0 mgmt: Error in the general None form_tcap_gen configuration of TCAP
Avaya CCSS 1000/2000 Feature Documentation August 2013 407 Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 0 form_tcap_usap: No configuration None local command is for tcap upper user not in ss7.conf file SAP MAJOR 0 form_tcap_lsap: No configuration None local command is for tcap lower not in ss7.conf file SCCP SAP MAJOR 0 Sm_Link_Trace: Unable to find the Check the could not find link mentioned link configuration in %d SS7.conf file MAJOR 0 cannot allocate Allocating space None space for id_name for the link set failed. MAJOR 0 cannot allocate Allocating space None space for lset id for the combined link set failed. MAJOR 0 modify_node: the Modify node None config code command failed. command is not done MAJOR 0 cannot allocate Unable to allocate Restart the CCSS ccme_proxy_host memory for configuring the proxy host MAJOR 0 cannot allocate Unable to allocate Restart the CCSS ccme_tms_host memory for configuring the tms host MAJOR 0 cannot allocate configuring the None ccme_timer_t timer failed. MAJOR 0 cannot allocate Unable to allocate Restart the CCSS store for ccme memory for proxy grp option configuring the proxy grp MAJOR 0 cannot allocate Unable to allocate Restart the CCSS store for ccme tms memory for grp option configuring the tms grp MAJOR 0 cannot allocate Unable to allocate Restart the CCSS store for ccme cn memory for dtcmap option configuring the cn dtcmap option
408 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] MGMT Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 0 cannot allocate Unable to allocate Restart the CCSS store for ccme cn memory for standby option configuring the cn standby option MAJOR 0 cannot allocate Unable to allocate Restart the CCSS store for ccme memory for default configuring the ccme default option MAJOR 0 cannot allocate Unable to allocate Restart the CCSS store for ccme memory for option configuring the ccme option MAJOR 0 cannot allocate link Unable to allocate None a link MAJOR 0 cannot allocate lset Unable to allocate None a link set MAJOR 0 cannot allocate Unable to allocate None cset combined link set MAJOR 0 cannot allocate Unable to allocate None rout a route MAJOR 0 cannot allocate Unable to allocate None Tcu_Timer_t Tcu Timer MAJOR 0 cannot allocate Unable to allocate None tgrp trunk group MAJOR 0 cannot allocate Allocation of None memory for sccp memory failed for local gt sccp local gt MAJOR 0 cannot allocate Allocation of None sccp local memory failed for sccp local node MAJOR 0 cannot allocate Failure in allocating None tcuser client memory for tcuser client MAJOR 0 cannot allocate Failure in allocating None tcuser host memory for tcuser host MAJOR 0 mgmt: node ptr is No configuration Check the null stored configuration in ss7.conf file
Avaya CCSS 1000/2000 Feature Documentation August 2013 409 Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 0 mgmt: ccme for fd Sending the None %d configuration details to CCME MAJOR 0 sending ccme Unable to send the None PROX_HOST proxy_host failed configuration to ccme MAJOR 0 sending ccme Unable to send the None TMS_HOST failed tms host configuration to CCME MAJOR 0 sending ccme Unable to send the None PROX_GRP failed proxy group configuration to CCME MAJOR 0 Invalid Invalid Check the configuration for configuration for configuration in TRK_GRP in trunk group ss7.conf file ss7.conf MAJOR 0 sending ccme Unable to send the None TMS_GRP failed tms group configuration to CCME MAJOR 0 sending ccme Unable to send the None DTCMAP failed dtcmap configuration to CCME MAJOR 0 sending ccme Failure in sending None STANDBY failed the configuration of CCME_CN_STAN DBY to ccme. MAJOR 0 Modifying Timer Sending the new None %d with %d... configuration of the timer to CCME MAJOR 0 sending ccme Failure in sending None TIMER failed the timer configuration to the ccme. MAJOR 0 sending ccme Unable to send the None DEFAULT failed default configuration to the ccme.
410 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] MGMT Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 0 sending ccme Failure in sending None OPTION failed the option configuration to ccme. MAJOR 0 sending Failure in sending None TCAP_GRS failed tcap configuration to ccme. MAJOR 0 sending ccme Unable to notify None CFG_STOP failed ccme of completion of the configuration items. MAJOR 0 Local ssn is not Local SSN None configured yet configuration not available. MAJOR 0 Invalid The configuration Check ss7.conf file. configuration for mentioned in TRK_GRP in ss7.conf file for ss7.conf TRK_GRP is invalid. MAJOR 0 bad configuration Invalid None for L4 configuration for ISUP. MAJOR 0 ToggleDebFlags Unable to toggle None failed the debug flags. MAJOR 0 Send_Msu gen Unable to send the None failed MSU MAJOR 0 mgmt: form_l4 for Configuring ISUP None type %d for the mentioned type. MAJOR 0 L4 gen failed Configuring ISUP None for general type failed. MAJOR 0 L4 config rout Configuration of Check out the failed. the routes failed. ss7.conf file. MAJOR 0 L4 sisap failed Failure in None configuring the SAP for ISUP layer. MAJOR 0 elmntInst1 = %d, Successful None spid = %d opc = configuration done with the mentioned
Avaya CCSS 1000/2000 Feature Documentation August 2013 411 Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required %d, ssf = %d var = entities like service %d provider sap id,.sub service selection and so on. MAJOR 0 L4 NSAP failed Failure in None configuring the network SAP for ISUP. MAJOR 0 L4 rout failed ISUP configuration None failed for route. MAJOR 0 L4 STICIR failed, Failure in None mismatch between configuring ISUP Node and Tgrp circuits due to DPC mismatch between node and trunk group DPC. MAJOR 0 L4 cir failed Failure in None configuring the circuits for ISUP. MAJOR 0 mgmt ERROR: Trying to configure Check out the Maximum number the system beyond ss7.conf file of Interface Iden the limit of allowed tifiers (DPC OPC maximum number combinations) if interface reached identifiers. MAJOR 0 invalid type for l4 Configuration None requested for ISUP with invalid type of configuration. MAJOR 0 mgmt ERROR: %d Restart request not None RESTART_REQD supported now. not supported %d MAJOR 0 SYNTAX ERROR: Syntax error in the None near '%.*s', line = command at %d mentioned string. MAJOR 0 mgmt: ccme_ctl Unable to send the None perm_send failed control for CCME. MAJOR 0 CCSSHOME is not Environment Verify that the defined variable package is installed CCSSHOME not properly. defined.
412 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] MGMT Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 0 cannot open file Unable to open Ensure that ss7.conf ss7.conf ss7.conf file. file exists with necessary permissions. MAJOR 0 mgmt: configuring Configuring the None host %s link %s mentioned link for the host. MAJOR 0 mgmt: Error Error in handling None handling Perm the mentioned event %d index %d perm event. which_Srv %d MAJOR 0 mgmt: Alarm Successful in None Connection establishing the established connection to Alarm. MAJOR 0 mgmt: L2 Successful in None Connection establishing the established to %s connection from MTP2 MAJOR 0 mgmt: error Error in configuring None configur ing routerif routerif for the for link %s mentioned link MAJOR 0 mgmt: error Error in configuring None configuring link %s the mentioned link. MAJOR 0 mgmt: TCUSER TCUSER client None Connection connected to established to %s MGMT. MAJOR 0 mgmt: CCME CCME client None Connection connected to established to %s MGMT. MAJOR 0 mgmt: L3 MTP3 client None Connection esta connected to blished to %s MGMT. MAJOR 0 mgmt: error Failure in None configuring routerif configuring routerif for mti for MTI. MAJOR 0 mgmt: %s MGMT lost None Connection lost %s connection to the mentioned client. MAJOR 0 mgmt: clients setup Clients setup failed None failed for MGMT.
Avaya CCSS 1000/2000 Feature Documentation August 2013 413 Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 0 No active Server configured None connection to the as a standalone remote server system. Remote server details not available. MAJOR 0 Remote System Remote system None State changed to state changed to %s the mentioned state. This is to intimate the major changes in the state of the remote server. MAJOR 0 mgmt: tcu_ctl perm send failed None perm_send failed for TCU control. MAJOR 0 Local System State Local system has None changed to %s And changed state to R emote server is the mentioned DEAD state while remote is DEAD. MAJOR 0 recording lset %s, Configuring the None link %s mentioned link set and link from ss7.conf file. MAJOR 0 recording cset %s, Configuring the None link %s mentioned combined link set and link from ss7.conf file. MAJOR 0 nature of address is Nature of address None out of range out of range for SCCP configuration. MAJOR 0 Numbering plan is Numbering plan None out of range mentioned in SCCP configuration is out of range. MAJOR 0 Encoding schem is Encoding scheme None out of range mentioned in SCCP configuration is out of range.
414 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] MGMT Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 0 recording Configuring the None sccp_local, id=%s, local SCCP from opc=%d ss7.conf file. MAJOR 0 recording Configuring the None sccp_network, id= SCCP network %s, dpc=%d, ssn= from SS7.conf file. %d\ MAJOR 0 recording Configuring None tcuser_client, id= TCUSER client %s, group=%d, from ss7.conf file. type=%s, vps=%d, line=%d MAJOR 0 "recording Recording tcUSER None tcuser_host, host configuration host_id=%s, from ss7.conf file. vas_id=%s MAJOR 0 recording Recording/ None redundant server configuring the redserv, host_id=% redundant server s details from ss7.conf file. MAJOR 0 SERVER ID should SERVER ID in the Check out the be either A or B redundant redundant server configuration can configuration be either A or B. command in Wrong server id ss7.conf file. mentioned in the configuration file. MAJOR 0 Maximum Two Maximum number Check out the hosts can be of hosts allowed for redundant server configured f or redundant configuration redundant server configuration is command in two. ss7.conf file. MAJOR 0 Maximum Two Maximum Ping Check out the Ping hosts can be hosts allowed for redundant server configured for configuring are configuration redundant server two. command in ss7.conf file. MAJOR 0 recording Configuring ccme None ccme_proxy_host proxy host from %s ss7.conf file MAJOR 0 Maximum Two Maximum number Check out the hosts can be of hosts allowed for ccme_proxy_host
Avaya CCSS 1000/2000 Feature Documentation August 2013 415 Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required configured f or configuring the configuration in ccme_proxy_host proxy host are two. ss7.conf file. MAJOR 0 recording Configuring ccme None ccme_tms_host TMS host from %s ss7.conf file MAJOR 0 Maximum Two Maximum number Check out the hosts can be of hosts allowed for ccme_proxy_host configured for c configuring the tms configuration in cme_tms_host host are two. ss7.conf file. MAJOR 0 ccme_proxy_grp ccme proxy group Check out the must be an already used in configuring CCME_PROXY_G configr ed the proxy should RP command in TRK_GRP number already be ss7.conf file. configured trunk group. MAJOR 0 host in Host in ccme proxy Check out the ccme_proxy_grp group must be CCME_PROXY_G must be an already already configured RP command in configured alias by by ss7.conf file. CCME_PROXY_H CCME_PROXY_H OST OST command. MAJOR 0 vps number in Zero is not the valid Check out the CCME_PROXY_G VPS number CCME_PROXY_G RP must be greater CCME_PROXY_G RP command in than ZERO RP configuration. ss7.conf file MAJOR 0 line number in Zero us invalid of Check out the CCME_PROXY_G LINe number in CCME_PROXY_G RP must be greater CCME_PROXY_G RP command in than ZERO RP configuration. ss7.conf file MAJOR 0 CCME_TMS_GRP ccme tms group Check out the must be an already used in configuring CCME_TMS_GRP configred the tms should command in TRK_GRP number already be ss7.conf file configured trunk group MAJOR 0 host in Host in ccme tms Check out the ccme_tms_grp group must be CCME_TMS_GRP must be an already already configured command in c onfigured alias by by ss7.conf file CCME_TMS_HOS CCME_TMS_HOS T T command MAJOR 0 span number in The valid range of Check out the CCME_TMS_GRP span for CCME_TMS_GRP
416 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] MGMT Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required must be in between CCME_TMS_GRP command in 1 and 8 is from 1 to 8. ss7.conf file MAJOR 0 grp in DTCMAP ccme proxy group Check out the must be an already used in CCME_CN_DTCM configred CCME_CN_DTCM AP _GRP command TRK_GRP number AP _GRP should in ss7.conf file already be configured trunk group. MAJOR 0 host in Host in Check out the CCME_CN_DTCM CCME_CN_DTCM CCME_CN_DTCM AP _GRP must be AP _GRP must be AP _GRP command an alr eady already configured in ss7.conf file configured alias by by CCME_TMS_HOS CCME_TMS_HOS T T command MAJOR 0 span number in The valid range of Check out the CCME_TMS_GRP span for CCME_CN_DTCM must be in between CCME_TMS_GRP AP _GRP command 1 and 8 is from 1 to 8 in ss7.conf file MAJOR 0 grp in STANDBY ccme proxy group Check out the must be an already used in CCME_CN_STAND configred CCME_CN_STAN BY _GRP command TRK_GRP number DBY _GRP should in ss7.conf file already be configured trunk group MAJOR 0 host in Host in Check out the CCME_CN_STAN CCME_CN_STAN CCME_CN_STAND DBY _GRP must DBY _GRP must BY _GRP command be an al ready be already in ss7.conf file configured alias by configured by CCME_PROXY_H CCME_PROXY_H OST OST command MAJOR 0 bad Timer The timer number Check out the mentioned in the CCME_TIMER ss7.conf file is not a command in valid timer number. ss7.conf file CRITICAL 0x010101 Could not allocate Unable to start ping None activate_ping_time timer. r CRITICAL 0x010101 Could not allocate Unable to allocate None SG enable retry SG enable retry timer timer.
Avaya CCSS 1000/2000 Feature Documentation August 2013 417 Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required CRITICAL 0x010101 Could not allocate Unable to allocate None confirm waiting confirm waiting timer timer. CRITICAL 0x010101 Could not allocate Unable to allocate None warmstart waiting warmstart waiting timer timer.
ISUP Alarms
The following table is a set of alarms associated with ISUP applications. They are displayed in the following manner:
Wed Dec 29 11:18:06 ISUP: Severity MAJOR code 3C Bind connection to ISUP re-established
Note: For details concerning setting the option values in the ccme0.conf file (if the old date format is required then set OLD_ALARM_DATE_FORMAT to 1).
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 01 Request received Bind Request to Fix configuration. If from ISUP user ISUP failed due to failure persists with Invalid SAP ID invalid SAP_ID. report to Avaya MAJOR 01 Connect request Application has Fix application received with no requested a non- circuit, transit N/W supported routing selector algorithm MAJOR 01 Request received Connect request Fix application for a circuit which is on an unequipped not configured circuit MAJOR 01 Request received Connect request to Fix application towards an non-configured interface which is circuit not configured MAJOR 01 Request received Connect request to Fix application on an unavailable non-available interface circuit.
418 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] ISUP Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 01 Connect request Connect Request If condition persists received on a busy attempted on a report to Avaya circuit circuit that is not idle MAJOR 01 Connect request Connect Request If condition persists received on a attempted on report to Avaya remotely blocked circuit that is circuit remotely blocked MAJOR 01 Lower SAP not MTP-3 SAP is in Report to Avaya Bound the unbound state MAJOR 01 Unexpected Event Unexpected event If condition persists received received on a report to Avaya connection MAJOR 01 Mismatch in The suInstid Report to Avaya suInstId received from Upper Layer does not match the one stored. MAJOR 01 Invalid suInstId Invalid suInstid Report to Avaya received from Upper Layer MAJOR 01 No route is Application has Fix application. configured for the requested a non- passed Called supported routing party number algorithm.is to be used for routing. MAJOR 01 No idle circuit Application has Fix application. available requested a non- supported routing algorithm is to be used for circuit selection. MAJOR 01 Number of Call The maximum If condition persists Reference is numbers of call report to Avaya exceeded references are in use. MAJOR 01 No memory Insufficient Report to Avaya. available for memory allocation connection control configured for the block system MAJOR 02 Status indication MTP-3 SAP is in Report to Avaya. from MTP3 on an the unbound state. invalid SAP
Avaya CCSS 1000/2000 Feature Documentation August 2013 419 Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 02 Invalid SCCP SAP SCCP SAP is in the Report to Avaya. unbound state MAJOR 05 UBL received in Unblock message If condition persists state IDLE received from report to Avaya. network for circuit in IDLE state. MAJOR 05 CGB received Circuit Group Block If condition persists when waiting for message received report to Avaya reset response from network when circuit group is waiting for reset response. MAJOR 05 CGU received Circuit Group If condition persists when waiting for Unblock message report to Avaya reset response received from network when circuit group is waiting for reset response MAJOR 05 Mismatch in The maintenance Report to Avaya. hardware and and hardware state Maintainence of the circuit do not states of the circuit match. MAJOR 101 No route is Application has Fix application. configured for the requested a non- passed TNS supported routing algorithm. MAJOR 103 User part available User part is None available. MAJOR 103 Remote User Remote User is If condition persists Unavailable unavailable. check configuration. MAJOR 103 Remote User Remote User is If condition persists Unequipped unequipped check configuration. MAJOR 104 REL received with REL received from None Congestion Level 1 network indicating congestion level 1. MAJOR 104 REL received with REL received from None Congestion Level 2 network indicating congestion level 2. MAJOR 104 Remote Block Block message None received received from the network.
420 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] ISUP Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 104 Remote unblock Unblock message None received received from the network. MAJOR 104 Invalid Range/ A mismatch Report to Avaya. Status in circuit between the range group message and status field of a received group message has occurred. MAJOR 105 REL Sent with Congestion level 1 Report to Avaya. Congestion Level 1 has occurred for resource availability MAJOR 105 REL Sent with Congestion level 2 Report to Avaya. Congestion Level 2 has occurred for resource availability. MAJOR 105 Local Block Request for a None Received circuit block sent to the network. MAJOR 105 Local unblock Request for a None Received circuit unblock sent to the network. MAJOR 105 Invalid range/ A mismatch Report to Avaya Status in circuit between the range group event and status field of a group event has occurred. MAJOR 106 CGB received with The range field in Report to Avaya Invalid range the received CGB is invalid. MAJOR 106 CGU received with The range field in Report to Avaya Invalid range the received CGU is invalid. MAJOR 106 Range mismatch A mismatch Report to Avaya between CQM and between the range CQR on the sent CGM and received CGR has occurred. MAJOR 107 Circuit in CGB The Report to Avaya response did not acknowledgement expect Block Ack identified a circuit not requested.
Avaya CCSS 1000/2000 Feature Documentation August 2013 421 Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 107 Circuit in CGU The Report to Avaya response did not acknowledgement expect UnBlock identified a circuit Ack not requested. MAJOR 108 Circuit Validation Circuit validation Report to Avaya response with test failed. failure indication MAJOR 108 Circuit Validation Circuit validation Report to Avaya response with test failed. Invalid CLLI MAJOR 108 Circuit Validation Circuit validation None response Success test was successful. MAJOR 0A Timer Expired A protocol timer Report to Avaya has elapsed.
MTP3 Alarms
The following table is a set of alarms associated with the MTP3 application. Alarms are displayed in the following manner:
Wed Dec 29 14:41:02 MTP3: Severity MAJOR code 4 [LSN_PROT_ST_DN : 1 LINK DOWN ]
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 8 LCM_EVENT_BN Failure in binding to None D _FAIL : Bind MTP3. Failure MAJOR 11 LCM_EVENT_BN Binding of MTP2 to None D _OK : Bind Ok MTP3 is successful MAJOR 100 LSN_PROT_ST_U Link has aligned None P : Link Up MAJOR 101 LSN_PROT_ST_D Link has gone Check network for N : Link Down down Link Out Of Service MAJOR 102 LSN_INH_DEN : Local link inhibit The last in service Link Inhibit Down has been denied link cannot be commanded inhibited. Check the
422 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] MTP3 Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required management command for errors MAJOR 103 LSN_UNINH_DEN Local link uninhibit Check the : Link Uninhibit has been denied management Denied command for errors MAJOR 104 LSN_EVENT_LOC Local link is None _INH_ACK: link Inhibited inhibited locally MAJOR 105 LSN_EVENT_RE Remote LInk None M _INH_ACK: link Inhibited inhibited remotely MAJOR 106 LSN_EVENT_LOC Local link is None _UNINHED : link UnInhibited un-inhibited locally MAJOR 107 LSN_EVENT_RE Remote LInk None M _UNINHED : link UnInhibited un-inhibited remotely MAJOR 110 LSN_RESUME : The destination None Concerned Dpc point code is Resume accessible. MAJOR 111 LSN_CONG : The destination Verify why the Concerned Dpc indicates network is Network congestion congested Congested MAJOR 112 LSN_SPTCONG : Congestion of the None Concerned Dpc network Dpc has Stop Network stopped Congestion MAJOR 113 LSN_RMTUSRUN A network user part Check the status of AV : Concerned has become the user part of the Dpc Remote User unavailable network Unavailable MAJOR 115 LSN_SDT_INV_D An internal error to Report to Avaya AT _DRP : Invalid MTP3 has been Data Dropped at detected SDT Interface. MAJOR 116 LSN_SNT_INV : An internal error to Report to Avaya Invalid Event at MTP3 has been SNT Interface detected
Avaya CCSS 1000/2000 Feature Documentation August 2013 423 Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 117 LSN_SDT_INV : An internal error to Report to Avaya Invalid Event at MTP3 has been SDT Interface detected MAJOR 118 LSN_LSNCFGRE Configuration None Q_OK : successful Configuration Success MAJOR 119 LSN_LSNCFGRE Configuration has Check the contents Q_NOK : failed of the SS7.conf file Configuration Failed MAJOR 120 LSN_EVENT_INV Invalid source Report to Avaya _SRCENT: Invalid Entity source Entity MAJOR 121 LSN_EVENT_INV Invalid OPC Check configuration _OPC_OTHER_E received of point codes ND : Invalid OPC received MAJOR 122 LSN_INV_SLC Invalid SLC None _OTHER_END : received Invalid SLC received. MAJOR 123 [SMSN] Concerned Dpc None LSN_EVENT_CRE Pause _HMAP_FLR: Concerned Dpc Pause 0x%lx MAJOR 124 LSN_EVENT_SLT Timeout Waiting for Check Network for : Timeout Waiting SLT link being enabled for SLT MAJOR 125 LSN_EVENT_PER Invalid SLTA Check IODIC_SLT : received Configuration of Invalid SLTA CCSS vs Network. received. MAJOR 126 LSN_EVENT_SRT Test Passed None EST: Test Passed MAJOR 126 LSN_EVENT_SRT Test Failed None EST: Test Failed MAJOR 126 [SMSN] STDLSAP Configured the None Link = %d mentioned link for data link SAP
424 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] MTP3 Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 126 [SMSN] STROUT Configured the None Linkset = %d route for the mentioned linkset. MAJOR 127 LSN_EVENT_DAT Invalid DPC Check configuration A _DRP : Invalid received. of point codes DPC received. MAJOR 10B LSN_UNINH_BLK Network has None D : Link Remotely remotely blocked Blocked this link MAJOR 10C LSN_RMT_UNBL Network has None KED : Link remotely Remotely unblocked this link Unblocked MAJOR 10D LSN_LOC_BLKD : The link has been None Link Locally locally blocked Blocked MAJOR 10E LSN_LOC_UNBLK The link has been None D : Link Locally locally unblocked Unblocked MAJOR 10F LSN_PAUSE : The destination None Concerned Dpc point code is Pause inaccessible. MAJOR 11A LSN_LSNSTARE Status Request None Q _OK : Status Success Request Success MAJOR 11B LSN_LSNSTARE Status request has Verify the syntax of Q _NOK : Status failed the status command Request Failed MAJOR 11C LSN_LSNSTSRE Statistics Request None Q _OK : Statistics Success Request Success MAJOR 11D LSN_LSNSTSRE Status request has Verify the syntax of Q _NOK : Statistics failed the statistics request Request Failed MAJOR 11E LSN_LSNCNTRLR Control Request None EQ_OK : Control Success Request Success MAJOR 11F LSN_LSNCNTRLR A control request Verify the syntax of EQ_NOK : Control has failed the command which Request Failed was issued
Avaya CCSS 1000/2000 Feature Documentation August 2013 425 Alarms
MTP2 Alarms
The following table is a set of alarms associated with the MTP2 application. Alarms are displayed in the following manner:
Wed Dec 29 14:41:02 MTP2: Severity MAJOR code 7 [LINK MANAGER: 1 LINK ALIGNED ]
Alarm Code Message Displayed Description Resolution Level Required MAJOR 1 [ LINK MANAGER : MTP2 has Let the system run for Entering overwhelmed its 10-20 minutes. If the CONGESTION ] transmission buffer alarm is still displayed, capture the alarm and send it to Avaya. MAJOR 2 [ LINK MANAGER : MTP2 cleared out the None Exiting transmission buffer. CONGESTION ] This indicates that the system is back to its normal state. MAJOR 3 [ LINK MANAGER : When L1 received None LINK UP ] the first message from the link, it sent connection confirmation to L2. MAJOR 4 [ LINK MANAGER : Physical link is None LINK DOWN ] disconnected or a request from MTP3 to disconnect L1. MAJOR 5 [ LINK MANAGER : Received message None PROTOCOL which violates SS7 ERROR ] (blue book) protocol specification. eg.: FSN is out of sequence. MAJOR 7 [ LINK MANAGER : L1 and L2 are in Capture the alarm LINK ALIGNED ] service. and send to Avaya MAJOR 8 [ LINK MANAGER : L1 is still connected, Capture the alarm ALIGNMENT LOST ] but L2 is out of and send to Avaya service.
426 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] MTP2 Alarms
Alarm Code Message Displayed Description Resolution Level Required MAJOR 9 [ LINK MANAGER : L2 has received bind Bind by upper layer and enable from failed ] MTP3. But l2 configuration has not ben done, or the link number is out of range, or SAP pointer is NULL. MAJOR 10 [ LINK MANAGER : Connection request Normally a UidiscReq failed ] from MTP2 to MTP3 configuration error. failed Check the SS7.conf file and examine the SLC parameter. If problem continues to exist, connect tip cable to com1000 card. Capture the dump from the terminal and send to Avaya. MAJOR 11 [ LINK MANAGER : Flow control request Connect tip cable to UiFlcReq failed ] from MTP2 to MTP3 com1000 card. failed Capture the dump from the terminal and send to Avaya. MAJOR 12 [ LINK MANAGER : Upper interface Connect tip cable to UiStaReq failed ] status request failed. com1000 card. Capture the dump from the terminal and send to Avaya. MAJOR 13 [ LINK MANAGER : Lower interface Connect tip cable to LiConCfm failed ] status request failed. com1000 card. Capture the dump from the terminal and send to Avaya. MAJOR 14 [ LINK MANAGER : Interface between Connect tip cable to LiDiscInd failed ] MTP2 and MTP1 com1000 card. disconnection failed. Capture the dump from the terminal and send to Avaya. MAJOR 15 [ LINK MANAGER : Interface between Connect tip cable to LiDatInd failed ] MTP2 and MTP1 com1000 card. failed on data Capture the dump indication from the terminal and send to Avaya.
Avaya CCSS 1000/2000 Feature Documentation August 2013 427 Alarms
Alarm Code Message Displayed Description Resolution Level Required MAJOR 16 [ LINK MANAGER : Interface between Connect tip cable to LiStaCfm failed ] MTP1 and MTP2 com1000 card. failed on status Capture the dump confirm from the terminal and send to Avaya. MAJOR 17 [ LINK MANAGER : Data confirm failed Connect tip cable to LiDatCfm failed ] between MTP1 and com1000 card. MTP2 Capture the dump from the terminal and send to Avaya. MAJOR 18 [ LINK MANAGER : Status indication Connect tip cable to LiStaInd failed ] failed between MTP1 com1000 card. and MTP2 Capture the dump from the terminal and send to Avaya. MAJOR 19 [ LINK MANAGER : Status request Connect tip cable to MiStaReq failed ] between com1000 card. management and Capture the dump MTP2 failed from the terminal and send to Avaya. MAJOR 20 [ LINK MANAGER : RTB (Retransmit Connect tip cable to RTB FULL OVER, Buffer) queue has com1000 card. time, fsnf, rtbLen, been cleared. Capture the dump ltxLen, OF ] from the terminal and send to Avaya. MAJOR 21 [ LINK MANAGER : Negative Capture the alarm NEG ACK, time, Acknowledgement and send to Avaya. glen ] MAJOR 22 [ LINK MANAGER : Report of number of Capture alarm and DAT_CFM_SDT, date frame has been send to Avaya time, credit ] confirmed. MAJOR 23 [ LINK MANAGER : L2 has received SIB Leave the system SD_RX_REMOTE_ (Status Identification running for 10 - 15 CONG_START, Busy) from remote minutes. If problem time, llSt ] system. persists, capture alarm and send to Avaya. MAJOR 24 [ LINK MANAGER : L2 receives SIB clear Indication is OK SD_RX_REMOTE_ from remote system CONG_END, time, llSt ]
428 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] MTP2 Alarms
Alarm Code Message Displayed Description Resolution Level Required MAJOR 25 [ LINK MANAGER : Indicates MTP3 of Check the remote SD_RX_REMOTE_ the remote system system (which can be SIPO, time, llSt ] has gone down switch or network) MAJOR 0A [ LINK MANAGER : MTP3 has sent bind Connect tip cable to Bind to MAC layer request to MTP2 com1000 card. failed ] which cannot send Capture the dump the request to from the terminal and MTP1. send to Avaya. MAJOR 0B [ LINK MANAGER : Unbind happened Normally a Unbind by upper before bind or link configuration error. layer failed ] assignment not Check the SS7.conf correct. file and examine the SLC parameter. If problem continues to exist, connect tip cable to com1000 card. Capture the dump from the terminal and send to Avaya. MAJOR 0C [ LINK MANAGER : Unbind happened Normally a Unbind to MAC layer before bind. This is a configuration error. failed ] request from MTP2 Check the SS7.conf to MTP1. file and examine the SLC parameter. If problem continues to exist, connect tip cable to com1000 card. Capture the dump from the terminal and send to Avaya. MAJOR 0D [ LINK MANAGER : Disconnect Normally a Disconnect with MAC happened before configuration error. layer failed ] connect. This is a Check the SS7.conf request from MTP2 file and examine the to MTP1. SLC parameter. If problem continues to exist, connect tip cable to com1000 card. Capture the dump from the terminal and send to Avaya.
Avaya CCSS 1000/2000 Feature Documentation August 2013 429 Alarms
Alarm Code Message Displayed Description Resolution Level Required MAJOR 0E [ LINK MANAGER : MTP2 to MTP3 failed Normally a Upper connect configuration error. failed ] Check the SS7.conf file and examine the SLC parameter. If problem continues to exist, connect tip cable to com1000 card. Capture the dump from the terminal and send to Avaya. MAJOR 0F [ LINK MANAGER : Data request from Connect tip cable to UiDatReq failed ] MTP2 to MTP3 com1000 card. failed. Capture the dump from the terminal and send to Avaya. MAJOR 1A [ LINK MANAGER : Statistic request Connect tip cable to MiStsReq failed ] between com1000 card. management and Capture the dump MTP2 interface failed from the terminal and send to Avaya. MAJOR 1B [ LINK MANAGER : Control request Connect tip cable to MiCntrlReq failed ] between com1000 card. management and Capture the dump MTP2 interface failed from the terminal and send to Avaya. MAJOR 1C [ LINK MANAGER : L2 has received Check SS7.conf file Configuration Failed ] configuration data from mgmt. Configuration data is incorrect. MAJOR 1D [ LINK MANAGER : L2 has received None Configuration OK ] configuration data from mgmt. Configuration data structures are filled OK. MAJOR 1E [ LINK MANAGER : Control request Connect tip cable to MiCntrlReq successful ENABLE com1000 card. succeeded ] \DISABLE Capture the dump from the terminal and send to Avaya.
430 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] MTP1 Alarms
Alarm Code Message Displayed Description Resolution Level Required MAJOR 1F [ LINK MANAGER : RTB (Retransmit Connect tip cable to RTB FULL, time, fsnf, Buffer) has exceeded com1000 card. rtbLen, ltxLen, OF ] maximum. (127) Capture the dump from the terminal and send to Avaya.
MTP1 Alarms
The following table is a set of alarms associated with the MTP1 application. Alarms are displayed in the following manner:
Wed Dec 29 14:41:02 MTP1: Severity MAJOR code 1 [LINK MANAGER: 1 LINK UP]
Alarm Code Message Displayed Description Resolution Level Required MAJOR 3 [ LINK MANAGER : MTP1 is up None LINK UP ] MAJOR 4 [ LINK MANAGER : MTP1 has gone Check signaling link LINK DOWN ] down cable. It may be broken. MAJOR 101 [ LINK MANAGER : The transmission Let the system run for hex LQI_TXQUEUE_FU queue of MTP1 is full 10 - 20 minutes. If LL ] problem persists, capture the alarm and send it to Avaya. MAJOR 102 [ LINK MANAGER : Configuration of Check hex LQI_USTA_CFG_N MTP1 is not $CCSSHOME/etc/ OK ] successful. ss7.conf file. If problem persists, capture alarm and send it to Avaya. MAJOR 103 [ LINK MANAGER : MTP1 general Check hex LQI_USTA_GENCF configuration is not $CCSSHOME/etc/ G_NOK ] successful. ss7.conf file. If problem persists, capture alarm and send it to Avaya.
Avaya CCSS 1000/2000 Feature Documentation August 2013 431 Alarms
Alarm Code Message Displayed Description Resolution Level Required MAJOR 104 [ LINK MANAGER : MTP1 general None hex LQI_USTA_GENCF configuration is G_OK ] successful MAJOR 105 [ LINK MANAGER : MTP1 Signaling Capture the alarm hex LQI_USTA_SAPCF Access Point and send to Avaya G_NOK ] configuration is not successful. MAJOR 106 [ LINK MANAGER : MTP1 Signaling None hex LQI_USTA_SAPCF Access Point is G_OK ] successful MAJOR 107 [ LINK MANAGER : MTP1 control None hex LQI_USTA_CNTRL request is REQ_OK ] successful. The system is operating normally. MAJOR 108 [ LINK MANAGER : MTP1 control Capture the alarm hex LQI_USTA_CNTRL request is not and send to Avaya REQ_NOK ] successful MAJOR 17 hex [ LINK MANAGER : MTP1 detects lost of Capture the alarm LINK DOWN Clear To Send (CTS) and send to Avaya (NOCTS1) ] during transmit data. MAJOR 18 hex [ LINK MANAGER : MTP1 detects the Capture the alarm LINK DOWN (LIDL) ] line is idle and send to Avaya MAJOR 1A hex [ LINK MANAGER : MTP1 detects loss of Capture the alarm LINK DOWN Clear To Sound and send to Avaya (NOCTS2) ] (CTS) during receiving of data. MAJOR 1B hex [ LINK MANAGER : MTP1 detects loss of Capture the alarm LINK DOWN Carrier Detect (CD) and send to Avaya (NOCD) ] MAJOR 1C hex [ LINK MANAGER : The dynamic Capture the alarm QI_NOT_ENOUGH_ memory pool is full. and send to Avaya RES ] MTP1 cannot allocate buffer to hold data.
432 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] SCCP Alarms
SCCP Alarms
The following table is a set of alarms associated with the SCCP application. Alarms are displayed in the following manner:
Wed Dec 29 14:41:02 SCCP: Severity MAJOR code 3 configuration request ok
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 0x0003 configuration The SCCP layer None request ok has accepted a configuration command. MAJOR 0x0004 configuration The SCCP layer Check the request not ok has found an error configuration of the in a configuration SS7.conf file. command. MAJOR 0x0005 control request ok The SCCP layer None has accepted a control request. MAJOR 0x0006 control request not The SCCP layer Validate the ok has rejected a command which control request. was just entered. MAJOR 0x0007 status request ok The SCCP layer None has accepted a status request. MAJOR 0x0008 status request not The SCCP layer Validate the ok has rejected a command which status request. was just entered. MAJOR 0x0009 statistics request The SCCP layer None ok has accepted a statistics request. MAJOR 0x000a status request not The SCCP layer Validate the ok has rejected a command which statistics request. was just entered. MAJOR 0x0001 invalid event at An invalid event Report to Avaya. SPT interface was detected by the SCCP.
Avaya CCSS 1000/2000 Feature Documentation August 2013 433 Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 0x0002 invalid event at An invalid event Report to Avaya. SNT interface was detected by the SCCP. MAJOR 0x0100 User in service - An SCCP None suid =%d subsystem has come into service. MAJOR 0x0101 User out of service An SCCP Check the network - suid = %d subsystem has gone out of service. MAJOR 0x0102 Routing error The SCCP layer Check the has detected an configuration of error while routing SCCP routes. a message. MAJOR 0x0103 bind on bound sap The TCAP layer None has bound to SCCP twice MAJOR 0x0104 syntax error A network Examine Analyzer message was traces. Report to received which Avaya. contains invalid data.
TCAP Alarms
The following table is a set of alarms associated with the TCAP application. Alarms are displayed in the following manner:
Wed Dec 29 11:19:08 TCAP: Severity MAJOR code 114 Bind ok
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 0x0101 Message buffer The TCAP layer Report to Avaya. allocation failure has encountered a memory allocation error. MAJOR 0x0102 Static memory The TCAP layer Report to Avaya allocation failed has encountered a
434 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] TCAP Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required memory allocation error. MAJOR 0x0103 Duplicate Invoke Id The TCAP layer Report to Avaya has received a component with a duplicate invoke ID MAJOR 0x0104 Mandatory element Missing component Check application missing in Uni-directional message. MAJOR 0x0105 Unexpected The TCAP has Check application message received received and unexpected message. This may be a duplicate BEGIN or END from the application MAJOR 0x0106 Unrecognized Invalid message Report to Avaya message type received from received TCUSER MAJOR 0x0107 Invalid dialogue Id An invalid Report to Avaya range configuration request was made MAJOR 0x0108 Unrecognized An invalid Invoke Report to Avaya Invoke Id ID was encountered. MAJOR 0x0109 Dialogue id A memory Report to Avaya. allocation failure allocation error has occurred. MAJOR 0x010a Hashing failure A hash table error Report to Avaya. has been encountered MAJOR 0x010b Max configuration The system has Report to Avaya reached exceeded some maximum configuration MAJOR 0x010c Invalid component An invalid Check the event structure component has component data in values in CmpReq been passed to the MPS Developer primitive TCAP application.
Avaya CCSS 1000/2000 Feature Documentation August 2013 435 Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 0x010d General TCAP has been None Unconfiguration unconfigured OK successfully. MAJOR 0x0114 Bind OK TCUSER has been None bound to TCAP successfully. MAJOR 0x0115 General General TCAP None configuration OK configuration has been successful MAJOR 0x0116 SAP configuration Configuration of None OK the TCUSER Service Access Point (SAP) is ok. MAJOR 0x0117 General An error was Report to Avaya. configuration Not encountered OK during the TCAP general configuration. MAJOR 0x0118 SAP configuration An error was Report to Avaya. Not OK encountered during SAP configuration.
TCU Alarms
The following table is a listing of alarms that the TCU process may generate on the CCSS console. Where appropriate, perform the suggested resolution.
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 0x10100 ccme startup TCU has None complete on sp %d completed startup and is ready to service dialogues. CRITICAL 0x010101 TCU: Could not Could not allocate Report to Avaya allocate specific internal activate_activate_ti timer mer sp %d TCU: Could not allocate activate_server_ti
436 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] TCU Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required mer sp %d TCU: Could not allocate activate_ping_time r sp %d TCU: Could not allocate activate_1sec_tim er sp %d TCU: Could not allocate Connection check activate_connect timer sp %d TCU: Could not allocate must reset timer sp %d group %d TCU: 1 second timer not running, restarting TCU: Connection check timer not running, restarting TCU: Ping timer not running, restarting TCU: server timer not running, restarting tcu: Could not allocate activate_smif_time r sp %d tcu: Could not allocate UOS Timer tcu: Could not allocate activate_mtp_timer sp %d tcu: Could not allocate KeepAlive timer sp %d VAS %s tcu: Could not allocate invoke_timer CRITICAL 0x10101 tcu: Could not TCU failed to Report to Avaya and allocate allocate a timer restart CCSS invoke_timer instance MAJOR 0x10110 Config File %s Not Error occurred Verify that the Found or error when attempting to CCME configuration CCME: DEST access the TCU file exists. registration failed configuration file. Fix error in the CCME: SOURCE A line containing CCME configuration registration failure the keyword DEST/ file SOUREC/DPC in
Avaya CCSS 1000/2000 Feature Documentation August 2013 437 Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required CCME: DPC the configuration registration failed file is in error. TCU: Required SERVER line not found in ccme config file!!! CRITICAL 0x10114 CCME: TIMER CCME Fix the configuration registration failure configuration file file and restart the CCME: OPTION contains a line with CCSS registration failure a specific keyword CCME: Overlap which contains an option registration error. failure CCME: SERVER registration failure FATAL 0x10115 TCU: Select failed Internal error Report to Avaya error %d reported from select FATAL 0x10115 TCU: Internal error Report to Avaya and Communication reported from restart CCSS failure bad file select descriptor INFO 0x10116 TCU: Connection All lines between Verify the VAS is up. totally lost VAS %s the CCSS and the Check Ethernet. TCU: Connection VAS listed as Verify the VAS is up. partially lost VAS down. Check Ethernet. %s One of the Report to Avaya TCU: Unknown redundant LANs read error from between the CCSS VAS %d and the VAS has gone down. An error has occurred reading data from a VAS. FATAL 0x10117 tcu: ccme/proxy There is a version Verify installation. version mismatch mismatch between cannot start tcu and proxy. MAJOR 0x10124 TCU: redundancy This CCSS server None active service has just become commencing the active server. CRITICAL 0x10124 tcu: Could not TCU failed to Report to Avaya allocate Inbq timer allocate a timer spdlgid %d ", instance spdlgid
438 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] TCU Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 0x10124 TCU: System TCU is in activating None Activation state MAJOR 0x10124 TCU Commanding TCU enable the None Vas to GO traffic from tcap proxy MAJOR 0x10125 tcu redundancy This CCSS server None standby service has just become commencing the standby server MAJOR 0x10125 TCU Commanding TCU disable the None Vas to STOP traffic from tcap proxy MAJOR 0x10130 (%s) TCU: Communication None Communication with the VAS has with VAS restored been restored. MAJOR 0x10131 (%s) TCU: Communication Verify that the VAS Communication with the VAS has is up. with VAS lost been lost MAJOR 0x10133 TCU got PAUSE - The changed state Verify signaling links pc %d of a Destination are available Point Code: Signaling Point inaccessible MAJOR 0x10133 TCU got SCCP CCSS reports None INACC - pc %d remote SCCP inaccessible MAJOR 0x10134 TCU got RESUME The changed state None - pc %d of a Destination Point Code: Signaling Point accessible MAJOR 0x10134 TCU got SCCP CCSS reports None ACC - pc %d remote SCCP become accessible MAJOR 0x10135 TCU got The changed state None CONGESTION - pc of point congested %d MAJOR 0x10136 TCU got SSN OUT The changed state Verify signaling links OF SERVICE - ssn od the subsystem are available. %d, pc %d user: Out of service
Avaya CCSS 1000/2000 Feature Documentation August 2013 439 Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 0x10137 TCU got SSN IN The changed state None SERVICE - ssn of the subsystem %d, pc %d user: In service MAJOR 0x10138 TCUSER: Receive Received Get cause from U_ABORT on U_ABORT from application. application peer Check application (%s/%d/%d) dlgid= Received status %d P_ABORT from TCUSER: Receive peer P_ABORT on application (%s/%d/%d) dlgid= %d MAJOR 0x10139 TCUSER: No Can't find the Check application application application status available for trans: attached for this dlgid %d, pc %d dlgid. TCUSER: No application available for comp dlgid %d MAJOR 0x10139 TCU: No TCU aborted the Check application Application transaction request status Available for from the peer due inbound request to the lack of in- spdlgid:%d service application MAJOR 0x10140 TCUSER: Drop Drop unexpected None unexpected component Verify application inbound message from logic component %d, TCAP layer dlgid=%d Drop unexpected TCUSER: Drop component unexpected message from the application application. (%s/%d/%d) component %d MAJOR 0x10141 Invalid Application TCU detected a Fix errors in UData Received malformed user application for data in the mode DMS_Internal_IP folder for Internal IP ACG, which caused a GetFail response to the application.
440 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] TCU Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required INFO 0x10141 Received Large The user data Report to Avaya udata in Dlg received in the Portion: %d bytes dialogue portion exceeded the maximum size defined in folder INFO 0x10141 Unknown stu Internal Error. Report to Avaya component type Unrecognized %d component type received in TCU MAJOR 0x10141 Broadcast %s to All TCU broadcasts None configured app condition to all application MAJOR 0x10141 Broadcast %s to TCU broadcasts None Group %d condition to specific group MAJOR 0x10142 (%d,%d) The operation is Fix errors in the STU_REJECT rejected by the application Local status:%d local system ProbFlag:%d ProbCode:%d MAJOR 0x10142 (%d,%d) The operation is Fix errors in the STU_REJECT rejected by the application Remote ProbFlag: remote system %d ProbCode:%d MAJOR 0x10143 (%d,%d) Bad Unexpected event Fix errors in the Dialogue State received at certain application Event %s at state dialogue state, %s which caused an abortion MAJOR 0x10144 (%d,%d) Bad Unexpected event Fix errors in Application State arrived at TCU application. Event %s at state application state %s Dialog Event machine, which %s caused an abort to both application and network MAJOR 0x10145 TCU RemoteUOS Remote sub- None Timeout Abort - ssn system out of %d, pc %d service timer expired. TCU broadcast notify event to all registered
Avaya CCSS 1000/2000 Feature Documentation August 2013 441 Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required application which may cause the abortion of transactions. FATAL 0x10017 ccme/proxy version There is a version Verify installation. mismatch cannot mismatch between start the CCME and TCAPproxy MAJOR 0x1011c CCME: terminating TCU is terminating None on signal %d due to receiving of CCME: terminating signal. on sp %d MAJOR 0x1012f TCU: Remote The redundant None server not server is not responding, force responding. this server active\n This server is TCU: Remote activating. server alive MAJOR 0x1013a TCUSER: Invoke Invoke timer None %d timeout, dlgid= expired %d, send CANCE to APP (%s/%d/%d) MAJOR 0x1013b TCUSER: Send Application sends None application abort (%s/%d/%d) ABORT dlgid=%d MAJOR 0x1013c TCUSER: send Abort uncleared None ABORT %d in APP dialogue when (%s/%d/%d) GET application issued TCUSER: send GET ABORT %d in APP Abort uncleared (%s/%d/%d) FREE dialogue when TCUSER: send application issued ABORT spdlgid %d FREE [%d] [%d] in UI kill Abort dialogue by command ui kill commands TCUSER: send Abort dialogue by ABORT spdlgid %d ui reset command [%d] [%d] in UI RESET command MAJOR 0x1013d TCUSER: Drop Drop unexpected Fix errors in unexpected transaction application application
442 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] PERM Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required (%s/%d/%d) message from the transaction %d application MAJOR 0x1013f TCUSER: Drop Drop unexpected None unexpected transaction inbound message from transaction %d, TCAP layer dlgid=%d
PERM Alarms
PERM alarms are generated when there is a loss of connection between any two process. The following is the format of the alarm message:
PERM %d: stalled connection to %s index %d timeout %d seconds blocked %d and the stall occurs due to %s failure The first %s in the message represents the character string which will contain IP address and the port number of the stalled connection. The second %s provides the appropriate client server connection layers where the stall occurs. Example: PERM: stalled connection to 97.151.121.1:5303 index 6 timeout 4 seconds blocked 0 and the stall occurs due to Config - Layer connection failure Here 97.151.121.1 is the IP address of the CCSS server and 5303 is the port number of the stalled connection. Config - Layer connection specifies the layer where the stall occurs. The following table lists the port number and its corresponding client server process. Contact Avaya for further assistance.
Alarm Alarm Message Description Resolution Level Code Displayed Required INFO 0 PERM %d: stalled Socket connection Report to Avaya connection to %s lost between Call index %d timeout Control and ISUP. %d seconds The associated blocked %d and the port for this socket stall occurs due to is 5300. Call Control to ISUP socket connection failure. INFO 0 PERM %d: stalled Socket connection Report to Avaya connection to %s lost between index %d timeout Layer3 and Layer2. %d seconds The associated
Avaya CCSS 1000/2000 Feature Documentation August 2013 443 Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required blocked %d and the port for this socket stall occurs due to is 5301. Layer 3 to Layer 2 socket connection failure. INFO 0 PERM %d: stalled Socket connection Report to Avaya connection to %s lost between index %d timeout Config and Layer. %d seconds The associated blocked %d and the port for this socket stall occurs due to is 5302. Config to Layer socket connection failure. INFO 0 PERM %d: stalled Socket connection Report to Avaya connection to %s lost between Layer index %d timeout and Alarm. The %d seconds associated port for blocked %d and the this socket is 5303. stall occurs due to Layer to Alarm socket connection failure. INFO 0 PERM %d: stalled Socket connection Report to Avaya connection to %s lost in Layer2 index %d timeout Debug. The %d seconds associated port for blocked %d and the this socket is 5304. stall occurs due to Layer2 Debug socket connection failure. INFO 0 PERM %d: stalled Socket connection Report to Avaya connection to %s lost between Call index %d timeout Control and User %d seconds Interface. The blocked %d and the associated port for stall occurs due to this socket is 5305. Call Control User Interface socket connection failure. INFO 0 PERM %d: stalled Socket connection Report to Avaya connection to %s lost between Call index %d timeout Control and %d seconds BTOSS. The blocked %d and the
444 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] PERM Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required stall occurs due to associated port for Call Control to this socket is 5306. BTOSS socket connection failure. INFO 0 PERM %d: stalled Socket connection Report to Avaya connection to %s lost between Stack index %d timeout manager and %d seconds Status Trace. The blocked %d and the associated port for stall occurs due to this socket is 5307. Stack Manager Status Trace Interface socket connection failure. INFO 0 PERM %d: stalled Socket connection Report to Avaya connection to %s lost between index %d timeout CCME/TCU. The %d seconds associated port for blocked %d and the this socket is 5308. stall occurs due to CCME/TCU Redundancy socket connection failure. INFO 0 PERM %d: stalled Socket connection Report to Avaya connection to %s lost in MGMT User index %d timeout Interface. The %d seconds associated port for blocked %d and the this socket is 5309. stall occurs due to MGMT User Interface socket connection failure. INFO 0 PERM %d: stalled Socket connection Report to Avaya connection to %s lost between TCIF index %d timeout and User Interface. %d seconds The associated blocked %d and the port for this socket stall occurs due to is 5310. TCAP User Interface socket connection failure. INFO 0 PERM %d: stalled Socket connection Report to Avaya connection to %s lost between TCAP index %d timeout and User Interface. %d seconds The associated
Avaya CCSS 1000/2000 Feature Documentation August 2013 445 Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required blocked %d and the port for this socket stall occurs due to is 5312. TCAP User Interface socket connection failure. INFO 0 PERM %d: stalled Socket connection Report to Avaya connection to %s lost between index %d timeout MGMT and TCAP %d seconds User Interface. The blocked %d and the associated port for stall occurs due to this socket is 5313. MGMT to TCAP User Interface socket connection failure. INFO 0 PERM %d: stalled Socket connection Report to Avaya connection to %s lost with DSSI index %d timeout Interface. The %d seconds associated port for blocked %d and the this socket is 5314. stall occurs due to DSSI(CcExt) Interface socket connection failure. INFO 0 PERM %d: stalled Socket connection Report to Avaya connection to %s lost with Router index %d timeout Interface. The %d seconds associated port for blocked %d and the this socket is 5315. stall occurs due to Router Interface Port socket connection failure. INFO 0 PERM %d: stalled Socket connection Report to Avaya connection to %s lost between Call index %d timeout Control PSF. The %d seconds associated port for blocked %d and the this socket is 5316. stall occurs due to Call-Control check pointing socket connection failure. INFO 0 PERM %d: stalled Socket connection Report to Avaya connection to %s lost between index %d timeout MGMT and Call %d seconds Control Interface.
446 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Agent Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required blocked %d and the The associated stall occurs due to port for this socket MGMT to CCME is 5317. Interface socket connection failure. INFO 0 PERM %d: stalled Socket connection Report to Avaya connection to %s lost with Stack index %d timeout Manager Interface. %d seconds The associated blocked %d and the port for this socket stall occurs due to is 3500. Stack Manager Interface socket connection failure.
Agent Alarms
The following table is a set of alarms associated with the FT Agent. Where appropriate, perform the suggested resolution.
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 4 Invalid Parameter Invalid Parameter If condition persists Value value received report to Avaya from the destination. MAJOR 4 Invalid Event Invalid event If condition persists occurred in the report to Avaya agent. MAJOR 9 NAK received from Negative Observe the reason destination acknowledge for the negative received from acknowledge destination MAJOR 10 timeout when Timed out when None waiting for reply waiting for a reply.
Avaya CCSS 1000/2000 Feature Documentation August 2013 447 Alarms
Router Alarms
The following table is a set of alarms associated with the FT Router. Where appropriate, perform the suggested resolution.
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 3 Peer interface Invalid event If condition persists invalid event received from peer report to Avaya interface. MAJOR 4 Invalid event Invalid event. If condition persists report to Avaya MAJOR 4 Invalid state Invalid state If condition persists report to Avaya MAJOR 7 Management Invalid event If condition persists interface invalid received from report to Avaya event management interface. MAJOR 100 Memory Buffer not Memory not Report to Avaya available available. MAJOR 101 Invalid resource set If condition persists report to Avaya MAJOR 102 Invalid sequence Invalid sequence If condition persists number in update number in the report to Avaya message update message. MAJOR 103 Invalid sequence Invalid sequence If condition persists number in update number in the report to Avaya ack received update ack message
Manager Alarms
The following table is a set of alarms associated with the FT Manager.Where appropriate, perform the suggested resolutionManager.
448 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Manager Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 101 Alarm Event Alarm event None Violation Violation MAJOR 102 Uneven Uneven None Redistribution Redistribution MAJOR 102 Even Even None Redistribution Redistribution MAJOR 103 Invalid Event Invalid Event If condition persists report to Avaya MAJOR 104 Entity Out of System manager None service due to OAM out of service due command to operation and maintenance command MAJOR 105 Entity Active due to System manager in None OAM command active due to operation and maintenance command MAJOR 106 Entity Standby due System manager in None to OAM comman standby due to operation and maintenance command MAJOR 107 Entity Master due System manager is None to OAM comman the master due to operation and maintenance command MAJOR 109 OAM command OAM command If condition persists Failue, NAK failed. Negative report to Avaya received acknowledge received. MAJOR 109 OAM command OAM command If condition persists Failue,Timeout failed and timed report to Avaya out. MAJOR 109 OAM command OAM command If condition persists Failure,No failed as there is no report to Avaya response from sys response from component system component MAJOR 10A Lost Heart Beat No response from Check the state of Event the standby. standby server
Avaya CCSS 1000/2000 Feature Documentation August 2013 449 Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 10A Event event sequence None Standby_OSS Out from standby is of Sequence invalid MAJOR 10A Event Bad update from None Standby_OSS: standby Bad Update MAJOR 10A Event Standby is in bad None Standby_OSS: state Standby Bad State
PSF-MTP3 Alarms
The following table is a set of alarms associated with the FT PSF-MTP3.
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 13 Memory Allocation Failure in dynamic Report to Avaya failure memory allocation. MAJOR 16 Incorrect Update Incorrect update None message message received. MAJOR 17 Heartbeat Timer Heartbeat timer None expired expiry
PSF-ISUP Alarms
The following table is a set of alarms associated with the FT PSF-ISUP.
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 6 Protocol Layer not ISUP layer not yet None active active MAJOR 13 Memory Allocation Failure in dynamic Report to Avaya failure allocation of the memory MAJOR 14 Runtime sequence Error in sequence None Error number.
450 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] VO (DCC3K) Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 16 Incorrect Update Incorrect update None MSG received message received from peer.
VO (DCC3K) Alarms
The following table is a set of alarms associated with the VO (DCC3K).
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 1 BndReq Bind Request None succeeded and succeeded and interface compiled interface compiled without correct flag without correct flag. MAJOR 258 VoUiMacUbndReq Binding request for None succeed MAC(Media Access Control) SAP to its service user is succeeded. MAJOR 7 Null pointer used in A NULL Vo Report to Avaya statistics request Management pointer was used for a statistics request. MAJOR 7 Null pointer used in A NULL Vo Report to Avaya status request Management pointer was used for a status request. MAJOR 7 Null pointer used in A NULL Vo Report to Avaya control request Management pointer was used for a control request. MAJOR 7 Unknow cause for Unknown cause for Report to Avaya Management Management interface invalid interface invalid event event
Avaya CCSS 1000/2000 Feature Documentation August 2013 451 Alarms
Alarm Alarm Message Description Resolution Level Code Displayed Required MAJOR 1 Incorrect Update Invalid service Report to Avaya MSG received provider ID (spId) given as parameter MAJOR 262 Receiver BD table Receiver BD table None busy busy MAJOR 262 Interrupt queue Interrupt queue None overflow overflow MAJOR 262 Transmitter Transmitter None underrun underrun MAJOR 262 Receiver overrun Receiver overrun None MAJOR 262 Transmitter not Transmitter not None ready ready MAJOR 262 Global buffer pool Global buffer pool None busy busy MAJOR 262 Unknown Cause Cause is not known Report to Avaya
452 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Appendix E: Advanced Installation, Configuration, and Testing
This Appendix provides manufacturing procedures for installing, configuring, and testing SS7/C7 servers. This information is intended for use only by the Avaya manufacturing department.
Hardware Installation and Configuration
DCCSS7 Cable connections
Avaya CCSS 1000/2000 Feature Documentation August 2013 453 Advanced Installation, Configuration, and Testing
DCCSS7 Configuration
Connect a terminal to DCC3K card and perform the following to setup the card for operation with the CCSS. The following will be seen after the dcc 3000 boots up. Answers to prompts should be made exactly as they appear in the following for dcc3k_ss7.smod to run correctly.
454 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] DCCSS7 Configuration
Avaya CCSS 1000/2000 Feature Documentation August 2013 455 Advanced Installation, Configuration, and Testing
456 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] DCCSS7 Configuration
Avaya CCSS 1000/2000 Feature Documentation August 2013 457 Advanced Installation, Configuration, and Testing
458 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Hostname, Ethernet Addresses, BOOTPTAB Configuration
Hostname, Ethernet Addresses, BOOTPTAB Configuration
Use the following information to configure the hostname, Ethernet address, and BOOTPTAB file. Example • The host names should be ccss1 and ccss2 for hosts A and B. • The servers normally have at least two (2) Ethernet interfaces. Additional interfaces should be assigned hostnames ccss-
10.7.18.32 dcc32 10.7.18.42 dcc42 5. Create the files /etc/hostname.
Note: Be sure that address does not conflict with existing address. 7. Enter each Ethernet hardware address for every DCCSS7 card connected to the system into the /etc/ethers file. The hostname for the cards should be assigned sequentially. Example:
00:80:01:d0:0d:3c dcc32 00:80:01:d0:0d:4c dcc42 For additional information, see DCCSS7 Configuration on page 454. 8. Modify the /etc/hosts file to contain a host entry for every DCCSS7card connected to the system.
Avaya CCSS 1000/2000 Feature Documentation August 2013 459 Advanced Installation, Configuration, and Testing
Example:
10.7.18.32 dcc32 10.7.18.42 dcc42 9. Reboot the system and verify all Ethernet connections work. Use the ping command to verify the connections (use the hostnames for the other SS7/C7 systems).
Configuring from the ccssinstall script
This section describes how the Hardware and IP addresses, for the DCC and COM cards can be configured using the ccssinstall script located at $CCSSHOME/bin. 1. Logon as superuser.
peri@ccss {1} su Password: ***** # 2. Execute ccssinstall to configure Hostname, Ethernet Address and BOOTPTAB, and respond to all prompts. The following will be seen after ccssinstall executes:
======CCSSINSTALL V1.2 Tue Aug30 (c) 2005 Nortel
CCSS SIP/SS7 Network Address : [10.7.0.1]164.164.8.247 Subnet Mask : [255.255.0.0]255.255.255.0 PrimaryGatewayAddress : [47.185.0.1]164.164.8.221 Secondary Gateway Address (Optional) : [164.164.8.221]164.164.8.222 Bootp Configuration: 1. TPM200 2. TPM800 3. TPM1100 4. DCC 5. COM Select (1-5): 4 IP of DCC3000 Card : [10.7.1.4]192.168.101.04 Hostname of DCC3000 Card : [dcc1]dcc3000 Ethernet Address : [00:80:01:80:nn:nn]00:80:01:80:00:04 Save changes (y/n)? : [n] y -- File/etc/hosts updated -- -- File/etc/ethers updated -- -- File/etc/bootptab updated -- Installanothercard (y/n)? : [n] n
SS7/C7 Software Installation
For software installation procedures, see SS7/C7 Server Software Installation on page 26.
#
460 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] SS7/C7 Software Installation
# Prerequisite for running mkccss script 1/ PERIglobl is installed to /opt/vps Instruction for running mkccss create ccss component (run mkccss): 1/ login as root 2/ source /home/peri/.cshrc 3/ at shell prompt type mkccss 1 4/ exit root
Note: The mkccss script automatically modifies the vos.cfg and vos-links.cfg files.These files can be modified manually using the following steps.
modified vos.cfg and vos-links.cfg files: 1/ source /etc/vpsrc.csh 2/ cd $MPSHOME/ccss1/etc 3/ cd /opt/vps/ccss1/etc (Do this step if command in step 2 fail due to $MPSHOME variable undefine) 4/ backup existing vos.cfg and vos-links.cfg files. 5/ edit vos.cfg and vos-links.cfg and make sure the content of these files match with the following default. vos.cfg: # # Example vos.cfg file. # # NAME HOST PORT PRI COMMAND LINE alarmd - - 0 alarmd vos-links.cfg # # Example vos-links.cfg file. # # NAME CONNECTION LIST alarmd - Configure vpshost file 1/ cd $MPSHOME/common/etc 2/ edit vpshost Example of vpshosts $1 # # Example vpshosts # # COMP NODE TYPE 1 - ccss 2 ccss2 ccss Where COMP: means component NODE: server node ( - mean local server) TYPE: always ccss if running mkccss
Note: For redundant servers, create ccss1 for one server and ccss2 for another server. The instruction for making ccss2 is the same as the procedure for making ccss1 (ex: mkccss 2).
Avaya CCSS 1000/2000 Feature Documentation August 2013 461 Advanced Installation, Configuration, and Testing
FFT - Field Factory Test
FFT for DCCSS7
The following test procedure will allow the user to test the system level functionality of DCC3K hardware installed on a MPS system environment in context with DCCSS7 software of CCSS system.
462 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] DCCSS7 Cable connections
DCCSS7 Cable connections
For addtional information, see System Cabling Diagrams on page 23.
ss7.conf.fft.a File
ss7.conf.fft.a file for System A
Avaya CCSS 1000/2000 Feature Documentation August 2013 463 Advanced Installation, Configuration, and Testing
CONFIG NODE=A1, OPC=2068, TYPE=SEP; CONFIG DCCHOST=dccl1, HOST=dcclinka; CONFIG DCCLINK=link1, SLC=0, DCCHOST=dccl1 ,PRIORITY=0, CHASSIS=1, BPS=1, SLOT=2, SPAN=4, CHANNEL=24, SS7SPAN=1, SS7CHAN=1, BR=64000; CONFIG LINKSET=ls1, DPC=2067, TYPE=FLINK, ACTIVELINK=1, LINKS=link1; CONFIG CMB_LINKSET=cs1, LSETS=ls1; CONFIG ROUTE=rt1, DPC=2067, LSETS=cs1; CONFIG TRK_GRP=1, CIR_GRP=0, GRP_TYPE=T1, DPC=2067; CONFIG TRK_GRP=2, CIR_GRP=1, GRP_TYPE=T1, DPC=2067; CONFIG TRK_GRP=3, CIR_GRP=2, GRP_TYPE=T1, DPC=2067; CONFIG TRK_GRP=4, CIR_GRP=3, GRP_TYPE=T1, DPC=2067; CONFIG CCME_PROXY_HOST=SCN1, HOSTNAMES=localhost; CONFIG CCME_PROXY_GRP=1, CCME_PROXY_HOST=SCN1, VPS=1, LINE=1; CONFIG CCME_PROXY_GRP=2, CCME_PROXY_HOST=SCN1, VPS=1, LINE=25; CONFIG CCME_PROXY_GRP=3, CCME_PROXY_HOST=SCN1, VPS=1, LINE=49; CONFIG CCME_PROXY_GRP=4, CCME_PROXY_HOST=SCN1, VPS=1, LINE=73;
ss7.conf.fft.b File
ss7.conf.fft.b file for System B
CONFIG NODE=A2, OPC=2067, TYPE=SEP; CONFIG DCCHOST=dccl2, HOST=dcclinkb; CONFIG DCCLINK=link1, SLC=0, DCCHOST=dccl2 ,PRIORITY=0, CHASSIS=1, BPS=1, SLOT=2, SPAN=1, CHANNEL=24, SS7SPAN=1, SS7CHAN=1, BR=64000; CONFIG LINKSET=ls1, DPC=2068, TYPE=FLINK, ACTIVELINK=1, LINKS=link1; CONFIG CMB_LINKSET=cs1, LSETS=ls1; CONFIG ROUTE=rt1, DPC=2068, LSETS=cs1; CONFIG TRK_GRP=1, CIR_GRP=0, GRP_TYPE=T1, DPC=2068; CONFIG TRK_GRP=2, CIR_GRP=1, GRP_TYPE=T1, DPC=2068; CONFIG TRK_GRP=3, CIR_GRP=2, GRP_TYPE=T1, DPC=2068; CONFIG TRK_GRP=4, CIR_GRP=3, GRP_TYPE=T1, DPC=2068; CONFIG CCME_PROXY_HOST=SCN1, HOSTNAMES=localhost; CONFIG CCME_PROXY_GRP=1, CCME_PROXY_HOST=SCN1, VPS=2, LINE=1; CONFIG CCME_PROXY_GRP=2, CCME_PROXY_HOST=SCN1, VPS=2, LINE=25; CONFIG CCME_PROXY_GRP=3, CCME_PROXY_HOST=SCN1, VPS=2, LINE=49; CONFIG CCME_PROXY_GRP=4, CCME_PROXY_HOST=SCN1, VPS=2, LINE=73;
tms.cfg Configuration File
[DTCMAP] ;------; Chassis Backplane DTC(TMS) Primary Secondary ; Num Slot (BPS) Num VOS Comp# VOS Comp# Config ;------BIND 1 1 1 1 - ;------; DTC PLI Span svc Vps ; Num Slot Num type Num
464 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] tms.cfg Configuration File
;------LOAD 1 4 1 - - LOAD 1 4 2 - - LOAD 1 4 3 - - LOAD 1 4 4 - - LOAD 1 4 5 - - LOAD 1 4 6 - - LOAD 1 4 7 - - LOAD 1 4 8 - -
;------;Outline Pool/class Protocol Pkg ; ;------SS7Line t1_esf_ss7_proxy_proto.cfg B=1-23 D=24 - SS7Line t1_esf_ss7_proxy_proto.cfg B=1-23 D=24 - SS7Line t1_esf_ss7_proxy_proto.cfg B=1-23 D=24 - SS7Line t1_esf_ss7_proxy_proto.cfg B=1-23 D=24 - SS7Line t1_esf_ss7_proxy_proto.cfg B=1-23 D=24 - SS7Line t1_esf_ss7_proxy_proto.cfg B=1-23 D=24 - SS7Line t1_esf_ss7_proxy_proto.cfg B=1-23 D=24 - SS7Line t1_esf_ss7_proxy_proto.cfg B=1-23 D=24 [SS7] ;------; TMS PLI Span Chan SS7 Span Chan ; Num Slot Num Num Slot Num Num ;------SS7MAP 1 4 1 24 2 1 1 SS7MAP 1 4 2 24 2 1 2 SS7MAP 1 4 3 24 2 1 3 SS7MAP 1 4 4 24 2 1 4 SS7MAP 1 4 5 24 2 1 5 SS7MAP 1 4 6 24 2 1 6 SS7MAP 1 4 7 24 2 1 7 SS7MAP 1 4 8 24 2 1 8 [VPS_LINE_DEF] ;------; MPS TMS PLI Slot Span:channel ; from:to Num Num ;------LINE 1:24 1 4 1:1 LINE 25:48 1 4 2:1 LINE 49:72 1 4 3:1 LINE 73:96 1 4 4:1 LINE 97:120 1 4 5:1 LINE 121:144 1 4 6:1 LINE 145:168 1 4 7:1 LINE 169:192 1 4 8:1 [RSET_TABLE] ;------; CTX Line DTC Rset_Profile ; Num Num Name ;------RSET = 1:24 1 SS7InLine
Avaya CCSS 1000/2000 Feature Documentation August 2013 465 Advanced Installation, Configuration, and Testing
Testing DCC Data Links
1. Connect the System as shown in the figure T1 2. Copy ss7.conf.fft.a to ss7.conf • Edit the ss7.conf file of System A so that they look exactly the same as in figure T1 3. Copy ss7.conf.fft.b to ss7.conf • Edit the ss7.conf file of System B so that they look exactly the same as in figure T1 4. On both systems run ccss_start. On the screen where ccss_start is running, an alarm will appear.
This will indicate that the signaling link is aligned
Note: All cables must be attached before link will show aligned. 5. Verify that all circuit states become IDLE • Issue a command "status cic * * state" at the UI prompt
Note: The CHASSIS, BPS, SLOT, SPAN and CHANNEL are the placeholders and should match up with appropriate entries made in tms.cfg configuration file. The tms.cfg configuration file contains information for the TMS. See tms.cfg configuration parameters on page 67.
Restoring The FT
System shipped with Fault Tolerance.
466 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Restoring The FT
1. Stop both the running systems. • Use command ccss_stop 2. Both systems must have exactly the same ss7.conf files. • System A must refer to hostname of System B as a fault tolerant peer.
CONFIG REDUNDANT_SERVER=ccssft, SERVER_ID=A, HOSTNAMES=
CONFIG REDUNDANT_SERVER=ccssft, SERVER_ID=B, HOSTNAMES=
Avaya CCSS 1000/2000 Feature Documentation August 2013 467 Advanced Installation, Configuration, and Testing
468 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Appendix F: Fault Tolerance Terminology
This chapter covers: 1. Fault Tolerance Terminology 2. Management State Machine States 3. Tokens used in MGMT Command Syntax
This section defines the general terms and commands used in Fault Tolerance.
Fault Tolerance
Controlled Switchover
This operation is executed to swap the states of the Active and Standby systems. The Active system is made Standby and the Standby is made Active. The newly active server will take over protocol processing and call control.
Note: In a controlled switchover, all established calls and those in transient states are preserved.
Forced Switchover
This operation is executed to recover from a failure of the Active system. This operation results in the Standby becoming Active, and the newly Active system taking over processing. The previously active system goes to shutdown state and will try to become Standby.
Note: In forced switchover, all established calls remain in the established state.
Avaya CCSS 1000/2000 Feature Documentation August 2013 469 Fault Tolerance Terminology
Active Node
One of the CCSS servers of a Fault Tolerant pair, which is connected to the network and can provide the necessary protocol functionality.
Standby Node
The CCSS server which serves as a backup for the Active system. The server can become active to process calls in the following events Example • A fault occurs on the active system. • The Active system is commanded to go standby. • The Standby system is commanded to go active. • A switchover is commanded on either system.
PSF (Protocol Specific Function)
The PSF software component provides the protocol layer with the capability to create and send update messages to its standby counterpart when its internal state changes. When the protocol layer is running in the standby mode, the PSF receives update messages from its active counterpart and updates the protocol layers internal data structures.
PSF Update
The protocol layers of the Active system handle protocol events which can result in internal state changes.These internal state changes on the Active system are sent to the Standby system in the form of PSF Updates.
470 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] WarmStart
WarmStart
When a Standby system come up, it receives a 'bulk update' of the internal states of the Active system. This process is called warm start.
MGMT State Machine States
This section describes the various states of the management state machine. The CCSS servers in a Fault Tolerant configuration can exist in or transition through any of the following states.
Initializing State
This is the state of MGMT when the executable is first invoked. In this state, command line arguments are parsed, static and global memory data items are initialized, and alarm and log streams are opened.
Configuration State
In this state, the server reads the configuration files, validates configuration items, and applies configuration to the server. If the configuration identifies a fault-tolerant server, then MGMT opens a connection to the fault-tolerant MGMT peer. MGMT does not communicate with any external processes until configuration is complete.
Shutdown State
After configuration, or when the server is returning to service from a commanded shutdown, MGMT enters this state to negotiate active or standby states with MGMT running on its fault- tolerant peer server. For a standalone server, this state is transient. A server that has no fault-tolerant state does not negotiate. Such a server will go active after completing server configuration.
Avaya CCSS 1000/2000 Feature Documentation August 2013 471 Fault Tolerance Terminology
Shutdown Maintenance State
This state is same as the Shutdown state except in shutdown maintenance state, server remains in this state untill the operator explicitly commands the server to go in service. This state allows operator to give any maintenance commands.
Shutdown, Going Active State
In the Shutdown state, the System Manager is disabled. The first action of a system in the shutdown state that is going active is to enable the system manager. During negotiation for active service, and before the System Manager is enabled, a server is in the Shutdown, Going Active state. This state stops the other server also going to Active state. After the System Manager is enabled, the system enters the OOS, Going Active.
Out-of-Service State
In this state the server is not actively processing protocol messages but the System Manager is enabled. MGMT has detected a process death or server fault that prevents MGMT from negotiating active or standby status. A server that experiences failures in the active or standby states is forcibly transitioned to the out of service state by management, until the failures are cleared and the server may be returned to active state.
Out-of-Service Standby State
This state is distinguished from Out-of-Service state by the state of the System Manager. Out- of-Service is defined as having the System Manager enabled and the protocol layers disabled. System Manager may be enabled as Standby or Active. A server on which the System Manager is enabled in standby mode requires an extra step before it can go active; it must make its System Manager active. This state distinguishes itself from Out-of-Service by the fact that the System Manager is enabled in standby mode.
472 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Out-of-Service, Going Active
Out-of-Service, Going Active
This state is a transitional state that occurs when a server in the Out-Of-Service or Shutdown, Going Active states, stays in after the System Manager is enabled and before all protocol layers are activated. The server in this state either successfully goes active or fails activation and enters the Out-Of-Service state. A server that cannot go active when commanded remains out- of-service until an operator commands it to become active or shutdown.
Out-of-Service, Going Standby
This state is a transitional state that occurs when a server that was previously in the shutdown state, through negotiation or management command, is waiting for the fault-tolerant peer to become active so it can become the standby. The server in this state either successfully goes standby or will fails and enter the out of service Standby state. A server that cannot go standby when commanded will remain in out of service Standby state until an operator commands it to become standby or shutdown.
Out-of-Service, Going Standby_2
This state is same as Out-of-Service, Going Standby state, but the difference is, in Out-of- Service, Going Standby state Trillium's system manager is enabled in standby mode. But Out- of-Service, Going standby_2 state System Manager was enabled in standby mode and remaining FT layers are being enabled.
Active, No Standby State
In this state the server is actively processing protocol messages. The system manager and protocol layers on the active server are enabled. Connections to proxy, tcapproxy and MTP2 are enabled and network traffic flows through the protocol layers. Peer connections for run- time that update capability between protocol layers are not enabled in this state. There is either a standalone server configuration or the fault-tolerant peer is not in standby state.
Avaya CCSS 1000/2000 Feature Documentation August 2013 473 Fault Tolerance Terminology
Active, With Standby State
In this state the server is actively processing protocol messages. The system manager and protocol layers on the active server are enabled. Connections to proxy, tcapproxy and MTP2 are enabled, and network traffic flows through the protocol layers. Peer connections for run- time update capability between protocol layers are enabled in this state. This state can only be entered if there is a fault-tolerant peer server, and the fault-tolerant peer is in the Standby state.
Standby State
In this state the server is not actively processing protocol messages. It is serving as the backup for an active server. The Trillium System Manager is enabled and Trillium and non-trillium layers are actively reporting status to MGMT. Connections to proxy, tcapproxy and MTP2 are disabled and network traffic does not flow through the protocol layers. Peer connections for run-time update capability between protocol layers are enabled, and protocol layers with such capability receive notification of state transitions as they occur within the active server. For this reason, there cannot be a standby server without a fault-tolerant (dual-server) configuration. Before a server can become a standby server, its peer server must be active.
STATE_ACTIVE_STBY_GOING_DOWN
In this state, the active server received indication from the standby that it is shutting down. The active server remains in this state until the standby shuts down, then returns to STATE_ACTIVE_NO_STANDBY.
Out-of-Service, Shutting Down
A server that is shutting down due to operator command or is recovering from a failure, remains in this state while the fault-tolerance control software is shutdown. In the case of failure and recovery, the CCSS returns to active or standby service after completion of shutdown.
474 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Going Standby, CCME Warm-start in Progress
Going Standby, CCME Warm-start in Progress
(STATE_GOING_STANDBY_CCME_WARMSTARTING)
Before a server becomes Standby, it must receive current state information for all circuits from the active server. This state is entered by the standby MGMT during this process.
Going Standby, CCME Warm-start Complete
(STATE_GOING_STANDBY_CCME_WARMSTARTED)
Before a server becomes Standby, it must receive current state information for all circuits from the active server. After the download process is complete, the server enters into this state. After the active server finishes the warm-start of the Trillium layers, and enters the Active, With Standby state, the standby server can leave the Going Standby, CCME Warm-start Complete state and enter the Standby state.
Active, Warm-start in Progress
(STATE_ACTIVE_STANDBY_WARMSTARTING)
Most System Manager commands are processed by the System Manager on the active server. Management on the active server is responsible for enabling the fault-tolerant protocol layers on the standby server to operate in standby mode. This process is called warm-start. The active server remains in this state while the active server is activating the protocol layers on the standby server for standby operation.
Avaya CCSS 1000/2000 Feature Documentation August 2013 475 Fault Tolerance Terminology
Active, Warm-start Complete
(STATE_ACTIVE_STANDBY_WARMSTARTED)
The active server that is activating the fault-tolerant layers on the standby server for standby service is in the Active, Warm-start in Progress state and enters the Active, Warm-start Complete state when the warm-start has finished. Before the standby can be considered fully enabled, the standby must complete the downloading of stable-state information from the active call-control. After this is complete, the active server can leave the Active, Warm-Start Complete state and enter the Active, With Standby State.
Standby, Going Active
This state is involved in forced switchover. When the standby server loses contact with the active server, or the active server enters the Shutdown State, the standby server enters the Standby, Going Active state while it is commanding the switchover of the System Manager and the protocol traffic to the standby server. When these tasks are complete, the server that was standby is in the Active, No Standby state.
Going Active Controlled
This state is involved in controlled switchover. When the standby server is retrieving state information from the active server's CCME, ISUP and MTP3 layers, it is in the Going Active Controlled state. When these tasks are complete, the server that was standby is in the Active, With Standby state; and the server that was active is in the Standby State.
Going Standby Controlled
This state is involved in controlled switchover. When the active MGMT receives a command from MGMTUI to perform a controlled switchover, or when the active MGMT receives a message from the standby that the standby has changed to 'Going Active, Controlled', the active MGMT sends commands to the active call-control and TCAP user processes to pause
476 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] STATE_GOING_OOS_STANDBY
(hold enqueued) traffic from proxy and tcapproxy, and to drain traffic currently enqueued within the server. After CCME and TCUSER confirm these requests, they have no more messages to process. MGMT changes its state from 'Active, With Standby' to 'Going Standby Controlled'.
STATE_GOING_OOS_STANDBY
This state is a transitional state involved in forced switchover. In forced switch over, earlier Active_with_standby server comes to this state and remains in this state untill all the layers are disabled.
STATE_GOING_STBY_FLOW_CTL
This state is a transitional state, involved in controlled switchover. When the transient calls are being redirected to new Active server; earlier Active server stays in this state.
STATE_GOING_ACTV_FLOW_CTL
This state is involved in controlled switchover. When the transient calls are being redirected to new Active server, new Active server stays in this state.
Server State Transitions
Server state transitions are sequential processes orchestrated by MGMT to effect a change in the service state of one or more CCSS servers. Management undergoes initialization and configuration of the MTI, CCME and TCUSER processes at startup. After startup, state transitions generally begin and end on MGMT states Shutdown, Out-Of-Service, Active Without Standby, Active With Standby, Standby or Out of service Standby. The other MGMT states are transient states assumed for a short period of time for the purposes of synchronizing the state transitions with the peer MGMT.
Avaya CCSS 1000/2000 Feature Documentation August 2013 477 Fault Tolerance Terminology
Tokens
This following table lists of all the tokens used in the CCSS server configuration files and the user interface commands.
Note: Tokens are keywords. They should not be used as names for hosts, servers, aliases, and so on when configuring the CCSS systems. Table 3: Tokens (reserved words)
ACN GTFORMATPARAM REV ACN_GRP GTFUNCSET ROUTE ACTION GTTFORMAT ROUTE_GT ACTIVELINK HELP ROUTE_SSN ADDR HOST ROUTING ALINK HOSTNAMES RULE ANSI INT RULE_DEFAULT ANSI88 ISUP RULE_DMSIP ANSI92 ITU SCCP ANSI96 ITU88 SCCP BPC ITU92 SCCP_GTASSO BR ITU96 SCCP_GTMAP CCME_DEFAULT LAYER SCCP_GTTNODE CCME_OPTION LEN SCCP_LOCAL CCME_PROXY_GRP LEVEL SCCP_LOCAL_GT CCME_PROXY_HOST LINE SCCP_LOCAL_SS CCME_TIMER LINK SCCP_NETWORK CCME_TMS_GRP LINK_INFO SEP CCME_TMS_HOST LINKS SERVER CIR_GRP LINKSET SERVER_ID CIRCUIT LOCAL_SS SLC CIRCUIT LOWER_NODE SPC CMB_LINKSET LSETS SSF CONFIG MASK SSN CONST MODIFY STATE_INPUT CONTROL MSU STATS EB MSU_PRIO_0 STP DEB_FLAG MSU_PRIO T1 DEB_FT_COMPONENT MTP1 T1S DEB_SWITCH MTP2 T_TYPE DELAY MTP3 TCAP DPC NAI TCAP DTC NAT TCUSER_CLIENT E1 NODE TCUSER_HOST ES NODENAME TCUSER_TIMER ETSI NP TIMER ETSIV2 OE TIMER_MAC ETSIV3 OPC TMS_SPAN FIX OUTPC TRACE FLINK PINGHOSTS TRK_GRP FT_COMPONENT PRIORITY TT GROUP Q767 TYPE
478 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Tokens
GRP_TYPE QUERY UPPER_NODE GT_TO_PC RANGE VALUE GTACTION REDUNDANT_SERVER VAR_ASC GTACTIONS REP_NO VAR_DES REP_YES VARIANT REPLACE VAS REPORT VPS RESTART_REQD
Avaya CCSS 1000/2000 Feature Documentation August 2013 479 Fault Tolerance Terminology
480 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Appendix G: CCSS Timers
This chapter covers 1. CCME Timers 2. ISUP Timers 3. MTP3 Timers 4. MTP2 Timers
This section describes the various timers on the CCSS system. This section also speaks about timers that are configurable on the system and how to configure them. Timers on a CCSS system are classified as one of the following: • CCME Timers • ISUP Timers • MTP3 Timers • MTP2 Timers
CCME Timers
The CCME timers are used for call control processes. These timers are configured in the ss7.conf configuration file. CONFIG CCME_TIMER
Configuration syntax for CCME timers. CONFIG CCME_TIMER=name, VALUE=value; CCME_TIMER Defines the timer name. VALUE Value for timer.
The complete list of CCME timers and their default values is detailed in the follwing table:
Avaya CCSS 1000/2000 Feature Documentation August 2013 481 CCSS Timers
Sl No Timer Description Default Configurable Value (s) Y/N 1. P0 The VAS or VPS/is connection retry 1 Y interval. 2. P1 Currently not used. - - 3. P2 The MTP grace period (if MTP goes down, 30 Y the application resets when P2 has expired). 4. P3 Currently not used. - - 5. P4 Dual seizure retry timer (if the circuit 5 Y experiences dual seizure, call setup is retried when P4 expires). 6. P5 Currently not used. - - 7. P6 The Release Complete (RLC) hold timer. 45 Y RLC is normally not transmitted to the network until the application performs an ISSUE GET. When P6 expires, RLC is sent automatically. 8. P7 Outbound IAM hold timer. The IAM is 20 Y normally held until the circuit clears. If the IAM is not sent within the P7 interval, the application receives the output failure (of) condition. 9. P8 Reset pacing timer (the interval between 1 Y GRS messages when many resets are being sent). 10. P9 Ping message transmission interval. 1 Y Messages are sent from the active server to the standby server (in a redundant configuration) to check for availability. A ping message is sent every P9 interval. 11. P10 Redundant server activate interval. If the 5 Y standby server does not receive a ping message from the active server within P10 time, the standby server makes itself the active server. 12. P11 Overlap receive timeout interval. After 5 Y receiving dialed number digits, this timer is started. if P11 expires, the call will proceed to setup. 13. P12 No ACM receive timeout interval. After 15 Y sending an IAM this timer is started. If P12
482 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] ISUP Timers
Sl No Timer Description Default Configurable Value (s) Y/N expires, an RSC message will be sent to reset the circuit. 14. P13 It defines the amount of time, in seconds, call 5 Y control will wait before unbinding a circuit after receiving ISSUE_FREE on a bound circuit. If the redundant SCN does not REBIND the circuit within the timeout period, the circuit will be idled and the call present on the circuit will be freed. This command is used for CN mode only, when CTX call protect is configured.
ISUP Timers
The ISUP Timers on the CCSS system are hardcoded and cannot be configured. The following table lists all the ISUP timers supported.
Sl No Timer Name Description Default Value ITU ANSI 1. TMR_T1 release sent timer 100 100 2. TMR_T2 1800 1800 3. TMR_T3 1200 1200 4. TMR_T5 initial release sent timer 600 600 5. TMR_T6 suspend received timer 600 100 6. TMR_T7 latest address sent timer 200 200 7. TMR_T8 initial address received timer 150 150 8. TMR_T9 latest address sent after ACM timer 1800 1800 9. TMR_T33 INR sent timer Not Not enabled enabled 10. TMR_T36 waiting segmentation timer 20 20 11. TMR_TCCRI timer CCR for incoming side 200 200 12. TMR_TCCR timer CCR for outgoing side - 20 O 13. TMR_TEX timer to send Exit message Not Not enabled enabled
Avaya CCSS 1000/2000 Feature Documentation August 2013 483 CCSS Timers
Sl No Timer Name Description Default Value ITU ANSI 14. TMR_T12 blocking sent timer 150 150 15. TMR_T13 initial blocking sent timer 3000 600 16. TMR_T14 unblocking sent timer 150 150 17. TMR_T15 initial unblocking sent timer 3000 600 18. TMR_T16 reset sent timer 150 150 19. TMR_T17 initial reset sent timer 600 600 20. TMR_T18 group blocking sent timer 150 150 21. TMR_T19 initial group blocking sent timer 600 600 22. TMR_T20 group unblocking sent timer 100 100 23. TMR_T21 initial group unblocking sent timer 600 600 24. TMR_T22 group reset sent timer 150 150 25. TMR_T23 initial group reset sent timer 600 600 26. TMR_T24 Check Tone sent Not Not supported supported 27. TMR_T25 initial continuity check failure is detected Not Not supported supported 28. TMR_T26 second continuity check failure is Not Not detected supported supported 29. TMR_T27 waiting for continuity recheck timer 2400 2400 30. TMR_T28 Circuit Query Message is sent - 100 31. TMR_T31 call reference frozen period timer Not Not enabled enabled 32. TMR_T34 waiting for continuity after recheck timer 120 120 33. TMR_TFGR timer started when first group blocking or - 50(VANSI reset message received. ) Not enabled(A NS88) 34. TMR_TGRE group reset timer 1 1 S 35. TMR_TCRM circuit reservation message timer - Not enabled 36. TMR_TCRA circuit reservation ack. timer - Not enabled 37. TMR_TECT loop prevention msg timer - Not enabled
484 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] MTP3 Timers
Sl No Timer Name Description Default Value ITU ANSI 38. TMR_GTCH GT_FTZ(German Telecom, option 23) 10 - G CGHEA msg timer 39. TMR_PAUS GT_FTZ (German Telecom, option 23) 5 - E PAUSE msg timer
MTP3 Timers
Some of the MTP3 timers are configurable. The syntax for commands entered in the ss7.conf configuration file is shown in the following table. CONFIG LAYER
Configuration syntax for MTP3 timers. CONFIG LAYER=layer, TIMER=timer, VAL=val; LAYER Specifies the layer. Values are MTP3 and MTP2. TIMER Timer name. VALUE Value for timer.
Sl No Timer Description Default Value Configurable Name ITU ANSI Y/N 1. T1 Delay to avoid missequencing on 12 12 N changeover 2. T2 Waiting for changeover 20 20 Y acknowledgement 3. T3 Delay to avoid miss-sequencing on 12 12 Y changeback 4. T4 Waiting for changeback ack(1st) 12 12 Y 5. T5 Waiting for changeback ack(2nd) 20 20 Y 6. T6 Delay to avoid message mis- 12 12 Y sequencing on controlled rerouting 7. T7 Waiting for signaling datalink 20 20 Y connection ack 8. T8 Transfer prohibited inhibition timer 12 12 Y (transient) 9. T9 Not used - -
Avaya CCSS 1000/2000 Feature Documentation August 2013 485 CCSS Timers
Sl No Timer Description Default Value Configurable Name ITU ANSI Y/N 10. T10 Waiting to repeat signaling route set 600 600 Y test message 11. T11 Transfer restricted timer 900 900 Y 12. T12 Waiting for uninhibit ack 15 15 Y 13. T13 Waiting for forced uninhibit 15 15 Y 14. T14 Waiting for inhibition ack 30 30 Y 15. T15 Waiting to start route set congestion 20 20 Y test 16. T16 Waiting for route set congestion 20 20 Y status update 17. T17 Delay to avoid oscillation of initial 15 15 Y alignment failure and link restart 18. T18 (STP) waiting for links to become 200 - Y available 19. T18 Repeat TFR once by respond 200 Y method 20. T19 (STP) started after T18 waiting to 40 - Y receive all TRA messages and restart remaining traffic 21. T19 Failed Link craft timer - 40 Y 22. T20 (STP) started after T19, waiting to 40 - Y broadcast TRA messages and restart remaining traffic 23. T20 Waiting to repeat local inhibit - 40 Y test(See T22 ITU) 24. T21 waiting to restart traffic routed 2 - Y through adjacent SP 25. T21 Waiting for repeat remote inhibit - 2 Y test(See T23 ITU) 26. T22 Local inhibit test timer 3000 - Y 27. T22 See T18 ITU - 1000 Y 28. T23 Remote inhibit test timer 3000 - Y 29. T23 See T19 ITU - 1000 Y 30. T24 Stabilizing timer 5 - Y 31. T24 See T20 ITU - 5 Y
486 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] MTP2 Timers
Sl No Timer Description Default Value Configurable Name ITU ANSI Y/N 32. T25 Timer at SP adjacent to restarting - 300 Y SP, waiting for traffic restart allowed message 33. T26 Timer at restarting SP waiting to - 120 Y repeat traffic restart waiting message 34. T31 False link congestion detection - 20 Y timer(Note T35 DLSAP internal) 35. T32 Not Supported - - Y 36. T33 Probation timer for link oscillation – - 50 Y Procedure B(Note T36 DLSAP internal) 37. T34 Suspension timer for link oscillation - 900 Y – Procedure B (note T37 DLSAP internal) 38. T35 - 100 Y 39. T36 - 600 Y 40. T37 - 50 Y 41. T19R 0 600 Y 42. T21R 300 300 Y
Signaling Link Test Timers
Sl No Timers Description Values (s) 1. SLT T1 Supervision timer for signaling link test 5 sec acknowledgement message. 2. SLT T2 Interval timer for sending signaling link test 90 sec messages
MTP2 Timers
Most of the MTP2 timers are configurable. The syntax for commands in the ss7.conf configuration file is shown in the following table. CONFIG LAYER
Avaya CCSS 1000/2000 Feature Documentation August 2013 487 CCSS Timers
Configuration syntax for MTP2 timers. CONFIG LAYER=layer, TIMER=timer, VAL=val; LAYER Specifies the layer. Values are MTP3 and MTP2. TIMER Timer name. VALUE Value for timer.
Sl No Timer Description Value100 ms Configuarble ITU ANSI Y/N 1. T1 Alignment ready timer 450 130 N 2. T2 Not aligned timer 1000 140 Y 3. T3 Aligned timer 12 125 Y 4. T5 Sending SIB timer 10 10 Y 5. T6 Remote congestion 60 30 Y timer 6. T7 Excessive delay of 15 15 Y acknowledgement 7. PROVEMRGCY Emergency proving 5 6 Y (T4e) period 8. PROVNORMAL Normal proving period 82 23 Y (T4n) The following values are for leaky bucket algorithm 9. SDT (Ti) SUERM error rate 64 64 Y threshold 10. SDTIE (Tie) AERM emergency error 1 1 Y rate threshold 11. SDTIN (Tin) AERM normal error rate 4 4 Y threshold
488 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Appendix H: DCCSS7 Debugging Utility
This appendix describes the l2debug program used to connect to a DCCSS7 card and retrieve release and status information related to the MTP2 and data link layers running on the DCCSS7.
The DCCSS7 Debugging Utility
The DCCSS7 debugging utility (l2debug) runs in a command shell on CCSS systems. The l2debug program connects to a single DCCSS7 card and presents the user with a numbered list of commands (a menu) used to request information about the state of the DCCSS7, or to enable and disable runtime debugging capabilities on the DCCSS7. When the user enters a number to select a choice from the menu, l2debug sends a request to the DCCSS7 card through a TCP/IP connection. The DCCSS7 card returns results back to l2debug over the same connection. Results include confirmations and/or current status information from the DCCSS7 card. Results are displayed as text in the l2debug standard output, usually the command window where l2debug was started.
Identifying DCCSS7 Cards About this task Before you can run l2debug you must determine the hostname of the DCCSS7 card you want to connect to. DCCSS7 hostnames are used in the ${CCSSHOME}/etc/ss7.conf file. To determine the DCCSS7 hosts configured on a CCSS system, perform the following procedure. Procedure
1. Log in as user peri. 2. Open ${CCSSHOME}/etc/ss7.conf file in an editor. peri@pdv210-251-107 {1} vi $CCSSHOME/etc/ss7.conf 3. In the editor, locate DCCSS7 hostname(s) in ‘CONFIG DCCHOST’ commands, after the equal sign in the ‘HOST’ argument. . . . CONFIG DCCHOST=dccss71, HOST=dcc42;
Avaya CCSS 1000/2000 Feature Documentation August 2013 489 DCCSS7 Debugging Utility
CONFIG DCCHOST=dccss72, HOST=dcc52; . . .
Note: In this example there are two DCCSS7 hosts configured with hostnames ‘dcc42’ and ‘dcc52’. When a DCCSS7 has been configured and the software has loaded, the DCCSS7 will respond to a ping request by hostname (for example, ping dcc42).
Starting an L2debug Session About this task The l2debug utility is installed with the PERIccss package, in the ${CCSSHOME}/bin directory. To start l2debug and connect to a DCCSS7, perform the following procedure. Procedure
1. Log in as user peri. 2. Enter the command l2debug
Important: The L2 debug capabilities are intended for use in analysis of SS7 problems. There is no intended use for the l2debug utility under normal operating conditions. Do not open an l2 debug session unless directed to do so by Avaya support personnel. Unintended execution of some of the l2 debug menu options will temporarily impair the functioning of the SS7 links, will cause interruption of SS7 traffic, and/or will ultimately cause applications or calls in progress to fail until link stability recovers.
The L2debug Menu
Once started, l2debug presents the following menu of options:
peri@pdv210-251-107 {3} l2debug dcc42 hostname len = 5
490 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] L2debug Menu Option Details
L2 debug Program: 1. Toggle enable/disable layer 2 (MSU/LSSU) tracing 2. Reboot board 3. Memory usage request 4. Display image information 10. Toggle Perm debug on and off, comm1000 only 11. Toggle L2if debug on and off 13. Display Link(s) stats 14. Reset Link(s) stats 15. Display MCC channel data 16. Start MCC channel logging. 17. Stop MCC channel logging 18. Query MCC channel logging state 19. Toggle MCC channel log stop trigger 20. Query MCC channel log stop trigger 21. Show Alarm hosts 99. Exit File descriptor available on: conn 0 fd 4 New connection ready on Connection 0 The program is ready for input once the “New connection ready on Connection 0” message is displayed. There is no prompt for input. The user types a number corresponding to one of the menu choices and the request is sent to the DCCSS7 card. The menu is redisplayed immediately. There is some time delay for the request and response to go to the DCCSS7 and back. When a response is displayed, the menu may scroll out of view. The user can enter the next command without seeing the menu. To see the menu choices again, press enter without any input. If the connection to the DCCSS7 has been lost and the user enters a choice, the message ‘connection not ready’ will be displayed and there will be no response from the DCCSS7.
L2debug Menu Option Details
1. Toggle enable/disable layer 2 (MSU/LSSU) tracing
Option 1 toggles on and off the tracing of Message Signal Unit (MSU) and Link Status Signal Units (LSSUs) for all SS7 links data links. If the tracing is currently off, it is turned on; and if tracing is currently on, it is turned off. Command output:
Layer 2 trace on Enter 1 again, output is:
Layer 2 trace off
Avaya CCSS 1000/2000 Feature Documentation August 2013 491 DCCSS7 Debugging Utility
The traces are sent to open mgmtui sessions. If none are open the traces will not be visible. Open mgmtui in another command shell to view the traces
peri@pdv210-251-107 {2} mgmtui * * * MGMT @ pdv210-251-107 * * * > MTP2 02/27/13 10:00:35 R 1 96 1 48 11 MSU MTP2 02/27/13 10:00:35 R 1 96 1 49 9 MSU MTP2 02/27/13 10:00:35 R 1 0 1 31 9 MSU MTP2 02/27/13 10:00:35 R 1 96 1 50 9 MSU MTP2 02/27/13 10:00:35 R 1 96 1 51 9 MSU MTP2 02/27/13 10:00:35 R 1 96 1 52 9 MSU MTP2 02/27/13 10:00:35 R 1 0 1 32 9 MSU MTP2 02/27/13 10:00:35 R 1 0 1 33 9 MSU MTP2 02/27/13 10:00:35 R 1 0 1 34 9 MSU
Layer TIME DIR BIB BSN FIB FSN LENGTH STATUS MTP2 02/27/13 10:00:35 R 1 0 1 35 9 MSU MTP2 02/27/13 10:00:35 R 1 96 1 53 9 MSU MTP2 02/27/13 10:00:35 T 1 53 1 97 63 MSU MTP2 02/27/13 10:00:35 T 1 35 1 1 63 MSU MTP2 02/27/13 10:00:35 R 1 0 1 36 9 MSU
Important: This tracing is intended for debugging purposes only. Do not turn on tracing unless directed to do so by Avaya support personnel. Use of tracing on a system under heavy call load could impair the performance of the system and could result in call failures.
2. Reboot board
Option 2 reboots the DCCSS7 card. All SS7 links on that DCCSS7 will be out of service until the board reboots and is reconfigured by the controlling CCSS server. Command output:
Reboot is accepted for board IP: 10.7.19.42, Please wait ... The reboot takes about 1 minute. The l2debug program does not have to be restarted. Commands entered before the reboot is complete will have no effect until the l2debug program re-establishes connection with the DCCSS7. After a reboot, the l2debug program will not establish a connection with the DCCSS7 while it is waiting for user input. Avoid entering an unintended command by using option 4 (Display image information) to test the connection, or enter option 99 (Exit) and restart l2debug. The message New connection ready on Connection 0 will appear when the DCCSS7 card is again ready to receive l2debug commands.
492 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] L2debug Menu Option Details
3. Memory usage request
Option 3 displays some internal statistics related to the usage of memory buffers in the DCCSS7 card. Command output:
memory usage: pool size = 255485 number of buffer = 255749 Pool available = 99%
4. Display image information
Option 4 displays information about the software image downloaded onto the DCCSS7 card. It also displays the processor type, the Ethernet address, the IP address, and the host name for the DCCSS7 card. Command output:
Processor: MPC8260 (Mask 0x24). Image Info: dcc3k_ss7.elf, Release Developmental [02/25/13 11:41:34 AM] Copyright (C) 2013, Avaya Inc. All rights reserved Ether: 00:80:01:d0:0d:4c DownLoad image: /dcc3k_ss7.smod Board IP:10.7.19.42 host name = dcc42-a
5-10. Unassigned
The l2debug menu does not have any items numbered 5 through 10. The numbers 5 through 10 are considered invalid input. The following is displayed if any of the values from 5 through 10 are entered:
Invalid input
11. Toggle L2if debug on and off
Option 11 toggles on and off l2if debugging. L2if (L2 interface) is the socket-based message interface for communication between the MTP3 running on the Solaris CCSS servers and MTP2 running on the DCCSS7 cards. The l2if debugging prints messages to the standard output to diagnose problems with the L2 interface should they occur. If the logging is currently off, it is turned on; and if logging is currently on, it is turned off. Command output:
Avaya CCSS 1000/2000 Feature Documentation August 2013 493 DCCSS7 Debugging Utility
L2if debug is on Enter 1 again, output is:
L2if debug is off
Important: The l2 interface is tested in Avaya design labs in controlled circumstances. Printing l2 interface debugging messages to the standard output (console) of a running DCCSS7 card is apt to impair its performance even on a system with little SS7 traffic. Do not turn on l2 interface debugging unless directed to do so by Avaya support personnel.
12. Unassigned
The l2debug menu does not have an item numbered 12. The number 12 is considered invalid input. The following is displayed if 12 is entered:
Invalid input
13. Display Link(s) stats
Option 13 displays statistics indicating the number of valid layer 2 packets transmitted and received on each SS7 link, and error counts for each SS7 data link configured on the DCCSS7. When requested by Avaya support personnel, run this option and return the results to Avaya for analysis. Command output:
Link 0: mTx 1329975 mRx 1975769 lTx 47 lRx 23 fTx 1949427 fRx 3656728 lclBusy 0 slFailAll 15 slFailAb 0 slFailAck 0 slFailErr 0 slFailCong 0 slFailAlign 1 slNSUErr 1 slNegAck 0 nSifSioTx 18 nRetrans 0 nSifSioRx 14
Link 1: mTx 1519535 mRx 2256961 lTx 45 lRx 22
494 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] L2debug Menu Option Details
fTx 2209623 fRx 3995277 lclBusy 0 slFailAll 14 slFailAb 0 slFailAck 0 slFailErr 0 slFailCong 0 slFailAlign 1 slNSUErr 2 slNegAck 0 nSifSioTx 17 nRetrans 0 nSifSioRx 12
14. Reset Link(s) stats
Option 14 sets the link statistics to 0 (or initial values) and displays the reset values. These are the same statistics indicating the number of valid layer 2 packets transmitted and received on each SS7 link, and error counts, as described in option 13. Command output:
Link 0: mTx 0 mRx 0 lTx 0 lRx 0 fTx 0 fRx 0 lclBusy 0 slFailAll 0 slFailAb 0 slFailAck 0 slFailErr 0 slFailCong 0 slFailAlign 0 slNSUErr 0 slNegAck 0 nSifSioTx 0 nRetrans 0 nSifSioRx 0
Link 1: mTx 0 mRx 0 lTx 0 lRx 0 fTx 0 fRx 0 lclBusy 0 slFailAll 0 slFailAb 0 slFailAck 0 slFailErr 0 slFailCong 0 slFailAlign 0 slNSUErr 0 slNegAck 0 nSifSioTx 0 nRetrans 0 nSifSioRx 0
Avaya CCSS 1000/2000 Feature Documentation August 2013 495 DCCSS7 Debugging Utility
15. Display MCC channel data
Option 15 shows register values from the Multi-Channel Controller (MCC) integrated into the MPC8260 processor running on the DCCSS7 card. Register values and their uses are documented in the Motorola microprocessor manuals known to Avaya personnel. When requested by Avaya support personnel, run this option and return the results to Avaya for analysis. Command output (some output omitted, for illustration purposes):
MCC global parameters, link 0 mccBase 0x01cbbdc0 mccState 0x0000 ... rInt4ptr 0x01c89cc0 Link 0 SS7 channel parameters tState 0x38008568 ziState 0x80000402 ... ss7State 0x10000003 Link 0 Extra parameters tBase 0x0080 tbPtr 0x00b9 ... rbPtr 0x0007 MCC global parameters, link 1 mccBase 0x01cbbdc0 mccState 0x0000 ... rInt4ptr 0x01c89cc0 Link 1 SS7 channel parameters tState 0x38008568 ziState 0x800bf202 ... ss7State 0x90000000 Link 1 Extra parameters tBase 0x0480 tbPtr 0x04cc ... rbPtr 0x042a MCC channel stats completed
16. Start MCC channel logging
Option 16 starts MCC channel logging. Multi-Channel Controller (MCC) runtime data is continuously collected in a ring buffer in the DCCSS7 memory space. The ring buffer keeps the newest data and overwrites the oldest data as long as the logging is on. MCC channel logging is off by default. Turn it on only if instructed to do so by Avaya support personnel. The data captured includes selected MCC data from the Motorola microprocessor manuals known to Avaya personnel. When requested by Avaya support personnel, run this option to start the capture.
496 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] L2debug Menu Option Details
Command output:
MCC logging is on There is another menu option to stop the MCC channel logging. When capture is stopped the data in the ring buffer can be captured by pointing a web browser at the DCCSS7, using the DCCSS7 hostname or DCCSS7 IP address in the URL. Examples: http://dcc42 or http://10.7.19.42, substituting your DCCSS7 hostname or IP address. When instructed by Avaya support, load the MCC logging page into the browser, save it as html and return it to Avaya for analysis. Procedure:
1. Load the main DCCSS7 web page (i.e. http://dcc42). 2. Select MCC Dlog from the Pages Selection pull-down menu. 3. Click go in the browser window. 4. Once the contents of the MCC logging ring buffer are loaded from the DCCSS7 into the web browser, save the current page as html from the web browser to a file.
17. Stop MCC channel logging
Option 17 stops the capture of MCC channel logging. When capture is stopped the captured MCC logging data can be examined or saved to a file using a web browser. For a full description of the process of MCC logging capture, see option 16, above. Command output:
MCC logging is off
18. Query MCC channel logging state
Option 18 indicates whether the capture of MCC channel logging is turned on or off without changing the capture status. Use options 16 or 17 to stop or start MCC channel log capture. For a full description of the process of MCC logging capture, see option 16, above. Command output if logging is on:
MCC logging is on Command output if logging is off:
MCC logging is off
Avaya CCSS 1000/2000 Feature Documentation August 2013 497 DCCSS7 Debugging Utility
19. Toggle MCC channel log stop trigger
Option 19 changes the state of the MCC channel logging stop trigger. If enabled, the MCC channel logging stop trigger will turn the log capture off any time an SS7 link goes out of alignment. The trigger exists because continued log capture after a link failure could cause the ring buffer to be completely overwritten in a short time, and the event that caused the link to fail would no longer be in the log capture. The trigger prevents any further capture from overwriting the link down event. Because the option toggles the trigger, the effect depends on the state of the trigger when the command is entered. Command output if the trigger is not in effect (the toggle turns the trigger on):
MCC logging stops on link down Command output if the trigger is in effect (the toggle turns the trigger off):
MCC logging continues on link down
20. Query MCC channel log stop trigger
Option 20 queries the state of the MCC channel logging stop trigger, without changing it. Use option 19 to change the state of the log stop trigger, only when instructed by Avaya support personnel. See option 19 for an explanation of the MCC channel logging stop trigger. Command output if the trigger is in effect:
MCC logging stops on link down Command output if the trigger is not in effect:
MCC logging continues on link down
21. Show Alarm hosts
Option 21 shows the IP addresses for CCSS servers that the DCCSS7 will send alarms to. This is an indication of which CCSS servers have connected to and configured the DCCSS7. This option is useful in determining if there could be a misconfiguration, such that a CCSS server is controlling the wrong DCCSS7. This option is also useful in revealing instances when CCSS server reconfiguration changes which CCSS servers control which DCCSS7 cards; but the DCCSS7 was not rebooted after the configuration were made. Cross-traffic to incorrect DCCSS7 cards can prevent a CCSS server from operating properly.
498 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] L2debug Menu Option Details
Command output if the DCCSS7 has been connected to and configured:
Alarm hosts: 1: 10.7.19.107 done. Command output if the DCCSS7 is not configured (no CCSS server has connected yet):
Alarm hosts: none. The IP address displayed is the IP address of the interface on the CCSS server through which a connection to the DCCSS7 is established. For fault-tolerant configuration there should be two IP addresses, one for each CCSS server in the fault-tolerant pair.
99. Exit
Option 99 exits the l2debug program. Command output:
Goodbye : root@pdv210-251-107 {5}
Avaya CCSS 1000/2000 Feature Documentation August 2013 499 DCCSS7 Debugging Utility
500 Avaya CCSS 1000/2000 Feature Documentation August 2013 Comments? [email protected] Index
B P backing up ...... 154–156, 160, 161 pass on flag ...... 86 cp ...... 160 passOnFlag ...... 86 devices and options ...... 154 methods ...... 155 restore ...... 156 R tar ...... 155 verify ...... 156 remove function ...... 298 restore. See backing up ...... 156 C
Cause Diagnostics ...... 271 T copy ...... 160 See also backing up ...... 160 tar ...... 155, 156 backup ...... 155 restore ...... 156 H verify ...... 156 How To ...... 152, 156, 164 back up with tar ...... 152, 156 V restore files with tar ...... 156, 164 verify a tar backup ...... 156 verify, backup ...... 156
Avaya CCSS 1000/2000 Feature Documentation August 2013 501