Not getting SIP 200 after the outgoing call is accepted.

[eesaeedkarimi]

I have used the package on Ubuntu. After the an outgoing call is accepted I don't get a SIP 200 from server.
I have checked it by debugging the python code.

I have also sniffed all SIP packets with wire shark.
I have done the same work with Windows Cisco Jabber and I get the SIP 200 from server when the outgoing call is accepted.
Here is the export of wire shark on Ubuntu:

No. | Time | Source | Destination | Protocol | Length | Info
-- | -- | -- | -- | -- | -- | --
14 | 3.86061746 | 10.100.11.18 | 192.168.111.231 | SIP/SDP | 1886 | Request: INVITE sip:[email protected];user=phone \|
16 | 3.872630074 | 192.168.111.231 | 10.100.11.18 | SIP | 434 | Status: 100 Trying \|
18 | 3.901356716 | 192.168.111.231 | 10.100.11.18 | SIP | 1196 | Request: SUBSCRIBE sip:[email protected]:36062;transport=tcp \|
20 | 3.914313951 | 10.100.11.18 | 192.168.111.231 | SIP | 556 | Status: 200 OK (SUBSCRIBE) \|
22 | 3.956318322 | 10.100.11.18 | 192.168.111.231 | SIP | 809 | Request: NOTIFY sip:[email protected];transport=tcp \|
24 | 3.979090743 | 192.168.111.231 | 10.100.11.18 | SIP | 416 | Status: 200 OK (NOTIFY) \|
25 | 3.97935105 | 10.100.11.18 | 192.168.111.231 | SIP | 1047 | Request: NOTIFY sip:[email protected];transport=tcp \|
26 | 4.001892981 | 192.168.111.231 | 10.100.11.18 | SIP | 438 | Status: 200 OK (NOTIFY) \|
27 | 4.021040412 | 192.168.111.231 | 10.100.11.18 | SIP | 686 | Request: SUBSCRIBE sip:[email protected]:36062;transport=tcp \|
29 | 4.02184363 | 10.100.11.18 | 192.168.111.231 | SIP | 557 | Status: 200 OK (SUBSCRIBE) \|
31 | 4.064974448 | 10.100.11.18 | 192.168.111.231 | SIP | 1029 | Request: NOTIFY sip:[email protected];transport=tcp \|
33 | 4.070768431 | 192.168.111.231 | 10.100.11.18 | SIP | 417 | Status: 200 OK (NOTIFY) \|
43 | 6.493687246 | 192.168.111.231 | 10.100.11.18 | SIP/SDP | 1194 | Status: 183 Session Progress \|
45 | 6.493687791 | 192.168.111.231 | 10.100.11.18 | SIP | 1135 | Request: SUBSCRIBE sip:[email protected]:36062;transport=tcp, in-dialog \|
48 | 6.59885332 | 10.100.11.18 | 192.168.111.231 | SIP | 822 | Request: ACK sip:[email protected];transport=tcp \|
55 | 6.643575391 | 10.100.11.18 | 192.168.111.231 | SIP | 1513 | Status: 200 OK (SUBSCRIBE) \| Request: NOTIFY sip:[email protected];transport=tcp \|
61 | 6.683318844 | 192.168.111.231 | 10.100.11.18 | SIP | 522 | Status: 200 OK (NOTIFY) \|
64 | 6.684247515 | 10.100.11.18 | 192.168.111.231 | SIP | 1155 | Request: NOTIFY sip:[email protected];transport=tcp \|
66 | 6.702576296 | 192.168.111.231 | 10.100.11.18 | SIP | 544 | Status: 200 OK (NOTIFY) \|
134 | 7.349199196 | 192.168.111.231 | 10.100.11.18 | SIP | 1115 | Request: UPDATE sip:[email protected]:36062;transport=tcp \|
1881 | 24.046678923 | 192.168.111.231 | 10.100.11.18 | SIP | 619 | Status: 500 Internal Server Error \|
3008 | 43.647757568 | 192.168.111.231 | 10.100.11.18 | SIP | 677 | Request: SUBSCRIBE sip:[email protected]:36062;transport=tcp, in-dialog \|

And here is the export of wire shark on Windows:

