|
|
|
nztim:
27.6 MB I highly doubt that is every telcos call server and sip settings etc
In plain text, 27.6 MB is about 9200 printed pages. Even riddled with XML tags etc, that's still plenty of room for servers and settings.
nztim:
27.6 MB I highly doubt that is every telcos call server and sip settings etc, but if it is, then Samsung or Pixel or whoever could load them all in but they choose not to
Let's take the latest Samsung S26 for example they have 4 variants SM-S942B, SM-S942U1, SM-S942N, SM-S9420 all exactly the same phone, all with a completely different set of VoLTE profiles depending on market served, Samsung is choosing to do this, making roaming, and inter compatibility a complete nightmare
Can't blame the telcos for any of that carry on.
It is indeed that small - taking Spark as an example:
I can't really understand why Samsung uses that distribution method. Apple does have different hardware variants globally for their iPhones but this is to support different bands, mmWave (or not) and SIM/eSIM configurations. But the carrier profiles are global, i.e. the IMS server used for Spark doesn't change depending on which model you buy, but the 5G settings may.
hio77:
Alot of the ims stacks as far as UE's are concerned have a RFC based dns record that's resolved.
as an example, that I can see in my dns cache at the moment for wifi calling, epdg.epc.mnc005.mcc530.pub.3gppnetwork.org
ahem except that carrier with the number in their name... Not sure what happened there.
|
|
|