On Thu, Jul 1, 2021 at 3:15 PM Jonas Kellens <jonas.kell...@telenet.be> wrote:
> Hello Joshua > > this is the SIP REGISTER at 11:10:45 > > REGISTER sip:tstv7.domain.tld SIP/2.0 > Via: SIP/2.0/UDP 192.168.1.18:5060 > ;branch=z9hG4bKcfd4c09d669ce595351ea3b2aba3e245;rport > From: <sip:testacc7700...@tstv7.domain.tld> > <sip:testacc7700...@tstv7.domain.tld>;tag=3630891428 > To: <sip:testacc7700...@tstv7.domain.tld> > <sip:testacc7700...@tstv7.domain.tld> > Call-ID: 3270725701@192_168_1_18 > CSeq: 452 REGISTER > Contact: <sip:testacc7700105@192.168.1.18:5060> > <sip:testacc7700105@192.168.1.18:5060> > Authorization: Digest username="testacc7700105", realm="tstv7.domain.tld", > algorithm=MD5, uri="sip:tstv7.domain.tld", nonce="42a70292", > response="e2945dacd2d95b47a4801b2471070702" > Max-Forwards: 70 > User-Agent: C610 IP/42.075.00.000.000 > Expires: 180 > Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, INFO, REFER, SUBSCRIBE, NOTIFY > Content-Length: 0 > > I see here "180". > > > I also see in the SIP debug traffic that a SIP REGISTER occurs every 180 > seconds, which is what is set in the SIP client. > > > This "Expired" notice occured only once at 11:20:55. How come this happens > only once ? > > And why should there *ever* be an "Expired" if there is a SIP REGISTER > every 180 seconds ?! > If what you are saying is correct, then I do not know. The chan_sip module decided that it should be expired. Why that is, I do not know. -- Joshua C. Colp Asterisk Technical Lead Sangoma Technologies Check us out at www.sangoma.com and 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
