Jonas Kellens
2021-Jul-01 18:15 UTC
[asterisk-users] Asterisk Manager gives event PeerStatus: Unregistered Cause: Expired
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:testacc7700105 at tstv7.domain.tld>;tag=3630891428 To: <sip:testacc7700105 at tstv7.domain.tld> Call-ID: 3270725701 at 192_168_1_18 CSeq: 452 REGISTER Contact: <sip:testacc7700105 at 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 ?! Kind regards. Op 01-07-21 om 17:41 schreef Joshua C. Colp:> On Thu, Jul 1, 2021 at 12:34 PM Jonas Kellens > <jonas.kellens at telenet.be <mailto:jonas.kellens at telenet.be>> wrote: > > Hello Joshua > > > these are the 2 previous events on the Manager interface : > > 2021-06-30 11:10:45 > Array > ( > [0] => Event: PeerStatus > [1] => Privilege: system,all > [2] => SystemName: tstv7 > [3] => ChannelType: SIP > [4] => Peer: SIP/testacc7700921 > [5] => PeerStatus: Registered > [6] => Address: my.lo.cal.ip:55014 > ) > > > > 2021-06-30 11:10:48 > Array > ( > [0] => Event: PeerStatus > [1] => Privilege: system,all > [2] => SystemName: tstv7 > [3] => ChannelType: SIP > [4] => Peer: SIP/testacc7700921 > [5] => PeerStatus: Reachable > [6] => > ) > > > So there is a re-register at 11:10:45 > > > How do you explain the "Expired" 10 minutes later ?? > > > Without the actual SIP REGISTER traffic to show how long the > registration was for, I can't really say anything further. > > -- > Joshua C. Colp > Asterisk Technical Lead > Sangoma Technologies > Check us out at www.sangoma.com <http://www.sangoma.com> and > www.asterisk.org <http://www.asterisk.org>-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20210701/fdb8f686/attachment.html>
Joshua C. Colp
2021-Jul-01 18:20 UTC
[asterisk-users] Asterisk Manager gives event PeerStatus: Unregistered Cause: Expired
On Thu, Jul 1, 2021 at 3:15 PM Jonas Kellens <jonas.kellens at 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:testacc7700105 at tstv7.domain.tld> > <sip:testacc7700105 at tstv7.domain.tld>;tag=3630891428 > To: <sip:testacc7700105 at tstv7.domain.tld> > <sip:testacc7700105 at tstv7.domain.tld> > Call-ID: 3270725701 at 192_168_1_18 > CSeq: 452 REGISTER > Contact: <sip:testacc7700105 at 192.168.1.18:5060> > <sip:testacc7700105 at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20210701/c9c545d3/attachment.html>