Yes, the same result. I made now a trace and found that in the "From" and "P-Asserted-Identity" the display name is correct (the number) but the display number is wrong (the account). Wondering now where to set them to correctly apply. Thanks Anestis _____ From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Avi Marcus Sent: Sunday, September 11, 2011 8:47 AM To: FreeSWITCH Users Help Subject: Re: [Freeswitch-users] mod_lcr transfer shows wrong caller id Did you set effective_caller_id in the A-leg to the value you want? -Avi On Sun, Sep 11, 2011 at 8:43 AM, Anestis Mavro <devel@omninet.eu> wrote: Hi, I've been using mod_lcr with nibblebill for a while and everything worked fine with the bridge application. Now I would like to add limit and I have to use it as dialplan like this: <action application="transfer" data="${callednumber} lcr ${lcrprofile}" /> I managed to configure the lcr.conf.xml correctly for Limit and everything seems to be working beside the caller id. Now the variable origination_caller_id_number gets the accountcode instead of the correct number. I've tried to explicitly set the variable before transferring and even in the lcr.conf.xml and export it. no chance. Any idea?? Thanks __________ Information from ESET NOD32 Antivirus, version of virus signature database 5054 (20100423) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org __________ Information from ESET NOD32 Antivirus, version of virus signature database 5054 (20100423) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com