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 problems

1. CallerID does not come in E164 format - only in local format
2. 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

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?

ANSWER:

Your DID number is forwarded with CLI as it,i.e exactly how we get 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.
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,
Lev V.
DID World Wide

Configuring DIDWW 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

---

First create new Provider (most important parts are marked in red, Device ID can/will be different in your case - REMEMBER IT!!!):

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]
type=friend
context=mor
accountcode=5
host=204.11.194.34

[didww_35]
type=friend
context=mor
accountcode=5
host=204.11.194.35

[didww_36]
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]
type=friend
context=mor
accountcode=5
host=204.11.194.38

========== VERY IMPORTANT!!! ==========
accountcode should be == Device ID in your Provider window. In our case it is == 5. Change it accordingly to your correct value!!!

DID configuration

Then:

• Save the file.
• Reload Asterisk.
• Create DID - IN E164 FORMAT!!!!!!!!
• Assign to DIDWW Provider
• Assign to some device
• Configure correct routing(mapping) 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:

It should look like this:

Aftre that we need to assign our DID to our just created "mapping":

It should look like this:

Troubleshooting

Watch Asterisk CLI to see whats happening.

Maybe you have DID in wrong format!? E.g. not E.164 compatible?

---

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