[ASTPPCOM-473] SIP-DID return USER_NOT_REGISTERED, but DID-local is working Created: 07/Dec/18 Updated: 01/Apr/21 Resolved: 01/Apr/21 |
|
| Status: | Done |
| Project: | ASTPP Community |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | ||
| Reporter: | Eduardo Felipe de Oliveira (Inactive) | Assignee: | Samir Doshi |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Good night, I updated ASTPP but I have a problem: Recently all calls that are with the DID set to call-type SIP-DID are returning USER_NOT_REGISTERED. When we test as DID-Local the call is received by the PBX normally. But this way I can not determine which DID this call belongs to. How can we find the error in this case? Regards, Eduardo. |
| Comments |
| Comment by Eduardo Felipe de Oliveira (Inactive) [ 07/Dec/18 ] |
|
My current configuration is according to the image above, where one works and the other does not. |
| Comment by Samir Doshi [ 07/Dec/18 ] |
|
Hi, Provide your call fs_cli log for SIP-DID. > eval ${domain_name} Thanks, Samir Doshi iNextrix Technologies Pvt. Ltd. Disclaimer: The information contained in this communication is confidential and may be [image: Mailtrack] On Fri, Dec 7, 2018 at 12:24 PM Eduardo Felipe de Oliveira < > [image: did-config] |
| Comment by Eduardo Felipe de Oliveira (Inactive) [ 07/Dec/18 ] |
|
Hi Samir, The return of eval $ {domain_name}is 172.31.6.59 which is the local IP of the machine. The ASTPP log is attached. Regards, Eduardo. |
| Comment by Elton Bahia (Inactive) [ 07/Dec/18 ] |
|
no log conta que o ramal não está registrado. |
| Comment by Eduardo Felipe de Oliveira (Inactive) [ 07/Dec/18 ] |
|
Esta registrado, tem sessão: Call-ID: 242dcda0a4664de2b45583e12ea7dc10 Mas o freeswitch não esta conseguindo encontrar. |
| Comment by Eduardo Felipe de Oliveira (Inactive) [ 07/Dec/18 ] |
|
Hi Samir I found what was causing the problem.
I had two profiles enabled. When I disabled the profile that was not in use and stopped it, the SIP-DID calls started again. Apparently the problem occurred when the profile that is not being used by the extensions was active before the "Default" profile that I am using. Regards, Eduardo. |
| Comment by Samir Doshi [ 10/Dec/18 ] |
|
Ok Great. Thanks, Samir Doshi iNextrix Technologies Pvt. Ltd. Disclaimer: The information contained in this communication is confidential and may be [image: Mailtrack] On Fri, Dec 7, 2018 at 10:28 PM Eduardo Felipe de Oliveira < > Hi Samir |