Re: [SR-Users] Kamailio auth_radius: duplicate User-Name attribute

s on your kamailio server. > Mos likely something is miss configured there. > Check what value do you have for "User-Name" and see if you have any > duplicates for that value. > > > Regards, > Ovidiu Sas > > On Sat, Mar 5, 2011 at 2:32 AM, Kosilov Fedor > wrote

Re: [SR-Users] Kamailio auth_radius: duplicate User-Name attribute

Again for testing, I pointed Kamailio directly to my billing radius, bypassing Freeradius. The situation is the same, so the problem is definitely not with the Freeradius server. 2011/3/5 Kosilov Fedor > Hello, Daniel, thank you for your attention to my problem. > > I actually d

Re: [SR-Users] Kamailio auth_radius: duplicate User-Name attribute

Digest-Attributes = 0x01106c696e6b2d726567696f6e2e7275 Digest-Attributes = 0x0222545848676630317833314f7076767759512b6b73674c63554d51784f6c347634 Digest-Attributes = 0x04147369703a6c696e6b2d726567696f6e2e7275 Digest-Attributes = 0x030a5245474953544552 Digest-Attributes = 0x050661757468 Dige

[SR-Users] Kamailio auth_radius: duplicate User-Name attribute

Hello List! I'm trying to set up authorization with our billing proprietary radius server, using Freeradius as a proxy. Currently I'm experiencing the following problem: The Access-Request packet, sent by Kamailio, contains two User-Name attribute records Here is a log from the Freeradius server:

Re: [SR-Users] Question about the Q-value.

Many thanks to everybody for the answers. 2010/11/2 Ovidiu Sas > kamctl is able to do that. The syntax is in the default help iirc. > > > Regards, > Ovidiu Sas > > On Tue, Nov 2, 2010 at 2:58 PM, Juha Heinanen wrote: > > Kosilov Fedor writes: > > > >

Re: [SR-Users] Question about the Q-value.

Do you mean ul_add? This is not quite what I want to have.. I want everything to work automatically ;). By the way, how do you make permanent registrations? 2010/11/2 Juha Heinanen > Kosilov Fedor writes: > > > OK, and how do you usually deal with this? I was thinking of putti

Re: [SR-Users] Question about the Q-value.

OK, and how do you usually deal with this? I was thinking of putting the Q-value into the "Display Name" field, so when the device registers, I could get it using $fn (reference to display name of 'From' header) and put it directly to the location table in the database... __

[SR-Users] Question about the Q-value.

Hello, everybody! As I understand, the Q-value must be set by a client-side device. We use mainly Linksys SPA2102, I have searched through the web interface of this device but have not found where this value should be set. Is this parameter not supported by simple SOHO devices? Or have I misunderst

Re: [SR-Users] Strange behavior when rewriting "To" header from failure_route (kamailio - 3.0.2)

With timestamp, which seems to me to be unusual. So maybe it's impossible to rewrite "To" header from failure_route for some reason... (For example according to RFC) Actually my phones ring, and everything works fine, I am just interested with this behavior of Kamailio. Thanks agai

[SR-Users] Strange behavior when rewriting "To" header from failure_route (kamailio - 3.0.2)

R. CSeq: 101 INVITE. Max-Forwards: 69. Timestamp: 1275979181. Contact: . Expires: 180. Allow-Events: telephone-event. Content-Type: application/sdp. Content-Disposition: session;handling=required. Content-Length: 401. ... I'm trying to rewrite this one: To: >. with this one: