Sponsored Links

RCS UK Carrier Support for iOS

Just to be clear as well - RCS on Android uses

Version 2.7 (June 2024)[


RACSCS Version 14.0. Adds support for sending message replies, custom emoji reactions, editing and deleting messages. Improves spam handling and adds chatbot features.This version is used in Google Messages.




Apple uses the 5 year old UP... ...



Version 2.4 (October 2019)


RACSCS Version 11.0. Removes plug-in integration and includes integrated seamless web-view. Added additional chatbot features.This version is used in Messages (Apple) with iOS 18.
Even if it's 2.4 then the only major changes are to do with chatbots?

What do you believe you're missing between 2.4 and 2.7 (serious question as I've not used RCS in many real life situations)?
 
Sponsored Links
RCS on Apple devices has nothing to do with Google, unless the network you use wants it to or already has a commercial agreement with them limiting what they can do technically outside of that agreement.

My understanding is that IOS 18 is using RCS 2.6. The latest version is 2.7 and was only released 3 months ago. According to a quick google and Wikipedia it only adds "support for sending message replies, custom emoji reactions, editing and deleting messages. Improves spam handling and adds chatbot features".

I didnt say it had anything to do with Google unless VF have a contract with the them for their IMS Platform...
 
I didnt say it had anything to do with Google unless VF have a contract with the them for their IMS Platform...
You mentioned Google might need to approve. I can see that being possible on a contractual basis (there were a lot of strange marketing press releases mentioning Google when the networks closed down their own RCS last year) but not technical. So that's only why I mentioned that.
 
O2 shutdown their RCS servers in October last year. Android devices then fell back to Google's services as the network had no support at all.
Yeah o2 move from Jibe to paying Google to manage it on the Google IMS platform..

To be honest, its more around feature parity with other OS providers of RCS such as Android and Microsoft
 
Sponsored Links
Yeah o2 move from Jibe to paying Google to manage it on the Google IMS platform..

To be honest, its more around feature parity with other OS providers of RCS such as Android and Microsoft

To clarify, they did NOT move. O2 shutdown their RCS. There is no RCS support at all in the O2 network at present. It was removed! It's a dead parrot. :)

With RCS removed from the network the Google Messaging app will use Google's servers with a not-quite-RCS protocol that ironically is rather better than actual RCS. However that only works with the Google Messaging app.
 
To clarify, they did NOT move. O2 shutdown their RCS. There is no RCS support at all in the O2 network at present. It was removed! It's a dead parrot. :)

With RCS removed from the network the Google Messaging app will use Google's servers with a not-quite-RCS protocol that ironically is rather better than actual RCS. However that only works with the Google Messaging app.

o2 must be updating presence info to jibe, is the number registered ? yes/no etc...
 
o2 must be updating presence info to jibe, is the number registered ? yes/no etc...
What do you mean presence info. O2 have no RCS support. If you're using RCS on Andorid via O2 you're using the Google not-quite-RCS server over the top of the network in exactly the same way as Whatsapp or Imessage.
 
With RCS removed from the network the Google Messaging app will use Google's servers with a not-quite-RCS protocol that ironically is rather better than actual RCS. However that only works with the Google Messaging app.
Samsung messages also has it's own RCS. And their own servers evidently.

I chose to use Google messages for their enhanced version of RCS, because i agree, it is evidently better. But Samsung still include the option to use their servers.
 
Samsung messages also has it's own RCS. And their own servers evidently.

I chose to use Google messages for their enhanced version of RCS, because i agree, it is evidently better. But Samsung still include the option to use their servers.
yes servers that o2 doesn't seemingly support as otherwise, they wouldn't have made people switch to the Google messaging app
 
Sponsored Links
What do you mean presence info. O2 have no RCS support. If you're using RCS on Andorid via O2 you're using the Google not-quite-RCS server over the top of the network in exactly the same way as Whatsapp or Imessage.
And perhaps so, same goes for Three. But what is important is that Google Jibe RCS is also backward compatible with EE RCS, Samsung RCS and a couple others too. It is still RCS at heart.
I am using Jibe to message an EE iPhone user with RCS as we speak.
 
yes servers that o2 doesn't seemingly support as otherwise, they wouldn't have made people switch to the Google messaging app
O2 don't 'need' to support samsung's servers, they will still work. It just takes your phone number and registers it on RCS so others devices can contact it over the 'Samsung RCS Bridge' if you will.

I know a couple people using Samsung RCS on O2.
 
