Adding messaging services

Add messaging services to the SafeLinx Server to enable applications to send messages to messaging clients, such as a pager or a phone, over mobile wireless networks. Messaging services include support for short message service (SMS) delivery, and mobile-originated message delivery.

Provide the port number on which the SafeLinx Server listens for requests from applications with the Messaging Services and Push APIs. This process is needed only when you define messaging services to the SafeLinx Server. The default port is 13131.
  • On the Resources page, right-click the SafeLinx Server to which you want to add messaging services, then click Add > messaging services.
  • For each messaging MNC that you want to define:
    • Choose a network type from the drop-down list. Each network type requires network-specific parameters, such as one or more physical ports.
    • Determine whether you want this MNC to belong to a preexisting MNC group.
    • Select the initial state of the MNC. Choose active if you want the MNC to be used by the SafeLinx Server when it is started. Choose inactive if you do not want the MNC to be used immediately.
    • Specify either an application service port number or default URL/port number combination. This port number indicates either a dotted decimal IP address or a host name followed by a port number. The MNC uses the port number to forward mobile-originated messages sent from the mobile device to the messaging services. If you specify a domain and host name, the messaging services use a domain name system (DNS) lookup operation to resolve the name to an IP address. If the DNS server is unavailable, the lookup operation might take several minutes to complete and might adversely affect the performance. If you anticipate that your network might encounter DNS resolution problems, make sure that the default URL is specified as a dotted decimal IP address.

    You can also configure connections to use the secure sockets layer (SSL) between the messaging services and applications with the Messaging Service and Push APIs. The default port for SSL requests is 13132. For more information, see Configuring SSL certificates for messaging services.

  • There are additional properties that are available for configuration after you complete adding messaging services:
    • The level of messages stored in the session information database. Choose from:
      None
      No messages are stored in the database. Any messages that are queued when the SafeLinx Server is shut down are not recovered when it is started again. This selection results in the quickest throughput by the messaging services.
      Only delayed-delivery messages
      Stores only messages that are queued and pending because an application submitted a message for future delivery. Any messages that are queued when the SafeLinx Server is shut down are recovered when the Manager is started again.
      All
      All messages are stored in the database. Any messages that are queued when the SafeLinx Server is shut down are recovered when the SafeLinx Server is started again. This selection results in a lessened throughput by the messaging services.
    • Two additional fields that specify when processed message status records are discarded or checked to determine whether they timed out.

    View the properties of the messaging services to edit these fields. See Editing resource properties.

    You can add a generic or pass-through application service to the messaging services. In the Tasks pane, right-click the messaging services to which you want to add an application service, then click Add application service.

  • For a generic application service, provide:
    • The common name of the service
    • The inbound port that the messaging client uses
    • Which transport protocol to use (UDP, TCP, or TCP that uses SSL) between the messaging services and the application server
    • The application server address and port number
    • The length of time that the messaging services maintains specific information about the mobile device after a time with no traffic in either direction.
    • Whether to include the device identifier in the DataStream
    • Which MNCs or MNC groups use the application service

    For a pass-through application service, provide the common name of the application service and which MNCs or MNC groups use the application service.