I have to implement Kamailio with Radius authentication process. Unfortunately, the available documentation for auth_radius module doesn't help me so much (I mean, I ve tried to use auth_radius module and radius_www_authorize(realm) function but without success). Are there some aditional steps that I should follow or I have to use new functions or modules? Can you provide me some tips in order to implement this authentication process?
Thank you for any help you can provide!
I do not know exact answer.
Probably you should read auth_radius module documentation and tweak kamailio.cfg.
Also you can post your question to Kamailio mailing list, thats the best place to get answer for it.
Related
I'd like to ask for recommendations. I want to write a client program using MQTT to publish data to the broker. I can´t use any client libraries available in the internet. I would like to ask where can I find examples that works similar to this as an inspiration for my work, or any suggestions regarding the steps I should follow is highly appreciated.
Thank you!
To do this, you have to know well the MQTT protocol, in order to use adequately commands and messages needed to perform the communication.
Regarding the protocol, you can find documentation in the official page and a good explanation in this HiveMQ page. One example of a simple MQTT client implementation, in Java, can be seen in this tutorial.
I have been provided with a WebService with a REST Interface, implemented as a DLL.The documentation is really poor, and does not detail all the possible parameters.
Is there any way to get all the parameters that the DLL can accept without disassembling the DLL(something like a man function)?
Thanks a lot for your help!
In general you can't.
Of course you can list all functions with DLL Export Viewer and hope that you will find something like man function. But most probably you should use trial and error method here. Call functions and examine what they do.
PS: if there's a way to obtain documentation or source code, it will be the most correct way.
The short answer is "very unlikely". It really depends on how those services were implemented. If they really are REST, they should comply with the HATEOAS principle, so you should theoretically be able to navigate all the services just by following links provided by the responses. If this is true, all you need to know is the entry point of the services.
Or, there could be a WADL describing the service 'topology' (https://en.wikipedia.org/wiki/Web_Application_Description_Language).
On the other hand, if the services were not implemented this way (I won't say 'properly', but..), I am afraid you don't have many options apart from diving into the implementation.
We are thinking about writing a softphone app. It would basically be a component of a system that has calls queued up from a database. It would interface with a LINUX server which has Asterisk installed.
My first question is
Whether we should write the softphone at all or just buy one?
Secondly, if we do,
what base libraries should be use?
I see SIP Sorcery on CodePlex. More than anything, I am looking for a sense of direction here. Any comments or recommendations would be appreciated.
The answer would depend on the capabilities you have in your team and the place you see your core value and the essence of the service you provide.
In most cases, I'd guess that you don't really care about SIP or doing anything fancy with it that require access to its low level. In such a case, I'd recommend getting a ready-made softphone - either a commercial one or an open source one. I'd go for a commercial one, as it will give you the peace of mind as to its stability and assistance with bug fixing and stuff.
To directly answer your question, one of the many open source softphones are likely to fit your needs, and allow slight modifications as needed. Under most open source licenses there is no obligation to distribute your code as long as you only use it internally (do not distribute the binary.)
Trying to guess what you are trying to do, it sounds like a call center like scenario, so one of the many call queue implementations out there might fit your needs.
I had to write an own softphone and I found a great guide how to achieve it. In the guide there are 10 steps provided for having an own softphone (voip-sip-sdk.com on page 272)
I found it useful and maybe you will find it as well.
I've been trying to get Thrift to work with WP7, but has put it on hold preliminary.
I'm now looking for other solutions to this and would like to get some feedback on which solution to choose, if any.
Any suggestions is much appreciated, so don't hesitate :)
You might need to hive us a little more detail. Like a link to Thrift would be helpful. Not sure what you are trying to do.
I bing "Thrift" and get a bunch of things (one of which appears to be a commercial service/web site). I bing "thrift api" and get references to an Apache project.
Help us to help you.
I have looked online at making a multi-threaded server in perl, but i cannot find any good ones that clearly explain how to create one. I have created a server and client in perl but i do not seem to be able to make it multi-threaded. Can someone help me?
Assuming you are using the Net::Server CPAN module (rather than rolling your own), you could make use of Net::Server::Coro to build a multi-threded server. Note that Net::Server can handle (pre)forking (i.e. multi-processes) servers and these may be easer to use.
I think POE might be what you're looking for.
See the POE Cookbook for examples.