On Sun, Dec 3, 2017, at 10:55 AM, [email protected] wrote: > If understand correctly type=identify is more for sip trunk > configuration ? > > > ;[mytrunk] > ;type=identify > ;endpoint=mytrunk > ;match=198.51.100.1 > ;match=198.51.100.2 > > > In chan_sip it was just reply 200 OK on keepalive packet without need > define trunks. > >
All incoming traffic into chan_pjsip is matched to an endpoint, this includes OPTIONS. The OPTIONS request is also treated as if it were an INVITE per the RFC, which is why the extension also has to exist. -- Joshua Colp Digium, Inc. | Senior Software Developer 445 Jan Davis Drive NW - Huntsville, AL 35806 - US Check us out at: www.digium.com & www.asterisk.org -- _____________________________________________________________________ -- 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
