Re: [asterisk-users] Disable NO_USER_RESPONSE (Hangupcause = 18) for certain SIP peer

2019-11-16 Thread Sebastian Nielsen
FINALLY solved it… Googled around for the problem, and found this: https://support.yeastar.com/hc/en-us/articles/360020908914-Call-Hangs-up-at-30-Seconds Apparently, sendrpid=yes causes Android Native SIP client not to respond to the packets, and this drops the call after 30 seconds. Disa

Re: [asterisk-users] Disable NO_USER_RESPONSE (Hangupcause = 18) for certain SIP peer

2019-11-16 Thread Joshua C. Colp
On Sat, Nov 16, 2019 at 7:59 PM Sebastian Nielsen wrote: > What would be the best way to solve this problem? Anyone else that have > got the same problem with Android’s native SIP client, especially on > Samsung phones? > > > > I do not know if the bug is in Android native SIP, or Samsung’s build

Re: [asterisk-users] Disable NO_USER_RESPONSE (Hangupcause = 18) for certain SIP peer

2019-11-16 Thread Sebastian Nielsen
What would be the best way to solve this problem? Anyone else that have got the same problem with Android’s native SIP client, especially on Samsung phones? I do not know if the bug is in Android native SIP, or Samsung’s build of the SIP client, or if the bug is even with the OpenVPN client,

Re: [asterisk-users] Disable NO_USER_RESPONSE (Hangupcause = 18) for certain SIP peer

2019-11-16 Thread Joshua C. Colp
On Sat, Nov 16, 2019 at 7:45 PM Sebastian Nielsen wrote: > Hello. > > I have a problem with the native Android SIP client, not acknowledging the > call. > > > > Sent a message to the list for some weeks ago containing a sip debug log, > but it only got stuck in moderation queue due to too large s

[asterisk-users] Disable NO_USER_RESPONSE (Hangupcause = 18) for certain SIP peer

2019-11-16 Thread Sebastian Nielsen
Hello. I have a problem with the native Android SIP client, not acknowledging the call. Sent a message to the list for some weeks ago containing a sip debug log, but it only got stuck in moderation queue due to too large size (and it said I would get a message if moderators rejected it, but di

Re: [asterisk-users] Asterisk 16.6.1: PJSIP: delayed action of core since update to 16.6.1

2019-11-16 Thread Joshua C. Colp
On Sat, Nov 16, 2019 at 4:07 AM O. Hartmann wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > > Hello, > > we're running a small Asterisk appliance on a PCengine APU2C4. Base > operating system is > FreeBSD 12-STABLE, most recent incarnation as of today. > > Since update of port net/

[asterisk-users] Asterisk 16.6.1: PJSIP: delayed action of core since update to 16.6.1

2019-11-16 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello, we're running a small Asterisk appliance on a PCengine APU2C4. Base operating system is FreeBSD 12-STABLE, most recent incarnation as of today. Since update of port net/asterisk16 to the latest bug fix revision 16.6.1, we face a severe "s