Is the Phone Number or Message Sender Name Used by SMN to Send SMS Messages Always the Same?

5



Yes. Usually, the phone number or sender name SMN uses to send SMS messages does not change. It changes only when the carrier changes the message sending channel.



Other related questions:
What Is the Limitation for SMS Messages?

If an SMS message contains less than or equal to 70 characters, it is counted as one message. If an SMS message exceeds 70 characters, every 67 characters are counted as one message. The maximum length of an SMS message cannot exceed 490 characters.


Does SMN Guarantee a Message Being Received by the Subscription Endpoint?

If a subscription endpoint is reachable, it will receive the messages sent by SMN.

If the endpoint is unreachable, SMN saves the failed message in the message queue and tries to send it again for another six times. If the message sending still fails, SMN discards the message and does not prompt that the message sending has failed.

The interval for re-sending a failed message varies depending on the length of the message queue. Usually, a failed message is processed within several hours. If the queue has too many failed messages, it will be processed within a day.


How does the SMC1.0 send the give-floor notification message?
To send the give-floor notification message using the SMC1.0, perform the following steps: 1. Modify the RMCC.ini configuration file to enable the give-floor notification function. 2. Set the currently connected output port as the caption output port of the site to which the floor is given. 3. Set the chair site on the RM and perform the Give Floor operation as the chair site.

Why cannot an AR router send trap messages

SNMP provides the trap function to control the output of trap messages. An AR router generates trap messages only when the trap function has been enabled on the AR router.

Perform the following operations to enable the trap function on an AR router:

  1. Run the system-view command to enter the system view.
  2. Run the snmp-agent trap enable command to enable the AR router to send trap messages to the NMS.
  3. Run the snmp-agent target-host trap-paramsname paramsname v1 securityname securityname [ binding-private-value ] [ trap-filterprofilename filterprofilename ] [ private-netmanager ] command to set parameters for sending trap messages.
    NOTE:
    • V200R001C01 and later versions support binding-private-value.
    • V200R002C00 and later versions support private-netmanager.
  4. Run the snmp-agent target-host trap-hostname hostname address ipv4-addr [ udp-port udp-portid ] [ public-net | vpn-instance vpn-instance-name ] trap-paramsname paramsname command to specify the destination host for receiving trap messages and error codes.
    NOTE:

    The default destination UDP port number is 162. To ensure secure communication between the NMS and managed devices, run the udp-port command to change the UDP port number to a non-well-known port number.


If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top