[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.
Also, run the following command in fs_cli and give its output

> eval ${domain_name}

Thanks,

Samir Doshi

iNextrix Technologies Pvt. Ltd.

https://www.inextrix.com

https://www.astppbilling.org

Disclaimer:

The information contained in this communication is confidential and may be
legally privileged. It is intended solely for the use of the individual or
entity to whom it is addressed and others authorized to receive it. If you
are not the intended recipient you are hereby notified that any disclosure,
copying, distribution or taking action in reliance on the contents of this
information is strictly prohibited and may be unlawful. Please notify the
sender immediately and destroy all copies of this message and any
attachments contained in it.

[image: Mailtrack]
<https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&>
Sender
notified by
Mailtrack
<https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&>
12/07/18,
5:00:42 PM

On Fri, Dec 7, 2018 at 12:24 PM Eduardo Felipe de Oliveira <
notifications@github.com> wrote:

> [image: did-config]
> <https://user-images.githubusercontent.com/20446658/49632225-1679c300-f9dc-11e8-8b98-18da2f157ace.png>
>
> My current configuration is according to the image above, where one works
> and the other does not.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/iNextrix/ASTPP/issues/473#issuecomment-445140889>, or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/AA6gcb9KItG4goH8iIVKg8-wb8qudBzgks5u2hC3gaJpZM4ZH4kT>
> .
>

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.
log-freeswitch-sip-did.log

Comment by Elton Bahia (Inactive) [ 07/Dec/18 ]

no log conta que o ramal não está registrado.
Rode o comando show registrations on CLI do freeswitch e verifica se ele contra-se conectado na lista.

Comment by Eduardo Felipe de Oliveira (Inactive) [ 07/Dec/18 ]

Esta registrado, tem sessão:

Call-ID: 242dcda0a4664de2b45583e12ea7dc10
User: TSingular@172.31.6.59
Contact: "TSingular" <sip:TSingular@192.168.4.10:64491;ob;fs_nat=yes;fs_path=sip%3ATSingular%40177.189.208.91%3A64491%3Bob>
Agent: MicroSIP/3.19.7
Status: Registered(UDP-NAT)(unknown) EXP(2018-12-07 12:07:02) EXPSECS(110)
Ping-Status: Reachable
Ping-Time: 0.00
Host: ip-172-31-6-59
IP: 177.189.208.91
Port: 64491
Auth-User: TSingular
Auth-Realm: singular.cloudcom.com.br
MWI-Account: TSingular@172.31.6.59

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.

https://www.inextrix.com

https://www.astppbilling.org

Disclaimer:

The information contained in this communication is confidential and may be
legally privileged. It is intended solely for the use of the individual or
entity to whom it is addressed and others authorized to receive it. If you
are not the intended recipient you are hereby notified that any disclosure,
copying, distribution or taking action in reliance on the contents of this
information is strictly prohibited and may be unlawful. Please notify the
sender immediately and destroy all copies of this message and any
attachments contained in it.

[image: Mailtrack]
<https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&>
Sender
notified by
Mailtrack
<https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&>
12/10/18,
6:31:41 PM

On Fri, Dec 7, 2018 at 10:28 PM Eduardo Felipe de Oliveira <
notifications@github.com> wrote:

> Hi Samir
>
> I found what was causing the problem.
>
> [image: sip profiles]
> <https://user-images.githubusercontent.com/20446658/49661560-82861680-fa30-11e8-8b11-38db0ce0f5fb.png>
>
> I had two profiles enabled.
>
> When I disabled the profile that was not in use and stopped it, the
> SIP-DID calls started again.
>
> Regards,
>
> Eduardo.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/iNextrix/ASTPP/issues/473#issuecomment-445296460>, or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/AA6gcaPxNnP0Yay3dU0M8zYMTm_ieYsnks5u2p43gaJpZM4ZH4kT>
> .
>

Generated at Sat Feb 10 07:17:27 CET 2024 using Jira 8.13.3#813003-sha1:22ebedbb75c99b147c66f14e031dd8a2d214753a.