Data Fields | |
| const char * | context |
| Test context. More... | |
| const struct exten_info * | exten |
| Expected extension match. More... | |
| const int | priority |
| The priority to find. More... | |
| const char * | test_cid |
| Test CID match. More... | |
| const char * | test_exten |
| Test extension number. More... | |
Detailed Description
Definition at line 111 of file test_pbx.c.
Field Documentation
◆ context
| const char* context |
Test context.
This is the context to look in for a specific extension.
Definition at line 118 of file test_pbx.c.
Referenced by test_exten().
◆ exten
| const struct exten_info* exten |
Expected extension match.
This struct corresponds to an extension that was previously added to our test context. Once we have used all the above data to find an extension in the dialplan. We compare the data from that extension to the data that we have stored in this structure to be sure that what was matched was what we expected to match.
Definition at line 153 of file test_pbx.c.
Referenced by test_exten().
◆ priority
| const int priority |
◆ test_cid
| const char* test_cid |
Test CID match.
If a specific CID match is required for pattern matching, then specify it in this parameter. Remember that a NULL CID and an empty CID are interpreted differently. For no CID match, leave this NULL. If you wish to explicitly match an empty CID, then use an empty string here.
Definition at line 138 of file test_pbx.c.
Referenced by test_exten().
◆ test_exten
| const char* test_exten |
Test extension number.
This should be in the form of a specific number or string. For instance, if you were trying to match an extension defined with the pattern "_2." you might have as the test_exten one of "2000" , "2legit2quit" or some other specific match for the pattern.
Definition at line 128 of file test_pbx.c.
Referenced by test_exten().
The documentation for this struct was generated from the following file:
