Since upgrading to version 8 a few weeks ago, my logs consistently report an error every 66 seconds. It obviously originates from the Resiprocate SIP stack, but as I know basically nothing about how that works, I don't have much clue to what might trigger it.
This is what it says (three instances, so you can see the exact spacing):
21:38:46.905|.\TransportSelector.cxx(260)|Error2|Resip|::ResipLogger:Exception thrown from Transport:
rocess: ParseException .\ParseBuffer.cxx:79, Parse failed skipped over eof in context:
ahjkhygj12378877942179877655433
^
@ .\ParseBuffer.cxx:79<br>
21:39:53.233|.\TransportSelector.cxx(260)|Error2|Resip|::ResipLogger:Exception thrown from Transport:rocess: ParseException .\ParseBuffer.cxx:79, Parse failed skipped over eof in context:
ahjkhygj12378877942179877655433
^
@ .\ParseBuffer.cxx:79<br>
21:40:59.546|.\TransportSelector.cxx(260)|Error2|Resip|::ResipLogger:Exception thrown from Transport:rocess: ParseException .\ParseBuffer.cxx:79, Parse failed skipped over eof in context:
ahjkhygj12378877942179877655433
^
@ .\ParseBuffer.cxx:79<br>
Despite the constant messages, my system appears to work normally. It's an SB setup with some 10 extensions, one Patton 4112, and five VOIP lines from three different providers. Phones are Linksys plus one Siemens A580 IP. It all runs on a 2003 server with IIS.
I have once before seen a similar exception message, which turned out to be caused by a misbehaving Zyxel ATA (which has since been retired and now runs a little used fax machine separately from 3CX).
This time I have not been able to find anything in our system that matches the frequency of the exception messages, and the usual tricks make no difference. I even tried reinstallning the whole 3CX system (simple enough with backup/restore), but to no avail.
So please, if anyone recognizes this and could give some hint about where to look! \ParseBuffer.cxx:79 rings no bells for me, nor does context: ahjkhygj12378877942179877655433.
/Peter
This is what it says (three instances, so you can see the exact spacing):
21:38:46.905|.\TransportSelector.cxx(260)|Error2|Resip|::ResipLogger:Exception thrown from Transport:
rocess: ParseException .\ParseBuffer.cxx:79, Parse failed skipped over eof in context: ahjkhygj12378877942179877655433
^
@ .\ParseBuffer.cxx:79<br>
21:39:53.233|.\TransportSelector.cxx(260)|Error2|Resip|::ResipLogger:Exception thrown from Transport:
rocess: ParseException .\ParseBuffer.cxx:79, Parse failed skipped over eof in context: ahjkhygj12378877942179877655433
^
@ .\ParseBuffer.cxx:79<br>
21:40:59.546|.\TransportSelector.cxx(260)|Error2|Resip|::ResipLogger:Exception thrown from Transport:
rocess: ParseException .\ParseBuffer.cxx:79, Parse failed skipped over eof in context: ahjkhygj12378877942179877655433
^
@ .\ParseBuffer.cxx:79<br>
Despite the constant messages, my system appears to work normally. It's an SB setup with some 10 extensions, one Patton 4112, and five VOIP lines from three different providers. Phones are Linksys plus one Siemens A580 IP. It all runs on a 2003 server with IIS.
I have once before seen a similar exception message, which turned out to be caused by a misbehaving Zyxel ATA (which has since been retired and now runs a little used fax machine separately from 3CX).
This time I have not been able to find anything in our system that matches the frequency of the exception messages, and the usual tricks make no difference. I even tried reinstallning the whole 3CX system (simple enough with backup/restore), but to no avail.
So please, if anyone recognizes this and could give some hint about where to look! \ParseBuffer.cxx:79 rings no bells for me, nor does context: ahjkhygj12378877942179877655433.
/Peter
