Configuring DIDWW
DID World Wide, International DIDs forwarded to PSTN and VoIP by SIP, IAX, H323, Skype, Gtalk, MSN Messenger. Origination services, SIP DIDs.
Known DIDWW issues
- CallerID does not come in E.164 format - only in the local format.
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 DIDWW 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:
USA: 204.11.194.34 204.11.194.35 204.11.194.36 204.11.194.37 204.11.194.38 204.11.194.39 204.11.194.40 204.11.194.41
UK: 81.85.224.39 81.85.224.40 81.85.224.41
ME: 212.150.88.21 212.150.88.23 212.150.88.24
The newest list can be found at DIDWW IP Adresses
Create one Provider for each IP:
NOTE: Picture shows old IP addresses, make sure you are using current ones from DIDWW page!
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?
