- Joined
- Jun 19, 2020
- Messages
- 4
- Reaction score
- 0
We are using SIPTRUNK / SIP.US for our sip trunk and have configured their SMS. Messaging is flowing properly overall, but we are having issues with the timestamp of the messages. SMS messages come in as GMT time, while MMS messages come in with the proper timezone information. I did a few tests to capture the JSON payload that is getting sent to 3CX, and noticed that the timestamp information is formatted a little differently:
SMS: "timestamp": "2024-01-17T17:54:04.960000Z"
MMS: "timestamp": "2024-01-17T17:51:49.00Z"
Both adhere to ISO 8601 standards for formatting, but as mentioned before the SMS does not parse the time information correctly. I attempted to reach out to Support to get information on how it is being parsed, but they referred me to the forum, though I do not know if anyone would have information on how the backend code is working. Anyone run into this before?
Thanks,
Alex
SMS: "timestamp": "2024-01-17T17:54:04.960000Z"
MMS: "timestamp": "2024-01-17T17:51:49.00Z"
Both adhere to ISO 8601 standards for formatting, but as mentioned before the SMS does not parse the time information correctly. I attempted to reach out to Support to get information on how it is being parsed, but they referred me to the forum, though I do not know if anyone would have information on how the backend code is working. Anyone run into this before?
Thanks,
Alex