I named it “custom-cid” as well which doesn’t work either.
I looked a the call trace and it just never goes to the custom-context so I’m not sure how useful that trace is besides confirming it isn’t there. I think we should figure out why it is not included.
I figured it out after a lot of debugging and pondering
So it went wrong after changing from chansip to pjsip because I switched the ports as well. (switched pjsip to 5060 instead of default on 5160 and vice versa for chan_sip). My provider was still using 5060 and therefore the calls came in (somehow) via pjsip and a non-existent trunk instead of the configured chansip trunk. The result was of course that the custom context was never used.
Thanks to @PitzKey as he suggested the calls were not coming through the trunk, it took some time but eventually it made the bell ring icw some other things I found in the log.
It’s a type=friend config, so the incoming and outgoing share all the same settings. Since context=anything is meaningless on an outbound connection, it can only be applicable to an incoming connection.