Re: [SR-Users] TLS conversion

Hello,

doesn't the ACK have a Route header for K1 and double Route headers for K2? K1 should use the first Route of K2 for routing, not the R-URI.

Cheers, Daniel

On 03/03/15 05:14, Kelvin Chua wrote:

I have 2 kamailio servers and 1 asterisk server.

1. asterisk calls kamailio1
2. kamailio1 relays INVITE to kamailio2
3. kamailio2 relays INVITE to client registered using TLS
4. client answers with 200 OK, sends to kamailio2
5. kamailio2 relays 200 OK to kamailio1
6. kamailio1 relays 200 OK to asterisk
7. asterisk sends ACK to kamailio1
8. kamailio1 complains "forward_request(): forward_req: ERROR: cannot

forward to af 2, proto 3 no corresponding listening socket" which is because 200 OK has a contact header with tls transport from client 9. call drops in 30 secs which is expected because client never received the ACK

any ideas on a fix or workaround?

Kelvin Chua

---

SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users