Hi Olli,
the problem is not yet solved - I’m still in discussion with both support teams (U-Blox and Deutsche Telekom).
The problem is that the modem sends in the “ATTACH REQUEST” message the requests for getting the DNS server addresses within the PCO (protocol configurations options):
…
Protocol-Config-Options
Length 10
Configuration-Protocol 00
EXT 01
IP-ALLOCATION-VIA-NAS
Container-Length 00
DNS-SERVER-IPV4-ADDRESS-REQ
Container-Length 00
DNS-SERVER-IPV6-ADDRESS-REQ
Container-Length 00
…
In the “ATTACH ACCEPT” received by the modem there’s no direct reply to the parameters asked above contained but the information about the DNS server addresses “is hidden” in another PCO container ID - “IPCP”:
…
Protocol-Config-Options
Length 20
Configuration-Protocol 00
EXT 01
Configuration-Protocol-Option-List
Protocol-Identifier
IPCP
Configuration-Protocol-Content-Length 16
Content 02000010810608080808830608080404
Additional-Parameter-List
…
So, now we are at the point there U-Blox says:
- “We request the data but we didn’t get an reply to our request ID.”
and Deutsche Telekom says:
- “We send the information.”
And: Yes, both are right.
From my understanding I would say if someone ask with a special request ID the reply must contain this request ID, too. The ETSI standard lists the PCO as optional parameter but this cannot mean that such optional parameters get simply ignored in the reply.
As a workaround I currently configure the DNS server addresses by setting up an own MNO profile but this should only be a workaround for the meantime.
BR
Mario