Call Monitoring triggers both after ingoing and outgoing calls. So there is a message about the last missed call after disconnecting an outgoing call.
Call Monitoring triggers both after ingoing _and_ outgoing calls. So there is a message about the last missed call after disconnecting an outgoing call.
homer77
added the bug label 2021-07-12 22:31:55 +02:00
homer77
self-assigned this 2021-07-12 22:31:56 +02:00
Incoming and outgoing calls differ regarding the numbers after "DISCONNECTED" that is looked for in the event variable.
incoming call:
15.07.21 13:23:05;DISCONNECT;0;526;
outgoing call:
16.07.21 09:49:25;DISCONNECT;1;0;
So it seems, that the digit after DISCONNECT decodes 0 for incoming and 1 for outgoing calls.
Rather strange during my experiments:
While the conditional clauses I setup differed validly as the referring print statements suggest
Unfortunately it triggers the func parameter every time 🤔
Update
Also I don't receive the last call but always the same from the same day?! ... I have to fix this urgently.
Incoming and outgoing calls differ regarding the numbers after "DISCONNECTED" that is looked for in the event variable.
__incoming call:__
```
15.07.21 13:23:05;DISCONNECT;0;526;
```
__outgoing call:__
```
16.07.21 09:49:25;DISCONNECT;1;0;
```
So it seems, that the digit after DISCONNECT decodes 0 for incoming and 1 for outgoing calls.
Rather strange during my experiments:
While the conditional clauses I setup differed validly as the referring print statements suggest
Unfortunately it triggers the func parameter _every_ time 🤔
### Update
Also I don't receive the last call but always the same from the same day?! ... I have to fix this urgently.
Not absolutely sure if the updated problem is also fixed but with the last tests it sent me the right messages.
For now I close this issue because the incoming/outgoing switch works now.
Not absolutely sure if the updated problem is also fixed but with the last tests it sent me the right messages.
For now I close this issue because the incoming/outgoing switch works now.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Call Monitoring triggers both after ingoing and outgoing calls. So there is a message about the last missed call after disconnecting an outgoing call.
Incoming and outgoing calls differ regarding the numbers after "DISCONNECTED" that is looked for in the event variable.
incoming call:
outgoing call:
So it seems, that the digit after DISCONNECT decodes 0 for incoming and 1 for outgoing calls.
Rather strange during my experiments:
While the conditional clauses I setup differed validly as the referring print statements suggest
Unfortunately it triggers the func parameter every time 🤔
Update
Also I don't receive the last call but always the same from the same day?! ... I have to fix this urgently.
Not absolutely sure if the updated problem is also fixed but with the last tests it sent me the right messages.
For now I close this issue because the incoming/outgoing switch works now.