- Joined
- Jul 18, 2018
- Messages
- 2
- Reaction score
- 0
Hello,
We configured a SIP Trunk on 3CX connected to a CallBridge/SIP-Trunk on a Cisco Meeting Server (LAN infrastructure).
Our issue on that configuration is when we call from 3CX to the CallBridge after 30 minutes call a SIP "UPDATE" message is coming from CMS going to 3CX and 3CX answers by SIP message "SIP/2.0 481 Call/Transaction Does Not Exist" and then "BYE".
We saw on CISCO support a communication about a bug which could be linked to the issue :
"SIP session refresh contains "Require:timer" causes call drop
CSCve08295
Description
Symptom:
The Cisco Meeting Server will include a require:timer header in SIP UPDATE messages. This can lead to call drops through some intermediate devices that do not support this feature.
Conditions:
Affects some SBCs and the Avaya session manager."
Could you please inform if this issue communicated by CISCO is known on 3CX or provide other resolution advises ?
I put the call logs in a text file in attached document.
Thanks in advance
We configured a SIP Trunk on 3CX connected to a CallBridge/SIP-Trunk on a Cisco Meeting Server (LAN infrastructure).
Our issue on that configuration is when we call from 3CX to the CallBridge after 30 minutes call a SIP "UPDATE" message is coming from CMS going to 3CX and 3CX answers by SIP message "SIP/2.0 481 Call/Transaction Does Not Exist" and then "BYE".
We saw on CISCO support a communication about a bug which could be linked to the issue :
"SIP session refresh contains "Require:timer" causes call drop
CSCve08295
Description
Symptom:
The Cisco Meeting Server will include a require:timer header in SIP UPDATE messages. This can lead to call drops through some intermediate devices that do not support this feature.
Conditions:
Affects some SBCs and the Avaya session manager."
Could you please inform if this issue communicated by CISCO is known on 3CX or provide other resolution advises ?
I put the call logs in a text file in attached document.
Thanks in advance