describes how to configure the IPNE feature.
Configuring IPNE includes
configuring the IPNE service, and then associating the IPNE service
with the GGSN, HA, HNBGW or P-GW service.
Use the following
example configuration to create the IPNE service.
bind [ ipv4 ipv4_address | ipv6 ipv6_address ]
peer [ ipv4 | ipv6 ] protocol tcp
- Both the bind and peer keywords
support IPv4 and IPv6 addressing.
- tcp is the
default transport protocol. SCTP is not supported at this time.
- The default XMPP protocol
port is 5222.
- The fqdn, priority and weight keywords
are not supported at this time.
HNBGW only. Usually,
notify messages are sent only on subscription. However, an exception
has been made for HNBGW UE Registration / Deregistration.
HNBGW UE Registration/Deregistration will always be notified
without any subscription. To control the sending of such unsolicited
notification, enter the following command:
- If unsolicited-notify-trigger
hnb-ue is configured, the IPNE service sends notifications
for UE Register/De-register requests on receiving the requests
from the HNBGW.
- If no ununsolicited-notify-trigger
hnb-ue is configured, the IPNE will not send UE Register/De-register
notifications. This is the default setting.
Once the IPNE service
has been created, it must be associated with the configured GGSN, HA,
P-GW or HNBGW service. Use the following example to associate the
IPNE service with the configured gateways service
associate ipne-service ipne_service_name
- context gw_context_name is
the name of the configured GGSN, HA, P-GW or HNBGW service name
configured on the StarOS
- To remove the association
between the IPNE service and the gateway service, use the no associate ipne-servicecommand.