[Spce-user] Counting concurrent calls on a peering

[Matthias Hohl]

One last question:

 

How can i found out the other PEER IDs of currently inactive peers?

Then i can build a script for validation my peering call limits.

 

Thanks

 

Von: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] Im Auftrag von Matthias Hohl
Gesendet: Freitag, 28. April 2017 13:47
An: 'Barry Flanagan' <barry at flanagan.ie>
Cc: Spce-user at lists.sipwise.com
Betreff: Re: [Spce-user] Counting concurrent calls on a peering

 

Hello,

 

thanks for info…

 

so first command is:

 

# redis-cli -h 127.0.0.1  -n 3

 

Then i check the peer ID with 

 

# keys peer*

 

And then i use the number of the number oft he peer and check the concurrent calls on this peer right? In my example peer:15

 

# get peer:15

 

The result ist he concurrent calls value.

 

 

So a faster way would be then:    

 

# redis-cli -h 127.0.0.1 -n 3 get peer:15

 

And i get back the current number.

 

 

Thats right?

 

 

Von: Barry Flanagan [mailto:barry at flanagan.ie] 
Gesendet: Freitag, 28. April 2017 13:31
An: Matthias Hohl <matthias.hohl at telematica.at <mailto:matthias.hohl at telematica.at> >
Cc: Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com> 
Betreff: Re: [Spce-user] Counting concurrent calls on a peering

 

On 28 April 2017 at 12:19, Matthias Hohl <matthias.hohl at telematica.at <mailto:matthias.hohl at telematica.at> > wrote:

Hello,

 

i want to count my „concurrent_max“ on a specific peering server.

How can i do this?

 

Currently i can do it with:

# ngcp-kamctl proxy fifo get_statistics :dialog::active_dialogs

 

But this is for all active dialogs on the server, so also local onces.

But i just want to check against my peering server. All incoming and outcoming calls, also this one, which are not already an active dialog.

 

 Hi

 

We get this directly from redis - fast and cheap.

 

Example:

 

redis-cli -h 127.0.0.1  -n 3

127.0.0.1:6379[3]>  keys peer*

 1) "peerout:95"

 2) "peer:34"

 3) "peer:32"

 4) "peerout:34"

 5) "peerout:11"

 6) "peer:93"

 7) "peer:87"

 8) "peer:77"

 9) "peer:11"

10) "peerout:32"

11) "peerout:93"

12) "peer:97"

13) "peer:85"

14) "peer:95"

192.168.255.251:6379[3]> get peer:93

"68"

192.168.255.251:6379[3]> 

 

 

Hope this helps.

 

-Barry Flanagan

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20170428/2b79e717/attachment-0001.html>