Difference between revisions of "Configuring DIDWW"

From Kolmisoft Wiki
Jump to navigationJump to search
 
(50 intermediate revisions by 5 users not shown)
Line 1: Line 1:
[[Image:didww.gif|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>
'''ATTENTION''':
Please add DIDWW provider several times for each ip . Check this page:
[https://www.didww.com/Knowledgebase/sip_ip_addresses_post Ip List]


'''Information provided below is not actual.'''


== Known DIDWW problems ==


# CallerID does not come in E164 format - only in local format
# FAS - Fast Call Answer - Call is answered instantly even if other end did not answered yet and user is ALWAYS charged for the call


=== CallerID does not come in E164 format - only in local format ===
'''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 [[How_to_add_DID_provider_with_multiple_IPs|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)
<br><br>
=== CallerID does not come in E.164 format, only in local format ===


'''QUESTION:'''
'''QUESTION:'''


  hello ! from Ukraine did caller id coming in not e164 format , coming in the local format like 80519539xx but must be 3805019539xx . Is it possible to fix this?
  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:'''
'''ANSWER:'''


  Your DID number is forwarded with CLI as it,i.e exactly how we get it.
  Your DID number is forwarded with CLI exactly as the local carrier sends it.
  Unfortunately, we cannot make any changes on Caller-ID format on particular number.However,we are checking what can be done it this case.
  Please check if it is possible to change the CLI on your end.<br>
Thank you for your patience in this matter.
 
Thank you for using DID World Wide services!
 
Best Regards,
Anna Remez
DID World Wide
 
 
=== FAS - Fast Call Answer - Call is answered instantly even if other end did not answered yet and user is ALWAYS charged for the call ===
 
'''QUESTION'''
 
hello ! people ,who is calling to this did getting ANSWER before i'm pickup the phone .
same if i'm not pickup long time they are have on the screen and in the billing invoice from there providers successfully connection like was ANSWER and paying money for nothing .
this is FAS ,, fake answer signal ,, and no good from yours side .
maybe this is problem not from you ,,,,,,,,-you are getting like this , but i'm have big problem with people who is calling to me !
 
----
 
'''ANSWER'''
 
With mobile phone service providers you will be billed from the second you hit the Send button, unlike landline phone service providers.
 
Thus it's normal that the mobile caller is billed even if the call wasn't answered on your side.
 
  Best Regards,
  Best Regards,
  Lev V.
  Customer Support Department
  DID World Wide
  DIDWW
 
<br><br>
== Configuring DIDWW for receiving calls to DID ==
= Configuring multiple DIDWW IPs for receiving calls to DID =
 
The problem with this DID Provider is that it send calls from many IP addresses:
 
* 212.150.36.116
* 212.150.88.20
* 212.150.88.21
* 204.11.194.34
* 204.11.194.35
* 204.11.194.36
* 204.11.194.37
* 204.11.194.38
* 81.85.224.41
 
 
Newest list can be fond [http://www.didww.com/support/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=35&nav=0,11 here]
 
<br><hr><br>
 
 
First create new Provider (most important parts are marked in red, '''Device ID can/will be different in your case - REMEMBER IT!!!'''):
 
[[Image:didww1.png]]
 
 
Then in '''/etc/asterisk/sip.conf''' at the very end enter (copy/paste):
 
[didww_116]
type=friend
context=mor
accountcode=5
host=212.150.36.116
 
[didww_21]
type=friend
context=mor
accountcode=5
host=212.150.88.21


[didww_34]
The problem with this DID Provider is that it sends calls from many IP addresses.
type=friend
context=mor
accountcode=5
host=204.11.194.34


[didww_35]
This is done due to load balancing techniques.
type=friend
context=mor
accountcode=5
host=204.11.194.35


[didww_36]
Please be sure you have granted access on your end to DIDWW Public IP Addresses:
type=friend
context=mor
accountcode=5
host=204.11.194.36


[didww_37]
type=friend
context=mor
accountcode=5
host=204.11.194.37


[didww_38]
The newest list can be found at [http://www.didww.com/Knowledgebase/the_list_of_didww_ip_addresses DIDWW IP Adresses]
type=friend
<!---This functionality is available from MOR 9--->
context=mor
accountcode=5
host=204.11.194.38


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


<center>'''<big><big><big>========== VERY IMPORTANT!!! ==========<br> accountcode should be == Device ID in your Provider window. In our case it is == 5. Change it accordingly to your correct value!!!</big></big></big>'''</center>
1. Create a provider in MOR, with a name didww:<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>
[[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]
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)
<br>
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
<br>
5. Make sure, file /etc/asterisk/sip.conf has this line included:
#include sip_didww.conf
<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>
6. [[How_to_restart_Asterisk_server | Restart Asterisk]]
<br>
Now your system is updated with all the DIDWW IP addresses that are listed in their recommendations.
<br><br>
'''Now there is no need to create one Provider for each IP'''
<br><br>


== DID configuration ==
= DID configuration =


Then:
Then:


* Save the file.
* Create DID - '''IN E.164 FORMAT!'''
* Reload Asterisk.
* Assign to a DIDWW Provider.
* Create DID - '''IN E164 FORMAT!!!!!!!!'''
* Assign to some device.
* Assign to DIDWW Provider
* Configure correct routing (mapping) in www.didww.com.
* Assign to some device
<br><br>
* Configure correct routing(mapping) in www.didww.com:
= Configuration in www.didww.com =
 
 
== Configuration in www.didww.com ==
 
We will assign Thailand, Bangkok number to our server:
 
First we need to create "mapping", e.g. route to our server, in format as SIP URI: SIP/did_on_our_server@our_server_ip:
 
[[Image:didww_pvz1.png]]
 
It should look like this:
 
[[Image:didww_pvz2.png]]
 
Aftre that we need to assign our DID to our just created "mapping":
 
[[Image:didww_pvz3.png]]
 
It should look like this:
 
[[Image:didww_pvz4.png]]
 
 
== Troubleshooting ==
 


Watch Asterisk CLI to see whats happening.
We will assign a Thailand, Bangkok number to our server:


Maybe you have DID in wrong format!? E.g. not E.164 compatible?
First we need to create "mapping", that is, the route to our server:
<br><br>
[[Image:didww11.png]]
<br><br>
After this, we need to assign our DID to our just-created "mapping":
<br><br>
[[Image:didww12.png]]
<br><br>
= Troubleshooting =


Watch Asterisk CLI to see what's happening.


<br><hr><br>
Maybe you have DID in the wrong format - for example, not E.164 compatible?
<br><br>
=See also=


If you are using IAX2 connection from DIDWW - create Provider with type = '''IAX2''' and paste sip.conf configuration in '''/etc/asterisk/iax.conf'''
* [[DID Management]]

Latest revision as of 12:19, 22 November 2019

Didww logo.jpg

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:
Provider create.png
2. Afterwards, enter any IP (or leave blank) in Provider Network settings, and write down Provider Device ID value, you will need it later.
Provider settings.png
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:

Didww11.png

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

Didww12.png

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