Home/Docs
Interconnect, without the guesswork.
The technical pack our NOC sends after a rate deck is agreed: SIP settings, test sequence, CDR format, API and escalation. Published here so your engineers can read it before the call.
Quickstart
Five settings and you're testing.
We'll send the hostnames and your credentials or IP allow-list entries in the interconnect email. Nothing below changes between accounts.
| SIP proxy | Provided per account (e.g. sip-us-east.megastice.com) |
|---|---|
| Transport | UDP 5060, TCP 5060, TLS 5061 |
| Auth | IP allow-list and/or digest credentials |
| Codec order | G.711 μ-law, G.729, Opus (G.722 optional) |
| DTMF | RFC 2833 / 4733 — payload 101 |
| Number format | E.164 with leading +; national accepted |
| Keepalive | OPTIONS every 30 seconds |
Firewall both directions for the RTP range. If you NAT, disable SIP ALG on the router — it rewrites headers and breaks media more often than it helps.
INVITE sip:+13075550142@us-east.megastice.com SIP/2.0
Via: SIP/2.0/TLS 203.0.113.24:5061;branch=z9hG4bK...
From: <sip:+13075550100@yourdomain.net>;tag=9as8d
To: <sip:+13075550142@us-east.megastice.com>
Call-ID: 3c2b7a1e@yourdomain.net
CSeq: 1 INVITE
Contact: <sip:+13075550100@203.0.113.24:5061;transport=tls>
Max-Forwards: 69
P-Asserted-Identity: <sip:+13075550100@yourdomain.net>
Content-Type: application/sdp
v=0
o=- 1 1 IN IP4 203.0.113.24
s=-
c=IN IP4 203.0.113.24
t=0 0
m=audio 10002 RTP/AVP 0 18 101
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
Example INVITE, trimmed. Use your assigned proxy and your own IPs.
Records & billing data
The CDR format, in full.
One row per call leg, comma-separated, UTF-8, delivered by 06:00 UTC for the previous day and available in the portal immediately after call completion.
| Field | Example | Notes |
|---|---|---|
| call_id | 3c2b7a1e-… | Unique per leg |
| start_utc | 2026-11-14T22:03:11Z | ISO 8601, UTC |
| duration_s | 184 | Billed seconds after increment rounding |
| from / to | +13075550100 / +447700900123 | E.164 |
| direction | outbound | outbound · inbound |
| destination | US-MOBILE | Matches the rate deck row |
| rate / amount | 0.0042 / 0.0129 | USD, 4 decimal places |
| disposition | ANSWERED | ANSWERED · BUSY · NOANSWER · FAILED |
| sip_code | 200 | Final response from the terminating side |
API
Enough API to stop emailing us.
Token-authenticated JSON over HTTPS. Use it for CDRs, balance, route status and DID inventory. Rate limits are 60 requests per minute per token.
GET /v1/cdr?from=&to=— paginated call recordsGET /v1/routes— destination status and active pathGET /v1/dids— numbers on your accountGET /v1/balance— prepay balance and credit limitPOST /v1/capacity— request a capacity change
Tokens are issued by the NOC after interconnect. Full OpenAPI spec on request from support@megastice.com.
curl https://api.megastice.com/v1/cdr \
-H "Authorization: Bearer $MS_TOKEN" \
-G --data-urlencode "from=2026-11-01" \
--data-urlencode "to=2026-11-14"
{
"data": [
{
"call_id": "3c2b7a1e",
"start_utc": "2026-11-14T22:03:11Z",
"duration_s": 184,
"to": "+447700900123",
"destination": "UK-MOBILE",
"amount": "0.0129",
"disposition": "ANSWERED"
}
],
"has_more": false
}
Example response, trimmed. All amounts USD.
Escalation
Who to call, in what order.
P1 means live traffic is failing. Don't email it. Call, then email the example calls so we can trace while you're on the line.
| P1 — traffic down | NOC phone · 15 min target · 24/7 |
|---|---|
| P2 — route degraded | NOC phone or support@ · 2 hours |
| P3 — provisioning | support@ · 1 business day |
| Commercial | sales@ · same business day |
| Compliance / traceback | weshan@ · 24 hours |
- Your account name and interconnect host
- Example calls: A-number, B-number, UTC timestamp
- SIP response code or cause code you received
- Scope: all destinations, or one route
- Whether the failure is signalling or media
With those five things, most P1s are diagnosed in the first call.
Need the full technical pack?
MSA, W-9, SIP settings, test plan and CDR spec — one email.