Search This Blog

Re: [mobicents-public] Tftp server resource adaptor

Simply some voip boxes don't give the opportunity to do http instead of tftp, from what I remember from previous experiences with a cisco phone.

--
Fab.

Le 1 avr. 2011 07:37, "Ivelin Ivanov" <ivelin.atanasoff.ivanov@gmail.com> a écrit :
> The new versions of http also support progressive download and resume.
> Isn't that sufficient in practice?
>
> Ivelin
>
> On Mar 31, 2011, at 18:10, Ibrahima Gaye <ibrahima.gaye@gmail.com>
> wrote:
>
>> One advantage i can tell is: tftp send file per chunk (512k i think)
>> then wait for a ack before sending again (so there is a real dialog
>> at 'application level')
>> - plus most of the advantages of ftp over http
>> regards,
>> ibrahim
>>
>> On Thu, Mar 31, 2011 at 10:20 PM, Ivelin Ivanov <ivelin.atanasoff.ivanov@gmail.com
>> > wrote:
>> Makes a lot of sense. The tftp RA will allow the JSLEE application to
>> act as a dynamic tftp server.
>>
>> I wonder if it is more common scenario for the voip user boxes to
>> download firmware from an http server or an tftp server?
>> What are the advantages of tftp over http?
>>
>>
>> On Thu, Mar 31, 2011 at 5:13 PM, Ibrahima Gaye <ibrahima.gaye@gmail.com
>> > wrote:
>> > Hi,
>> > 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.
>> >>
>> >> Ivelin
>> >> On Mar 31, 2011, at 4:22, Ibrahima Gaye <ibrahima.gaye@gmail.com>
>> wrote:
>> >>
>> >> Hi Tom,
>> >> it will be very helpful for those working on VoIP termination;
>> >> regards,
>> >> Ibrahim
>> >>
>> >> On 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.
>> >>>
>> >>
>> >
>> >
>>

Re: [mobicents-public] Tftp server resource adaptor

The new versions of http also support progressive download and resume. Isn't that sufficient in practice?

Ivelin

On Mar 31, 2011, at 18:10, Ibrahima Gaye <ibrahima.gaye@gmail.com> wrote:

One advantage i can tell is: tftp send file per chunk (512k i think) then wait for a ack before sending again (so there is a real dialog at 'application level')
- plus most of the advantages of ftp over http
regards,
ibrahim

On Thu, Mar 31, 2011 at 10:20 PM, Ivelin Ivanov <ivelin.atanasoff.ivanov@gmail.com> wrote:
Makes a lot of sense. The tftp RA will allow the JSLEE application to
act as a dynamic tftp server.

I wonder if it is more common scenario for the voip user boxes to
download firmware from an http server or an tftp server?
What are the advantages of tftp over http?


On Thu, Mar 31, 2011 at 5:13 PM, Ibrahima Gaye <ibrahima.gaye@gmail.com> wrote:
> Hi,
> 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.
>>
>> Ivelin
>> On Mar 31, 2011, at 4:22, Ibrahima Gaye <ibrahima.gaye@gmail.com> wrote:
>>
>> Hi Tom,
>> it will be very helpful for those working on VoIP termination;
>> regards,
>> Ibrahim
>>
>> On 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.
>>>
>>
>
>

Re: [mobicents-public] mgcp example help

hi, i've configured the xlite, but when i try to run the example, dialing 2010, in the mms console i have this: (the mms and mobicents, also the UAS client is in the same machine)

00:01:54,231 INFO  [JainMgcpStackImpl] Jain Mgcp stack bound to IP /127.0.0.1 an
d UDP port 2427
Jain Mgcp stack bound to IP /127.0.0.1 and UDP port 2427
00:01:54,261 INFO  [MgcpController] Started MGCP Controller module for MMS
00:01:54,263 INFO  [MainDeployer] [[[[[[[[[ Mobicents Media Server: release.vers
ion=2.0.0.GA Started ]]]]]]]]]
Connection index=0
00:06:50,193 ERROR [CreateConnectionAction] Could not apply remote descriptor
java.net.SocketException: Network is unreachable: connect
        at sun.nio.ch.Net.connect(Native Method)
        at sun.nio.ch.DatagramChannelImpl.connect(DatagramChannelImpl.java:530)
        at org.mobicents.media.server.impl.rtp.RtpSocketImpl.setPeer(RtpSocketIm
pl.java:414)
        at org.mobicents.media.server.RtpConnectionImpl.setRemoteDescriptor(RtpC
onnectionImpl.java:361)
        at org.mobicents.media.server.ctrl.mgcp.CreateConnectionAction.createRtp
Connection(CreateConnectionAction.java:121)
        at org.mobicents.media.server.ctrl.mgcp.CreateConnectionAction.call(Crea
teConnectionAction.java:413)
        at org.mobicents.media.server.ctrl.mgcp.CreateConnectionAction.call(Crea
teConnectionAction.java:42)
        at org.mobicents.media.server.ctrl.mgcp.MgcpController.processMgcpComman
dEvent(MgcpController.java:221)
        at org.mobicents.protocols.mgcp.stack.JainMgcpStackProviderImpl.processM
gcpCommandEvent(JainMgcpStackProviderImpl.java:246)
        at org.mobicents.protocols.mgcp.stack.TransactionHandler.receiveRequest(
TransactionHandler.java:600)
        at org.mobicents.protocols.mgcp.stack.MessageHandler.scheduleMessages(Me
ssageHandler.java:196)
        at org.mobicents.protocols.mgcp.stack.JainMgcpStackImpl.run(JainMgcpStac
kImpl.java:327)
00:06:50,207 INFO  [CreateConnectionAction] Response TX = 186173485, Response: 5
27 Missing RemoteConnectionDescriptor.
Connection index=0
00:07:52,708 ERROR [CreateConnectionAction] Could not apply remote descriptor
java.net.SocketException: Network is unreachable: connect
        at sun.nio.ch.Net.connect(Native Method)
        at sun.nio.ch.DatagramChannelImpl.connect(DatagramChannelImpl.java:530)
        at org.mobicents.media.server.impl.rtp.RtpSocketImpl.setPeer(RtpSocketIm
pl.java:414)
        at org.mobicents.media.server.RtpConnectionImpl.setRemoteDescriptor(RtpC
onnectionImpl.java:361)
        at org.mobicents.media.server.ctrl.mgcp.CreateConnectionAction.createRtp
