Difference between revisions of "DID is not working"

From Kolmisoft Wiki
Jump to navigationJump to search
Line 1: Line 1:
* 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.
* 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
* If you can't see any output on Asterisk CLI when making call to DID, use '''sip debug''' or '''iax2 set debug''' commands

Revision as of 11:23, 31 March 2008

  • 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

'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:

  1. In register string add /SOME_DID at the end
  2. Create SOME_DID in DIDs window
  3. 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.

MOR can't determine who is calling. Make sure accountcode is set for caller (Provider or Device)

MOR can't determine who is calling. Make sure accountcode is set for caller (Provider or Device)