ParseException e:\jenkins\workspace\16.0\...

Status
Not open for further replies.

cemg8r

Customer
Joined
May 17, 2019
Messages
1
Reaction score
0
05/17/2019 4:08:09 PM - Exception: ParseException e:\jenkins\workspace\16.0\spbuild\sources\3rdparty\resiprocate\rutil\parsebuffer.cxx:87, Parse failed Expected " " in context: Contents Messages-Waiting: no Message-Account: sip:{DID masked}@callcentric.com Voice-Message: 0/0 (0/0) Fax-Message: 0/0 (0/0) None: 0/0 (0/0) ^ @ e:\jenkins\workspace\16.0\spbuild\sources\3rdparty\resiprocate\rutil\parsebuffer.cxx:87

I have seen several queries on parsing errors and many say they are benign. I have two trunks however registered through the same provider and with this exception I can't get anything to route except to the primary DID/trunk. I can make outbound calls fine across the second trunk. If anybody calls the DID that is registered on this trunk, it ends up ringing the default ring group as the inbound rule doesn't get processed.

Thanks
 
The exception has nothing to do with that. It has to do with your call identification settings, typically when not using supported trunks.
 
Hi @cemg8r

If you are not using supported providers, you can still try playing with the Call Source Identification option under the inbound Parameters of each trunk. Your provider might be able to help you choose the correct fields to use as source identification.

Are you using CallCentric btw? They are supported and use registration-based trunks which should not pose a problem for call identification. Just make sure that you have entered the DIDs in the trunk settings in the same format that CallCentric sends them, so that your PBX can match them to the correct trunk. Your logs should help you see how the number is sent from CallCentric.
 
Last edited:
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,924
Messages
589,756
Members
164,798
Latest member
Call_Flow.co.uk