Hi,
I have sent this to asterisk-users list but no one
seems to be willing to discuss that matter...

Since * 1.2-beta1 (incl CVS HEAD) there is a change in the
callerid's output to STDERR when an AGI environment
dump is requested:

Asterisk CVS HEAD built by root @ chick on a i686 running
Linux on 2005-11-06 16:35:14 UTC
AGI Environment Dump:
 -- accountcode =
 -- callerid = 1234689
 -- calleridname = Caller Name
 -- callingani2 = 0
 -- callingpres = 0
 -- callingtns = 0
 -- callington = 0
 -- channel = SIP/222222-f55e
 -- context = default
 -- dnid = 19147858756
 -- enhanced = 0.0
 -- extension = 19147858756
 -- language = en
 -- priority = 1
 -- rdnis = unknown
 -- request = dump.agi
 -- type = SIP
 -- uniqueid = 1131381756.13

but ... Connected to Asterisk 1.0.9 currently running on dog
(pid = 28360)
AGI Environment Dump:
 -- accountcode =
 -- callerid = "Caller Name" <1234689>
 -- channel = SIP/222222-9351
 -- context = default
 -- dnid = 19147858756
 -- enhanced = 0.0
 -- extension = 19147858756
 -- language = en
 -- priority = 1
 -- rdnis = unknown
 -- request = dump.agi
 -- type = SIP
 -- uniqueid = 1131381457.0

Thus my question was "which is the future-to-be" callerid
format?
1.  -- callerid = 1234689
 -- calleridname = Callee Name
OR
2. -- callerid = "Callee Name" <1234689>
Nothing wrong with that in general since clid, as
${CDR(clid)}, is still being written correctly in 1.0.7,
1.0.9,
1.2-beta1&2 and CVS HEAD in the usual cdr database/table,
and in any custom table through
$dbh->quote($callerid).

However, since * 1.2-beta1 (incl CVS HEAD), when
AGI(perl) script try $callerid=$input{callerid} it results
to $dbh->quote($callerid) "calleridnum"(by
default it appears eq to "callerid"), only.

/* Obviously, because in res_agi.c "$Revision: 1.53 $":
fdprintf(fd, "agi_callerid: %s\n", chan->cid.cid_num ?
chan->cid.cid_num : "unknown");
fdprintf(fd, "agi_calleridname: %s\n", chan->cid.cid_name ?
chan->cid.cid_name : "unknown"); */

Changing to "$callerid=$input{calleridname}" is inserted as
requested.

Trying to group both callerid attributes results in an empty
string.

Playing with the dilaplan yet damages ${CDR(clid)}
record.

Any thoughts?
benchev


-----------------------------

Ñïîðòíè çàëàãàíèÿ!
bg.sportingbet.com

Reply via email to