Connection(CreateConnectionAction.java:121)
        at org.mobicents.media.server.ctrl.mgcp.CreateConnectionAction.call(Crea
teConnectionAction.java:413)
        at org.mobicents.media.server.ctrl.mgcp.CreateConnectionAction.call(Crea
teConnectionAction.java:42)
        at org.mobicents.media.server.ctrl.mgcp.MgcpController.processMgcpComman
dEvent(MgcpController.java:221)
        at org.mobicents.protocols.mgcp.stack.JainMgcpStackProviderImpl.processM
gcpCommandEvent(JainMgcpStackProviderImpl.java:246)
        at org.mobicents.protocols.mgcp.stack.TransactionHandler.receiveRequest(
TransactionHandler.java:600)
        at org.mobicents.protocols.mgcp.stack.MessageHandler.scheduleMessages(Me
ssageHandler.java:196)
        at org.mobicents.protocols.mgcp.stack.JainMgcpStackImpl.run(JainMgcpStac
kImpl.java:327)
00:07:52,715 INFO  [CreateConnectionAction] Response TX = 186173486, Response: 5
27 Missing RemoteConnectionDescriptor.
Connection index=0
00:08:38,590 ERROR [CreateConnectionAction] Could not apply remote descriptor
java.net.SocketException: Network is unreachable: connect
        at sun.nio.ch.Net.connect(Native Method)
        at sun.nio.ch.DatagramChannelImpl.connect(DatagramChannelImpl.java:530)
        at org.mobicents.media.server.impl.rtp.RtpSocketImpl.setPeer(RtpSocketIm
pl.java:414)
        at org.mobicents.media.server.RtpConnectionImpl.setRemoteDescriptor(RtpC
onnectionImpl.java:361)
        at org.mobicents.media.server.ctrl.mgcp.CreateConnectionAction.createRtp
Connection(CreateConnectionAction.java:121)
        at org.mobicents.media.server.ctrl.mgcp.CreateConnectionAction.call(Crea
teConnectionAction.java:413)
        at org.mobicents.media.server.ctrl.mgcp.CreateConnectionAction.call(Crea
teConnectionAction.java:42)
        at org.mobicents.media.server.ctrl.mgcp.MgcpController.processMgcpComman
dEvent(MgcpController.java:221)
        at org.mobicents.protocols.mgcp.stack.JainMgcpStackProviderImpl.processM
gcpCommandEvent(JainMgcpStackProviderImpl.java:246)
        at org.mobicents.protocols.mgcp.stack.TransactionHandler.receiveRequest(
TransactionHandler.java:600)
        at org.mobicents.protocols.mgcp.stack.MessageHandler.scheduleMessages(Me
ssageHandler.java:196)
        at org.mobicents.protocols.mgcp.stack.JainMgcpStackImpl.run(JainMgcpStac
kImpl.java:327)
00:08:38,604 INFO  [CreateConnectionAction] Response TX = 186173487, Response: 5
27 Missing RemoteConnectionDescriptor.

On Thu, Mar 31, 2011 at 6:37 AM, Ishmael Makitla <ishmael.makitla@gmail.com> wrote:
Good day Ariel,

On your X-lite, please ensure that your configure the "Account settings" as follows; this is the way I use it currently:
Account Name: here put in your name or any other name
Protocol: must be SIP
Allow the account for Call (put check mark) and IM/Presence (put a check mark here too - if u need these services)

User details:
User ID put some unique user id (can still be your name e.g ArielXlite)
Domain: I have just put in the IP address here (your call will show as userID@domain)

Domain Proxy:
Here if you are using domain, then put a check mark to "register with domain and receive calls"
Then selected "Send outbound via : Domain"
Otherwise, do NOT check the "register with domain and receive calls" and then select "Send outbound via: Proxy"
the address has to be the IP address of your JAIN SLEE ( where SIP service is deployed) like this: 127.0.0.1:5060 (if running on localhost)

I've attached the screen shot.

Hope this helps,

Ishmael



On Thu, Mar 31, 2011 at 1:58 AM, Ariel Guerrero <ariel.guerrero@gmail.com> wrote:
Hi, i am trying to configure a xlite to test the mgcp-demo (mobicents-2.3.0.FINAL), the mms server, the mobicents server and also de voip client is in the same machine. How i have to configure the xlite to test de demo?
The example was correctly deployed, but when  i try to register, in the console i saw the message 


21:56:25,299 INFO  [SipResourceAdaptor] Received response not forked, without tx
, without dialog, can't proceed, dropping...
21:56:27,796 INFO  [SipResourceAdaptor] Received Response:
SIP/2.0 482 Loop detected
Via: SIP/2.0/UDP 186.17.58.238:5060;rport=5060;branch=z9hG4bK12B0DACB499D4D0082A
CC537AC7A2DE7;received=127.0.0.1
CSeq: 11269 INVITE
From: "torosvi2" <sip:torosvi2@127.0.0.1>;tag=2049248109
Content-Length: 0


21:56:27,799 INFO  [SipResourceAdaptor] Received response not forked, without tx
, without dialog, can't proceed, dropping...



Re: [mobicents-public] Tftp server resource adaptor

One advantage i can tell is: tftp send file per chunk (512k i think) then wait for a ack before sending again (so there is a real dialog at 'application level')
- plus most of the advantages of ftp over http
regards,
ibrahim

On Thu, Mar 31, 2011 at 10:20 PM, Ivelin Ivanov <ivelin.atanasoff.ivanov@gmail.com> wrote:
Makes a lot of sense. The tftp RA will allow the JSLEE application to
act as a dynamic tftp server.

I wonder if it is more common scenario for the voip user boxes to
download firmware from an http server or an tftp server?
What are the advantages of tftp over http?


On Thu, Mar 31, 2011 at 5:13 PM, Ibrahima Gaye <ibrahima.gaye@gmail.com> wrote:
> Hi,
> 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.
>>
>> Ivelin
>> On Mar 31, 2011, at 4:22, Ibrahima Gaye <ibrahima.gaye@gmail.com> wrote:
>>
>> Hi Tom,
>> it will be very helpful for those working on VoIP termination;
>> regards,
>> Ibrahim
>>
>> On 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.
>>>
>>
>
>

[mobicents-public] Re: Mobicents Diameter v1.4.0.BETA1 Released!

Good milestone!

