Difference between revisions of "MOR API callback init"
From Kolmisoft Wiki
Jump to navigationJump to search
| Line 3: | Line 3: | ||
=Request= | =Request= | ||
http://<YOUR_SERVER_IP>/mor/api/callback?u=<USERNAME>&p=<PASSWORD>device=<DEVICE_ID>&src=<SOURCE>&dst=<DESTINATION> | http://<YOUR_SERVER_IP>/mor/api/callback?u=<USERNAME>&p=<PASSWORD>&device=<DEVICE_ID>&src=<SOURCE>&dst=<DESTINATION> | ||
* USERNAME/PASSWORD - for user, not device! | * USERNAME/PASSWORD - for user, not device! | ||
Revision as of 10:56, 10 August 2009
Request
http://<YOUR_SERVER_IP>/mor/api/callback?u=<USERNAME>&p=<PASSWORD>&device=<DEVICE_ID>&src=<SOURCE>&dst=<DESTINATION>
- USERNAME/PASSWORD - for user, not device!
- DEVICE_ID - which device should be used to initiate callback and which CALLERID will be set on the call
- SOURCE - which number to dial first
- DESTINATION - will be dialed when SOURCE will answer
You can omit <DESTINATION>. SOURCE will be asked to enter it if you do so.
Response
<Status>Ok</Status>
- Means callback is initiated
Errors
Not authenticated
<Status>Not authenticated</Status>
- User is not present with provided username
- User's password is wrong
Bad device
<Status>Bad device</Status>
- Device does not exist
- Device should belong to user if user does not have 'admin' rights.
No source
<Status>No source</Status>
- No source in request
Call is not received
- Check your CDR for FAILED call and reason why it failed
- Check Asterisk CLI for error
- Use Call Tracing to locate error and fix it
