Hi guys,

I'd like to propose a neat feature for handling mobile clients running
on iphones and androids.

You might be aware that both mobile platforms support a push
notification feature to remotely start certain services/apps. It means
that you can have a mobile sip client provisioned on kamailio, but it
might not be running when a call arrives (that is, it's not registered).
Using the iphone/android notification framework, you can notify the
device to start the client and register the subscriber, then finish call
setup.

There are various ways to hack this together with kamailio and some
third party apps, but here's a proposal for a clean way to do it:

A calls B via kamailio, and kamailio sees that B is not registered.
Either in any case or based on a user preference indicating support for
such a notification, kamailio could send the call to sems. Sems would
subscribe to the registration status on kamailio leveraging the
pua_reginfo module. Sems could play some early announcement (some ring
tone or whatever), send out the push notification to the framework, then
wait for the publish from kamailio to know when the client came online.
Once B is registered, sems could deflect the call back to kamailio (e.g.
with 302), and kamailio would then do the lookup and finish the call
setup. In case of timeout (no PUBLISH within a certain time) it would
unsubscribe and pass back a 4xx error.

Not sure about the missing pieces in Sems to do so (support for
SUBSCRIBE/PUBLISH). Comments on that?

Andreas

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems

Reply via email to