On Tue, Mar 29, 2011 at 11:19 AM, Amit Bhayani <amit.bhayani@gmail.com> wrote:
> Congrats Guys!
>
> 2011/3/29 Alexandre Mendonça <brainslog@gmail.com>
>>
>> We are happy to announce a new Mobicents Diameter release, v1.4.0.BETA1 !
>> What's new in this release?
>>
>> -------------------------------------------------------------------------------
>> In this release we bring the following main improvements:
>>  - Better Cluster Support: Improved cluster support by updating to the
>> latest Mobicents Cluster framework and fine-graining replicated data;
>>  - More Performance: Stack performance was improved mostly at high load,
>> with benefit to both standalone and JAIN SLEE Resource Adaptors;
>>
>>  - Enhanced Stability: Several issues regarding stack failure point
>> (either in functionality or conformance with specification) were identified
>> and fixed, providing a more stable stack;
>>  - New Dictionary Format: A better format for the Diameter Dictionary was
>> adopted in order to be more easily extendable and provide extended features
>> in the next releases.
>> This is a BETA release as there are API and deep core changes happening,
>> but it's been thoroughly tested, with the testsuite extended to cover more
>> than ever, including message flows for all applications both in standalone
>> and cluster mode!
>> As usual, it includes several improvements and fixes to the Stack,
>> Multiplexer and Resource Adaptors.
>> Mobicents JAIN SLEE 2.4.0.CR1 "SAKURA" compliant Resource Adaptors with HA
>> support are included, for the following applications:
>>  > Base
>>  > CCA
>>  > Sh-Client
>>  > Sh-Server
>>  > Ro
>>  > Rf
>>  > Cx/Dx
>>  > Gx
>> It is also included the User Guides for Core (Stack and Multiplexer),
>> Resource Adaptors and Jopr Plugin for Mobicents Diameter.
>> Diameter MUX component for JBoss 4.x and JBoss 5.x are also released as a
>> standalone.
>> Issues List:
>>
>> -------------------------------------------------------------------------------
>> The list of issues fixed can be found at
>>
>> http://code.google.com/p/mobicents/issues/list?can=1&q=component=Diameter%20version=1.4.0%20release=Type-Beta
>> Where to download:
>>
>> ------------------------------------------------------------------------------
>>
>> https://sourceforge.net/projects/mobicents/files/Mobicents%20Diameter/mobicents-diameter-1.4.0.BETA1/
>>   » Full bundle (Stack, Mux, JAIN SLEE RAs and Examples)
>>   » Source code
>>   » Standalone MUX (JBoss 5.x)
>>   » Standalone MUX (JBoss 4.x)
>>
>> What is included in this release?
>>
>> ------------------------------------------------------------------------------
>> Core:
>> » Mobicents jDiameter Stack v1.5.5.0-build440
>> » Mobicents jDiameter HA v1.0.0.BETA3
>> » Mobicents Diameter Mux v1.4.0.BETA1
>> Resource Adaptors:
>> » Mobicents Diameter Base RA v2.4.0.CR1
>> » Mobicents Diameter CCA RA v2.4.0.CR1
>> » Mobicents Diameter Sh-Client RA v2.4.0.CR1
>> » Mobicents Diameter Sh-Server RA v2.4.0.CR1
>> » Mobicents Diameter Ro RA v2.4.0.CR1
>> » Mobicents Diameter Rf RA v2.4.0.CR1
>> » Mobicents Diameter Cx/Dx RA v2.4.0.CR1
>> » Mobicents Diameter Gx RA v2.4.0.CR1
>> Examples:
>> » Mobicents Diameter Base Example v2.1.2.FINAL
>> » Mobicents Diameter OpenIMS Example v2.1.2.FINAL
>> Management:
>> » Mobicents Diameter Jopr Plugin 1.0.0.BETA2
>> SVN source code and tag:
>>
>> -------------------------------------------------------------------------------
>>
>> http://mobicents.googlecode.com/svn/tags/servers/diameter/core/jdiameter/jdiameter-1.5.5.0-build440/
>>
>> http://mobicents.googlecode.com/svn/tags/servers/diameter/core/mux/mobicents-diameter-mux-1.4.0.BETA1/
>>
>> http://mobicents.googlecode.com/svn/tags/servers/jain-slee/2.x.y/resources/diameter-base/2.4.0.CR1/
>>
>> http://mobicents.googlecode.com/svn/tags/servers/jain-slee/2.x.y/resources/diameter-cca/2.4.0.CR1/
>>
>> http://mobicents.googlecode.com/svn/tags/servers/jain-slee/2.x.y/resources/diameter-sh-client/2.4.0.CR1/
>>
>> http://mobicents.googlecode.com/svn/tags/servers/jain-slee/2.x.y/resources/diameter-sh-server/2.4.0.CR1/
>>
>> http://mobicents.googlecode.com/svn/tags/servers/jain-slee/2.x.y/resources/diameter-ro/2.4.0.CR1/
>>
>> http://mobicents.googlecode.com/svn/tags/servers/jain-slee/2.x.y/resources/diameter-rf/2.4.0.CR1/
>>
>> http://mobicents.googlecode.com/svn/tags/servers/jain-slee/2.x.y/resources/diameter-cx-dx/2.4.0.CR1/
>>
>> http://mobicents.googlecode.com/svn/tags/servers/jain-slee/2.x.y/resources/diameter-gx/2.4.0.CR1/
>>
>> http://mobicents.googlecode.com/svn/tags/servers/jain-slee/2.x.y/examples/diameter-base/2.1.2.FINAL/
>>
>> http://mobicents.googlecode.com/svn/tags/servers/jain-slee/2.x.y/examples/diameter-openims/2.1.2.FINAL/
>>
>> http://mobicents.googlecode.com/svn/tags/servers/diameter/tools/jopr-plugin/mobicents-diameter-jopr-plugin-1.0.0.BETA2/
>> How to get started:
>>
>> -------------------------------------------------------------------------------
>> Each component contains a README and/or User Guide file which explains how
>> to use it, please refer to it.
>> Documentation
>>
>> -------------------------------------------------------------------------------
>> For documentation and information about this release components, please
>> visit Mobicents Diameter Homepage at
>> http://www.mobicents.org/diameter/
>> For the latest version of Mobicents Diameter User Guide, visit:
>>
>> http://hudson.jboss.org/hudson/job/MobicentsBooks/lastSuccessfulBuild/artifact/diameter/index.html
>> The Mobicents Team
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "mobicents-core" group.
>> To post to this group, send email to mobicents-core@googlegroups.com.
>> To unsubscribe from this group, send email to
>> mobicents-core+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/mobicents-core?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups
> "mobicents-core" group.
> To post to this group, send email to mobicents-core@googlegroups.com.
> To unsubscribe from this group, send email to
> mobicents-core+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/mobicents-core?hl=en.
>

Re: [mobicents-public] Tftp server resource adaptor

Makes a lot of sense. The tftp RA will allow the JSLEE application to
act as a dynamic tftp server.

