Summary:ASTERISK-17234: Asterisk "new" sip peers status.
Reporter:Alejandro Donato (coyote)Labels:
Date Opened:2011-01-12 14:41:03.000-0600Date Closed:2017-10-11 11:41:48
Versions:Frequency of
Description:Updating from 1.6 to 1.8 branch noticed that sip peer status report is slightly different causing to, ie FreePBX and Flash Operator Panel to fail to determine extension status.

Dynamic peers previous state when not registered was "Unregistered", now, in 1.8 changed to "UNKNOWN". Even static channels change to "UNREACHABLE" status, so, panels to control peers status which works in 1.6 branch stop working on 1.8 branch.


example of 2 dynamic peers in 1.8

06        (Unspecified)                            D   N   A  0        UNKNOWN    
07        (Unspecified)                            D   N   A  0        UNKNOWN    

example of 2 static peers
11                             A  5060     UNREACHABLE
12                             A  5060     UNREACHABLE
Comments:By: Paul Belanger (pabelanger) 2011-01-13 01:12:50.000-0600

We require a complete debug log to help triage the issue.

This document will provide instructions on how to collect debugging logs from an Asterisk machine for the purpose of helping bug marshals troubleshoot an issue:


By: Leif Madsen (lmadsen) 2011-01-13 11:11:49.000-0600

UNKNOWN means the device state status could not be found. This is not an alternative message to the Unreachable message previous.

By: Alejandro Donato (coyote) 2011-01-14 01:56:35.000-0600

Thx both for the answers.

This particular issue i don't know if can be considered a bug, but for sure breaks backwards compatibility with 1.6 branch.

The difference between status reports in both branchs (ie. UNREACHABLE vs Unreachable) make any software that "pharse" this text to know peers status (like Flash Operator Panel or FreePBX do) confuse. Question is.. is this change intentional?

By: Massimo MUCCI (furinfo) 2011-08-24 04:53:14.531-0500

I'm seeing the same behaviour on the Lynksys SPA932 sidecar.
After updating Asterisk from 1.6.X to 1.8.X I actually have the same signaling of the FOP, i.e. the unregistered Extensions all show as connected.

By: Corey Farrell (coreyfarrell) 2017-10-11 11:41:48.630-0500

I believe this change was made for ASTERISK-4694.  Breaking changes happen between major releases, from what I can tell this is not a bug.