when client hold the call -> the call was hangup

[tienhoangkhmt]

DEBUG | 20251203-202603.508 | callmanager | RESIP:TRANSPORT | 0x7fd93d7aa6c0 | Transport.cxx:403 | incoming from: [ V4 10.205.159.4:5069 TCP targetDomain=10.205.159.4 flowKey=44 transportKey=1 ]
DEBUG | 20251203-202603.508 | callmanager | RESIP:TRANSPORT | 0x7fd93d7aa6c0 | ConnectionBase.cxx:452 | ##Connection: CONN_BASE: 0x7fd92400a6f0 [ V4 10.205.159.4:5069 TCP targetDomain=10.205.159.4 flowKey=44 transportKey=1 ] received: BYE sip:0902375327@10.205.157.98:5063;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 10.205.159.4:5069;branch=z9hG4bK-524287-1---6f69632bb3a3e133;rport=5069
Via: SIP/2.0/WSS gjfnbi5l6s4e.invalid;branch=z9hG4bK3370479;received=42.116.7.92
Max-Forwards: 69
To: sip:0902375327@voice.omicx.vn;tag=a6dd5a03
From: sip:12253@voice.omicx.vn;tag=q1a0557gbu
Call-ID: Q2vSBY7jyQ1Kg_wFCkv4ZQ..
CSeq: 2 BYE
Supported: outbound
User-Agent:
Reason: SIP;cause=488;text="Not Acceptable Here"
X-ClientAddress: XgIAAAIAAAAACHZ0KnQHXA==
Content-Length: 0

I am having a problem in version 0.20 that when holding the call is turned off. Is there any way to help me solve this problem?

I also want to ask why version 0.20 often has errors 486 and 430
Thank you!

[skotow]

Have this been solved ?

[tienhoangkhmt]

Have this been solved ?

Currently, I don't know how to resolve why it's 486.

[skotow]

I have solved

Use this function to replace mismatch on hold from SIP provider and SIPjs

`function forceInactiveModifier(description) {
if (!description.body) return Promise.resolve(description);

let sdp = description.body;
sdp = sdp.replace(/a=(sendrecv|sendonly|recvonly)/g, "a=inactive");

return Promise.resolve({
    ...description,
    body: sdp
});

}`

a=sendonly / a=sendrecv mismatches were tolerated in old browsers but not anymore after update

[tienhoangkhmt]

I have another question unrelated to holdcall: when a call comes in and is immediately rejected, and the server records a 486 error, how can I fix this? Why does it show a 486 error?
thank @skotow