[Serusers] Vovida's B2BUA and SER ?
Lucas Aimaretto
lucas at cyneric.com
Thu Apr 28 18:23:30 CEST 2005
> > ... It works nicely. Nicely if the User
> > has NO PASSWORD ASSIGNED ...
> >
> > This is the configuration:
> >
> >
> > UA <----> B2BUA <---> SER
> > |
> > |
> > RADIUS
> >
> > When an INVITE is sent ... b2bua sends Authorization to
> > RADIUS ... but
> > as User-Password value, it sends a dot ( yes!!! a DOT "." ) ... look
> >
> > rad_recv: Access-Request packet from host 192.168.1.253:1024, id=1,
> > length=82
> > User-Name = "1992001"
> > User-Password = "."
> > NAS-IP-Address = 192.168.1.253
> > NAS-Port = 1000
> > Called-Station-Id = "543515684478"
> > Calling-Station-Id = "1992001"
> >
> > [ ... ]
> >
> > .... obviously, the user will never authenticate.
> >
> > [ ... ]
> >
> You could give your users a password ='.' that would make it work
> :-), or use asterisk B2BUA, or there is a commercial one called sippy.
Nice solution, but I do not think my boss will like to have that
password assigned to the clients ;-)
> From vovida doc ...
>
> 2. The password sent for authorization is hard-coded to "." .
> To suit a
> specific vendor in the future, there is a plan to incorporate
> a vendor
> specific password in the B2BUA configuration file. This password can
> also come from provisioning.
Any docs where to have asterisk working as a b2bua ??? Have you tried it
??? Is it a nice solution ??? Any body tried sippy ???
Thanx
Regards,
Lucas
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.10.4 - Release Date: 27/04/2005
More information about the sr-users
mailing list