[ASTPPCOM-62] Accountcode is not authenticated Created: 15/Aug/16 Updated: 02/Sep/16 Resolved: 02/Sep/16 |
|
| Status: | Done |
| Project: | ASTPP Community |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | ||
| Reporter: | Hein Tonny Køien (Inactive) | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
We are not able to dial out from a successful registered SIP-endpoint. The logfile shows: But the wireshark trace shows that it is. I have included the trace from freeswithc, pcap from the endpoint (Bria Stretto). |
| Comments |
| Comment by juancarlosg6 [ 16/Aug/16 ] |
|
You must create a SIP device into the account and use the information created for the system to log SIP device. |
| Comment by Hein Tonny Køien (Inactive) [ 16/Aug/16 ] |
|
The account 33994110 alreaddy have a sip-device named 33994110, and the pcap shows that we have a successfull SIP login. |
| Comment by Samir Doshi [ 16/Aug/16 ] |
|
Please share fs_cli log. use http://pastebin.com/ |
| Comment by Hein Tonny Køien (Inactive) [ 16/Aug/16 ] |
|
Here it is. It includes the SIP login and first call attempt. |
| Comment by Samir Doshi [ 22/Aug/16 ] |
|
Hi Hein, It seems the sip device ip address is already added in ACL and not linked with proper account. That is causing the issue. 2016-08-16 09:33:35.927162 [DEBUG] sofia.c:9488 IP 10.20.50.100 Approved by acl "default[]". Access Granted. Please remove this ip from acl OR link it with correct account to get account code. |
| Comment by Samir Doshi [ 02/Sep/16 ] |
|
We assume the issue has been resolved from your end. So we are closing the ticket. |