SIP Failure Code during the first ~30 a user is disconnected #142
Assignees
Labels
Comments
|
|
|
please collect a trace from the server. |
|
I'm getting *Permission denied (publickey). *I guess this means that I'm
not authorized to ssh rhizortc (I never gave my public key for that). I
think that the shortest way to move on is @gmarcos87 to log this test,
since I understand he knows how to reproduce the SIP Failure Code message
and has the necessary permisions.
Anyway, I'm available to run the test if someone gives me the support for
that.
rodrigo@rodrigo-UX303UB:~$ ssh root@rhizortc.specialstories.org
The authenticity of host 'rhizortc.specialstories.org (138.68.99.252)'
can't be established.
ECDSA key fingerprint is SHA256:d52zMlx0IPM3llEU3MjWLRl
QDOIKF/fBkl1dhQS8yU0.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'rhizortc.specialstories.org,138.68.99.252'
(ECDSA) to the list of known hosts.
*Permission denied (publickey).*
***@***.***:~$ tail -f /var/log/daemon.log >
kamailio_log_date +"%F-%H_%M_%S".txt
tail: no se puede abrir '/var/log/daemon.log' para lectura: No existe el
archivo o el directorio
tail: no se puede abrir '+%F-%H_%M_%S.txt' para lectura: No existe el
archivo o el directorio
tail: no queda ningún fichero
2017-11-22 12:31 GMT-04:00 Stefan Sayer <notifications@github.com>:
… please collect a trace from the server.
ssh ***@***.***
run this:
tail -f /var/log/daemon.log > kamailio_log_date +"%F-%H_%M_%S".txt
and make the test. thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#142 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AZmH3kjUK1D_nfNpRK-USkw3kHyZUvQ0ks5s5Ex1gaJpZM4QmpD9>
.
|
I did the following steps:
|
|
@gmarcos87 thanks for the log (the interesting part was much lower in the log, but I could actually find it on the server). I have added a |
|
re log tracing: you can on rhizortc now run |
|
Can you see the app logs when try to pick up? Maybe it's an error. What
browser do you use? Are you using the app from https?
El 27 nov. 2017 2:55 p. m., "Stefan Sayer" <notifications@github.com>
escribió:
@gmarcos87 <https://github.com/gmarcos87> thanks for the log (the
interesting part was much lower in the log, but I could actually find it on
the server).
I have added a t_set_disable_internal_reply(1); which should prevent the
server from generating that reply, but I am struggling to reproduce (I get
always 480 back from the app when I try to pick up - 4af84ff)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#142 (comment)>,
or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AKRlThVs38E2hHBYiUev9lzuH-80JND9ks5s6veRgaJpZM4QmpD9>
.
|
|
Hi @sanchi I tested and I still get the "SIP Failure Code" message. |
|
Is related to the user status. It is independent of whether it is call or message. |
|
hm, can you please try to get a log? @rodrigomonelos your key is on the server. just ssh to it (ssh rhizortc.specialstories.org) and run kamailio-trace |
|
I logged in and ran the command you indicated, getting a *cannot open* error
message. Find below the log from my terminal.
I ran the test anyway, I don't know if there is something logged anyway.
I also remember you saying that we should turn off the logging after
testing. I do not know if it is actually turned on, but anyway can you
check if it is necessary to turn it off?
tnks
rodrigo@rodrigo-UX303UB:~$ ssh root@rhizortc.specialstories.org
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
***@***.***:~# tail -f /var/log/daemon.log > kamailio_log_date
+"%F-%H_%M_%S".txt
tail: cannot open '+%F-%H_%M_%S.txt' for reading: No such file or directory
packet_write_wait: Connection to 138.68.99.252 port 22: Broken pipe
2017-11-27 19:34 GMT-04:00 Stefan Sayer <notifications@github.com>:
… hm, can you please try to get a log? @rodrigomonelos
<https://github.com/rodrigomonelos> your key is on the server. just ssh
to it (ssh rhizortc.specialstories.org) and run kamailio-trace
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#142 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AZmH3rqBiCyicdRkCffxi5OLn-RVvONBks5s60cbgaJpZM4QmpD9>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I get a SIP Failure Code message on the sms-version of the app when trying to send a message to a user that has just disconnected. Messaging works fine both when both users are online as well as when the one offline has been on that state for more than ~30''.
Steps to reproduce:
According with @gmarcos87 this has to do with the time that the backend is taking to register that a user went offline. How can we know this?
The text was updated successfully, but these errors were encountered: