> For the complete documentation index, see [llms.txt](https://prosbcdocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prosbcdocs.telcobridges.com/tmedia-documentation/configuration/web-portal-3-3/protocol-stack/ss7-isup/creating-isup-cic-groups.md). # Creating ISUP CIC Groups > **Applies to:** Tmedia 3.0, 3.2, 3.3 A CIC represents a physical timeslot between two SS7 nodes. Both of these nodes must commonly agree upon a CIC numbering scheme. Once you have created an ISUP interface, you must create a new ISUP cicuit identification code (CIC) group for your system. To create an ISUP CIC group: 1- Click **ISUP** in the navigation panel. ![CreateIsupStack 0](https://docs.telcobridges.com/w/images/7/71/CreateIsupStack_0.png) 2- Select the ISUP stack ![SelectIsupStack 0](https://docs.telcobridges.com/w/images/5/5f/SelectIsupStack_0.png) 3- Select the ISUP interface ![SelectIsupInterface 0](https://docs.telcobridges.com/w/images/6/6b/SelectIsupInterface_0.png) 4- Click **Create New Isup Cic Group** in the ISUP interface configuration window (a number of groups can be created at once by clicking **Create Multiple New Isup Cic Group**) ![Create ISUP CIC Group 0](https://docs.telcobridges.com/w/images/8/86/Create_ISUP_CIC_Group_0.png) 5- Configure the new ISUP CIC group: * Enter a **name** for the group * Enter a number for the **first CIC** in the group (this value must follow other CIC group values, and not overlap) * Select a **line service** * Check the appropriate **timeslots** (click "Select all" to check all timeslots) * Select a **CIC mapping** * Select a **call control method** (Advance Parameters) * Click **Create** ![Create ISUP CIC Group 1](https://docs.telcobridges.com/w/images/0/08/Create_ISUP_CIC_Group_1.png) 6- Verify that the **"IsupCicGroup was successfully created"** message appears ![Create ISUP CIC Group 2](https://docs.telcobridges.com/w/images/9/9a/Create_ISUP_CIC_Group_2.png) **Path** ``` /configurations/@[configuration_name]/isup_stacks/@[isup_stack]/isup_interfaces/@[isup_interface]/isup_cic_groups/@[isup_cic] ``` **Parameters (text)** ``` /configurations/@[configuration_name]/isup_stacks/@[isup_stack]/isup_interfaces/@[isup_interface]/isup_cic_groups/@[isup_cic] first_cic = 1 line_service = "@[line_service_name]" name = "@[isup_cic]" skip_ts16_cic = false timeslot_mask = 0x7fff7fff /configurations/@[configuration_name]/isup_stacks/@[isup_stack]/isup_interfaces/@[isup_interface]/isup_cic_groups/@[isup_cic]/advanced_parameters call_control = "Bothway" cic_mapping = "Linear" cic_options = [ ] generate_exit_message = false location_id = "" trunk_group_number = "" /configurations/@[configuration_name]/isup_stacks/@[isup_stack]/isup_interfaces/@[isup_interface]/isup_cic_groups/@[isup_cic]/state all_cics_forced_blocked = false all_cics_forced_unblocked = false cic_forced_blocked_mask = 0x0 cic_forced_unblocked_mask = 0x0 /configurations/@[configuration_name]/isup_stacks/@[isup_stack]/isup_interfaces/@[isup_interface]/isup_cic_groups/@[isup_cic]/timers circuit_validation_timer = "10 seconds" t3_timer = "2 minutes" t12_timer = "15 seconds" t13_timer = "5 minutes" t14_timer = "15 seconds" t15_timer = "5 minutes" t16_timer = "15 seconds" t17_timer = "5 minutes" ``` **Parameters (json)** ``` { "advanced_parameters" : { "call_control" : "Bothway", "cic_mapping" : "Linear", "cic_options" : [ ], "generate_exit_message" : false, "location_id" : "", "trunk_group_number" : "" }, "first_cic" : 1, "line_service" : "@[line_service_name]", "name" : "@[isup_cic]", "skip_ts16_cic" : false, "state" : { "all_cics_forced_blocked" : false, "all_cics_forced_unblocked" : false, "cic_forced_blocked_mask" : 0, "cic_forced_unblocked_mask" : 0 }, "timers" : { "circuit_validation_timer" : "10 seconds", "t3_timer" : "2 minutes", "t12_timer" : "15 seconds", "t13_timer" : "5 minutes", "t14_timer" : "15 seconds", "t15_timer" : "5 minutes", "t16_timer" : "15 seconds", "t17_timer" : "5 minutes" }, "timeslot_mask" : 2147450879 } ``` ### List of Parameters * [Name](https://prosbcdocs.telcobridges.com/telecom-references/parameter-reference/m3ua#n) * [First CIC](https://prosbcdocs.telcobridges.com/telecom-references/parameter-reference/isup#f) * [Line Service](https://prosbcdocs.telcobridges.com/telecom-references/parameter-reference/tdm#l) * [Skip timeslot 16 CIC](https://prosbcdocs.telcobridges.com/telecom-references/parameter-reference/isup#s) * [Timeslots](https://prosbcdocs.telcobridges.com/telecom-references/parameter-reference/isup#t) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://prosbcdocs.telcobridges.com/tmedia-documentation/configuration/web-portal-3-3/protocol-stack/ss7-isup/creating-isup-cic-groups.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.