debian 3.0
freeradius 1.0.1
postgresql 7.3.5
with quintum nas
 
radius_xlat:  'SELECT * FROM radcheck( '1234', '1234', '192.168.0.25', '', 'Async', '', '', 'h323-ivr-out=3DACCESSCODE:00800112233')
rlm_sql (sql): Reserving sql socket id: 0
rlm_sql_postgresql: query: SELECT * FROM radcheck( '1234', '1234', '192.168.0.25', '', 'Async', '', '', 'h323-ivr-out=3DACCESSCODE:2943000')
rlm_sql_postgresql: Status: PGRES_TUPLES_OK
rlm_sql_postgresql: affected rows =
radius_xlat:  ''
radius_xlat:  'SELECT * FROM radreply( '1234', '1234', '192.168.0.25', '', 'Async', '', '', '', 'h323-conf-id=3D34323131 64316430 32313400 00000031', '', '', '', '0049121154223')'
rlm_sql_postgresql: query: SELECT * FROM radreply( '1234', '1234', '213.204.65.162', '', 'Async', '', '', '', 'h323-conf-id=3D34323131 64316430 32313400 00000031', '', '', '', '0049121154223')'
and my query is like this:
authorize_check_query = "SELECT * radcheck( \
'%{User-Name}', \
'%{User-Password}', \
'%{NAS-IP-Address}', \
'%{NAS-Identifier}', \
'%{NAS-Port-Type}', \
'%{Service-Type}', \
'%{Framed-IP-Address}', \
'%{Quintum-AVPair}');"
 
variables takes 3D at the beginning of the content
for example;
the variable h323-ivr-out returns 3DACCESSCODE:00800112233 but it should be ACCESSCODE:00800112233
is there any opinion about this problem?
 
thank you for your help...


Do you Yahoo!?
Yahoo! Search presents - Jib Jab's 'Second Term'

Reply via email to