Re: [asterisk-users] Asterisk simply stops call processing

On Wednesday 22 February 2023 at 15:29:38, John Harragin wrote: > If there are multiple connections that the utilize the same driver, try > putting: > > Threading = 2 > > in the appropriate driver section of > /etc/odbcinst.ini I'll give that a go, however I doubt that it is the problem,

Re: [asterisk-users] RTP address learning and timing problem

On Tue, Feb 28, 2023 at 9:50 AM David Cunningham wrote: > Hello, > > Does anyone know if one of the "strictrtp" options disables RTP learning? > As far as I can tell from the documentation the values "no" and "seqno" are > more permissive in allowing other sources rather than less, but I thought

Re: [asterisk-users] 5s delays before executing the dialplan

On Tue, Feb 28, 2023 at 9:48 AM Kingsley Tart wrote: > Hi, > > We've recently hit an issue with Asterisk 18.8.0 where a call comes in > via SIP (using pjsip) but it can take 5 seconds before starting to > execute the dialplan. > > This was intermittent, but frequent (eg approx half of the

[asterisk-users] Ping

My last post did not make it back or to the archive... testing... Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G-Leiter Commerce Kunden __ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln

[asterisk-users] Asterisk PJSIP setting don't fragment bit on UDP

Hi Gang I noticed, that when I enable multiple codecs and rtp encrypting (generating a large SDP) invites with credentials do not get through anymore. So sniffed the connection and found that the IP packets have the don't fragment bit set, causing a VDSL router with 1472 MTU in the path to

Re: [asterisk-users] RTP address learning and timing problem

Hello, Does anyone know if one of the "strictrtp" options disables RTP learning? As far as I can tell from the documentation the values "no" and "seqno" are more permissive in allowing other sources rather than less, but I thought I'd check. Thanks. On Thu, 23 Feb 2023 at 12:13, David

[asterisk-users] 5s delays before executing the dialplan

Hi, We've recently hit an issue with Asterisk 18.8.0 where a call comes in via SIP (using pjsip) but it can take 5 seconds before starting to execute the dialplan. This was intermittent, but frequent (eg approx half of the calls). We have verbose logging on, but I didn't see any errors.

[asterisk-users] RTP address learning and timing problem

Hello, We have a system that interoperates with an external service, so that the basic call flow is: PSTN origination -> Asterisk A -> External service -> Asterisk B Initially the SDP from the external service tells the two Asterisks to send RTP directly to each other. Part way through the call

Re: [asterisk-users] Asterisk simply stops call processing

If there are multiple connections that the utilize the same driver, try putting: Threading = 2 in the appropriate driver section of /etc/odbcinst.ini ...this would be a possibility if the problem is intermittent. Also can you successfully execute the same SQL from the cli? By the way,

Re: [asterisk-users] Changing the contact header

Hi David, I chanced upon your question while I was looking for the same thing myself. I don't know whether this is still relevant to you, given that it's over 2 years ago since you asked the question. There's an option in the global section of pjsip.conf that defaults to "no", but if you set it