Hello, provider responded the behavior is intentional from their side. So this should be fixed in asterisk. The pjsip cleanly does not do any unregistrations where it should.
Marek 2020-06-07 12:30 GMT+02:00, Marek Greško <mgres...@gmail.com>: > Hello, > > I found the problem and also the workaround. > > Clearly, since it was working with chan_sip it should not be dialplan > problem, but sip stack problem. > > I have line=yes set up. After asterisk restart the old registration is > not unregistered and new one is registered with different line value. > Then incoming invites and qualify requests are sent to all the > registrations and there the problem lies. > > I am thinking of how could asterisk prevent such situations. > > 1. I think it should send unregistration requests on shutdown. > > 2. I think it should keep the database of active registrations and > unregister and reregister all of them during startup in case some of > them remain active after unclean shutdown. > > Also probably provider side should be fixed? > > Thanks for your insight. > > Marek > > > 2020-06-05 19:29 GMT+02:00, Doug Lytle <supp...@drdos.info>: >> On 6/5/20 12:24 PM, Marek Greško wrote: >>> How can this behavior been overriden? I do not expect this is problem >>> on provider side, since it was working normally using chan_sip. >> >> Console output and dial plan snippets are always useful when diagnosing, >> >> Doug >> >> > -- _____________________________________________________________________ -- 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
