Closed lgaetz closed 9 years ago
Wow! I make that about an hour from me raising a ticket to a full fix.
Now if only I could get that sort of service from the developers in my day job...
Patch implemented in my system, and all looks good so far.
Does anyone else get non numerical characters in the CLI?
I am still trying to figure out exactly under what circumstances the hyphen and space are presented. I only see them on my POTS line, and only when the caller is also calling from a POTS line in my city.
I have heard of Superfecta failing for this reason before, just recently in fact. The situation was with an incoming POTS line being answered by an Obihai FXO device, and either the POTS line was supplying the CID with non-digit characters, or the Obihai was modifying the CID before passing it to the PBX. The hack was to fix the CID string with a custom context before passing to the from-trunk context.
Doesnt seem like this was fixed. Anyways I just changed it to !empty() since there is no reason to run the checks on an empty CID
As reported by user @rambo1152, if superfecta is invoked with an incoming CID containing non-digits, it will not run. Log output:
Located on line 36 of /agi/superfecta.agi is this line:
this check will only permit Superfecta to run if the CID contains digits. For testing purposes I changed it to:
and reran the test with this output:
Success! I can't see any reason to force this check. I will leave in production on a few systems for a few days and report back if any issues.