Hi Tryba
> A (very) dirty workaround would be to drop these packets with iptables
> (assuming Linux as OS), something like:
>
> iptables -t raw -I OUTPUT -p udp -d ipaddrofpbx -m string --algo bm
> --from 0 --to 32 --string "SIP/2.0 100 " -j DROP
>
> Don't try it with TCP :)
:-)
Indeed, this i
On Mon, Mar 19, 2018 at 12:59:47PM -0300, Joshua Colp wrote:
> > To try to reproduce the problem with our SBC, is there a way to tell
> > the asterisk, preferably PJSIP, to directly answer with 180 ringing
> > without prior 100 trying?
>
> The PJSIP channel driver has no option or ability to do th
On Mon, Mar 19, 2018, at 12:53 PM, Benoit Panizzon wrote:
> Hey List
>
> I sometimes use our asterisk server to do some debugging or other PBX
> and SBC.
>
> Now we have a case where a PBX is replying an incomming invite with 180
> ringing immediately. It looks like the SBC does not accept this.
Hey List
I sometimes use our asterisk server to do some debugging or other PBX
and SBC.
Now we have a case where a PBX is replying an incomming invite with 180
ringing immediately. It looks like the SBC does not accept this.
According to my understanding of the RFC 3261 any provisional (aka
1XX)
