Re: [OpenSIPS-Users] Dispatcher radius messages are not valid
Hi Maciej, Sounds quite clear (from the err message) that the secrets on radius server and radius client are not the sameIt is not an opensips issue, it is a matter of configuring the radius server and radius client library. Regards, Bogdan Maciej Bylica wrote: Hello, I am working on opensips 1.6.3 $Revision: 4448 together with media-dispatcher 2.4.3, media-relay 2.4.3, python 2.5.2-3, freeradius 2.1.8, radiusclient-ng 0.5.6 Freeradius should gather radius messages directly from opensips and dispatcher. Both are installed on the same server and use the same radiusclient.conf file. The problem is that radius messages generated from dispatcher are not taken into account while i have no problem with opensips radius messages (secred for dispatcher and opensips is the same) Here is an output from radius server Waking up in 0.10 seconds. Thread 9 got semaphore Thread 9 handling request 121, (13 handled so far) [] Received Accounting-Request packet from client 10.1.1.229 with invalid signature! (Shared secret is incorrect.) Dropping packet without response. I've already tested freeradius-xs from debian pkg with same effect. I am running 32bit os linux debian lenny. Has anybody similiar problem. Could you guys pls point me what should i check? Thx in advance, Maciej ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -- Bogdan-Andrei Iancu OpenSIPS Bootcamp 15 - 19 November 2010, Edison, New Jersey, USA www.voice-system.ro ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Dispatcher radius messages are not valid
Nevertheless, thank You Bogdan. Has Anybody more less similiar problem like me? Thx, Maciej. 2010/11/12 Bogdan-Andrei Iancu : > I see... > > unfortunately I cannot help you with media-dispatchernever used it :-/ > > Regards, > Bogdan > > Maciej Bylica wrote: >> >> Ups sorry for not being so precise. >> I am talking about media-dispacher (not dispacher module) which is >> installed on the same server using radiusclient-ng >> Additionally there is media-relay running different ip. >> >> Thx, >> Maciej. >> >> 2010/11/11 Bogdan-Andrei Iancu : >> >>> >>> lost meif "dispatcher" is not "opensips acting as dispatcher", what >>> is >>> this "dispatcher" ??? >>> >>> Regards, >>> Bogdan >>> >>> Maciej Bylica wrote: >>> Hi Bogdan, >From my point of view it is not so clear, because opensips and dispatcher use the same secret (the same radiusclient.conf file) and are located on the same server. There are only one entry provided in radius server clients file describing ip address (the same for opensips and dispatcher) and secret (the same for opensips and dispatcher). So if opensips had permission to sent messages then in the same way dispatcher should be able to massage radius server. Thx, Maciej > > Hi Maciej, > > Sounds quite clear (from the err message) that the secrets on radius > server > and radius client are not the sameIt is not an opensips issue, it > is > a > matter of configuring the radius server and radius client library. > > Regards, > Bogdan > > Maciej Bylica wrote: > > >> >> Hello, >> >> I am working on opensips 1.6.3 $Revision: 4448 together with >> media-dispatcher 2.4.3, media-relay 2.4.3, python 2.5.2-3, freeradius >> 2.1.8, radiusclient-ng 0.5.6 >> Freeradius should gather radius messages directly from opensips and >> dispatcher. Both are installed on the same server and use the same >> radiusclient.conf file. >> >> The problem is that radius messages generated from dispatcher are not >> taken into account while i have no problem with opensips radius >> messages (secred for dispatcher and opensips is the same) >> Here is an output from radius server >> >> Waking up in 0.10 seconds. >> Thread 9 got semaphore >> Thread 9 handling request 121, (13 handled so far) >> [] Received Accounting-Request packet from client 10.1.1.229 >> with invalid signature! (Shared secret is incorrect.) Dropping packet >> without response. >> >> I've already tested freeradius-xs from debian pkg with same effect. >> I am running 32bit os linux debian lenny. >> >> Has anybody similiar problem. Could you guys pls point me what should >> i >> check? >> >> Thx in advance, >> Maciej >> >> ___ >> Users mailing list >> Users@lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> >> >> > > -- > Bogdan-Andrei Iancu > OpenSIPS Bootcamp > 15 - 19 November 2010, Edison, New Jersey, USA > www.voice-system.ro > > > ___ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>> >>> -- >>> Bogdan-Andrei Iancu >>> OpenSIPS Bootcamp >>> 15 - 19 November 2010, Edison, New Jersey, USA >>> www.voice-system.ro >>> >>> >>> ___ >>> Users mailing list >>> Users@lists.opensips.org >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>> >>> >> >> ___ >> Users mailing list >> Users@lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> > > > -- > Bogdan-Andrei Iancu > OpenSIPS Bootcamp > 15 - 19 November 2010, Edison, New Jersey, USA > www.voice-system.ro > > > ___ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Dispatcher radius messages are not valid
I see... unfortunately I cannot help you with media-dispatchernever used it :-/ Regards, Bogdan Maciej Bylica wrote: Ups sorry for not being so precise. I am talking about media-dispacher (not dispacher module) which is installed on the same server using radiusclient-ng Additionally there is media-relay running different ip. Thx, Maciej. 2010/11/11 Bogdan-Andrei Iancu : lost meif "dispatcher" is not "opensips acting as dispatcher", what is this "dispatcher" ??? Regards, Bogdan Maciej Bylica wrote: Hi Bogdan, >From my point of view it is not so clear, because opensips and dispatcher use the same secret (the same radiusclient.conf file) and are located on the same server. There are only one entry provided in radius server clients file describing ip address (the same for opensips and dispatcher) and secret (the same for opensips and dispatcher). So if opensips had permission to sent messages then in the same way dispatcher should be able to massage radius server. Thx, Maciej Hi Maciej, Sounds quite clear (from the err message) that the secrets on radius server and radius client are not the sameIt is not an opensips issue, it is a matter of configuring the radius server and radius client library. Regards, Bogdan Maciej Bylica wrote: Hello, I am working on opensips 1.6.3 $Revision: 4448 together with media-dispatcher 2.4.3, media-relay 2.4.3, python 2.5.2-3, freeradius 2.1.8, radiusclient-ng 0.5.6 Freeradius should gather radius messages directly from opensips and dispatcher. Both are installed on the same server and use the same radiusclient.conf file. The problem is that radius messages generated from dispatcher are not taken into account while i have no problem with opensips radius messages (secred for dispatcher and opensips is the same) Here is an output from radius server Waking up in 0.10 seconds. Thread 9 got semaphore Thread 9 handling request 121, (13 handled so far) [] Received Accounting-Request packet from client 10.1.1.229 with invalid signature! (Shared secret is incorrect.) Dropping packet without response. I've already tested freeradius-xs from debian pkg with same effect. I am running 32bit os linux debian lenny. Has anybody similiar problem. Could you guys pls point me what should i check? Thx in advance, Maciej ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -- Bogdan-Andrei Iancu OpenSIPS Bootcamp 15 - 19 November 2010, Edison, New Jersey, USA www.voice-system.ro ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -- Bogdan-Andrei Iancu OpenSIPS Bootcamp 15 - 19 November 2010, Edison, New Jersey, USA www.voice-system.ro ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -- Bogdan-Andrei Iancu OpenSIPS Bootcamp 15 - 19 November 2010, Edison, New Jersey, USA www.voice-system.ro ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Dispatcher radius messages are not valid
Ups sorry for not being so precise. I am talking about media-dispacher (not dispacher module) which is installed on the same server using radiusclient-ng Additionally there is media-relay running different ip. Thx, Maciej. 2010/11/11 Bogdan-Andrei Iancu : > lost meif "dispatcher" is not "opensips acting as dispatcher", what is > this "dispatcher" ??? > > Regards, > Bogdan > > Maciej Bylica wrote: >> >> Hi Bogdan, >> >> >From my point of view it is not so clear, because opensips and >> dispatcher use the same secret (the same radiusclient.conf file) and >> are located on the same server. >> There are only one entry provided in radius server clients file >> describing ip address (the same for opensips and dispatcher) and >> secret (the same for opensips and dispatcher). >> So if opensips had permission to sent messages then in the same way >> dispatcher should be able to massage radius server. >> >> Thx, >> Maciej >> >> >>> >>> Hi Maciej, >>> >>> Sounds quite clear (from the err message) that the secrets on radius >>> server >>> and radius client are not the sameIt is not an opensips issue, it is >>> a >>> matter of configuring the radius server and radius client library. >>> >>> Regards, >>> Bogdan >>> >>> Maciej Bylica wrote: >>> Hello, I am working on opensips 1.6.3 $Revision: 4448 together with media-dispatcher 2.4.3, media-relay 2.4.3, python 2.5.2-3, freeradius 2.1.8, radiusclient-ng 0.5.6 Freeradius should gather radius messages directly from opensips and dispatcher. Both are installed on the same server and use the same radiusclient.conf file. The problem is that radius messages generated from dispatcher are not taken into account while i have no problem with opensips radius messages (secred for dispatcher and opensips is the same) Here is an output from radius server Waking up in 0.10 seconds. Thread 9 got semaphore Thread 9 handling request 121, (13 handled so far) [] Received Accounting-Request packet from client 10.1.1.229 with invalid signature! (Shared secret is incorrect.) Dropping packet without response. I've already tested freeradius-xs from debian pkg with same effect. I am running 32bit os linux debian lenny. Has anybody similiar problem. Could you guys pls point me what should i check? Thx in advance, Maciej ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>> >>> -- >>> Bogdan-Andrei Iancu >>> OpenSIPS Bootcamp >>> 15 - 19 November 2010, Edison, New Jersey, USA >>> www.voice-system.ro >>> >>> >>> ___ >>> Users mailing list >>> Users@lists.opensips.org >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>> >>> >> >> ___ >> Users mailing list >> Users@lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> > > > -- > Bogdan-Andrei Iancu > OpenSIPS Bootcamp > 15 - 19 November 2010, Edison, New Jersey, USA > www.voice-system.ro > > > ___ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Dispatcher radius messages are not valid
lost meif "dispatcher" is not "opensips acting as dispatcher", what is this "dispatcher" ??? Regards, Bogdan Maciej Bylica wrote: Hi Bogdan, >From my point of view it is not so clear, because opensips and dispatcher use the same secret (the same radiusclient.conf file) and are located on the same server. There are only one entry provided in radius server clients file describing ip address (the same for opensips and dispatcher) and secret (the same for opensips and dispatcher). So if opensips had permission to sent messages then in the same way dispatcher should be able to massage radius server. Thx, Maciej Hi Maciej, Sounds quite clear (from the err message) that the secrets on radius server and radius client are not the sameIt is not an opensips issue, it is a matter of configuring the radius server and radius client library. Regards, Bogdan Maciej Bylica wrote: Hello, I am working on opensips 1.6.3 $Revision: 4448 together with media-dispatcher 2.4.3, media-relay 2.4.3, python 2.5.2-3, freeradius 2.1.8, radiusclient-ng 0.5.6 Freeradius should gather radius messages directly from opensips and dispatcher. Both are installed on the same server and use the same radiusclient.conf file. The problem is that radius messages generated from dispatcher are not taken into account while i have no problem with opensips radius messages (secred for dispatcher and opensips is the same) Here is an output from radius server Waking up in 0.10 seconds. Thread 9 got semaphore Thread 9 handling request 121, (13 handled so far) [] Received Accounting-Request packet from client 10.1.1.229 with invalid signature! (Shared secret is incorrect.) Dropping packet without response. I've already tested freeradius-xs from debian pkg with same effect. I am running 32bit os linux debian lenny. Has anybody similiar problem. Could you guys pls point me what should i check? Thx in advance, Maciej ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -- Bogdan-Andrei Iancu OpenSIPS Bootcamp 15 - 19 November 2010, Edison, New Jersey, USA www.voice-system.ro ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -- Bogdan-Andrei Iancu OpenSIPS Bootcamp 15 - 19 November 2010, Edison, New Jersey, USA www.voice-system.ro ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Dispatcher radius messages are not valid
Hi Bogdan, >From my point of view it is not so clear, because opensips and dispatcher use the same secret (the same radiusclient.conf file) and are located on the same server. There are only one entry provided in radius server clients file describing ip address (the same for opensips and dispatcher) and secret (the same for opensips and dispatcher). So if opensips had permission to sent messages then in the same way dispatcher should be able to massage radius server. Thx, Maciej > Hi Maciej, > > Sounds quite clear (from the err message) that the secrets on radius server > and radius client are not the sameIt is not an opensips issue, it is a > matter of configuring the radius server and radius client library. > > Regards, > Bogdan > > Maciej Bylica wrote: >> >> Hello, >> >> I am working on opensips 1.6.3 $Revision: 4448 together with >> media-dispatcher 2.4.3, media-relay 2.4.3, python 2.5.2-3, freeradius >> 2.1.8, radiusclient-ng 0.5.6 >> Freeradius should gather radius messages directly from opensips and >> dispatcher. Both are installed on the same server and use the same >> radiusclient.conf file. >> >> The problem is that radius messages generated from dispatcher are not >> taken into account while i have no problem with opensips radius >> messages (secred for dispatcher and opensips is the same) >> Here is an output from radius server >> >> Waking up in 0.10 seconds. >> Thread 9 got semaphore >> Thread 9 handling request 121, (13 handled so far) >> [] Received Accounting-Request packet from client 10.1.1.229 >> with invalid signature! (Shared secret is incorrect.) Dropping packet >> without response. >> >> I've already tested freeradius-xs from debian pkg with same effect. >> I am running 32bit os linux debian lenny. >> >> Has anybody similiar problem. Could you guys pls point me what should i >> check? >> >> Thx in advance, >> Maciej >> >> ___ >> Users mailing list >> Users@lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> > > > -- > Bogdan-Andrei Iancu > OpenSIPS Bootcamp > 15 - 19 November 2010, Edison, New Jersey, USA > www.voice-system.ro > > > ___ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] Dispatcher radius messages are not valid
Hello, I am working on opensips 1.6.3 $Revision: 4448 together with media-dispatcher 2.4.3, media-relay 2.4.3, python 2.5.2-3, freeradius 2.1.8, radiusclient-ng 0.5.6 Freeradius should gather radius messages directly from opensips and dispatcher. Both are installed on the same server and use the same radiusclient.conf file. The problem is that radius messages generated from dispatcher are not taken into account while i have no problem with opensips radius messages (secred for dispatcher and opensips is the same) Here is an output from radius server Waking up in 0.10 seconds. Thread 9 got semaphore Thread 9 handling request 121, (13 handled so far) [] Received Accounting-Request packet from client 10.1.1.229 with invalid signature! (Shared secret is incorrect.) Dropping packet without response. I've already tested freeradius-xs from debian pkg with same effect. I am running 32bit os linux debian lenny. Has anybody similiar problem. Could you guys pls point me what should i check? Thx in advance, Maciej ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
