MC7455 IPv6 Session Gets Disconnected

IoT Modules MC/EM Series
1

Working on IPv6 data session on MC7455 modem with Roger’s network. After data session is connected successfully with IP address:

at+cgdcont?
+CGDCONT: 1,“IPV6”,"",“0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”,0,0,0,0

at+cgcontrdp
+CGCONTRDP: 1,5,lteinternet.apn,38.5.141.128.5.1.22.234.213.228.97.188.246.112.46.154, 254.128.0.0.0.0.0.0.0.0.0.0.0.0.0.1, 38.7.247.152.0.24.0.16.0.0.6.64.113.37.82.84, 38.7.247.152.0.24.0.16.0.0.6.64.113.37.82.83

The v6 session gets disconnected by itself with reason “client ended the call” even though I didn’t issue any commands to disconnect. The IP address is still assigned in this state. Anybody has an idea why? For v4 the session remains up after the attach unless it’s explicitly disconnected.

sessionStateCb: instance 0, svcType 1, v4 session 0, v6 session 63043216
sessionStateCb: state 2(connected), reconfig 0(no need to reconfigure), end reason 0 (session not ended)
packetServiceStatusCb: instance 0, svcType 1, v4 session 0, v6 session 63043216
packetServiceStatusCb: bearer id 5, status 2(connected), reconfReq 0(no need to reconfigure), endReason 65535(???), verboseEndReasonType 65535, verboseEndReason 65535, ipFamily 6,

… 2 minutes elasped

sessionStateCb: instance 0, svcType 1, v4 session 0, v6 session 63043216
sessionStateCb: state 1(disconnected), reconfig 0(no need to reconfigure), end reason 2 (client ended the call)
packetServiceStatusCb: instance 0, svcType 1, v4 session 0, v6 session 63043216
packetServiceStatusCb: bearer id 255, status 1(disconnected), reconfReq 0(no need to reconfigure), endReason 2(client ended the call), verboseEndReasonType 3, verboseEndReason 2000, ipFamily 6,

2

Not sure about this, but I suspect the firmware might disconnect if it doesn’t see either a Router Solicitation or a DHCPv6 request from the host. Normally a host will always send RS when an IPv6 capable interface goes up, but maybe you don’t do that?

Could be completely irrelevant, but easy enough to check out at least…