IPv6 is enabled globally. Each Session Manager instance is administered with IP Address Family value of both with valid IPv4 and IPv6 addresses. However, endpoints in the network can not register to the Session Manager over IPv6.
Cause
Session Manager IP addresses are administered on the SIP Entity Details page, but the prefix length and default gateway settings are not added to the Edit Session Manager page.
Solution
On the home page of the System Manager web console, in Elements Routing SIP Entities verify that the listen ports of Session Manager instances are administered with IP Address Family type of IPv6 or Both.
Verify that the listen ports and protocols match the endpoint settings from the settings file.
Verify that Session Manager is active on administered endpoint listen ports.
Run the netstat -nap | grep AasSipMgr command to check whether the ASSET component is listening on the correct ports and Session Manager IPv6 ASSET address.
ADDITIONAL INFORMATION:
The netstat output might display IPv6 addresses in the truncated form.
Check if Session Manager is not listening on the expected IP address and ports.
Check the Session Manager IPv6 network setup.
Run the ifconfig eth1 command to check if the ASSET component has configured the Session Manager’s IPv6 address. Check components such as, line of output beginning with ‘inet6’, the IPv6 address, the prefixlen value, and scopeid of global.
Check if Session Manager ASSET has not configured the IPv6 address on eth1 interface.
On the home page of the System Manager web console in Elements Session Manager Session Manager Instances check, if correct Security Module settings of Session Manager instances are applied including, IPv6 Network prefix length and IPv6 Default Gateway.
Check if IPv6 Network prefix length, IPv6 Default Gateway, or both settings are blank or incorrect.
