Legacy Asterisk Configuration#

This page preserves the legacy DIDWW configuration for Asterisk installations that still use chan_sip and sip.conf. chan_sip was deprecated in Asterisk 17, was no longer built by default beginning with Asterisk 19, and was removed in Asterisk 21.

Warning

Do not use this configuration for new installations. For current Asterisk releases, see Asterisk PJSIP Configuration (v20–23).

DIDWW SIP trunks can be used with Asterisk for inbound and outbound calls.

Dialplan example#

Add the inbound context to extensions.conf:

1[from-didww]
2exten => _X.,1,Ringing
3exten => _X.,n,Answer
4exten => _X.,n,Echo
5exten => _X.,n,Wait(600)
6exten => _X.,n,Hangup

Inbound trunk example#

Add the following peers to sip.conf:

 1[didww-ny]
 2host=46.19.209.14
 3dtmfmode=rfc2833
 4dtmf=rfc2833
 5type=peer
 6context=from-didww
 7insecure=invite,port
 8nat=never
 9allow=all
10
11[didww-fra]
12host=46.19.210.14
13dtmfmode=rfc2833
14dtmf=rfc2833
15type=peer
16context=from-didww
17insecure=invite,port
18nat=never
19allow=all
20
21[didww-la]
22host=46.19.212.14
23dtmfmode=rfc2833
24dtmf=rfc2833
25type=peer
26context=from-didww
27insecure=invite,port
28nat=never
29allow=all
30
31[didww-mia]
32host=46.19.213.14
33dtmfmode=rfc2833
34dtmf=rfc2833
35type=peer
36context=from-didww
37insecure=invite,port
38nat=never
39allow=all
40
41[didww-sg]
42host=46.19.214.14
43dtmfmode=rfc2833
44dtmf=rfc2833
45type=peer
46context=from-didww
47insecure=invite,port
48nat=never
49allow=all
50
51[didww-hk]
52host=46.19.215.14
53dtmfmode=rfc2833
54dtmf=rfc2833
55type=peer
56context=from-didww
57insecure=invite,port
58nat=never
59allow=all

For the current signaling address list, including Amsterdam and IPv6 addresses, see SIP Signaling Addresses.

Outbound trunk example#

Add the outbound peer to sip.conf:

1[didww-outbound]
2type=peer
3dtmfmode=rfc2833
4dtmf=rfc2833
5fromuser=DID_NUMBER
6auth=USERNAME:PASSWORD@out.didww.com
7secret=PASSWORD
8host=any.out.didww.com
9fromdomain=ASTERISK_IP_ADDRESS

Replace the placeholder values with your DIDWW outbound trunk details. For the current gateway list and authentication realm, see SIP Protocol Details.

Note

If Asterisk cannot find an extension within the given context, it returns an unhelpful No such context/extension error. Use the catch-all _X. pattern while troubleshooting, then replace it with the routing rules required by your deployment.