on 30.06.2011 08:14 Ondrej Zajicek wrote: > On Wed, Jun 29, 2011 at 12:59:56AM +0100, Matthew Walster wrote: >> Arnold, >> >> I could be wrong, but the most logical explanation would be: >> >>> 2011-04-29 18:24:36 <RMT> XXXX: Received: Hold timer expired >> >> Notification received, hold timer expired (error code 3.4, as per RFC1771). >> >>> 2011-04-30 00:05:42 <RMT> YYYY: Error: Hold timer expired >> >> Hold timer expired locally. Presumably a notification would be >> generated and sent to the remote peer before session tear-down. > > Yes, exactly that. >
Thanks ... and what does "<RMT>" stand for? When analysing the log I see <INFO> <RMT> <TRACE> <WARN> flags. All but "RMT" at least have an intuitive meaning to me. Arnold -- Arnold Nipper / nIPper consulting, Sandhausen, Germany email: [email protected] phone: +49 6224 9259 299 mobile: +49 152 53717690 fax: +49 6224 9259 333
signature.asc
Description: OpenPGP digital signature
