File: linkedid_check.py

package info (click to toggle)
asterisk-testsuite 0.0.0%2Bsvn.5781-2
  • links: PTS, VCS
  • area: main
  • in suites: jessie, jessie-kfreebsd, stretch
  • size: 18,632 kB
  • sloc: xml: 33,912; python: 32,904; ansic: 1,599; sh: 395; makefile: 170; sql: 17
file content (278 lines) | stat: -rw-r--r-- 10,768 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
#!/usr/bin/env python
""" Asterisk TestSuite LinkedId Propagation Test

Copyright (C) 2014, Digium, Inc.
Scott Griepentrog <sgriepentrog@digium.com>

This program is free software, distributed under the terms
of the GNU General Public License Version 2.


This monitors bridge enter/exit and CEL events, and builds
a picture of which channels are bridged together, and when
their LinkedID changes, and then verifies that each change
is correct.

Note: The BridgeEnter and CEL 'BRIDGE_ENTER' events can be
in either order - so wait for both to arrive before making
a judgement on the LinkedID.

This test can be added to any other bridging test to add a
layer of LinkedId Propagation checking to it.  However the
creation of channels has to be done one at a time by using
a Newchannel event to trigger the next one - so that order
of creation can be determined.  Also required is that this
test module is listed before others to that it can process
bridge events first before the test makes changes.

"""

import logging

LOGGER = logging.getLogger(__name__)


class LinkedIdChannel(object):
    def __init__(self, uniqueid, order, test):
        """ This initializes the LinkedID Channel object

        Keyword Arguments:
        uniqueid    - channel unique id
        order       - creation order
        test        - the test_object used to set failure indication
        """
        self.order = order              # creation order for age test
        self.uniqueid = uniqueid        # uniqueid for channel
        self.linkedid = False           # what linkedid should be
        self.cel_linkedid = False       # linkedid from last CEL event
        self.failed = False             # squelch repeated errors
        self.test = test                # copy of test object (to set fail)

        LOGGER.info('New channel %s created order #%d' %
                    (uniqueid, self.order))

    def event(self, event):
        """ This handles a channel event

        Keyword Arguments:
        event       - key value pairs in dict from AMI CEL event
        """
        uniqueid = event['uniqueid']
        linked = event['linkedid']

        if self.cel_linkedid != linked:
            previous = self.cel_linkedid
            self.cel_linkedid = linked
            LOGGER.info('%s changed LinkedID %s to %s after CEL %s' %
                        (uniqueid, previous, linked, event['eventname']))

            # this could be a CEL BRIDGE_ENTER showing up before the
            # BridgeEnter, so don't evaluate what it should be here
            # as it will caught on the next CEL event if wrong
            return

        # check that this CEL event has the correct LinkedId
        if self.cel_linkedid != self.linkedid and not self.failed:
            LOGGER.info('%s has LinkedID %s after CEL %s ' %
                        (uniqueid, self.cel_linkedid, event['eventname']))

            """ This is not currently considered an error but should be!

            If the first channel that entered the bridge has it's linkedid
            changed when the second channel enters, there is not another CEL
            event divulging the new linkedid, and it can be an old linkedid
            pulled from the stasis cache when the next event occurs on this
            channel.

            TODO: change this to error and set failure when Asterisk fixed
            """
            LOGGER.warning('LinkedID Propagation error:  ' +
                           'Last CEL on %s has %s should be %s' %
                           (uniqueid, self.cel_linkedid, self.linkedid))

            self.failed = True
            #self.test.set_passed(False)

    def getvar_callback(self, result):
        LOGGER.info('AMI query indicates channel %s has linkedid %s' %
                    (self.uniqueid, result))

        if self.linkedid != result:
            LOGGER.error('LinkedID Propagation error:  ' +
                         'Channel %s has %s should be %s' %
                         (self.uniqueid, result, self.linkedid))
            self.test.set_passed(False)

    def getvar_failback(self, reason):
        LOGGER.error('Failed to getvar linkedid for channel %s: %s' %
                     (self.uniqueid, reason))

    def query_linkedid(self, ami):
        """ query the channel to get the current linkedid

        Keyword Arguments:
        ami     - The ami manager object
        """
        ami.getVar(self.uniqueid, 'CHANNEL(linkedid)'
                   ).addCallbacks(self.getvar_callback, self.getvar_failback)


