Configuring DIDWW

DID World Wide, International DIDs forwarded to PSTN and VoIP by SIP, IAX, H323, Skype, Gtalk, MSN Messenger. Origination services, SIP DIDs.

ATTENTION: Please add DIDWW provider several times for each ip . Check this page: Ip List

Information provided below is not actual.

PLEASE NOTE: DIDww provider is already configured in MOR system by default, so you not need to add DIDww Provider in MOR again. Use this manual as example to configure other DID Providers which have many IPs. If DID provider have one or few IPs, then please refer to this manual instead.

Known DIDWW issues

• CallerID does not come in E.164 format - only in the local format.
• Not possible to use for Callback: No Callback Calls: by entering into this Agreement the Customer acknowledges and agrees that the DID numbers provided by DIDWW cannot be used for callback applications.(http://www.didww.com/DIDWW-Terms-and-Agreements)

CallerID does not come in E.164 format, only in local format

QUESTION:

Hello ! from Ukraine DID CallerID is not coming in the E.164 format.
It is coming in the local format like 80519539xx, but must be 3805019539xx. 
Is it possible to fix this?

ANSWER:

Your DID number is forwarded with CLI exactly as the local carrier sends it.
Please check if it is possible to change the CLI on your end.

Best Regards,
Customer Support Department
DIDWW

Configuring multiple DIDWW IPs for receiving calls to DID

The problem with this DID Provider is that it sends calls from many IP addresses.

This is done due to load balancing techniques.

Please be sure you have granted access on your end to DIDWW Public IP Addresses:

The newest list can be found at DIDWW IP Adresses

It is possible to implement multiple DIDWW IP addresses by making these changes:

1. Create a provider in MOR, with a name didww:

2. Afterwards, enter any IP (or leave blank) in Provider Network settings, and write down Provider Device ID value, you will need it later.

3. Now connect to your server over ssh and locate this file /etc/asterisk/extensions_mor_didww.conf and find these lines:

[from-didww]
exten => _X.,1,Set(CDR(ACCOUNTCODE)=0)
exten => _X.,2,Goto(mor,${EXTEN},1)

Now you need to change (ACCOUNTCODE)=0 value (0) to Provider Device ID value as follows:

exten => _X.,1,Set(CDR(ACCOUNTCODE)=6)
exten => _X.,2,Goto(mor,${EXTEN},1)

4. Make sure, file /etc/asterisk/extensions_mor_custom.conf (which is not overwritten during the update) has this line included:

 #include extensions_mor_didww.conf

5. Make sure, file /etc/asterisk/sip.conf has this line included:

#include sip_didww.conf

NOTE: sip_didww.conf file contains list of DIDWW server IPs, so this file must be included if you are using DIDWW DIDs. Without this list, all incoming calls from DIDWW will not be allowed by MOR.

6. Restart Asterisk
Now your system is updated with all the DIDWW IP addresses that are listed in their recommendations.

Now there is no need to create one Provider for each IP

DID configuration

Then:

• Create DID - IN E.164 FORMAT!
• Assign to a DIDWW Provider.
• Assign to some device.
• Configure correct routing (mapping) in www.didww.com.

Configuration in www.didww.com

We will assign a Thailand, Bangkok number to our server:

First we need to create "mapping", that is, the route to our server:



After this, we need to assign our DID to our just-created "mapping":

Troubleshooting

Watch Asterisk CLI to see what's happening.

Maybe you have DID in the wrong format - for example, not E.164 compatible?

See also

• DID Management