Queries on MSRP capabilities of the IMS/RCS bogue client

[GoogleCodeExporter]

I have a few queries regarding the MSRP capabilities of the IMS/RCS bogue 
client.

Setupinfo: 
O.S: Windows XP 32 Bit
Client: Boghe_1.0.55.539

-Does the clinet support the draft-ietf-simple-msrp-sessmatch-07.This 
specification defines an MSRP extension,  sessmatch, that allows MSRP entities 
to communicate with ALGs that do not implement MSRP B2BUA functionality. This 
draft relaxes the MSRP URI matching criteria to match only the session ID in 
the MSRP URI.

- Does the clinet support the draft-ietf-simple-msrp-acm-09. This document 
defines an alternative connection model for Message Session Relay Protocol 
(MSRP) User Agents (UAs), which uses the connection-oriented media (COMEDIA) 
mechanism in order to create the MSRP transport connection.This draft mentions 
that MSRP UAs MUST NOT use the SDP a=connection attribute, but I see the same 
being used by the client. Is there any way to disable it?

-  We are trying to run an MSRP call and the client sends back a 603 Decline 
after sending back a reliable 183 with session description(Attached ethereal 
trace for the same). How can we see logs of the calls?

Any response is highly appreciated!!!.

I would like to appreciate the efforts in bringing up 'BOGUE IMS/RCS client'.

Thanks in advance,
Sudhir
PS:
We are testing with SBC, which supports only IETF. 

Original issue reported on code.google.com by t.sudhir...@gmail.com on 7 Jan 2011 at 12:25

Attachments:

• msrp_boghe_603.pcap

[GoogleCodeExporter]

- The client doesn't support "draft-ietf-simple-msrp-sessmatch-10" but it's in 
our roadmap.
- "draft-ietf-simple-msrp-acm-09" is support but we continue to add 
"a=connection" attribute line for backward compatibility. According to this 
draft the remote peer MUST ignore this attribute. If you are a developer then 
you can comment line 673 and 681 from 
"http://code.google.com/p/doubango/source/browse/trunk/tinyDAV/src/msrp/tdav_ses
sion_msrp.c" to remove this attribute.
- Decline response should only be sent on user action. I'll check your trace.

Original comment by boss...@yahoo.fr on 7 Jan 2011 at 4:37

• Changed state: Accepted

[GoogleCodeExporter]

Have you got time to check 603 response?

Original comment by t.sudhir...@gmail.com on 9 Feb 2011 at 7:09

[GoogleCodeExporter]

Original comment by boss...@yahoo.fr on 18 May 2012 at 3:35

• Changed state: Done