Difference between revisions of "Configuring DIDWW"
| Line 1: | Line 1: | ||
[[Image:didww_logo.jpg|right]][http://www.didww.com DID World Wide], International DIDs forwarded to PSTN and VoIP by SIP, IAX, H323, Skype, Gtalk, MSN Messenger. Origination services, SIP DIDs. | [[Image:didww_logo.jpg|right]][http://www.didww.com DID World Wide], International DIDs forwarded to PSTN and VoIP by SIP, IAX, H323, Skype, Gtalk, MSN Messenger. Origination services, SIP DIDs. | ||
<br><br> | <br><br> | ||
= Known DIDWW issues = | = Known DIDWW issues = | ||
| Line 6: | Line 5: | ||
* CallerID does not come in E.164 format - only in the local format. | * 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) | * 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) | ||
<br><br> | <br><br> | ||
=== CallerID does not come in E.164 format, only in local format === | === CallerID does not come in E.164 format, only in local format === | ||
| Line 23: | Line 21: | ||
Customer Support Department | Customer Support Department | ||
DIDWW | DIDWW | ||
<br><br> | <br><br> | ||
= Configuring multiple DIDWW IPs for receiving calls to DID = | = Configuring multiple DIDWW IPs for receiving calls to DID = | ||
| Line 36: | Line 32: | ||
The newest list can be found at [http://www.didww.com/Knowledgebase/the_list_of_didww_ip_addresses DIDWW IP Adresses] | The newest list can be found at [http://www.didww.com/Knowledgebase/the_list_of_didww_ip_addresses DIDWW IP Adresses] | ||
<!---This functionality is available from MOR 9---> | |||
It is possible to implement multiple DIDWW IP addresses by making these changes: | It is possible to implement multiple DIDWW IP addresses by making these changes: | ||
1 | 1. Create a provider in MOR, with a name didww:<br> | ||
[[File:provider_create.png]] <br> | [[File:provider_create.png]] <br> | ||
2. Afterwards, enter any IP (or leave blank) in Provider Network settings, and write down Provider Device ID value, you | |||
will need it later.<br> | will need it later.<br> | ||
[[File:provider_settings.png]]<br> | [[File:provider_settings.png]]<br> | ||
3. Now connect to your server over ssh and locate this file /etc/asterisk/extensions_mor_didww.conf and find these lines: | |||
[from-didww] | [from-didww] | ||
exten => _X.,1,Set(CDR(ACCOUNTCODE)=0) | exten => _X.,1,Set(CDR(ACCOUNTCODE)=0) | ||
| Line 55: | Line 49: | ||
exten => _X.,2,Goto(mor,${EXTEN},1) | exten => _X.,2,Goto(mor,${EXTEN},1) | ||
<br> | <br> | ||
4. Make sure, file /etc/asterisk/sip.conf has this line included: | |||
#include sip_didww.conf | #include sip_didww.conf | ||
<br> | <br> | ||
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.<br> | 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.<br> | ||
<br> | <br> | ||
5. [[How_to_restart_Asterisk_server | Restart Asterisk]] | |||
<br> | <br> | ||
Now your system is updated with all the DIDWW IP addresses that are listed in their recommendations. | Now your system is updated with all the DIDWW IP addresses that are listed in their recommendations. | ||
| Line 66: | Line 60: | ||
'''Now there is no need to create one Provider for each IP''' | '''Now there is no need to create one Provider for each IP''' | ||
<br><br> | <br><br> | ||
= DID configuration = | = DID configuration = | ||
| Line 75: | Line 68: | ||
* Assign to some device. | * Assign to some device. | ||
* Configure correct routing (mapping) in www.didww.com. | * Configure correct routing (mapping) in www.didww.com. | ||
<br><br> | <br><br> | ||
= Configuration in www.didww.com = | = Configuration in www.didww.com = | ||
| Line 84: | Line 74: | ||
First we need to create "mapping", that is, the route to our server: | First we need to create "mapping", that is, the route to our server: | ||
<br><br> | |||
[[Image:didww11.png]] | [[Image:didww11.png]] | ||
<br><br> | |||
After this, we need to assign our DID to our just-created "mapping": | After this, we need to assign our DID to our just-created "mapping": | ||
<br><br> | |||
[[Image:didww12.png]] | [[Image:didww12.png]] | ||
<br><br> | <br><br> | ||
= Troubleshooting = | = Troubleshooting = | ||
| Line 97: | Line 86: | ||
Maybe you have DID in the wrong format - for example, not E.164 compatible? | Maybe you have DID in the wrong format - for example, not E.164 compatible? | ||
<br><br> | |||
=See also= | |||
* [[DID Management]] | |||
Revision as of 08:54, 7 March 2013
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.
- 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)=8)
exten => _X.,2,Goto(mor,${EXTEN},1)
4. 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.
5. 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?
