https://jira.astppbilling.org This file is an XML representation of an issue en-us 8.13.3 813003 14-01-2021 https://jira.astppbilling.org/browse/ASTPPCOM-62 ASTPP Community <p>We are not able to dial out from a successful registered SIP-endpoint.</p> <p>The logfile shows:<br/> Accountcode is not authenticated</p> <p>But the wireshark trace shows that it is.</p> <p>I have included the trace from freeswithc, pcap from the endpoint (Bria Stretto).</p> ASTPPCOM-62

Accountcode is not authenticated

Task Done Done Unassigned Hein Tonny Køien Tue, 16 Aug 2016 03:20:24 +0530 Fri, 2 Sep 2016 13:45:14 +0530 Fri, 2 Sep 2016 13:45:14 +0530 0 0 <p>You must create a SIP device into the account and use the information created for the system to log SIP device.</p> <p>The account 33994110 alreaddy have a sip-device named 33994110, and the pcap shows that we have a successfull SIP login.</p> <p>Please share fs_cli log. use <a href="http://pastebin.com/" class="external-link" target="_blank" rel="nofollow noopener">http://pastebin.com/</a></p> <p>Here it is. It includes the SIP login and first call attempt.<br/> <a href="http://pastebin.com/023W1D6h" class="external-link" target="_blank" rel="nofollow noopener">http://pastebin.com/023W1D6h</a></p> <p>Hi Hein, </p> <p>It seems the sip device ip address is already added in ACL and not linked with proper account. That is causing the issue. </p> <p>2016-08-16 09:33:35.927162 <span class="error">&#91;DEBUG&#93;</span> sofia.c:9488 IP 10.20.50.100 Approved by acl "default[]". Access Granted.</p> <p>Please remove this ip from acl OR link it with correct account to get account code. </p> <p>We assume the issue has been resolved from your end. So we are closing the ticket. </p> Development External issue ID 62 Rank 0|i0090n: