Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

investigate futel.pstn.twilio.com entries in metrics #410

Open
kra opened this issue Nov 23, 2020 · 7 comments
Open

investigate futel.pstn.twilio.com entries in metrics #410

kra opened this issue Nov 23, 2020 · 7 comments

Comments

@kra
Copy link
Collaborator

kra commented Nov 23, 2020

CHANNEL=SIP/futel.pstn.twilio.com-00000190 etc

@kra
Copy link
Collaborator Author

kra commented Nov 23, 2020

karl@dispater:/Downloads$ ls metrics*
metrics-20200831 metrics-20200930 metrics-20201031
karl@dispater:
/Downloads$ grep futel.pstn.twilio.com metrics-* | sed 's/.*name=//' | sort | uniq -c
14 default-incoming
8 incoming-dialstatus-BUSY-opensignal
1 incoming-dialstatus-BUSY-oskar
1 incoming-dialstatus-BUSY-paz
1 incoming-dialstatus-BUSY-taylor
8 ring-opensignal
2 ring-oskar
2 ring-paz
1 ring-robotron
1 ring-taylor

@kra
Copy link
Collaborator Author

kra commented Nov 23, 2020

sip.conf:
; termination for twilio elastic sip
twilio-termination
host=futel.pstn.twilio.com
; to be populated in sip_callcentric.conf
defaultuser=
remotesecret=

@kra
Copy link
Collaborator Author

kra commented Nov 23, 2020

twilio-termination is the outgoing channel for most extensions

@kra kra changed the title grep futel.pstn.twilio.com entries in metrics investigate futel.pstn.twilio.com entries in metrics Nov 23, 2020
@kra
Copy link
Collaborator Author

kra commented Nov 23, 2020

karl@dispater:~/Downloads$ cat metrics-* | sed 's/.CHANNEL=//' | sed 's/-[0-9].//' | sort | uniq -c | sort -n
6 SIP/610
6 SIP/sip.us2.twilio.com
16 SIP/callcentric.com
28 SIP/681
37 SIP/700
39 SIP/515
79 SIP/callcentric
97 SIP/702
153 SIP/500
191 SIP/twilio-termination
193 SIP/199.87.151.75
215 SIP/615
216 SIP/501
220 SIP/199.87.151.78
230 SIP/670
237 SIP/futel.pstn.twilio.com
246 SIP/680
281 SIP/695
455 SIP/640
484 SIP/620
493 SIP/twilio-origination
646 SIP/525
675 SIP/510
987 SIP/685
991 SIP/645
1214 SIP/660
2117 SIP/voipms
2489 SIP/655
4322 SIP/668

@kra
Copy link
Collaborator Author

kra commented Nov 23, 2020

I think these channel attrs are just bogus
probably asterisk is not preserving env vars as a call moves through a context

karl@dispater:/Downloads$ grep CHANNEL=SIP/futel.pstn.twilio.com metrics-* | sed 's/.*name=//' | sort | uniq -c | sort -n
1 incoming-dialstatus-BUSY-hoyt
1 incoming-dialstatus-BUSY-mykle
1 incoming-dialstatus-BUSY-paz
1 ring-hoyt
1 ring-xnor
2 incoming-dialstatus-CHANUNAVAIL-breckenridgest
2 incoming-dialstatus-CHANUNAVAIL-oskar
2 ring-robotron
3 incoming-dialstatus-BUSY-breckenridgest
3 ring-detroitbusco
3 ring-mykle
4 ring-paz
8 incoming-dialstatus-BUSY-opensignal
8 incoming-dialstatus-BUSY-taylor
9 incoming-dialstatus-BUSY-oskar
19 ring-opensignal
21 ring-breckenridgest
21 ring-oskar
26 ring-taylor
101 default-incoming
karl@dispater:
/Downloads$ grep CHANNEL=SIP/twilio-origination metrics-* | sed 's/.*name=//' | sort | uniq -c | sort -n
1 futel-conf
1 incoming-dialstatus-BUSY-mykle
1 incoming-dialstatus-CHANUNAVAIL-breckenridgest
1 incoming-dialstatus-CHANUNAVAIL-hoyt
1 incoming-voicemail
1 message_one_play
1 outgoing-dialstatus-ANSWER-twilio-termination
1 ring-detroitbusco
1 ring-hoyt
1 ring-mykle
1 ring-robotron
1 ring-xnor
1 voicemail-information
1 wildcard-line
1 wildcard-line-play-6
2 hold_the_phone_incoming
2 incoming-dialstatus-BUSY-breckenridgest
2 incoming-dialstatus-BUSY-opensignal
2 missed_connections
2 missed_connections_listen
3 community-incoming
3 incoming-dialstatus-BUSY-paz
3 ring-opensignal
7 ring-souwester
8 ring-paz
9 incoming-ivr
22 ring-jesse
45 ring-breckenridgest
63 incoming-dialstatus-BUSY-oskar
103 ring-oskar
202 default-incoming

@kra
Copy link
Collaborator Author

kra commented Nov 23, 2020

these could all be incoming call events
oh, default-incoming is ok, that is just the context that routes the call to where it should go, it can be ignored and should be superset of all incoming calls

@kra
Copy link
Collaborator Author

kra commented Nov 23, 2020

I think the CHANNEL variable is OK for all outgoing calls in which case it starts with the extension, and partially bogus for all incoming calls, in which case it starts with one of the incoming channels but maybe not the correct one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant