Ucp 31 is generally used to maintain an ucp session over the smsc. Most of operators don't allow the use of this (they said that this overload the smsc) When an UCP 31 is sent from your gateway, the smsc need to ACK your request, to maintain the session If it's not acked/nack during the time you specified, then your connection will be closed then you will be in reconnect-mode. (for safety reason) The smsc can respond either with ack or nack. In both cases it will maintain the ucp session and no disconnect will happens.
Please just ask your operator if they allow ucp 31, if not, you need to "google-search" for using TCP_KEEP_ALIVE in order to have the same effect but not in UCP layer :-) regards Vincent -- Telemaque - NICE - (FR) Service Technique - Developpement http://www.telemaque.fr/ [EMAIL PROTECTED] Tel : +33 4 93 97 71 64 (fax 68) ----- Original Message ----- From: "Hoffmann, Jürgen" <[EMAIL PROTECTED]> To: <users@kannel.org> Sent: Wednesday, May 31, 2006 11:39 AM Subject: heartbeat received but Alert: operation 31 not ACKed Hi everybody, I found the following problem today: We are sending hearbeats to our SMS-C, usually there aren't any problems. But today I receive "Alert (operation 31) was not ACKed within 120 seconds" and in parallel: "hearbeat with load value 0 received" 120 seconds is our configured timeout. When the heartbeat is received, why the alert happen?. Or does operation 31 have a different meaning? Or is the message due to hearbeat-requests sent from the sms-c and not the answer to our request? Our GSM provider can see our heartbeats in their logs and send an answer. Thanks!
