Strange, A BYE should be replied with 200 OK, 481 (non matching dialogid), 408 request time out or similar responses, but it should never be challenged. Only INVITE, REGISTER and PUBLISH requests are challenged with 401/407. As per rfc3261 it should not challenge the BYE Requests. *The workaround is to add a SIP Proxy(opensips/kamillio) in between your Provider and Asterisk server and manipulate the BYE message with challenge.
Regards, Muhammad Faheem On Thu, Jun 23, 2016 at 12:19 AM, Owais Ahmad <millennium....@gmail.com> wrote: > Hi all, > > My provider proxy expects authentication header on BYE packets as well. Is > there a way in asterisk to add this header on BYE packets? > > When proxy replies with a 401 on BYE, asterisk just retransmits the BYE > packet. > > Regards, > Owais > > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > New to Asterisk? Join us for a live introductory webinar every Thurs: > http://www.asterisk.org/hello > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users