If you gateway support the a=direction:passive directive, it is not necessary to proxy the media. I'm not sure how mediaproxy handle this situation.
Multiple c= lines is allowed and well documented in RFC 2327. The first one is the connection information for the whole session. It applies to all media in the session. One can also specify media specific connection.
An example would be setting a session level connection information for voice and video but a different media level connection information to a power point presentation running somewhere outside.
Hi
The message below is from ser to the UA, now it seems as if the c= is wrong, because the UA is behind a NAT, and the c= should be of my mediaproxy (...correct ?), but it is actually of my pstn GW
1.2.3.4 = ser x.x.x.x = client a.b.c.d = pstn gw
Also why are there two c= lines
Iqbal
U 2005/09/08 15:35:37.529854 1.2.3.4:5060 -> x.x.x.x:5060
. v=0. o=CiscoSystemsSIP-GW-UserAgent 3096 5788 IN IP4 a.b.c.d. s=SIP Call. c=IN IP4 a.b.c.d. t=0 0. m=audio 19570 RTP/AVP 0. c=IN IP4 a.b.c.d. a=rtpmap:0 PCMU/8000.
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers