Dave Horton

Uh, I don't see any call being proxied in that log. I see an outbound INVITE sent as a UAC, which is different. timer C only applies to proxies

timer C specifically and only applies to proxy transactions: https://tools.ietf.org/html/rfc3261#page-265 And per your request, that is what I have done. This means that it will be triggered when an app...

ah, ok I removed all that in order to create the smallest possible image size. Will look at putting it back in..

I would recommend doing this differently. When receiving the REGISTER from a websocket client, do not proxy it or send it anywhere. Authenticate it locally and send a 200 OK....

Alternatively, if you want to continue working the approach you outlined, I think the one change you should try making is not to proxy that INVITE on the final leg,...

actually, I could build a test branch that could make the proxy work for you.....?

yes, it has nothing to do ".invalid" actually. When sending a 200 OK to a REGISTER (but not as proxy), _and_ if the transport is not udp, the drachtio server...

can you show me a drachtio server log (debug) for the incoming call? I'd like to first verify how that is being handled. Then I can look at the outbound...

in your outbound example, you are tryin to send to ``` sip:urn:service:sos.fire ``` Since RFC 5031 defines a URN namespace, I don't think the `sip:` scheme should be in front...

Well this timeout indicates an error of some kind....it means it sent an invite over to a drachtio client and never got a response back as to how to handle...