Closed GoogleCodeExporter closed 9 years ago
Update to the latest version. Then run Advanced -> Upgrade Schema. Then test
the ringback again.
Original comment by markjcrane@gmail.com
on 9 Feb 2013 at 6:51
I've updated to r3762 but the problem still persist.
If the modified file is lib_switch (variable ignore_early_media), I've seen
that when I enable follow me, the extension dial string is set to:
{group_confirm_key=exec,group_confirm_file=lua confirm.lua,instant_ringback=true,ignore_early_media=true,sip_invite_domain=<DOMAIN>,call_prompt=true}[presence_id=<EXTNUMBER>@<DOMAIN>,leg_delay_start=10,leg_timeout=30]loopback/<EXTNUMBER>
Is the "ignore_early_media=true" correct? Anyway, if I cancel this variable
from the dial string, I don't hear the ringback and DTMF are still no working.
Original comment by carlo.di...@gmail.com
on 11 Feb 2013 at 8:29
for the DTMF issue, start_dtmf in confirm.lua resolved it:
- diff confirm.lua confirm.lua.orig
58d57
< session:execute("start_dtmf");
the ringback problem persists.
Original comment by carlo.di...@gmail.com
on 11 Feb 2013 at 11:39
ok, more info on this.
I have bypass_media=true, so it seems that fs doesn't send ringback in this
mode. Changing to bypass_media_after_bridge=true it works.
Now, the last problems are:
1) the confirm is asket even if the Call Prompt: false
2) if the call is originated form an external number (sip trunk), the script
show this error:
EXECUTE sofia/external/<EXTNUMBER> lua(confirm.lua)
2013-02-11 13:11:28.349614 [ERR] mod_lua.cpp:198
/usr/local/freeswitch/scripts/confirm.lua:50: attempt to concatenate global
'domain_name' (a nil value)
stack traceback:
/usr/local/freeswitch/scripts/confirm.lua:50: in main chunk
Original comment by carlo.di...@gmail.com
on 11 Feb 2013 at 12:14
"for the DTMF issue, start_dtmf in confirm.lua resolved it: "
"bypass_media_after_bridge=true"
Could be set in the dialplan or in the inbound route.
This is a provider specific issue for a carrier that uses inband.
Original comment by markjcrane@gmail.com
on 24 Feb 2013 at 7:01
Original issue reported on code.google.com by
carlo.di...@gmail.com
on 8 Feb 2013 at 5:07