Phone goes from IDLE to UNAVAILABLE

FreePBX Endpoints
1

I can’t seem to figure out how one of my phones (extension 100) keeps going from IDLE to UNAVAILABLE. It’s only doing it on one phone - but there’s nothing to indicate why it’s go to UNAVAILABLE.

I only have 7 other extensions, as you’ll see. The xx.xx.xx.xx is the external IP of the firewall that all of the phones are behind.

[2022-02-21 01:12:29] VERBOSE[3438] chan_sip.c: Registered SIP ‘100’ at xx.xx.xx.xx:56848
26164 [2022-02-21 01:12:29] VERBOSE[3219] chan_sip.c: Extension Changed 100[ext-local] new state Idle for Notify User 101
26165 [2022-02-21 01:12:29] VERBOSE[3219] chan_sip.c: Extension Changed 100[ext-local] new state Idle for Notify User 104
26166 [2022-02-21 01:12:29] VERBOSE[3219] chan_sip.c: Extension Changed 100[ext-local] new state Idle for Notify User 108
26167 [2022-02-21 01:12:29] VERBOSE[3219] chan_sip.c: Extension Changed 100[ext-local] new state Idle for Notify User 106
26168 [2022-02-21 01:12:29] VERBOSE[3219] chan_sip.c: Extension Changed 100[ext-local] new state Idle for Notify User 103
26169 [2022-02-21 01:12:29] VERBOSE[3219] chan_sip.c: Extension Changed 100[ext-local] new state Idle for Notify User 107
26170 [2022-02-21 01:12:29] VERBOSE[3219] chan_sip.c: Extension Changed 100[ext-local] new state Idle for Notify User 105
26171 [2022-02-21 01:12:29] VERBOSE[3219] chan_sip.c: Extension Changed 100[ext-local] new state Idle for Notify User 102
26172 [2022-02-21 01:15:39] VERBOSE[3219] chan_sip.c: Extension Changed 100[ext-local] new state Unavailable for Notify User 101
26173 [2022-02-21 01:15:39] VERBOSE[3219] chan_sip.c: Extension Changed 100[ext-local] new state Unavailable for Notify User 104
26174 [2022-02-21 01:15:39] VERBOSE[3219] chan_sip.c: Extension Changed 100[ext-local] new state Unavailable for Notify User 108
26175 [2022-02-21 01:15:39] VERBOSE[3219] chan_sip.c: Extension Changed 100[ext-local] new state Unavailable for Notify User 106
26176 [2022-02-21 01:15:39] VERBOSE[3219] chan_sip.c: Extension Changed 100[ext-local] new state Unavailable for Notify User 103
26177 [2022-02-21 01:15:39] VERBOSE[3219] chan_sip.c: Extension Changed 100[ext-local] new state Unavailable for Notify User 107
26178 [2022-02-21 01:15:39] VERBOSE[3219] chan_sip.c: Extension Changed 100[ext-local] new state Unavailable for Notify User 105
26179 [2022-02-21 01:15:39] VERBOSE[3219] chan_sip.c: Extension Changed 100[ext-local] new state Unavailable for Notify User 102
26180 [2022-02-21 01:15:42] VERBOSE[3438] chan_sip.c: Registered SIP ‘100’ at xx.xx.xx.xx:56848
26181 [2022-02-21 01:15:42] VERBOSE[3219] chan_sip.c: Extension Changed 100[ext-local] new state Idle for Notify User 101
26182 [2022-02-21 01:15:42] VERBOSE[3219] chan_sip.c: Extension Changed 100[ext-local] new state Idle for Notify User 104
26183 [2022-02-21 01:15:42] VERBOSE[3219] chan_sip.c: Extension Changed 100[ext-local] new state Idle for Notify User 108
26184 [2022-02-21 01:15:42] VERBOSE[3219] chan_sip.c: Extension Changed 100[ext-local] new state Idle for Notify User 106
26185 [2022-02-21 01:15:42] VERBOSE[3219] chan_sip.c: Extension Changed 100[ext-local] new state Idle for Notify User 103
26186 [2022-02-21 01:15:42] VERBOSE[3219] chan_sip.c: Extension Changed 100[ext-local] new state Idle for Notify User 107
26187 [2022-02-21 01:15:42] VERBOSE[3219] chan_sip.c: Extension Changed 100[ext-local] new state Idle for Notify User 105
26188 [2022-02-21 01:15:42] VERBOSE[3219] chan_sip.c: Extension Changed 100[ext-local] new state Idle for Notify User 102

SIDE NOTE -
Periodically, I get this message (or similar - but always with the STATIC IP of extension 100):
WARNING[3438] chan_sip.c: Retransmission timeout reached on transmission [email protected] for seqno 103 (Critical Request)

2

Both of these indicate an unreliable network that is either losing large numbers of packets, or delaying them by large amounts of time. If the whole network path is within your control, you might be able to mitigate this by implementing differentiated service code points (DSCP) in the routers, phones, and Asterisk, to prioritise SIP traffic

1 Like
3

What I don’t understand is that it’s only with this ONE phone. They’re all on the same network.

4

A network should be able to manage the QoS for any RTP protocol using diffserv=46 value.
The SIP protocol has a QoS too. (Diffserv=43) if I recall correctly.
Without a good QoS, you can get some problems.

Also, Maybe your network has a loop somewere and if your network doesn’t manage the Spanning Tree, your can get a big problem in the part of network or entire network.

Also, check your system, if the CPU load is normal.

5

It seems to be managing QoS fine with all of the other phones - it’s just this one extension. CPU load appears minimal - we only have 9 phones. I remembered that the problem phone is a Yealink - all of our others are Panasonic. Possibly there are settings there that aren’t correct?

6

If it’s only for a specific extension, then if you’ve got the chance to use EPM, removes the phone and release the extension.
Don’t forget to update EPM before too. (Do fwconsole ma updateall)
Next, scan the network again. and assign the phone to the extension.
Go to the firmware menu, and select the last one in the slot 1.
Update you phone and check again.
With the latest firmware and everything uodated, we can imagine to have a good setting for this phone and eliminate everything about bugs side the firmware and EPM I guess.

7

Default trephine and manually add only the SIP credentials in the phone’s web interface.

If the problem go aways, then it was something in the phone config. If not, then it is your network or the phone itself is bad. Did you buy the phone new? I have never had this type of problem with the hundreds of Yealinks I have deployed.

Yealink phones do not have any issues like this by default.

8

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.