Server replies with "503" response on receiving &a

[Nancy]

1. Brekeke Product Name and Version:
Brekeke SIP Server, Version 3.6.3.0

2. Java version:
no
3. OS type and the version:
win10
4. UA (phone), gateway or other hardware/software involved:

5. Your problem:

1). A call B, B answer it;
2). B disconnect the call;
from network packets, I can see that B can send out "Bye", but brekeke server repies with "503 service unavailable".

and I have tried another scenario as below:
1). B call A, A answer it;
2). B disconnect the call;
from network packets, I can see that B can send out "Bye", and brekeke server replies with "200 OK".

in the 2 scenarios above, "Bye" packet from B is almost the same, but why server replies with different responses.

Thanks.

[Harold]

It seems the BYE sent from B doesn't meet SIP standard.

Which SIP client product are you using?
Can you paste INVITE sent from A, 200-OK and BYE sent from B?

[Nancy]

INVITE sent from A, 200-OK for invite and BYE sent from B are attached:

1.>>>>>> Invite sent from A:
INVITE sip:1003@192.168.29.2:5010 SIP/2.0
Via: SIP/2.0/UDP 192.168.29.33:5060;branch=z9hG4bK53a7b4f67d4d-30-18e315
Via: SIP/2.0/TCP 192.168.29.33:62370;rport=62370;branch=z9hG4bKPj15ba539e78d5409685a93afe69ec4e26;alias
Max-Forwards: 69
From: "1002" <sip:1002@192.168.29.33>;tag=9eef20fd797a4487aa31e04a78977671
To: <sip:1003@192.168.29.33>
Contact: "1002" <sip:1002@192.168.29.33:5060;ob>
Call-ID: ae760d67ee83459cb6bc10fbd3bfd2af
CSeq: 20352 INVITE
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Supported: replaces, 100rel, timer, norefersub
Session-Expires: 1800
Min-SE: 90
User-Agent: MicroSIP/3.15.9
Proxy-Authorization: Digest username="1002", realm="myname", nonce="52a65945eb6452606303dc3e657e48bf0e306e92", uri="sip:1003@192.168.29.33", response="bad3fc0b3850c0256b4cc14b456e65e2", algorithm=MD5
Record-Route: <sip:192.168.29.33:5060;ftag=null;lr>
Content-Type: application/sdp
Content-Length: 628

v=0
o=- 3859887780 3859887780 IN IP4 192.168.29.33
s=pjmedia
b=AS:84
t=0 0
a=X-nat:0
m=audio 10124 RTP/AVP 8 101
c=IN IP4 192.168.29.33
b=TIAS:64000
a=sendrecv
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=crypto:1 AES_256_CM_HMAC_SHA1_80 inline:Fb2mFOlhjpEtu86u7Mzund8HVyTa1DYCr0VVRD1k+3G9kKr34lEFwf8d4+rXvg==
a=crypto:2 AES_256_CM_HMAC_SHA1_32 inline:JBWHjmqSPPJ0K5rfMaJQEx3yPcMVWLu6ARAm5WJ5B3DufMdxkWrurxiJMooBUA==
a=crypto:3 AES_CM_128_HMAC_SHA1_80 inline:qQRgmpHmU3eofBuXyKgFEPLmmOsk4xsStWs2vJil
a=crypto:4 AES_CM_128_HMAC_SHA1_32 inline:ZyjR1FEfMLz2av/zs6Zg/k5Vrb2G63KmDiTa6zs+


2.>>>>>>200 OK sent from B:
SIP/2.0 200 OK
From: "1002"<sip:1002@192.168.29.33>;tag=9eef20fd797a4487aa31e04a78977671
To: <sip:1003@192.168.29.33>;tag=7c9888d1-2b0e5586-50-cf5f30-c0a81d02-1392-7219
Call-ID: ae760d67ee83459cb6bc10fbd3bfd2af
CSeq: 20352 INVITE
Via: SIP/2.0/UDP 192.168.29.33:5060;branch=z9hG4bK53a7b4f67d4d-30-18e315
Via: SIP/2.0/TCP 192.168.29.33:62370;alias;rport=62370;branch=z9hG4bKPj15ba539e78d5409685a93afe69ec4e26
Supported: 100rel,replaces,path,sec-agree,precondition,timer
Require: timer
User-Agent: test12345
Record-Route: <sip:192.168.29.33:5060;lr;ftag=null>
Contact: <sip:1003@192.168.29.2:5010>;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";+g.3gpp.mid-call
Session-Expires: 1800;refresher=uac
Allow: INVITE,ACK,CANCEL,BYE,REFER,NOTIFY,PRACK,OPTIONS,UPDATE,MESSAGE,INFO
Content-Type: application/sdp
Content-Length: 256

v=0
o=sip:1003@192.168.29.33 120 0 IN IP4 192.168.29.2
s=SIP
c=IN IP4 192.168.29.2
t=0 0
a=sendrecv
m=audio 50000 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv
a=sqn:0
a=cdsc:1 image udptl t38


3.>>>>>>Bye sent from B:
BYE sip:1002@192.168.29.33:5060;ob SIP/2.0
From: <sip:1003@192.168.29.33>;tag=7c9888d1-2b0e5586-50-cf5f30-c0a81d02-1392-7219
To: "1002"<sip:1002@192.168.29.33>;tag=9eef20fd797a4487aa31e04a78977671
Call-ID: ae760d67ee83459cb6bc10fbd3bfd2af
CSeq: 1 BYE
Contact: <sip:1003@192.168.29.2:5010>;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";+g.3gpp.mid-call
Via: SIP/2.0/UDP 192.168.29.2:5010;branch=z9hG4bK-6fbaf584-5d-16d27-cdcce8
Max-Forwards: 70
Supported: 100rel,replaces,path,sec-agree,precondition,timer
User-Agent: test12345
Allow: INVITE,ACK,CANCEL,BYE,REFER,NOTIFY,PRACK,OPTIONS,UPDATE,MESSAGE,INFO
Content-Length: 0

[Harold]

These SIP packets look no problem.
Can you also paste the "503 service unavailable" packet here? It might have Reason phrase.
Is "503" sent from the SIP Server or the caller-A?
Also check the [Result phrase] at [Logs]->[Session Logs].

[Nancy]

Can you also paste the "503 service unavailable" packet here?
>>>> It does not include any Reason phrase.
Is "503" sent from the SIP Server or the caller-A?
>>>> Yes
Also check the [Result phrase] at [Logs]->[Session Logs].
>>>> web page shows "HTTP Status 500 - Exception caught.".

[Harold]

> Brekeke SIP Server, Version 3.6.3.0

You are using a pretty old version. The 3.6.3.0 was released 6 years go.

Let you update it to the latest version. It is 3.13.0.0.
Refer to the page below.
https://docs.brekeke.com/sip/minor-version-update