When I used to do it at a previous job, I had to edit the alerts so the stay under 160 characters in length. I was going of the idea that only the most important pages should go out via page/cell, and the less important ones can go out via email. What that meant is that if I get a page via SMS, it's 100% required to login and thus see the full size alert in the email. If that's the premise, then the page can be easily scaled down to 160 characters that will enough to send the name of the node failed and the kind of failure.
-andrey -------------- Andrey Khomyakov | Senior Network Engineer | +1.617.879.5945 Confidentiality Note: This e-mail, and any attachment to it, is intended to be confidential and might be legally privileged. It is intended solely for the use of the addressee. If you are not the intended recipient, you are hereby notified that reading, copying, disseminating or distributing this email is strictly prohibited. If you have received this e-mail in error, please immediately return it to the sender and delete it from your system. Thank you. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Matthew Willis Sent: Friday, August 13, 2010 1:50 PM To: [email protected] Subject: [IM-Talk] Dealing with long SMS pages Dear List, When we're receiving SNMP traps and sending SMS pages out as a result of them, they are getting truncated. This often means the most important info -- that at the end of the trap -- gets dropped. What are other folks doing to get around this? Can InterMapper do SMS slicing and send sequential pages with the full data? Thanks -lilmatt____________________________________________________________________ List archives: http://www.mail-archive.com/intermapper-talk%40list.dartware.com/ To unsubscribe: send email to: [email protected] ____________________________________________________________________ List archives: http://www.mail-archive.com/intermapper-talk%40list.dartware.com/ To unsubscribe: send email to: [email protected]