class LinkedIdCheck(object):
    def __init__(self, module_config, test_object):
        """ This initializes the LinkedId Check test object.

        Keyword Arguments:
        module_config  - configuration section (not used)
        test_object    - the TestCase object running the test
        """
        # ask AMI to let us hook in for events
        test_object.register_ami_observer(self.ami_connect)
        # keep a ref to test_object so we can set failure
        self.test_object = test_object

        #  initialize variables used in this class
        self.channels = {}          # channel objects
        self.bridges = {}           # bridge num for readable logs
        self.chan_bridge = {}       # what bridgeid is chan in or False

    def ami_connect(self, ami):
        """ register with StarPy AMI manager to get events

        This registers with the StarPY AMI manager to get
        the events we are interested in.

        Keyword Arguments:
        ami    - The AMI manager object
        """
        ami.registerEvent('Newchannel', self.new_channel)
        ami.registerEvent('CEL', self.channel_event)
        ami.registerEvent('BridgeEnter', self.bridge_enter)
        ami.registerEvent('BridgeLeave', self.bridge_leave)

    def new_channel(self, ami, event):
        """ handle new channel events to get correct order

        It is possible for CEL CHAN_START events to arrive in
        the wrong order, which throws off age calculations.
        It is also possible for the New Channel event to be
        later than the CEL CHAN_START, so handle creation on
        either.

        Keyword Arguments:
        ami     - The AMI manager object
        event   - The event key/value pairs in a dict
        """
        uniqueid = event['uniqueid']
        if uniqueid not in self.channels.keys():
            new_chan = LinkedIdChannel(uniqueid,
                                       len(self.channels) + 1,
                                       self.test_object)
            self.channels[uniqueid] = new_chan
            self.chan_bridge[uniqueid] = False

    def channel_event(self, ami, event):
        """ handle channel events to get channel's LinkedID

        This handles Channel Event Logger events, which
        are monitored because they contain the LinkedID
        associated with the channel

        Keyword Arguments
        ami    - The AMI manager object
        event  - The event key/value pairs in a dict
        """

        # insure the channel object is created for a new uniqueid
        uniqueid = event['uniqueid']
        linkedid = event['linkedid']
        if not uniqueid in self.channels.keys():
            new_chan = LinkedIdChannel(uniqueid,
                                       len(self.channels) + 1,
                                       self.test_object)
            self.channels[uniqueid] = new_chan
            self.chan_bridge[uniqueid] = False

        # insure starting linkedid is updated
        if not self.channels[uniqueid].linkedid:
            self.channels[uniqueid].linkedid = linkedid
            self.channels[uniqueid].cel_linkedid = linkedid
            LOGGER.info('%s has LinkedID %s at %s ' %
                        (uniqueid, event['linkedid'], event['eventname']))

        # pass event to the channel
        self.channels[uniqueid].event(event)

    def bridge_enter(self, ami, event):
        """ handle bridge enter events, track bridged channels

        This handles Bridge Enter events, used to track
        which channels are in which bridges together.

        Keyword Arguments
        ami    - The AMI manager object
        event  - The event key/value pairs in a dict
        """
        uniqueid = event['uniqueid']
        bridgeid = event['bridgeuniqueid']

        # uniqueid bridges numerically in logs for better readability
        if bridgeid not in self.bridges.keys():
            self.bridges[bridgeid] = len(self.bridges) + 1

        # list of channels in this bridge
        bridged_with = [uid for uid in self.chan_bridge.keys()
                        if self.chan_bridge[uid] == bridgeid]

        LOGGER.info('%s entered bridge #%d with %s' %
                    (uniqueid, self.bridges[bridgeid], bridged_with))

        # mark this channel in the bridge
        self.chan_bridge[uniqueid] = bridgeid

        # if alone in the bridge, skip the checks
        if not bridged_with:
            return

        # determine the correct linkedid for chans in this bridge
        bridged_with.append(uniqueid)
        oldest = False
        for uid in bridged_with:
            linkedid = self.channels[uid].linkedid
            LOGGER.info('EVAL => %s has LinkedID %s (%d)' %
                        (uid, linkedid, self.channels[linkedid].order))
            if not oldest:
                oldest = self.channels[uid].linkedid
            elif self.channels[linkedid].order < self.channels[oldest].order:
                oldest = self.channels[uid].linkedid

        LOGGER.info('EVAL RESULT: oldest LinkedID in bridge #%d is %s (%d)' %
                    (self.bridges[bridgeid], oldest,
                     self.channels[oldest].order))

        # set the value that it should be for comparison later
        # when the next CEL event arrives
        for uid in bridged_with:
            self.channels[uid].linkedid = oldest

            # have each channel query the linkedid because CEL may be old
            self.channels[uid].query_linkedid(ami)

    def bridge_leave(self, ami, event):
        """ handle bridge leave events

        This handles Bridge Leave events, used to track
        which channels are in which bridges together.

        Keyword Arguments
        ami    - The AMI manager object
        event  - The event key/value pairs in a dict
        """
        uniqueid = event['uniqueid']
        bridgeid = event['bridgeuniqueid']
        self.chan_bridge[uniqueid] = False
        bridged_with = [uid for uid in self.chan_bridge.keys()
                        if self.chan_bridge[uid] == bridgeid]
        LOGGER.info('%s left bridge #%d leaving %s' %
                    (uniqueid, self.bridges[bridgeid], bridged_with))

# vim:sw=4:ts=4:expandtab:textwidth=79