|
Dear all, does anyone here use *bubua with Freeradius? I notice that when *bubua want to get the
Session-Timeout values, *bubua will send the following message to radius
servers(Here I use Freeradius): rad_recv: Access-Request packet from host 59.64.180.238:33150,
id=57, length=246
Cisco-Call-Type = "VoIP"
Calling-Station-Id = "005001"
Called-Station-Id = "005000"
Cisco-NAS-Port = "SIP/59.64.141.26-b7b13d20"
Cisco-AVPair = "call-codec=ulaw;useragent=X-Lite release 1105x;"
h323-call-origin = "originate" User-Name =
"005001"
NAS-Identifier = "Asterisk"
Framed-IP-Address = 59.64.141.26
NAS-IP-Address = 59.64.180.238 NAS-Port =
5060
h323-conf-id = [EMAIL PROTECTED] Here is the problem: the message didn’t contain any
password information (in fact *bubua won’t send the password), and then
Freeradius will reject the request because of lack of password. The Freeradius
debug information is: auth: No User-Password or CHAP-Password attribute in
the request auth: Failed to validate the user. My question is how to make the radius server accept
the request which do not contain the password and reply the Session-Timeout to
the *b2bua? Thanks! |
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
