parsing error on incoming call

[todd_nance]

The following activity log shows 3cx encountering a parsing error. the message further states that the code should never get into that error state...however, it is...

other than what's listed, there isnt much information to go on...except a code location....

I believe that this parsing error is on the incoming caller id which comes in as “last, first, xxxyyyzzzz” (I’m just using placeholders and not the actual name and phone number).

I’m using the free version of 3cx for my home pbx...can someone help with this problem...it really needs to go to technical support...

regards

todd

17:27:29.250 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.1.21:5060
17:07:29.140 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.1.21:5060
16:47:28.968 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.1.21:5060
16:41:36.343 Exception thrown in TransactionStatehandleBadRequest. This shouldn't happen. ParseException .\ParseBuffer.cxx:949, Parse failed unexpected eof in context: From
BRYANT
^
@ .\ParseBuffer.cxx:949
16:27:28.765 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.1.21:5060
16:07:28.578 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.1.21:5060
15:47:28.281 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.1.21:5060

 

[todd_nance]

btw...

pstn gateway device for incoming call is a linksys spa3102...3cx version is the latest....

regards,

todd

 

[KerryG]

Looks like a configuration issue on the SPA3102, it should only be sending a phone number, not caller ID name info.