On 25/08/20 7:20, Andrew Yager wrote:

On Sun, 23 Aug 2020 at 18:23, Antony Stone <antony.st...@asterisk.open.source.it <mailto:antony.st...@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


    We are zeroing in on something with the SIP trunk provider.  We have are testing a new carrier and so far we have not seen the same problem.

--
Telecomunicaciones Abiertas de México S.A. de C.V.
Carlos Chávez
+52 (55)8116-9161

-- 
_____________________________________________________________________
-- 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

Reply via email to