I wonder if it is more common scenario for the voip user boxes to
download firmware from an http server or an tftp server?
What are the advantages of tftp over http?


On Thu, Mar 31, 2011 at 5:13 PM, Ibrahima Gaye <ibrahima.gaye@gmail.com> wrote:
> Hi,
> 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.
>>
>> Ivelin
>> On Mar 31, 2011, at 4:22, Ibrahima Gaye <ibrahima.gaye@gmail.com> wrote:
>>
>> Hi Tom,
>> it will be very helpful for those working on VoIP termination;
>> regards,
>> Ibrahim
>>
>> On 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.
>>>
>>
>
>

Re: [mobicents-public] Tftp server resource adaptor

Hi,
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.   

Ivelin

On Mar 31, 2011, at 4:22, Ibrahima Gaye <ibrahima.gaye@gmail.com> wrote:

Hi Tom,
it will be very helpful for those working on VoIP termination;
regards,
Ibrahim

On 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.



Re: [mobicents-public] Tftp server resource adaptor

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.   

Ivelin

On Mar 31, 2011, at 4:22, Ibrahima Gaye <ibrahima.gaye@gmail.com> wrote:

Hi Tom,
it will be very helpful for those working on VoIP termination;
regards,
Ibrahim

On 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.


Re: [mobicents-public] Re: Suggest new Mobicents SLEE example application(s)

+1 (from a newbie)


On Thu, Mar 31, 2011 at 5:35 PM, Sachin Parnami <sachin.mobite@gmail.com> wrote:
+ IMHO we must have a simplest examples clubbed in each respective RAs, which should have a very basic functionality working in it.
e.g. sip (a example demonstrating Invite->ok->Ack), SMPP (receiving and sending SMSs) and so on.........

Because most of the time we see newbie coming and asking for a working example of xyz RA, the community directs him/her to the example demonstrating, and then it gets difficult for the new comer to actually understand the SLEE logic and RA functionality, so the simplest way club them in RA and KISS ( Keep It Short and Simple ) :).


Regards,
Sachin Parnami





On Mon, Mar 28, 2011 at 5:52 AM, Eduardo Martins <emmartins@gmail.com> wrote:
Aayush, Teresa, Oifa, tks for the ideas, very good stuff in this topic
already, we will provide feedback soon.

-- Eduardo
..............................................
http://emmartins.blogspot.com
http://redhat.com/solutions/telco



