Difference between revisions of "DID is not working"
From Kolmisoft Wiki
Jump to navigationJump to search
Line 4: | Line 4: | ||
* Check for error message | * Check for error message | ||
<br><br> | |||
= DID in wrong format = | |||
DID in the system must be in E.164 format. | |||
# Create DID in the system in E.164 format | |||
# Call to the system, watch CLI | |||
# If DID comes not in E.164 format - use Localization to fix incoming broken DID number and convert it to E.164 format | |||
<br><br> | |||
=='s' extension== | =='s' extension== | ||
Revision as of 10:06, 6 May 2011
- Do you need to register to your Provider in order to use DID from him? (Usual answer is YES). Did you registered to your provider?
- Check Asterisk CLI for error message.
- If you can't see any output on Asterisk CLI when making call to DID, use sip debug or iax2 set debug commands
- Check for error message
DID in wrong format
DID in the system must be in E.164 format.
- Create DID in the system in E.164 format
- Call to the system, watch CLI
- If DID comes not in E.164 format - use Localization to fix incoming broken DID number and convert it to E.164 format
's' extension
- If 's' extension is reached means your provider does not send destination information.
Usually you will hear "SOMETHING IS TERRIBLY WRONG" when call goes to s extension.
Solution:
- In register string add /SOME_DID at the end
- Create SOME_DID in DIDs window
- Assign this SOME_DID to some device
Example:
register => username:secret@sip.provider.com/1234567890
Now every call which comes from sip.provider.com will go to DID 1234567890.
We need to create such DID and assign some device to it to receive all calls coming from this provider.
This solution is workaround when provider does not send correct destination information (most of providers do this).
One bad thing about this is that only 1 device can receive calls from this provider.
In order to receive calls to several DIDs->Devices you need to tell your provider to send correct destination information.