No. | Time | Source | Destination | Protocol | Length | Info
-- | -- | -- | -- | -- | -- | --
39 | 4.233104 | 10.100.11.45 | 192.168.111.231 | SIP | 1121 | Request: NOTIFY sip:[email protected] \|
40 | 4.245197 | 192.168.111.231 | 10.100.11.45 | SIP | 419 | Status: 200 OK (NOTIFY) \|
59 | 4.607413 | 10.100.11.45 | 192.168.111.231 | SIP/SDP | 776 | Request: INVITE sip:[email protected];user=phone \|
62 | 4.616354 | 192.168.111.231 | 10.100.11.45 | SIP | 421 | Status: 100 Trying \|
63 | 4.642067 | 192.168.111.231 | 10.100.11.45 | SIP | 1186 | Request: SUBSCRIBE sip:[email protected]:3423;transport=tcp \|
65 | 4.644925 | 10.100.11.45 | 192.168.111.231 | SIP | 567 | Status: 200 OK (SUBSCRIBE) \|
66 | 4.646943 | 10.100.11.45 | 192.168.111.231 | SIP | 722 | Request: NOTIFY sip:[email protected]:5060;transport=tcp \|
68 | 4.652403 | 192.168.111.231 | 10.100.11.45 | SIP | 413 | Status: 200 OK (NOTIFY) \|
96 | 7.651882 | 10.100.11.45 | 192.168.111.231 | SIP | 1032 | Request: NOTIFY sip:[email protected]:5060;transport=tcp \|
97 | 7.659216 | 192.168.111.231 | 10.100.11.45 | SIP | 413 | Status: 200 OK (NOTIFY) \|
98 | 7.663125 | 192.168.111.231 | 10.100.11.45 | SIP | 713 | Request: SUBSCRIBE sip:[email protected]:3423;transport=tcp, in-dialog \|
100 | 7.665438 | 10.100.11.45 | 192.168.111.231 | SIP | 564 | Status: 200 OK (SUBSCRIBE) \|
101 | 7.667018 | 10.100.11.45 | 192.168.111.231 | SIP | 1041 | Request: NOTIFY sip:[email protected]:5060;transport=tcp \|
103 | 7.672003 | 192.168.111.231 | 10.100.11.45 | SIP | 413 | Status: 200 OK (NOTIFY) \|
110 | 9.885032 | 192.168.111.231 | 10.100.11.45 | SIP/SDP | 1211 | Status: 183 Session Progress \|
111 | 9.887008 | 192.168.111.231 | 10.100.11.45 | SIP | 1122 | Request: SUBSCRIBE sip:[email protected]:3423;transport=tcp, in-dialog \|
122 | 10.125199 | 10.100.11.45 | 192.168.111.231 | SIP | 718 | Status: 200 OK (SUBSCRIBE) \|
123 | 10.126082 | 10.100.11.45 | 192.168.111.231 | SIP | 860 | Request: NOTIFY sip:192.168.111.231:5060;transport=tcp \|
125 | 10.130663 | 192.168.111.231 | 10.100.11.45 | SIP | 477 | Status: 200 OK (NOTIFY) \|
198 | 10.752204 | 192.168.111.231 | 10.100.11.45 | SIP | 1102 | Request: UPDATE sip:[email protected]:3423;transport=tcp \|
199 | 10.754098 | 10.100.11.45 | 192.168.111.231 | SIP | 782 | Status: 200 OK (UPDATE) \|
1146 | 19.109488 | 192.168.111.231 | 10.100.11.45 | SIP/SDP | 1312 | Status: 200 OK (INVITE) \|
1147 | 19.118402 | 10.100.11.45 | 192.168.111.231 | SIP | 796 | Request: ACK sip:[email protected]:5060;transport=tcp \|
1151 | 19.131676 | 192.168.111.231 | 10.100.11.45 | SIP/SDP | 1398 | Request: INVITE sip:[email protected]:3423;transport=tcp \|
1152 | 19.134359 | 10.100.11.45 | 192.168.111.231 | SIP | 1087 | Status: 100 Trying \|
1171 | 19.252655 | 10.100.11.45 | 192.168.111.231 | SIP/SDP | 57 | Status: 200 OK (INVITE) \|
1174 | 19.257942 | 192.168.111.231 | 10.100.11.45 | SIP | 588 | Request: ACK sip:[email protected]:3423;transport=tcp \|
1177 | 19.261102 | 192.168.111.231 | 10.100.11.45 | SIP | 1050 | Request: INVITE sip:[email protected]:3423;transport=tcp, in-dialog \|
1180 | 19.268193 | 10.100.11.45 | 192.168.111.231 | SIP | 1125 | Status: 100 Trying \|
1195 | 19.380765 | 10.100.11.45 | 192.168.111.231 | SIP/SDP | 315 | Status: 200 OK (INVITE) \|
1200 | 19.410436 | 192.168.111.231 | 10.100.11.45 | SIP/SDP | 1397 | Request: INVITE sip:[email protected]:3423;transport=tcp \|
1201 | 19.411978 | 10.100.11.45 | 192.168.111.231 | SIP | 1087 | Status: 100 Trying \|
1208 | 19.440889 | 10.100.11.45 | 192.168.111.231 | SIP/SDP | 57 | Status: 200 OK (INVITE) \|
1211 | 19.447402 | 192.168.111.231 | 10.100.11.45 | SIP | 588 | Request: ACK sip:[email protected]:3423;transport=tcp \|
1212 | 19.449712 | 192.168.111.231 | 10.100.11.45 | SIP | 1050 | Request: INVITE sip:[email protected]:3423;transport=tcp, in-dialog \|
1214 | 19.454362 | 10.100.11.45 | 192.168.111.231 | SIP | 1125 | Status: 100 Trying \|
1225 | 19.531979 | 10.100.11.45 | 192.168.111.231 | SIP/SDP | 315 | Status: 200 OK (INVITE) \|
1248 | 19.731738 | 192.168.111.231 | 10.100.11.45 | SIP/SDP | 927 | Request: ACK sip:[email protected]:3423;transport=tcp \|
1250 | 19.742333 | 192.168.111.231 | 10.100.11.45 | SIP/SDP | 927 | Request: ACK sip:[email protected]:3423;transport=tcp \|
2496 | 25.611184 | 192.168.111.231 | 10.100.11.45 | SIP | 686 | Request: BYE sip:[email protected]:3423;transport=tcp \|
2497 | 25.613572 | 10.100.11.45 | 192.168.111.231 | SIP | 1125 | Request: NOTIFY sip:[email protected] \|
2499 | 25.620286 | 192.168.111.231 | 10.100.11.45 | SIP | 418 | Status: 200 OK (NOTIFY) \|
2517 | 25.746379 | 10.100.11.45 | 192.168.111.231 | SIP | 688 | Status: 200 OK (BYE) \|
2519 | 25.755933 | 192.168.111.231 | 10.100.11.45 | SIP | 663 | Request: SUBSCRIBE sip:[email protected]:3423;transport=tcp, in-dialog \|
2520 | 25.763528 | 10.100.11.45 | 192.168.111.231 | SIP | 711 | Request: BYE sip:192.168.111.231:5060;transport=tcp \|
2522 | 25.771045 | 192.168.111.231 | 10.100.11.45 | SIP | 1294 | Request: BYE sip:[email protected]:3423;transport=tcp \| Request: BYE sip:[email protected]:3423;transport=tcp \|
2524 | 25.772102 | 10.100.11.45 | 192.168.111.231 | SIP | 663 | Status: 200 OK (BYE) \|
2525 | 25.77529 | 192.168.111.231 | 10.100.11.45 | SIP | 462 | Status: 200 OK (BYE) \|
2532 | 25.898775 | 10.100.11.45 | 192.168.111.231 | SIP | 663 | Status: 200 OK (BYE) \|
2537 | 26.037793 | 10.100.11.45 | 192.168.111.231 | SIP | 628 | Status: 200 OK (SUBSCRIBE) \|
2538 | 26.039809 | 10.100.11.45 | 192.168.111.231 | SIP | 1085 | Request: NOTIFY sip:192.168.111.231:5060;transport=tcp \|
2541 | 26.055691 | 192.168.111.231 | 10.100.11.45 | SIP | 477 | Status: 200 OK (NOTIFY) \|

[schorschii]

It's hard to say what the problem is here without knowing the contents of the SIP packages. You may send the Wireshark .pcap files to me at [email protected] if you like.