Activity Log ParseException error in 15.5 SP 4

[JulieMc]

Has anyone seen this parse exception in the Activity log?

05/30/2018 10:33:03 AM - Exception: ParseException E:\jenkins\workspace\15.5SP4\SPBuild\Sources\3rdParty\Resiprocate\rutil/ParseBuffer.hxx:230, Parse failed unexpected eof in context:
*9202
^
@ E:\jenkins\workspace\15.5SP4\SPBuild\Sources\3rdParty\Resiprocate\rutil/ParseBuffer.hxx:230

Just started happening since 15.5 SP4 . I have two new installations reporting this error in the activity log. Two different companies and no E:\ drives on either network.

 

[Moawia Noor]

Same here two installations of SP4,, it's really an annoying message.
I've noticed it happens when using 9 as dialing rule, other rules are not showing the same. Try to check your outbound rules and see what happens, and let's both wait for an expert .

 

[JulieMc]

You mean dialing rule is "Calls to numbers starting with prefix 9"?
I'm using dialing rule "Calls to numbers with a length of 10". But all local calls use area code 903, so the prefix on all calls is 9.

 

[YiannisH_3CX]

Hello,

We have seen this error generated when Fanvil or Yealink phones call a number that does not exist or there are no available routes for the call. We are currently looking into what exactly is causing this.
Is this causing any issues apart from the generated exception?

 

[JulieMc]

Yes we are using Yealink phones.

I found the entries in the activity log while troubleshooting a problem with incoming calls. Since this was something new, I had no idea if it related the problem at hand or not. The ParseException does not seem to be showing up today and call flow is operating normally.

 

[YiannisH_3CX]

Keep an eye on it and let us know if the issue occurs again and if the error appears with it.