The answer is chan_pjsip. You can do this with chan_pjsip. There’s no real
support for chan_sip anymore. It’s dead, it’s going away. No fixes or updates
will be accepted against it as of this point.
From: asterisk-users on behalf of
Dovid Bender
Reply-To: Asterisk Users Mailing List -
Moving to chan_pjsip solves this problem.
From: asterisk-users on behalf of
David Cunningham
Reply-To: Asterisk Users Mailing List - Non-Commercial Discussion
Date: Sunday, July 17, 2022 at 5:53 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users]
The answer is to use chan_pjsip since chan_sip is all but dead, unsupported and
going away in v21. Instead of making chan_sip listen on all IPs then making a
bunch of firewall/filtering rules that block one of them from being used, use
chan_pjsip. It is the right solution as it is the supported
From: asterisk-users on behalf of
"Joshua C. Colp"
Reply-To: Asterisk Users Mailing List - Non-Commercial Discussion
Date: Wednesday, September 7, 2022 at 10:23 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] Channel names with semicolons
From https://wiki.asterisk.org/wiki/display/AST/Channels
"The primary exception is with Local Channels. In the case of local channels,
you'll typically have two local channel legs, one that is treated as outbound
and the other as inbound. In this case both are really inside Asterisk, but one
On 2022-10-14, 11:31 AM, "asterisk-users on behalf of marek"
wrote:
hi,
we are migrating from chan_sip to pjsip
i want logs like this about pjsip endpoints
[Oct 14 17:20:36] NOTICE[35629] chan_sip.c: Peer 'endpoint22' is now
Reachable. (15ms / 2000ms)
is it
