Hi Olle,

Thank you for your feedback about this subject, was really important to me receive this in order to follow the correct path.

Once that WebRTC is growing fast i also see some solutions based on xmpp through websockets and others using a custom implementation based on websockts and json.

I will continue my investigation to reach the correct solution to follow :)

Once again, thank you. Regards José Seabra

2017-10-17 8:27 GMT+01:00 Olle E. Johansson oej@edvina.net:

On 16 Oct 2017, at 22:24, José Seabra joseseabra4@gmail.com wrote:

Hello there, I'm writing here in order to get your experiences about a Presence & IM server.

I would like to know what is the best solution to follow:

• SIP Simple or XMPP?

I've more knowledge about SIP Simple with kamailio but i did some researches and i found several open sources unified communications software that's implement Presence and IM using an XMPP server. So what is your opinion about which is the best solution to choose, taking in considerations the following aspects:

1. scalability
2. interopeability
3. permornace
4. features(like: Personal assistance, voicemail integration, chat

group, integration with social media)

Should i choose Kamailio SIP Simple with xcap or an XMPP server(Prosody or ejabberd, etc)

I will appreciate a lot your opinion.

With very sad eyes I have to say that SIP Simple is a big failure. There’s no interoperability as every vendor did their own thing and there was no focus on interoperability in the group. Vendors have stated to me that they just want their customers to buy their servers and their clients and problem is solved. I tried really hard to set up a vendor-neutral solution but failed miserably - the various clients and servers parse the standards in different ways. The working group is closed and I have seen almost no activity in the IETF in that area since.

XMPP on the other hand thrives and continues their development. There is a core of developers that work with standards and interoperability and it continues.

I think scalability, performance and features are almost the same, but XMPP wins in regards to interoperability.

And please José, don’t start diving down into the SIMPLE specifications, because there are way too many from different organisations and you’ll end up quite mad.

This is my personal view after a complete failure trying to build a Lync competitor based on open standards. The bad feeling in my stomach may affect my clarity in this matter. ;-)

/O

---

Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Hello Daniel, Thank you for your feedback, it was also important receive another point of view.

we won't follow the SIP SIMPLE path. Right now we are looking for two options, XMPP(Prosidy, ejabberd, etc) or a solution based on websocktes and JSON for webrtc Apps, itegrated with kamailio for notifications to call states from and between physical phones and webrtc app.

Thank you for your opinion

Best Regards José

2017-10-18 16:59 GMT+01:00 Daniel-Constantin Mierla miconda@gmail.com:

Hello,

sip presence spec doesn't have many client library implementing it, so if you don't want to invest in that direction, it is minus, I expect xmpp has more options here.

In terms of scalability, I cannot comment on xmpp, as I never did any large installation.

SIP has a plus in routing flexibility, given by the headers and the fact that you can decide easier what would be the next hop in the path. Another plus with SIP would be integration with 4G networks where the core is using SIP for routing. One issue when running two protocols is the operations, practically there are two different infrastructures, one for sip and one for xmpp, adding the overhead of maintaining/monitoring/upgrading over the time.

If you want the basic presence features, it should not be that complex even with sip. If you want to fully implement SIMPLE specs, then might be a lot of work.

As a conclusion, if there is going to be use only one type of SIP client with IM&Prensece that you develop, then probably is ok to go for this way. If you expect to have many types of SIP IM&P clients implemented by different vendors, I expect difficult times ahead to get them work together nicely.

Cheers, Daniel

On 16.10.17 22:24, José Seabra wrote:

Hello there, I'm writing here in order to get your experiences about a Presence & IM server.

I would like to know what is the best solution to follow:

• SIP Simple or XMPP?

I've more knowledge about SIP Simple with kamailio but i did some researches and i found several open sources unified communications software that's implement Presence and IM using an XMPP server. So what is your opinion about which is the best solution to choose, taking in considerations the following aspects:

1. scalability
2. interopeability
3. permornace
4. features(like: Personal assistance, voicemail integration, chat

group, integration with social media)

Should i choose Kamailio SIP Simple with xcap or an XMPP server(Prosody or ejabberd, etc)

I will appreciate a lot your opinion. Thank you

Regards José

-- Cumprimentos José Seabra

---

Kamailio (SER) - Users Mailing Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- Daniel-Constantin Mierlawww.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training, Nov 13-15, 2017, in Berlin - www.asipto.com Kamailio World Conference - www.kamailioworld.com