A new SIP line generally requires 3 things:
- A SIP line in the Lines container (minimum is to configure the name, domain, address for Identity (Out), transport (protocol, adapter, port), proxy (IP, port), and access (denied to all, explicit grant to IP of gateway)
- A line group (configure as dial group, add new SIP line as member)
- Dial plan entry (create new dial plan entry with desired input pattern, classification, standardized number (E.164), display string, and add dial group with appropriate dial string)
If the configuration above is present (sounds like it probably is from your description), then the next place to check is the SIPEngine log (turned up to Notes) for an example outbound call attempt. Use a quick string filter for SIP/2.0 and look at the SIP messaging for the call attempt (if any). If there are messages present, they should help to point to one side or the other (CIC or gateway) as being the cause. If no messages, then look in TSServer log (also at Notes) to see why). Some common causes are a transport protocol mismatch (TCP vs. UDP), port mismatch, incorrect IP (either in gateway pointing to CIC or in CIC SIP line pointing to gateway), or incorrect outbound routing to PSTN in gateway.