> say “I have been using opensource tools to analyze the logs from this phone and think it’s a failure with Jibe”. Do you get how crazy this sounds?

No sir, this isnt crazy, the problem is that we're paying for a service that isnt accountable for their issues.

Thats crazy.

▲

joecool1029 5 hours ago | parent [-]

> No sir, this isnt crazy, the problem is that we're paying for a service that isnt accountable for their issues.

Once again there's no direct business relationship between Google Jibe and me. The carriers ceded monopoly control to Google Jibe, at that point they have effectively become a wholesale utility; for the US market at least. Internationally this may not be the case.

Apple is adamant to say they don't handle running RCS and there's nothing to suggest in the phone logs that they do anything but connect to carrier, verify RCS provisioning from the carrier, and then try to activate on jibecloud.net and (mis)handle the response from it.

So from my view: Jibe is a black box that customer facing Apple employees are not even aware exists for RCS and the only way to handle a device Jibe service doesn't like is to replace it or swap the board, since they can't troubleshoot it. I can't see Google's documentation and my guess is carriers only handle the initial provisioning to communicate to Jibe that <blank> phone number on <blank> IMEI/IMSI should be allowed to register presence on Jibe. Just like I was able to reset my phone's state by wiping the esims and factory resetting, Jibe should have such an accessible function from either the carrier's end or Apple's end.

I actually forgot to mention in the post that I tried https://messages.google.com/disable-chat weeks ago on both numbers and then waiting days after before re-enabling. Didn't work, and transferring the lines to other phones after would activate on RCS within seconds.

	▲	jeroenhd 2 hours ago \| parent [-]
		Jibe has different forms, but essentially, it's software that's supposed to be run on your carrier's network. As a customer, it doesn't matter if your carrier is using the network-hosted version of Jibe or the cloud version, it's your carrier's responsibility to Make It Work. For things like SMS/MMS servers, SIP servers, and other carrier infrastructure, carriers still like to run this stuff themselves. For RCS this was also the case a decade ago, but then RCS died an unceremonious death when third party messengers ate its lunch and carriers failed spectacularly trying to advertise "joyn". Jibe is a black box that must follow the RCS specification. It's your carrier's responsibility to make that work. As long as Apple is following the RCS spec, they're right in saying it's not their problem. Your carrier should be telling Google to fix their shit.