I had a similiar problem, but with calls dropping after 30 sec. It turned out that Android didn't support RP-CID (Reverse Party Caller ID) so when I sent the name of the callee to the caller (as some sort of "centralized phonebook function") it caused calls to be dropped as android refused to reply on the packets or sent rejections back. Check if you have some equipment on the line which doesn't support a specific function, and configure the equipment to use a separate SIP account with these features turned off. I first tought it would just ignore unsupported features, but it turned out it outright rejects packets with unsupported features. Best regards, Sebastian Nielsen -----Ursprungligt meddelande----- Från: asterisk-users-bounces at lists.digium.com <asterisk-users-bounces at lists.digium.com> För C.Maj Skickat: den 22 augusti 2020 20:03 Till: asterisk-users at lists.digium.com Ämne: Re: [asterisk-users] Channels freeze on Confbridge On 2020-08-18 13:00, Carlos Chavez wrote:> users complain that confbridge calls end after about 30 minutes or soYou might want to turn up SIP debug logging -- could be a re-INVITE is getting dropped, NAT pin-hole is closing, or some other network issue. -- 🤠 C. Maj, Technology Captain @ Penguin PBX Solutions 📞 USA Toll Free 1-833-PNGNPBX (1-833-764-6729) 🤙 International & SMS Texting +1.720.32.42.72.9 🐧 Visit on the World Wide Web at PENGUINPBX.COM -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- Check out the new Asterisk community forum at: https://community.asterisk.org/ New to Asterisk? Start here: https://wiki.asterisk.org/wiki/display/AST/Getting+Started asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5249 bytes Desc: S/MIME Cryptographic Signature URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20200822/6b44cd13/attachment.bin>
On Saturday 22 August 2020 at 22:51:48, Sebastian Nielsen wrote:> I had a similiar problem, but with calls dropping after 30 sec. > It turned out that Android didn't support RP-CID (Reverse Party Caller ID) > so when I sent the name of the callee to the caller (as some sort of > "centralized phonebook function") it caused calls to be dropped as android > refused to reply on the packets or sent rejections back.I can see the point you're making here, but what's going to do this after 30 *minutes* of normal call?> Check if you have some equipment on the line which doesn't support a > specific function, and configure the equipment to use a separate SIP > account with these features turned off. > > I first tought it would just ignore unsupported features, but it turned out > it outright rejects packets with unsupported features.Antony. -- Atheism is a non-prophet-making organisation. Please reply to the list; please *don't* CC me.
>>I can see the point you're making here, but what's going to do this after 30*minutes* of normal call? I was more into, if there is some feature that somehow triggers after 30 minutes of call - and this feature is unsupported on some client, which causes it to drop the call. For example, if you are trying to send some call cost notification for long calls out of band or similiar, and some devices doesn't support this feature. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5249 bytes Desc: S/MIME Cryptographic Signature URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20200823/a2ec7279/attachment.bin>
On Sun, 23 Aug 2020 at 18:23, Antony Stone < Antony.Stone at asterisk.open.source.it> wrote:> On Saturday 22 August 2020 at 22:51:48, Sebastian Nielsen wrote: > > > I had a similiar problem, but with calls dropping after 30 sec. > > It turned out that Android didn't support RP-CID (Reverse Party Caller > ID) > > so when I sent the name of the callee to the caller (as some sort of > > "centralized phonebook function") it caused calls to be dropped as > android > > refused to reply on the packets or sent rejections back. > > I can see the point you're making here, but what's going to do this after > 30 > *minutes* of normal call? >Have seen plenty of ALGs do weird things like this. 30 minutes is a nice number, and nice enough that I'd go hunting for ALG issues. It's a good multiple of 3 minutes, and quite possibly is some big number someone thought to set in something that "no one would ever hit". A tcpdump would probably show you what's going on if the logs are otherwise unclear, and you could also make sure you have sensible RTP timeout rules. Andrew -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20200825/d34371b1/attachment.html>