<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi,<br>
I made some interesting observations regarding this.<br>
Remind the following scenario:<br>
asterisk registers number A towards provider A (sipgate.de)<br>
asterisk also registers another number towards provider B
(tel.t-online.de)<br>
<br>
I make a test call from a remote location, which is registered as
well towards provider B.<br>
<br>
What happens on the asterisk?<br>
<font face="Courier New, Courier, monospace"><br>
have a look below.<br>
It seems that the registration to number </font><font
face="Courier New, Courier, monospace">B of provider B, which
sends the incoming call to asterisk, brings asterisk out of order,
because the ACKs are sent to the wrong port.<br>
after some time the ACK of provider B reaches asterisk on the
right port (55060), but that is maybe by accident. when the trunk
to provider B is disabled it works fine immediately.<br>
That explains, why calls to sipgate.de are cancelled after about
30s.<br>
But can someone explain that? Is it an issue of provider B (which
I can't believe, it is one of the biggest here in germany)?<br>
<br>
<br>
<br>
217.10.79.9:5060
10.17.46.99:55060 217.0.23.36:5060
10.17.46.99:65319 10.17.46.99:505<br>
──────────┬─────────
──────────┬───────── ──────────┬─────────
──────────┬───────── ──────────┬──────<br>
▒ │ INVITE (SDP)
│ │
│ │ <br>
▒ 18:26:47.695820 │ ──────────────────────────>
│ │
│ │ <br>
▒ +0.001354 │ 100 Trying
│ │
│ │ <br>
▒ 18:26:47.697174 │ <──────────────────────────
│ │
│ │ <br>
▒ +0.024128 │ 200 OK (SDP)
│ │
│ │ <br>
▒ 18:26:47.721302 │ <──────────────────────────
│ │
│ │ <br>
▒ +0.418916 │ INVITE (SDP)
│ │
│ │ <br>
▒ 18:26:48.140218 │ ────────────────────────>>>
│ │
│ │ <br>
▒ +0.000464 │ 200 OK (SDP)
│ │
│ │ <br>
▒ 18:26:48.140682 │ <<<────────────────────────
│ │
│ │ <br>
▒ +0.047604 │
│ │ ACK
│ │ <br>
▒ 18:26:48.188286 │
│ │ ──────────────────────────>
│ │ <br>
▒ +0.033199 │ 200 OK (SDP)
│ │
│ │ <br>
▒ 18:26:48.221485 │ <<<────────────────────────
│ │
│ │ <br>
▒ +0.413234 │
│ │ ACK
│ │ <br>
▒ 18:26:48.634719 │
│ │ ──────────────────────────>
│ │ <br>
▒ +0.073871 │
│ │ ACK
│ │ <br>
▒ 18:26:48.708590 │
│ │ ──────────────────────────>
│ │ <br>
▒ +1.513110 │ 200 OK (SDP)
│ │
│ │ <br>
▒ 18:26:50.221700 │ <<<────────────────────────
│ │
│ │ <br>
▒ +0.478899 │
│ │ ACK
│ │ <br>
▒ 18:26:50.700599 │
│ │ ──────────────────────────>
│ │ <br>
▒ +3.520824 │ 200 OK (SDP)
│ │
│ │ <br>
▒ 18:26:54.221423 │ <<<────────────────────────
│ │
│ │ <br>
▒ +0.524939 │
│ │ ACK
│ │ <br>
▒ 18:26:54.746362 │
│ │ ──────────────────────────>
│ │ <br>
▒ +3.475120 │ 200 OK (SDP)
│ │
│ │ <br>
▒ 18:26:58.221482 │ <<<────────────────────────
│ │
│ │ <br>
▒ +0.482321 │
│ │ ACK
│ │ <br>
▒ 18:26:58.703803 │
│ │ ──────────────────────────>
│ │ <br>
▒ +3.519206 │ 200 OK (SDP)
│ │
│ │ <br>
▒ 18:27:02.223009 │ <<<────────────────────────
│ │
│ │ <br>
▒ +0.481228 │
│ │ ACK
│ │ <br>
▒ 18:27:02.704237 │
│ │ ──────────────────────────>
│ │ <br>
▒ +3.518524 │ 200 OK (SDP)
│ │
│ │ <br>
▒ 18:27:06.222761 │ <<<────────────────────────
│ │
│ │ <br>
│ +0.483722 │
│ │ ACK
│ │ <br>
│ 18:27:06.706483 │
│ │ ──────────────────────────>
│ │ <br>
│ +3.516816 │ 200 OK (SDP)
│ │
│ │ <br>
│ 18:27:10.223299 │ <<<────────────────────────
│ │
│ │ <br>
│ +0.484398 │ │
ACK │
│ │ <br>
│ 18:27:10.707697 │ │
<────────────────────────── │
│ │ <br>
│ +59.790625 │
│ │
BYE │ <br>
│ 18:28:10.498322 │
│ │
────────────────────────────────────────────────────────> │ <br>
<br>
</font><br>
<br>
<br>
<div class="moz-cite-prefix">Am 15.10.2016 um 15:39 schrieb Andre
Gronwald:<br>
</div>
<blockquote
cite="mid:e9a5c551-5a21-6641-7b4c-8723b276869b@gmail.com"
type="cite">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
ok, now it is getting weird...<br>
actually i don't see any firewall issues, but i am not able to get
a call from outside to my sipgate account. in asterisk nothing is
visible, core set verbose is activated.<br>
sngrep (on my asterisk server) shows me indeed the invite from
sipgate!?<br>
<font face="Courier New, Courier, monospace"><br>
What I see via sngrep is the following options-flow:<br>
192.168.3.50:55060 -> 217.10.79.9:5060</font><br>
<font face="Courier New, Courier, monospace"><font face="Courier
New, Courier, monospace">217.10.79.9:5060 ->
192.168.3.50:48757 (200 OK)<br>
<br>
shouldn't sipgate answer on the same port that the
communication initiated??? in this case 55060?<br>
</font><br>
</font> </blockquote>
<br>
</body>
</html>