Feature Request: Incorporate Sip Show Peers functionality.

[GoogleCodeExporter]

Replicate the sip show peers functionality from asterisk. Sip show peers is a 
command in the asterisk CLI which reports back all of the extensions on the 
system, whether they are registered, and the ping time of each of the 
registered end points. The ports the extension is using are also included in 
the list. 

Original issue reported on code.google.com by i...@terraenetworks.com on 3 Dec 2014 at 4:13

[GoogleCodeExporter]

Status - Registrations page has all this information

Original comment by Sergey.M...@gmail.com on 6 Jan 2015 at 1:36

[GoogleCodeExporter]

Hello,

The registrations page has a lot of useful information, Whether and what is
registered, how it is registered (tcp,udp, auto-nat), I don't know why the
IP never seems to reflect my Public IP, but thats there too. What isn't
there, is the ping to each endpoint. This is useful to know if there are
issues with call quality, transmission, pdd, etc, is whether those issues
are related to network issues on the client side.

If a client has a ping of 300+ MS, well, no wonder the calls are failing.
We can easily make a diagnosis that rules out things quickly.

Also, In sip show peers, all the extensions are shown and whether they are
registered or not. It is arranged by extension number as well so its a
little cleaner.

On a multi-tenant system, FusionPBX displays by extension too, across all
domains so there's no order. If I have 7 ext. 100, I see those first, then
101 etc. Looks cluttered. Might be a separate feature request, and I might
have already made it, but I would like to be able to arrange those
registrations by domain, but see all domains and extension on one page.

Original comment by i...@terraenetworks.com on 6 Jan 2015 at 1:48

[GoogleCodeExporter]

that page doesn't show ping time.

Original comment by blackc2004@gmail.com on 6 Jan 2015 at 1:49

[GoogleCodeExporter]

Thought it is a handy feature to have, it does come at a cost. It seems that 
this would be achieved with sip options packets and so there would be some 
extra load involved.

With regard to the public IP not being displayed, I believe that means that NAT 
is having to be handled server side and it is likely you are sending a local IP 
in the contact.

Original comment by Digitald...@gmail.com on 6 Jan 2015 at 1:59

[GoogleCodeExporter]

While I am sure there's a great deal of work involved, is it something that
could be introduced and made an option. Perhaps just while troubleshooting
calling issues. Or a one shot kind of command - what makes this important
is that a regular ping wont navigate sip.

Original comment by i...@terraenetworks.com on 6 Jan 2015 at 2:08

[GoogleCodeExporter]

This is an enhancement, not a defect.

Original comment by Digitald...@gmail.com on 16 Jan 2015 at 8:18

• Added labels: Type-Enhancement