On Mon, Mar 28, 2011 at 1:10 AM, Eduardo Martins <emmartins@gmail.com> wrote:
> By the way, this happens for all data in the presence server that is
> originated from the network, for instance the geo location data is in
> some particular server, accesible by some particular protocol, but it
> is pushed to the presence server using SIP. The complete user state in
> the presence server is the state published directly by the user (or
> its devices), merged with all the state, related with such user and
> devices, published by the network itself.
>
> -- Eduardo
> ..............................................
> http://emmartins.blogspot.com
> http://redhat.com/solutions/telco
>
>
>
> On Mon, Mar 28, 2011 at 1:04 AM, Eduardo Martins <emmartins@gmail.com> wrote:
>> Yes, it may happen in this particular case, but like I said, only the
>> presence server interface is "public", and of course, we are talking
>> about different network protocols.
>>
>> -- Eduardo
>> ..............................................
>> http://emmartins.blogspot.com
>> http://redhat.com/solutions/telco
>>
>>
>>
>> On Mon, Mar 28, 2011 at 12:44 AM, Ivelin Ivanov
>> <ivelin.atanasoff.ivanov@gmail.com> wrote:
>>> Well this is even more confusing. Are you saying that IMS just allows two
>>> different ways to achieve the same goal?
>>>
>>> Ivelin
>>>
>>> On Mar 27, 2011, at 18:29, Eduardo Martins <emmartins@gmail.com> wrote:
>>>
>>>> As the XDM allows subscriptions to changes in the managed XML docs,
>>>> the HSS also allows subscriptions (through Diameter Sh not SIP), to
>>>> changes in the user/service data it manages.
>>>>
>>>> -- Eduardo
>>>> ..............................................
>>>> http://emmartins.blogspot.com
>>>> http://redhat.com/solutions/telco
>>>>
>>>> On Mon, Mar 28, 2011 at 12:13 AM, Ivelin Ivanov
>>>> <ivelin.atanasoff.ivanov@gmail.com> wrote:
>>>>>
>>>>> Thank you. This help. Related question: wouldn't RCS/XDM registration and
>>>>> SIP presence notifications be an alternative way to implement this same
>>>>> scenario. When would one use Diamter Sh to inquire about user
>>>>> online/offline
>>>>> status as opposed to XDM/SIP.
>>>>>
>>>>> Ivelin
>>>>> On Mar 25, 2011, at 1:40, Mosiuoa Tsietsi <mosiuoat@gmail.com> wrote:
>>>>>
>>>>> precisely, there are a lot of similarities between the existing openims
>>>>> example and yulian's proposed example, the difference being media
>>>>> integration instead of an im sent to user when she logs on, media is
>>>>> played
>>>>> back to the caller when callee is offline - are there examples in
>>>>> Diameter
>>>>> package that also use media?
>>>>>
>>>>>
>>>>>
>>>>> 2011/3/25 Alexandre Mendonça <brainslog@gmail.com>
>>>>>>
>>>>>> Ivelin,
>>>>>> Like in our Diameter OpenIMS integration example, the Sh interface is
>>>>>> used
>>>>>> to be verify the user state.
>>>>>> In our example, the AS subscribes to changes to that particular part of
>>>>>> the user data, and once the user registers its client in the IMS
>>>>>> network,
>>>>>> the AS is notified about the change, and sends him a SIP MESSAGE
>>>>>> notifying
>>>>>> about the missed calls, if any.
>>>>>> In Yulian's example, it's similar, with the AS querying the HSS about
>>>>>> the
>>>>>> user state, via Sh interface, to decide whether to establish the call or
>>>>>> send the caller to an announcement, if I got it correctly.
>>>>>>
>>>>>> --
>>>>>> Alexandre Mendonça // JBoss R&D
>>>>>> http://ammendonca.blogspot.com/
>>>>>>
>>>>>>
>>>>>> On Thu, Mar 24, 2011 at 20:23, Ivelin Ivanov
>>>>>> <ivelin.atanasoff.ivanov@gmail.com> wrote:
>>>>>>>
>>>>>>> Mos,
>>>>>>> What role does Diameter play in this scenario?
>>>>>>>
>>>>>>> Ivelin
>>>>>>> On Mar 24, 2011, at 15:00, Mosiuoa Tsietsi <mosiuoat@gmail.com> wrote:
>>>>>>>
>>>>>>> Oifa's proposed example sounds alot like the openims example in
>>>>>>> Mobicents
>>>>>>> Diameter that stores missed calls and when the user is online, sends
>>>>>>> them an
>>>>>>> IM notifying them of missed calls. In OIfa's case, he is adding an
>>>>>>> announcement to involve MMS into the solution.
>>>>>>>
>>>>>>> Mos
>>>>>>>
>>>>>>> On 24 March 2011 20:27, Ivelin Ivanov
>>>>>>> <ivelin.atanasoff.ivanov@gmail.com>
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Oifa,
>>>>>>>>
>>>>>>>> Can you describe with a bit more details or maybe a diagram how
>>>>>>>> Diameter comes into use for this example?
>>>>>>>>
>>>>>>>> Ivelin
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, Mar 24, 2011 at 12:37 PM, yulian_o <oifa.yulian@gmail.com>
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Hello Eduardo.
>>>>>>>>> I have the application that gets the invite , checks against hss if
>>>>>>>>> client is local and online , if not moves him to
>>>>>>>>> announcement , otherwise creates the media connection and creates the
>>>>>>>>> call.
>>>>>>>>> It will be added in future to support complete voice mail , allow
>>>>>>>>> recording and so on ,based on presence,
>>>>>>>>> but currently i am having problem with forked in OpenIMSCore and rtp
>>>>>>>>> issues on media server.
>>>>>>>>> I can publish the code , so everyone interested in writing sip/media/
>>>>>>>>> diameter application can extend from here.
>>>>>>>>> In the end of all its supposed to have complete MRFC functionality.
>>>>>>>>>
>>>>>>>>> Best regards
>>>>>>>>> Oifa Yulian
>>>>>>>>>
>>>>>>>>> On Mar 23, 6:45 pm, Teresa Reis <zizata...@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> According to the posts present in this group, I suggest some global
>>>>>>>>>> examples
>>>>>>>>>> that involve several modules from Mobicents. You could provide an
>>>>>>>>>> example
>>>>>>>>>> that connects Mobicents JAIN SLEE + Mobicents Media Server +
>>>>>>>>>> Mobicents
>>>>>>>>>> Presence Server.
>>>>>>>>>>
>>>>>>>>>> For example, an IMS youtube; a user transmits video, and all of the
>>>>>>>>>> friends
>>>>>>>>>> present in users contact list receive an INVITE, and accept that
>>>>>>>>>> invite
>>>>>>>>>> responding SIP_OK. When they respond that, they receive the video
>>>>>>>>>> transmitted by the initial user.
>>>>>>>>>>
>>>>>>>>>> Cumps,
>>>>>>>>>>
>>>>>>>>>> ziza
>>>>>>>>>>
>>>>>>>>>> 2011/3/23 aayush <abhatnagar192...@gmail.com>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Registrar application which publishes presence with default status
>>>>>>>>>>> "online".
>>>>>>>>>>
>>>>>>>>>>> After half of the registration time is elapsed, status is
>>>>>>>>>>> republished to
>>>>>>>>>>> idle.
>>>>>>>>>>
>>>>>>>>>>> Once there is a re-registration, status goes back to online.
>>>>>>>>>>
>>>>>>>>>>> Upon de-registration, publication is terminated - offline.
>>>>>>>>>>
>>>>>>>>>>> On Mar 23, 2011 3:56 PM, "Eduardo Martins" <emmart...@gmail.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi all, the team would like to add new example application(s) to
>>>>>>>>>>> the
>>>>>>>>>>> SLEE binary release, which demos real usage of the current
>>>>>>>>>>> enablers:
>>>>>>>>>>> IMS user profile, SIP subscription and publication clients and XDM
>>>>>>>>>>> client, and thus we are looking for your suggestions. Of course
>>>>>>>>>>> it's
>>>>>>>>>>> not mandatory to have a single app which uses all at same time.
>>>>>>>>>>
>>>>>>>>>>> The new example app(s) should be as simple and "code clean" as
>>>>>>>>>>> possible, but we may also go for a recycle of the current complex
>>>>>>>>>>> apps
>>>>>>>>>>> (call controller 2, converged demo) too.
>>>>>>>>>>
>>>>>>>>>>> Thanks in advance.
>>>>>>>>>>
>>>>>>>>>>> -- Eduardo
>>>>>>>>>>> ..............................................
>>>>>>>>>>> http://emmartins.blogspot.com
>>>>>>>>>>> http://redhat.com/solutions/telco
>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> You received this message because you are subscribed to the Google
>>>>>>>>>>> Groups
>>>>>>>>>>> "mobicents-core" group.
>>>>>>>>>>> To post to this group, send email to
>>>>>>>>>>> mobicents-core@googlegroups.com.
>>>>>>>>>>> To unsubscribe from this group, send email to
>>>>>>>>>>> mobicents-core+unsubscribe@googlegroups.com.
>>>>>>>>>>> For more options, visit this group at
>>>>>>>>>>> http://groups.google.com/group/mobicents-core?hl=en.
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>
>>
>


Re: [mobicents-public] Re: Suggest new Mobicents SLEE example application(s)

true Sachin. However there is no such thing as "simplest" example in presence, it touches too many technologies to be simple. In my opinion(and that was my idea for this example) it should mix sip services+presence+maybe more(BUT still very basic). To show how to manipulate xml data in XDM/Mobicents Presence (or any other trully :) ) and act on changes to that data. From newbie position it should be best example, it took me a bit of time to understand how things work there and what actauly stored in presence/XDM.



Bartosz Baranowski
JBoss R & D
==================================
Word of criticism meant to improve is always step forward.


On Thu, Mar 31, 2011 at 7:35 PM, Sachin Parnami <sachin.mobite@gmail.com> wrote:
+ IMHO we must have a simplest examples clubbed in each respective RAs, which should have a very basic functionality working in it.
e.g. sip (a example demonstrating Invite->ok->Ack), SMPP (receiving and sending SMSs) and so on.........

Because most of the time we see newbie coming and asking for a working example of xyz RA, the community directs him/her to the example demonstrating, and then it gets difficult for the new comer to actually understand the SLEE logic and RA functionality, so the simplest way club them in RA and KISS ( Keep It Short and Simple ) :).


Regards,
Sachin Parnami





On Mon, Mar 28, 2011 at 5:52 AM, Eduardo Martins <emmartins@gmail.com> wrote:
Aayush, Teresa, Oifa, tks for the ideas, very good stuff in this topic
already, we will provide feedback soon.

