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