Difference between revisions of "VoiceBlue Ring problem"
| Line 53: | Line 53: | ||
*Add extension which should be dialed on SIP server in "List of called numbers" list. | *Add extension which should be dialed on SIP server in "List of called numbers" list. | ||
[[Image:voiceblue_incoming_conf. | [[Image:voiceblue_incoming_conf.png]] | ||
<br><br> | <br><br> | ||
Revision as of 10:58, 13 December 2012
Ring problem
set to ->2 (instead of 0 or 1) "Delay of ALERTING (s)" parameter.
This parameter should indicated how much second voip interface have to wait from gsm interface to send ring information. Manual say:
"Delay for ALERTING [s]: a delay before sending information on ringing start"
Then, about RING, you can choose if sending Ringing made from Asterisk ("Send 180 ringing instead of 183 Session progress" option checked) or let the user calling listen the ringing signal information sent from the GSM Network.
Bad setting
Good setting
SIP setting
If nothing works
Then try to communicate with Device over Telnet.
Set Alert from 0sec to 2sec via telnet: at%g19=2,0,0,0
Set SIP/180 instead of SIP/183: at%e08=2
Got SIP response 484 "Address Incomplete" back from X.X.X.X
Try to change number format. In Lithuania it is necessary to add international prefix 00.
GSM to SIP server configuration
In order to forward incoming call to SIP server (like MOR), following changes should be made:
- Go to "GSM Incoming groups" section in VoiceBlue configuration program;
- Set "Mode" to "Accept incoming calls + dialtone";
- Set "Timeout of entering DTMF digits" to 0;
- Add extension which should be dialed on SIP server in "List of called numbers" list.