-- Eduardo
..............................................
http://emmartins.blogspot.com
http://redhat.com/solutions/telco



On Mon, Mar 28, 2011 at 1:10 AM, Eduardo Martins <emmartins@gmail.com> wrote:
> By the way, this happens for all data in the presence server that is
> originated from the network, for instance the geo location data is in
> some particular server, accesible by some particular protocol, but it
> is pushed to the presence server using SIP. The complete user state in
> the presence server is the state published directly by the user (or
> its devices), merged with all the state, related with such user and
> devices, published by the network itself.
>
> -- Eduardo
> ..............................................
> http://emmartins.blogspot.com
> http://redhat.com/solutions/telco
>
>
>
> On Mon, Mar 28, 2011 at 1:04 AM, Eduardo Martins <emmartins@gmail.com> wrote:
>> Yes, it may happen in this particular case, but like I said, only the
>> presence server interface is "public", and of course, we are talking
>> about different network protocols.
>>
>> -- Eduardo
>> ..............................................
>> http://emmartins.blogspot.com
>> http://redhat.com/solutions/telco
>>
>>
>>
>> On Mon, Mar 28, 2011 at 12:44 AM, Ivelin Ivanov
>> <ivelin.atanasoff.ivanov@gmail.com> wrote:
>>> Well this is even more confusing. Are you saying that IMS just allows two
>>> different ways to achieve the same goal?
>>>
>>> Ivelin
>>>
>>> On Mar 27, 2011, at 18:29, Eduardo Martins <emmartins@gmail.com> wrote:
>>>
>>>> As the XDM allows subscriptions to changes in the managed XML docs,
>>>> the HSS also allows subscriptions (through Diameter Sh not SIP), to
>>>> changes in the user/service data it manages.
>>>>
>>>> -- Eduardo
>>>> ..............................................
>>>> http://emmartins.blogspot.com
>>>> http://redhat.com/solutions/telco
>>>>
>>>> On Mon, Mar 28, 2011 at 12:13 AM, Ivelin Ivanov
>>>> <ivelin.atanasoff.ivanov@gmail.com> wrote:
>>>>>
>>>>> Thank you. This help. Related question: wouldn't RCS/XDM registration and
>>>>> SIP presence notifications be an alternative way to implement this same
>>>>> scenario. When would one use Diamter Sh to inquire about user
>>>>> online/offline
>>>>> status as opposed to XDM/SIP.
>>>>>
>>>>> Ivelin
>>>>> On Mar 25, 2011, at 1:40, Mosiuoa Tsietsi <mosiuoat@gmail.com> wrote:
>>>>>
>>>>> precisely, there are a lot of similarities between the existing openims
>>>>> example and yulian's proposed example, the difference being media
>>>>> integration instead of an im sent to user when she logs on, media is
>>>>> played
>>>>> back to the caller when callee is offline - are there examples in
>>>>> Diameter
>>>>> package that also use media?
>>>>>
>>>>>
>>>>>
>>>>> 2011/3/25 Alexandre Mendonça <brainslog@gmail.com>
>>>>>>
>>>>>> Ivelin,
>>>>>> Like in our Diameter OpenIMS integration example, the Sh interface is
>>>>>> used
>>>>>> to be verify the user state.
>>>>>> In our example, the AS subscribes to changes to that particular part of
>>>>>> the user data, and once the user registers its client in the IMS
>>>>>> network,
>>>>>> the AS is notified about the change, and sends him a SIP MESSAGE
>>>>>> notifying
>>>>>> about the missed calls, if any.
>>>>>> In Yulian's example, it's similar, with the AS querying the HSS about
>>>>>> the
>>>>>> user state, via Sh interface, to decide whether to establish the call or
>>>>>> send the caller to an announcement, if I got it correctly.
>>>>>>
>>>>>> --
>>>>>> Alexandre Mendonça // JBoss R&D
>>>>>> http://ammendonca.blogspot.com/
>>>>>>
>>>>>>
>>>>>> On Thu, Mar 24, 2011 at 20:23, Ivelin Ivanov
>>>>>> <ivelin.atanasoff.ivanov@gmail.com> wrote:
>>>>>>>
>>>>>>> Mos,
>>>>>>> What role does Diameter play in this scenario?
>>>>>>>
>>>>>>> Ivelin
>>>>>>> On Mar 24, 2011, at 15:00, Mosiuoa Tsietsi <mosiuoat@gmail.com> wrote:
>>>>>>>
>>>>>>> Oifa's proposed example sounds alot like the openims example in
>>>>>>> Mobicents
>>>>>>> Diameter that stores missed calls and when the user is online, sends
>>>>>>> them an
>>>>>>> IM notifying them of missed calls. In OIfa's case, he is adding an
>>>>>>> announcement to involve MMS into the solution.
>>>>>>>
>>>>>>> Mos
>>>>>>>
>>>>>>> On 24 March 2011 20:27, Ivelin Ivanov
>>>>>>> <ivelin.atanasoff.ivanov@gmail.com>
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Oifa,
>>>>>>>>
>>>>>>>> Can you describe with a bit more details or maybe a diagram how
>>>>>>>> Diameter comes into use for this example?
>>>>>>>>
>>>>>>>> Ivelin
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, Mar 24, 2011 at 12:37 PM, yulian_o <oifa.yulian@gmail.com>
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Hello Eduardo.
>>>>>>>>> I have the application that gets the invite , checks against hss if
>>>>>>>>> client is local and online , if not moves him to
>>>>>>>>> announcement , otherwise creates the media connection and creates the
>>>>>>>>> call.
>>>>>>>>> It will be added in future to support complete voice mail , allow
>>>>>>>>> recording and so on ,based on presence,
>>>>>>>>> but currently i am having problem with forked in OpenIMSCore and rtp
>>>>>>>>> issues on media server.
>>>>>>>>> I can publish the code , so everyone interested in writing sip/media/
>>>>>>>>> diameter application can extend from here.
>>>>>>>>> In the end of all its supposed to have complete MRFC functionality.
>>>>>>>>>
>>>>>>>>> Best regards
>>>>>>>>> Oifa Yulian
>>>>>>>>>
>>>>>>>>> On Mar 23, 6:45 pm, Teresa Reis <zizata...@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> According to the posts present in this group, I suggest some global
>>>>>>>>>> examples
>>>>>>>>>> that involve several modules from Mobicents. You could provide an
>>>>>>>>>> example
>>>>>>>>>> that connects Mobicents JAIN SLEE + Mobicents Media Server +
>>>>>>>>>> Mobicents
>>>>>>>>>> Presence Server.
>>>>>>>>>>
>>>>>>>>>> For example, an IMS youtube; a user transmits video, and all of the
>>>>>>>>>> friends
>>>>>>>>>> present in users contact list receive an INVITE, and accept that
>>>>>>>>>> invite
>>>>>>>>>> responding SIP_OK. When they respond that, they receive the video
>>>>>>>>>> transmitted by the initial user.
>>>>>>>>>>
>>>>>>>>>> Cumps,
>>>>>>>>>>
>>>>>>>>>> ziza
>>>>>>>>>>
>>>>>>>>>> 2011/3/23 aayush <abhatnagar192...@gmail.com>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Registrar application which publishes presence with default status
>>>>>>>>>>> "online".
>>>>>>>>>>
>>>>>>>>>>> After half of the registration time is elapsed, status is
>>>>>>>>>>> republished to
>>>>>>>>>>> idle.
>>>>>>>>>>
>>>>>>>>>>> Once there is a re-registration, status goes back to online.
>>>>>>>>>>
>>>>>>>>>>> Upon de-registration, publication is terminated - offline.
>>>>>>>>>>
>>>>>>>>>>> On Mar 23, 2011 3:56 PM, "Eduardo Martins" <emmart...@gmail.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi all, the team would like to add new example application(s) to
>>>>>>>>>>> the
>>>>>>>>>>> SLEE binary release, which demos real usage of the current
>>>>>>>>>>> enablers:
>>>>>>>>>>> IMS user profile, SIP subscription and publication clients and XDM
>>>>>>>>>>> client, and thus we are looking for your suggestions. Of course
>>>>>>>>>>> it's
>>>>>>>>>>> not mandatory to have a single app which uses all at same time.
>>>>>>>>>>
>>>>>>>>>>> The new example app(s) should be as simple and "code clean" as
>>>>>>>>>>> possible, but we may also go for a recycle of the current complex
>>>>>>>>>>> apps
>>>>>>>>>>> (call controller 2, converged demo) too.
>>>>>>>>>>
>>>>>>>>>>> Thanks in advance.
>>>>>>>>>>
>>>>>>>>>>> -- Eduardo
>>>>>>>>>>> ..............................................
>>>>>>>>>>> http://emmartins.blogspot.com
>>>>>>>>>>> http://redhat.com/solutions/telco
>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> You received this message because you are subscribed to the Google
>>>>>>>>>>> Groups
>>>>>>>>>>> "mobicents-core" group.
>>>>>>>>>>> To post to this group, send email to
>>>>>>>>>>> mobicents-core@googlegroups.com.
>>>>>>>>>>> To unsubscribe from this group, send email to
>>>>>>>>>>> mobicents-core+unsubscribe@googlegroups.com.
>>>>>>>>>>> For more options, visit this group at
>>>>>>>>>>> http://groups.google.com/group/mobicents-core?hl=en.
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>
>>
>


