Greetings list,
Wondering if anyone can shed some light on an apparent change in CDRs between
1.2 and 1.4.
One of our clients runs a virtual PA service and has a few hundred DDIs - one
for each client. Their * box is set up with short codes they prefix their calls
with to set the correct outbound CLID, so for example:
123*<number_to_be_dialled>
This simply does the following:
Set(CALLERID(number)=<clid_to_use>
Goto(outbound,${EXTEN:4},1)
In * 1.2, this resulted in the callerid field of their CDRs reflecting the
change from their extension number to <clid_to_use>, which they could then
use to correctly apportion outbound calls to their clients. However, in 1.4, the
callerid field retains the original extension number which initiated the call,
which means billing is next to impossible based on callerid.
Our current workaround is to append the CLID to the accountcode field, which
works, but does require extra processing of the CDRs each month, which is far
from ideal.
So, two questions if I may:
1) is this a result of the 1.2 -> 1.4 upgrade, or is it possible something
else has caused this? (basically, is this a known issue or "feature"
of 1.4?)
2) Is it possible to revert back to the previous behaviour?
Thanks in advance!
Regards,
Chris
--
For full contact details visit http://www.minotaur.it
This email is made from 100% recycled electrons
On Thursday 06 August 2009 05:27:57 Chris Bagnall wrote:> Greetings list, > > Wondering if anyone can shed some light on an apparent change in CDRs > between 1.2 and 1.4. > > One of our clients runs a virtual PA service and has a few hundred DDIs - > one for each client. Their * box is set up with short codes they prefix > their calls with to set the correct outbound CLID, so for example: > > 123*<number_to_be_dialled> > > This simply does the following: > Set(CALLERID(number)=<clid_to_use> > Goto(outbound,${EXTEN:4},1) > > In * 1.2, this resulted in the callerid field of their CDRs reflecting the > change from their extension number to <clid_to_use>, which they could then > use to correctly apportion outbound calls to their clients. However, in > 1.4, the callerid field retains the original extension number which > initiated the call, which means billing is next to impossible based on > callerid.While not a change in the callerid management, it is possible that one or more channels now set CALLERID(ani), in addition to CALLERID(num). The ANI, when present, is preferred over the number for presentation in the CDR. I suspect that if you modify this value, the CDR will work as it did before. -- Tilghman & Teryl with Peter, Cottontail, Midnight, Thumper, & Johnny (bunnies) and Harry, BB, & George (dogs)