Razvan,
Thanks ! I tried what you indicated but I don’t see the contact changing.
Im taking care of the fix contacts where it needs to be bet but still on
the bye it can’t find it.
root@gcwregistrar151:~$ opensipsctl fifo dlg_list. *(Call Connected)*
dialog:: ID=5820137817639
state::
Actually, after further investigation I'm no longer sure that is true.
According to http://www.json.org/ the "\n" is valid in JSON.
Ben Newlin
On 7/19/18, 8:58 AM, "Ben Newlin" wrote:
I believe newline characters used within JSON must be escaped. So if the
JSON actually contains "\n" th
I believe newline characters used within JSON must be escaped. So if the JSON
actually contains "\n" that is invalid. It must be "\\n".
Ben Newlin
On 7/19/18, 3:19 AM, "Users on behalf of Răzvan Crainea"
wrote:
Hi, Kirill!
This doesn't seem to be an invalid JSON, but only a bad
Hi, Kirill!
This doesn't seem to be an invalid JSON, but only a bad formatting of
the date. I agree it should not include the "\n", because it is useless,
but this doesn't make it invalid. Are you experiencing trouble with
using JSON libraries that don't support this format?
Best regards,
Ră
