Andrzej

@syssi - opened, with log and description

Just checked against last stable - works, proper CLIP identification, no hang up. Having it implemented like: ``` on_incoming_call: - logger.log: format: "Incoming call from '%s'" args: ["caller_id.c_str()"] - lambda:...

Tested it more througously - apart from not being able to drop incoming call (and also outgoing) it works perfect. Every "RING"/CLIP casues on_incoming_call to be called so one incoming...

I've tested the latest addition trying to add 'sim800l.disconnect' action just fater reporting incoming call. What surprised me after flashing:  Not sure why routine with incoming call doesn't work...

one more finding: everytime there's unhandled RING/CLIP, soon after that API connection to HA drops  not sure why tho :-)

Latest addition fixed CLIP identification works well and stable, I've just retested it. Last thing that may be worth implementing to prevent multiple calls of `on_incoming_call` during one connection would...

I did just test it in all variants I think: It works as desired: **CALL OUT - ANSWERED** in scenario when call is made by sim800l and picked up on...

Let me know if you need anything else as I'm not fully aware when is the cutoff for next release

@glmnet sure. using same yaml without even one change: ``` scenario 1 - call answered [21:09:39][I][sim800l:311]: Dialing: 'xxxxxxxxx' [21:09:41][D][sim800l:235]: Call state is now: 2 [21:09:43][D][sim800l:235]: Call state is now: 3...

I did compile with ``` external_components: - source: github://pr#3630 refresh: 0s components: - sim800l ``` so I guess it's with `dev`. maybe GPIO issue then, I have only 3 relays...