Re: [SR-Users] TLS conversion

2015-03-04 Thread Kelvin Chua
It is visible on the other kamailio. I did this to be sure onreply_route[MANAGE_REPLY] { xlog("L_NOTICE","record route 1 $(hdr(Record-route)[0])"); xlog("L_NOTICE","record route 2 $(hdr(Record-route)[1])"); xlog("L_NOTICE","record route 3 $(hdr(Record-route)[2])");

Re: [SR-Users] TLS conversion

2015-03-04 Thread Daniel-Constantin Mierla
Record-Route is not yet visible at that moment. Maybe a solution is to use record_route_preset(..) with parameters instead of record_route(). Cheers, Daniel On 04/03/15 09:00, Kelvin Chua wrote: > i was thinking of changing the record-route before sending out. > I tried it, but it's not working >

Re: [SR-Users] TLS conversion

2015-03-04 Thread Kelvin Chua
i was thinking of changing the record-route before sending out. I tried it, but it's not working subst_hf("Record-route", "/^ wrote: > just an idea, will it work if i used subst_hf? > > Kelvin Chua > > On Tue, Mar 3, 2015 at 5:16 PM, Daniel-Constantin Mierla < > mico...@gmail.com> wrote:

Re: [SR-Users] TLS conversion

2015-03-03 Thread Kelvin Chua
just an idea, will it work if i used subst_hf? Kelvin Chua On Tue, Mar 3, 2015 at 5:16 PM, Daniel-Constantin Mierla wrote: > Hello, > > We need to review this in rr. > > Meanwhile you can use s.substr transformation to get whats after sips and > prefix it with sip in r-uri. > > Cheers, > Daniel

Re: [SR-Users] TLS conversion

2015-03-03 Thread Daniel-Constantin Mierla
Hello, We need to review this in rr. Meanwhile you can use s.substr transformation to get whats after sips and prefix it with sip in r-uri. Cheers, Daniel On Tuesday, March 3, 2015, Kelvin Chua wrote: > Found the problem, on the 200 OK, I have this record route list > > Record-Route: IP>:605

Re: [SR-Users] TLS conversion

2015-03-03 Thread Kelvin Chua
Found the problem, on the 200 OK, I have this record route list Record-Route: :6056;transport=tls;r2=on;lr;ftag=as620b910c;did=242.fd92;nat=yes>. Record-Route: :6055;r2=on;lr;ftag=as620b910c;did=242.fd92;nat=yes>. Record-Route: :5080;lr=on;did=242.968> the second entry is wrong. it should be sip:

Re: [SR-Users] TLS conversion

2015-03-02 Thread Daniel-Constantin Mierla
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. kamailio

[SR-Users] TLS conversion

2015-03-02 Thread Kelvin Chua
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 ast