A user case:
lets assume company A is a VoIP minutes resellers and has N clients.
'A' will have to install/configure a voip box in the clients' premices and sometimes 'A' will need to update/upgrade(firmware) the voip boxes;
the real case we had here is the number of clients was growing very fast so:
- either configure the boxes then send it to the clients (in this case the client will not have the choice of buying voip boxes from other hardware suppliers) or
- go visit each client and do the setup there (this solution will kill the business)
Knowing that almost all voip boxes can load firmware or config files from a given tftp server, the best solution (for some voip providers) is to send the voip boxes to the clients and let the boxes upload the configs or firmware remotely (from an tftp server) once they have internet connectivity.
That tftp server could be an an 'AS' for for mobicents.
hoping to be correct,
Regards,
On Thu, Mar 31, 2011 at 9:22 PM, Ivelin Ivanov <ivelin.atanasoff.ivanov@gmail.com> wrote:
Tom, thank you for the contribution.Ibrahim, can you please describe the use cases that you have in mind. A blog post related to this contribution with reference to a practical example would be nice.
IvelinHi Tom,it will be very helpful for those working on VoIP termination;regards,IbrahimOn Tue, Mar 29, 2011 at 1:12 PM, Tom Uijldert <tom.uijldert@gmail.com> wrote:
Hi,
We currently deploy a TFTP server resource adaptor to intercept and handle
TFTP requests within the SLEE.
It is based on the Apache Commons Net code.
It is used to provision several kinds of SIP-phones using either http or
tftp.
If there is any community interest, I'd be happy to contribute this resource
adaptor to the Mobicents code base.
So please let me know.
Hope this helps,
Tom Uijldert.