Closed GoogleCodeExporter closed 9 years ago
Any ETA on this? It creates lots of confusion in hunt groups, since we don't
know if a call is being xferred to us, or it's the hunt group ringing.
Original comment by nik.mar...@gmail.com
on 17 Jan 2013 at 3:58
I have the same problem, I changed
//$tmp .= "caller_id_name = session:getVariable(\"caller_id_name\");\n";
//$tmp .= "caller_id_number = session:getVariable(\"caller_id_number\");\n";
to
$tmp .= "caller_id_name = session:getVariable(\"effective_caller_id_name\");\n";
$tmp .= "caller_id_number =
session:getVariable(\"effective_caller_id_number\");\n";
in lib_switch, we also changed to callerID based number called, 3 Businesses in
one.
Original comment by erin.ome...@salmonbaytechnology.com
on 15 Mar 2013 at 1:26
Updated libswitch.php to use effective_caller_id_name and
effective_caller_id_number. Please update, then save your huntgroup, call the
huntgroup, and report back the result.
Original comment by markjcrane@gmail.com
on 15 Mar 2013 at 2:23
this is a better solution in hind sight :)
$tmp .= "if session:getVariable(\"effective_caller_id_name\") == nil then\n";
$tmp .= "\tcaller_id_name = session:getVariable(\"caller_id_name\");\n";
$tmp .= "\tcaller_id_number = session:getVariable(\"caller_id_number\");\n";
$tmp .= "else\n";
$tmp .= "\tcaller_id_name = session:getVariable(\"effective_caller_id_name\");\n";
$tmp .= "\tcaller_id_number = session:getVariable(\"effective_caller_id_number\");\n";
$tmp .= "end\n";
Original comment by erin.ome...@salmonbaytechnology.com
on 18 Mar 2013 at 7:13
After doing a svn update, calls that did not have the effective_caller_id_name
set broke.
After updating to my above comment, that problem is fixed but my huntgroups are
broken. really unhappy customers :( seems like the leg_timeout is not being
used. debugging now.
Original comment by erin.ome...@salmonbaytechnology.com
on 18 Mar 2013 at 8:54
If the problem is critical and you need it solved immediately you need to
consider paid support.
This may be fixed in the soon to be released FusionPBX 3.3.
Original comment by markjcrane@gmail.com
on 29 Apr 2013 at 1:58
Hunt groups have been replaced by ring groups. Ring group have been improved to
provide all the features of hunt groups and more. Ring groups also have an
easier interface and superior design. Please upgrade your system if you haven't
done so already.
Original comment by markjcrane@gmail.com
on 27 Apr 2014 at 7:00
Original issue reported on code.google.com by
nik.mar...@gmail.com
on 21 Nov 2012 at 3:23