Re: [mobicents-public] Re: Suggest new Mobicents SLEE example application(s)

+ IMHO we must have a simplest examples clubbed in each respective RAs, which should have a very basic functionality working in it.
e.g. sip (a example demonstrating Invite->ok->Ack), SMPP (receiving and sending SMSs) and so on.........

Because most of the time we see newbie coming and asking for a working example of xyz RA, the community directs him/her to the example demonstrating, and then it gets difficult for the new comer to actually understand the SLEE logic and RA functionality, so the simplest way club them in RA and KISS ( Keep It Short and Simple ) :).


Regards,
Sachin Parnami




On Mon, Mar 28, 2011 at 5:52 AM, Eduardo Martins <emmartins@gmail.com> wrote:
Aayush, Teresa, Oifa, tks for the ideas, very good stuff in this topic
already, we will provide feedback soon.

-- Eduardo
..............................................
http://emmartins.blogspot.com
http://redhat.com/solutions/telco



On Mon, Mar 28, 2011 at 1:10 AM, Eduardo Martins <emmartins@gmail.com> wrote:
> By the way, this happens for all data in the presence server that is
> originated from the network, for instance the geo location data is in
> some particular server, accesible by some particular protocol, but it
> is pushed to the presence server using SIP. The complete user state in
> the presence server is the state published directly by the user (or
> its devices), merged with all the state, related with such user and
> devices, published by the network itself.
>
> -- Eduardo
> ..............................................
> http://emmartins.blogspot.com
> http://redhat.com/solutions/telco
>
>
>
> On Mon, Mar 28, 2011 at 1:04 AM, Eduardo Martins <emmartins@gmail.com> wrote:
>> Yes, it may happen in this particular case, but like I said, only the
>> presence server interface is "public", and of course, we are talking
>> about different network protocols.
>>
>> -- Eduardo
>> ..............................................
>> http://emmartins.blogspot.com
>> http://redhat.com/solutions/telco
>>
>>
>>
>> On Mon, Mar 28, 2011 at 12:44 AM, Ivelin Ivanov
>> <ivelin.atanasoff.ivanov@gmail.com> wrote:
>>> Well this is even more confusing. Are you saying that IMS just allows two
>>> different ways to achieve the same goal?
>>>
>>> Ivelin
>>>
>>> On Mar 27, 2011, at 18:29, Eduardo Martins <emmartins@gmail.com> wrote:
>>>
>>>> As the XDM allows subscriptions to changes in the managed XML docs,
>>>> the HSS also allows subscriptions (through Diameter Sh not SIP), to
>>>> changes in the user/service data it manages.
>>>>
>>>> -- Eduardo
>>>> ..............................................
>>>> http://emmartins.blogspot.com
>>>> http://redhat.com/solutions/telco
>>>>
>>>> On Mon, Mar 28, 2011 at 12:13 AM, Ivelin Ivanov
>>>> <ivelin.atanasoff.ivanov@gmail.com> wrote:
>>>>>
>>>>> Thank you. This help. Related question: wouldn't RCS/XDM registration and
>>>>> SIP presence notifications be an alternative way to implement this same
>>>>> scenario. When would one use Diamter Sh to inquire about user
>>>>> online/offline
>>>>> status as opposed to XDM/SIP.
>>>>>
>>>>> Ivelin
>>>>> On Mar 25, 2011, at 1:40, Mosiuoa Tsietsi <mosiuoat@gmail.com> wrote:
>>>>>
>>>>> precisely, there are a lot of similarities between the existing openims
>>>>> example and yulian's proposed example, the difference being media
>>>>> integration instead of an im sent to user when she logs on, media is
>>>>> played
>>>>> back to the caller when callee is offline - are there examples in
>>>>> Diameter
>>>>> package that also use media?
>>>>>
>>>>>
>>>>>
>>>>> 2011/3/25 Alexandre Mendonça <brainslog@gmail.com>
>>>>>>
>>>>>> Ivelin,
>>>>>> Like in our Diameter OpenIMS integration example, the Sh interface is
>>>>>> used
>>>>>> to be verify the user state.
>>>>>> In our example, the AS subscribes to changes to that particular part of
>>>>>> the user data, and once the user registers its client in the IMS
>>>>>> network,
>>>>>> the AS is notified about the change, and sends him a SIP MESSAGE
>>>>>> notifying
>>>>>> about the missed calls, if any.
>>>>>> In Yulian's example, it's similar, with the AS querying the HSS about
>>>>>> the
>>>>>> user state, via Sh interface, to decide whether to establish the call or
>>>>>> send the caller to an announcement, if I got it correctly.
>>>>>>
>>>>>> --
>>>>>> Alexandre Mendonça // JBoss R&D
>>>>>> http://ammendonca.blogspot.com/
>>>>>>
>>>>>>
>>>>>> On Thu, Mar 24, 2011 at 20:23, Ivelin Ivanov
>>>>>> <ivelin.atanasoff.ivanov@gmail.com> wrote:
>>>>>>>
>>>>>>> Mos,
>>>>>>> What role does Diameter play in this scenario?
>>>>>>>
>>>>>>> Ivelin
>>>>>>> On Mar 24, 2011, at 15:00, Mosiuoa Tsietsi <mosiuoat@gmail.com> wrote:
>>>>>>>
>>>>>>> Oifa's proposed example sounds alot like the openims example in
>>>>>>> Mobicents
>>>>>>> Diameter that stores missed calls and when the user is online, sends
>>>>>>> them an
>>>>>>> IM notifying them of missed calls. In OIfa's case, he is adding an
>>>>>>> announcement to involve MMS into the solution.
>>>>>>>
>>>>>>> Mos
>>>>>>>
>>>>>>> On 24 March 2011 20:27, Ivelin Ivanov
>>>>>>> <ivelin.atanasoff.ivanov@gmail.com>
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Oifa,
>>>>>>>>
>>>>>>>> Can you describe with a bit more details or maybe a diagram how
>>>>>>>> Diameter comes into use for this example?
>>>>>>>>
>>>>>>>> Ivelin
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, Mar 24, 2011 at 12:37 PM, yulian_o <oifa.yulian@gmail.com>
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Hello Eduardo.
>>>>>>>>> I have the application that gets the invite , checks against hss if
>>>>>>>>> client is local and online , if not moves him to
>>>>>>>>> announcement , otherwise creates the media connection and creates the
>>>>>>>>> call.
>>>>>>>>> It will be added in future to support complete voice mail , allow
>>>>>>>>> recording and so on ,based on presence,
>>>>>>>>> but currently i am having problem with forked in OpenIMSCore and rtp
>>>>>>>>> issues on media server.
>>>>>>>>> I can publish the code , so everyone interested in writing sip/media/
>>>>>>>>> diameter application can extend from here.
>>>>>>>>> In the end of all its supposed to have complete MRFC functionality.
>>>>>>>>>
>>>>>>>>> Best regards
>>>>>>>>> Oifa Yulian
>>>>>>>>>
>>>>>>>>> On Mar 23, 6:45 pm, Teresa Reis <zizata...@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> According to the posts present in this group, I suggest some global
>>>>>>>>>> examples
>>>>>>>>>> that involve several modules from Mobicents. You could provide an
>>>>>>>>>> example
>>>>>>>>>> that connects Mobicents JAIN SLEE + Mobicents Media Server +
>>>>>>>>>> Mobicents
>>>>>>>>>> Presence Server.
>>>>>>>>>>
>>>>>>>>>> For example, an IMS youtube; a user transmits video, and all of the
>>>>>>>>>> friends
>>>>>>>>>> present in users contact list receive an INVITE, and accept that
>>>>>>>>>> invite
>>>>>>>>>> responding SIP_OK. When they respond that, they receive the video
>>>>>>>>>> transmitted by the initial user.
>>>>>>>>>>
>>>>>>>>>> Cumps,
>>>>>>>>>>
>>>>>>>>>> ziza
>>>>>>>>>>
>>>>>>>>>> 2011/3/23 aayush <abhatnagar192...@gmail.com>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Registrar application which publishes presence with default status
>>>>>>>>>>> "online".
>>>>>>>>>>
>>>>>>>>>>> After half of the registration time is elapsed, status is
>>>>>>>>>>> republished to
>>>>>>>>>>> idle.
>>>>>>>>>>
>>>>>>>>>>> Once there is a re-registration, status goes back to online.
>>>>>>>>>>
>>>>>>>>>>> Upon de-registration, publication is terminated - offline.
>>>>>>>>>>
>>>>>>>>>>> On Mar 23, 2011 3:56 PM, "Eduardo Martins" <emmart...@gmail.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi all, the team would like to add new example application(s) to
>>>>>>>>>>> the
>>>>>>>>>>> SLEE binary release, which demos real usage of the current
>>>>>>>>>>> enablers:
>>>>>>>>>>> IMS user profile, SIP subscription and publication clients and XDM
>>>>>>>>>>> client, and thus we are looking for your suggestions. Of course
>>>>>>>>>>> it's
>>>>>>>>>>> not mandatory to have a single app which uses all at same time.
>>>>>>>>>>
>>>>>>>>>>> The new example app(s) should be as simple and "code clean" as
>>>>>>>>>>> possible, but we may also go for a recycle of the current complex
>>>>>>>>>>> apps
>>>>>>>>>>> (call controller 2, converged demo) too.
>>>>>>>>>>
>>>>>>>>>>> Thanks in advance.
>>>>>>>>>>
>>>>>>>>>>> -- Eduardo
>>>>>>>>>>> ..............................................
>>>>>>>>>>> http://emmartins.blogspot.com
>>>>>>>>>>> http://redhat.com/solutions/telco
>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> You received this message because you are subscribed to the Google
>>>>>>>>>>> Groups
>>>>>>>>>>> "mobicents-core" group.
>>>>>>>>>>> To post to this group, send email to
>>>>>>>>>>> mobicents-core@googlegroups.com.
>>>>>>>>>>> To unsubscribe from this group, send email to
>>>>>>>>>>> mobicents-core+unsubscribe@googlegroups.com.
>>>>>>>>>>> For more options, visit this group at
>>>>>>>>>>> http://groups.google.com/group/mobicents-core?hl=en.
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>
>>
>