Samsung messages also has it's own RCS. And their own servers evidently.

I chose to use Google messages for their enhanced version of RCS, because i agree, it is evidently better. But Samsung still include the option to use their servers.
I didn't know Samsung did that but it makes sense. Connectivity between RCS servers is a solved problem, so someone using Google's servers could message a Samsung phone or even an Iphone on a network with RCS support.

The issue is networks that don't have native RCS support where you're relying on these third party servers. In that case no other devices will have working RCS.
 
so someone using Google's servers could message a Samsung phone or even an Iphone on a network with RCS support.
Yes that's absolutely the case and has been for a while now. Jibe to Samsung is the exact same as Jibe to Jibe but just without E2EE.
The issue is networks that don't have native RCS support where you're relying on these third party servers. In that case no other devices will have working RCS.
If they're hooking devices to Jibe at network level (which it sounds as if will become the case soon enough) then this is a none issue
 
And perhaps so, same goes for Three. But what is important is that Google Jibe RCS is also backward compatible with EE RCS, Samsung RCS and a couple others too. It is still RCS at heart.
I am using Jibe to message an EE iPhone user with RCS as we speak.
I think some of the issue here is there might have been an expectation from some users that Apple would provide their own RCS servers in the same way that Google and Samsung have. That would work but is even more exclusionary to new mobile devices (not that Apple would care about that).

However if they did that it would break RCS at the network level and there's a lot of suspicion that Apple only really added RCS due to pressure for the Chinese market, who would absolutely require standards based RCS (so they can monitor it in exactly the same way as SMS etc).
 
Sponsored Links
Yes that's absolutely the case and has been for a while now. Jibe to Samsung is the exact same as Jibe to Jibe but just without E2EE.

If they're hooking devices to Jibe at network level (which it sounds as if will become the case soon enough) then this is a none issue

I jumped into this really regarding the Iphone. The Iphone will only support standards based RCS for the reasons above, so if there's any involvement with Jibe it will be the choice of the network operators if they integrate it with their IMS.
 
I jumped into this really regarding the Iphone
I am also talking about the iPhone too, but just the end of it that i see. And also that Google Jibe RCS is not the walled garden you portray it to be. And also that there is ineroperabillity between EE/Samsung/Google etc. More to come of course, but more to show that it can and is being done.
 
A reminder that Google sells RCS as a service to networks: https://jibe.google.com/jibe-platform/

This is not that different from buying an RCS implementation and running it on your own servers. They're just paying Google to keep RCS up-to-date and for the servers.

Just because we see "jibe" somewhere, it doesn't mean that the network doesn't support RCS or something like that. They might just be paying Google to run RCS because it's cheaper or more convenient to do that.

Edit: Jibe = Universal Profile.
 
Top
Cheap BIG ISPs for 100Mbps+
Community Fibre UK ISP Logo
150Mbps
Gift: None
Virgin Media UK ISP Logo
Virgin Media £22.99
132Mbps
Gift: None
Vodafone UK ISP Logo
Vodafone £24.00 - 26.00
150Mbps
Gift: None
NOW UK ISP Logo
NOW £24.00
100Mbps
Gift: None
Plusnet UK ISP Logo
Plusnet £25.99
145Mbps
Gift: £50 Reward Card
Large Availability | View All
Cheapest ISPs for 100Mbps+
Gigaclear UK ISP Logo
Gigaclear £17.00
200Mbps
Gift: None
Community Fibre UK ISP Logo
150Mbps
Gift: None
Virgin Media UK ISP Logo
Virgin Media £22.99
132Mbps
Gift: None
Hey! Broadband UK ISP Logo
150Mbps
Gift: None
Youfibre UK ISP Logo
Youfibre £23.99
150Mbps
Gift: None
Large Availability | View All
Sponsored Links
The Top 15 Category Tags
  1. FTTP (6024)
  2. BT (3638)
  3. Politics (2720)
  4. Business (2439)
  5. Openreach (2405)
  6. Building Digital UK (2330)
  7. Mobile Broadband (2143)
  8. FTTC (2083)
  9. Statistics (1899)
  10. 4G (1813)
  11. Virgin Media (1762)
  12. Ofcom Regulation (1582)
  13. Fibre Optic (1467)
  14. Wireless Internet (1462)
  15. 5G (1404)
Sponsored

Copyright © 1999 to Present - ISPreview.co.uk - All Rights Reserved - Terms  ,  Privacy and Cookie Policy  ,  Links  ,  Website Rules