[From nobody Fri Jul  9 15:27:31 2010
Received: from [10.0.144.231] (Forwarded-For: [10.0.146.231]) by
	pd7ims1.prod.shaw.ca (mshttpd); Fri, 09 Jul 2010 11:06:40 -0700
From: Tchavdar Paskov <chavpaskov@shaw.ca>
To: rupa@rupa.com
Message-ID: <d22f8d7c44613.4c3702c0@shaw.ca>
Date: Fri, 09 Jul 2010 11:06:40 -0700
X-Mailer: Sun Java(tm) System Messenger Express 6.2-7.05 (built Sep  5
 2006)
MIME-Version: 1.0
Content-Language: en
Subject: Mod_lcr lcr_user_rate suggestion
X-Accept-Language: en
Priority: normal
Content-Type: multipart/alternative; boundary="--dc636793472a6380c246"

This is a multi-part message in MIME format.

----dc636793472a6380c246
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi Rupa=2C

I found while working on the last version of the mod=5Flcr=A0 that by
default=A0 only lcr=5Fcarrier and lcr=5Frate=A0 are imported as channel
variables=A0 and in case of custom sql being used the=A0 lcr=5Fuser=5Fra=
te is
being populated only in the b-leg=2E

So currently=A0 if i want to have the complete info on call server by mo=
d=5Flcr=A0 i have to read both a =26 b-legs=2E

I went trhough the source and found lines=3A

1314

1317

1318

1436

1439

1440

1585

1588

1589



where string=A0 =22lcr=5Fcarrier=2Clcr=5Frate=22=A0 could be changed to
=22lcr=5Fcarrier=2Clcr=5Frate=2Clcr=5Fuser=5Frate=22=A0 and this will el=
iminate the need
of=A0 collecting the b-leg info=2E

This also obviously applies to=A0 all other lcr generated variables that=
 might be of any interest for billing purposes=2E

Pls let me know if this makes sense to you=2E

Regards

Chav Paskov

----dc636793472a6380c246
Content-Type: text/html; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Hi Rupa,<br>
I found while working on the last version of the mod_lcr  that by
default  only lcr_carrier and lcr_rate  are imported as channel
variables  and in case of custom sql being used the  lcr_user_rate is
being populated only in the b-leg.<br>
So currently  if i want to have the complete info on call server by mod_lcr  i have to read both a & b-legs.<br>
I went trhough the source and found lines:<br>
1314<br>
1317<br>
1318<br>
1436<br>
1439<br>
1440<br>
1585<br>
1588<br>
1589<br>
<br>
where string  "lcr_carrier,lcr_rate"  could be changed to
"lcr_carrier,lcr_rate,lcr_user_rate"  and this will eliminate the need
of  collecting the b-leg info.<br>
This also obviously applies to  all other lcr generated variables that might be of any interest for billing purposes.<br>
Pls let me know if this makes sense to you.<br>
Regards<br>
Chav Paskov

----dc636793472a6380c246--
]