Adrian Currently my sip/msrp client can only talk TLS to an MSRP-Relay using relay procedure. It can talk to an MSRP switch (co-media sdp) with normal TCP using connect in procedure. Is this a bottleneck now ? Seems like I cannot connect sip-chatserver with my current msrp client implementation. Am I right ?
On Wed, Nov 4, 2009 at 4:50 PM, mani sivaraman <[email protected]>wrote: > Adrian > I'm using msrps now. Still I get the same 488 message. Note that my client > uses MSRP Relay procedure. Before it send the INVITE , it sends an msrpAuth > (TLS auth) , gets a msrp relay path , puts that in SDP and then sends it. > This is how we send MSRP File trasnfer with other MSRP peers. I guess the > chat server is expecting the UA to open a direct TLS pip for MSRP. AM I > right ? Even though we use msrps in SDP, the m=field in SDK still has TCP, > not TLS. IS this the problem ? If I change that to TLS will it work ? > > Here is the trace. > > > > msrpAuth calling relayAuth .. > AppProcessMessage BIND_RESPONSE The operation was successful > OpenSSL connect successful > AppProcessMessage CONNECT_RESPONSE The operation was successful > msrpAuth call returned... > acOutIM_PlaceCall Media Relay Auth Success for SessionHdl = 1 relayUsePath > = msrps:// > 63.148.166.215:2855/Di6RIi0+0KMIoiwi6X5izjEyNTczNzUxODkuMzAyOjYzLjE0OC4xNjY > uMw==;tcp msrps://[email protected];tcp > > -------------------------------------------------------------- > > INVITE sip:[email protected] <sip%[email protected]>SIP/2.0 > Via: SIP/2.0/UDP 172.16.1.125:7146;rport;branch=z9hG4bK222612060-22410152 > Max-Forwards: 70 > Allow: > INVITE,BYE,CANCEL,ACK,INFO,PRACK,OPTIONS,SUBSCRIBE,NOTIFY,PUBLISH,MESSAGE,REFER,REGISTER,UPDATE > Supported: timer,replaces,norefersub,100rel > Accept-Contact: *;+g.oma.sip-im > User-Agent: SMSI IMS Client R02.0.00 > P-Preferred-Identity: sip:[email protected] <sip%[email protected]> > From: car1<sip:[email protected] <sip%[email protected]> > >;tag=smsiUA_222612060-22410153 > To: <sip:[email protected] <sip%[email protected]>> > Call-ID: 222612060-22410151 > CSeq: 1 INVITE > Contact: car1<sip:[email protected]:7146;transport=udp>;+g.oma.sip-im > Content-Type: application/sdp > Content-Length: 384 > > v=0 > o=SMSI 256 2 IN IP4 172.16.1.125 > s=SipSession with SMSIUA > i=SIP Session in SMSIUA > u=http://www.mydomain.com > c=IN IP4 172.16.1.125 > t=0 0 > m=message 8876 TCP/MSRP * > c=IN IP4 172.16.1.125 > a=accept-types:Message/CPIM text/plain > a=path:msrps:// > 63.148.166.215:2855/Di6RIi0+0KMIoiwi6X5izjEyNTczNzUxODkuMzAyOjYzLjE0OC4xNjYuMw==;tcpmsrps:// > [email protected];tcp > a=sendrecv > -------------------------------------------------------------- > > acOutIM_PlaceCall Succeded SessionId = 23 > IMEnabled::Trying > > Wed Nov 04 16:37:12 2009 > > ------------------------------------------------------------ > > SIP/2.0 100 Giving a try > Via: SIP/2.0/UDP 172.16.1.125:7146 > ;rport=15528;branch=z9hG4bK222612060-22410152;received=63.148.166.3 > From: car1<sip:[email protected] <sip%[email protected]> > >;tag=smsiUA_222612060-22410153 > To: <sip:[email protected] <sip%[email protected]>> > Call-ID: 222612060-22410151 > CSeq: 1 INVITE > Server: OpenSIPS (1.5.3-tls (i386/linux)) > Content-Length: 0 > > -------------------------------------------------------------- > > Got a message on UDP > > ------------------------------------------------------------ > Trace generated at : > Wed Nov 04 16:37:12 2009 > > ------------------------------------------------------------ > SIP/2.0 488 Not Acceptable Here > Via: SIP/2.0/UDP 172.16.1.125:7146 > ;rport=15528;received=63.148.166.3;branch=z9hG4bK222612060-22410152 > Call-ID: 222612060-22410151 > From: "car1" <sip:[email protected] <sip%[email protected]> > >;tag=smsiUA_222612060-22410153 > To: <sip:[email protected] <sip%[email protected]> > >;tag=ush3.lWer92-QdTNqGG-52kLWY16sROg > CSeq: 1 INVITE > > Server: sip-chatserver-0.9.2 > Content-Length: 0 > > Got an Event > > > On Wed, Nov 4, 2009 at 3:23 PM, Adrian Georgescu <[email protected]>wrote: > >> You must use TLS, see SDP example below: >> >> SENDING: Packet 11, +0:00:41.217882 >> 2009-11-04 22:22:22.660361: 192.168.1.124:58143 -(SIP over UDP)-> >> 81.23.228.129:5060 >> *INVITE sip:[email protected] SIP/2.0* >> Via: SIP/2.0/UDP 192.168.1.124:58143 >> ;rport;branch=z9hG4bKPjSF0ovdCJTdFi3LOJR9br4y6Ub-7z5ZwI >> Max-Forwards: 70 >> From: "Adrian G." <sip:[email protected] >> >;tag=fQJyDYb06LqeemqHW8pX3L6i4xaxmPIs >> To: <sip:[email protected]> >> Contact: <sip:[email protected]:58143> >> Call-ID: prtAsF0Fp5eRkQdnNfcY59zEPOYjBhUU >> CSeq: 11220 INVITE >> Route: <sip:81.23.228.129;lr> >> Allow: SUBSCRIBE, NOTIFY, PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, MESSAGE >> Supported: 100rel >> User-Agent: blink-0.10.4-beta >> Proxy-Authorization: Digest username="31208005169", realm=" >> ag-projects.com", nonce="4af1f0ac56c8329304dd616851ff758d1c56b7ea", uri=" >> sip:[email protected]", >> response="584521bbc6a8211222d8a7343f148c55" >> Content-Type: application/sdp >> Content-Length: 258 >> >> v=0 >> o=- 3466358542 3466358542 IN IP4 192.168.1.124 >> s=blink-0.10.4-beta >> c=IN IP4 192.168.1.124 >> t=0 0 >> m=message 2855 TCP/TLS/MSRP * >> a=path:msrps://192.168.1.124:2855/a328a18ea183e864b8c8;tcp >> a=accept-types:message/cpim text/* >> a=accept-wrapped-types:* >> >> RECEIVED: Packet 12, +0:00:41.249248 >> 2009-11-04 22:22:22.691727: 81.23.228.129:5060 -(SIP over UDP)-> >> 192.168.1.124:58143 >> *SIP/2.0 100 Giving a try* >> Via: SIP/2.0/UDP 192.168.1.124:58143 >> ;rport=58143;branch=z9hG4bKPjSF0ovdCJTdFi3LOJR9br4y6Ub-7z5ZwI;received=80.101.96.20 >> From: "Adrian G." <sip:[email protected] >> >;tag=fQJyDYb06LqeemqHW8pX3L6i4xaxmPIs >> To: <sip:[email protected]> >> Call-ID: prtAsF0Fp5eRkQdnNfcY59zEPOYjBhUU >> CSeq: 11220 INVITE >> Server: SIP Thor on OpenSIPS XS 1.4.5 >> Content-Length: 0 >> >> RECEIVED: Packet 13, +0:00:41.270382 >> 2009-11-04 22:22:22.712861: 81.23.228.129:5060 -(SIP over UDP)-> >> 192.168.1.124:58143 >> *SIP/2.0 200 OK* >> Via: SIP/2.0/UDP 192.168.1.124:58143 >> ;rport=58143;received=80.101.96.20;branch=z9hG4bKPjSF0ovdCJTdFi3LOJR9br4y6Ub-7z5ZwI >> Record-Route: < >> sip:85.17.186.7;lr;ftag=fQJyDYb06LqeemqHW8pX3L6i4xaxmPIs;did=69b.62cb94c2 >> > >> Record-Route: < >> sip:81.23.228.129;lr;ftag=fQJyDYb06LqeemqHW8pX3L6i4xaxmPIs;did=69b.9aa264a6 >> > >> Call-ID: prtAsF0Fp5eRkQdnNfcY59zEPOYjBhUU >> From: "Adrian G." <sip:[email protected] >> >;tag=fQJyDYb06LqeemqHW8pX3L6i4xaxmPIs >> To: <sip:[email protected] >> >;tag=ZwvT6xOtX.ESzg4usO-fgyEUZsUZo9fd >> CSeq: 11220 INVITE >> Contact: <sip:[email protected]:6060> >> Allow: SUBSCRIBE, NOTIFY, PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, MESSAGE >> Supported: 100rel >> Server: sip-chatserver-0.9.2 >> Content-Type: application/sdp >> Content-Length: 244 >> >> v=0 >> o=- 3466358542 3466358543 IN IP4 81.23.228.146 >> s= >> c=IN IP4 81.23.228.146 >> t=0 0 >> m=message 2856 TCP/TLS/MSRP * >> a=path:msrps://81.23.228.146:2856/385d080f7a9ae04fb513;tcp >> a=accept-types:message/cpim >> a=accept-wrapped-types:text/plain >> >> SENDING: Packet 14, +0:00:41.270787 >> 2009-11-04 22:22:22.713266: 192.168.1.124:58143 -(SIP over UDP)-> >> 81.23.228.129:5060 >> *ACK sip:[email protected]:6060 SIP/2.0* >> Via: SIP/2.0/UDP 192.168.1.124:58143 >> ;rport;branch=z9hG4bKPj6tNNz.H6Y9X5tuH-j8UTiuUA2P.5wrAg >> Max-Forwards: 70 >> From: "Adrian G." <sip:[email protected] >> >;tag=fQJyDYb06LqeemqHW8pX3L6i4xaxmPIs >> To: <sip:[email protected] >> >;tag=ZwvT6xOtX.ESzg4usO-fgyEUZsUZo9fd >> Call-ID: prtAsF0Fp5eRkQdnNfcY59zEPOYjBhUU >> CSeq: 11220 ACK >> Route: < >> sip:81.23.228.129;lr;ftag=fQJyDYb06LqeemqHW8pX3L6i4xaxmPIs;did=69b.9aa264a6 >> > >> Route: < >> sip:85.17.186.7;lr;ftag=fQJyDYb06LqeemqHW8pX3L6i4xaxmPIs;did=69b.62cb94c2 >> > >> User-Agent: blink-0.10.4-beta >> Content-Length: 0 >> >> >> -- >> Adrian >> >> >> >> >> >> >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> >
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
