Asterisk Manager Gives Event PeerStatus: Unregistered Cause: Expired

Home » Asterisk Users » Asterisk Manager Gives Event PeerStatus: Unregistered Cause: Expired
Asterisk Users 7 Comments

Hello

I see the following event from the Asterisk Manager :

2021-06-30 11:20:55
Array
(
    [0] => Event: PeerStatus
    [1] => Privilege: system,all
    [2] => SystemName: tstv7
    [3] => ChannelType: SIP
    [4] => Peer: SIP/testacc7700921
    [5] => PeerStatus: Unregistered
    [6] => Cause: Expired
)

But I see no SIP REGISTER with SIP-header Expires:0 (so an UNregister if you like) in my SIP debug.

What I do see is a SIP OPTION, following a SIP 200 OK (so this is the qualify frequenty) at 11:20:45

[Jun 30 11:20:45] VERBOSE[1581] chan_sip.c: Reliably Transmitting (NAT)
to my.lo.cal.ip:55014:
OPTIONS sip:testacc7700921@192.168.1.9:5060 SIP/2.0
Via: SIP/2.0/UDP my.aste.risk.ip:5060;branch=z9hG4bK357689ec;rport Max-Forwards: 70
From: “asterisk” ;tag=as0da9cbe1
To:
Contact:
Call-ID: 0b8c7f5745051ae73193231f5a487b11@my.aste.risk.ip:5060
CSeq: 102 OPTIONS
User-Agent: TSTv7
Date: Wed, 30 Jun 2021 09:20:45 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer Content-Length: 0

–

7 thoughts on - Asterisk Manager Gives Event PeerStatus: Unregistered Cause: Expired

  • The cause is in this message, the registration expired. A re-registration did not occur before the registration expiration so it expired and was unregistered.

  • 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 ??

    Op 30-06-21 om 20:32 schreef Joshua C. Colp:

  • Without the actual SIP REGISTER traffic to show how long the registration was for, I can’t really say anything further.

  • 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: ;tag630891428
    To:
    Call-ID: 3270725701@192_168_1_18
    CSeq: 452 REGISTER
    Contact:
    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:

  • 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.

  • Hello Joshua

    could it be a bug ?

    I am using asterisk-certified-13.21-cert6

    Kind regards.

    J.

    Op 01-07-21 om 20:20 schreef Joshua C. Colp:

  • There’s been no other reports of issues, but it could be. The 13 branch, however, only receives bug fixes. Additionally the chan_sip module is community supported meaning if there is a bug then there is no timeframe on when it would get looked at, or if it would. You’d also have to provide a complete SIP trace and debug log.