[OpenSIPS-Users] mediaproxy 2.3: reinvites' SDP not modified

[Ruud Klaver]

Hi Carlo,

On 07 Feb 2009, at 22:36, Carlo Dimaggio wrote:

>
> Il giorno 06/gen/09, alle ore 20:10, Ruud Klaver ha scritto:
>
>> Maybe you can still find it somewhere in your syslog? Grep for
>> "image", which is the media type used by T.38 IIRC. The point is that
>> we tried to implement this well, but it was very difficult actually
>> obtaining test devices to see if it worked in a real life testbed.
>
> Hi Ruud,
>
> I'm working now on t.38 fax with opensips 1.4.3 + mediaproxy 2.3.1  
> and I have the same problem as Jeff.
> Here's my scenario.
> I have a fax connected to a patton (sip number 1004) with a private  
> ip (192.168.1.253) and a hylafax/t38modem (sip number 08321111) with  
> a public ip (IP_T38MODEM).
>
> Calls are established at g711, proxied with engage_media_proxy()  
> (all is ok as i can see, the c=line has the media-relay ip), but  
> when there is a re-invite for t38 the media is not proxied and the  
> packets have c=line with original ip (private and public) (In this  
> way t38modem sends packets to the private ip...). There's no "image"  
> media type in syslog.
> The problem is in both ways (patton to t38modem and t38modem to  
> patton). If the patton has the public ip all works fine.
>
> I have some logs. I hope these information can be useful for you  
> (sorry for the length :-)):
>
>
> Thanks and Regards,
> Carlo Dimaggio
>
>
> ---------------------------------------------------
>
> 1) Syslog media-dispatcher
>
> Feb  7 21:02:49 sip media-dispatcher[4614]: [OpenSIPSControlProtocol, 
> 7,] Issuing "update" command to relay at <IP_MEDIA_RELAY>
> Feb  7 21:02:49 sip media-dispatcher[4614]: [OpenSIPSControlProtocol, 
> 6,] Issuing "update" command to relay at <IP_MEDIA_RELAY>
>
>
> 2) Syslog media-relay
>
> Feb  7 21:01:21 media media-relay[3339]:  
> [RelayClientProtocol,client] Received new SDP offer
> Feb  7 21:01:21 media media-relay[3339]:  
> [RelayClientProtocol,client]  
> mediaproxy.mediacontrol.StreamListenerProtocol starting on 50000
> Feb  7 21:01:21 media media-relay[3339]:  
> [RelayClientProtocol,client]  
> mediaproxy.mediacontrol.StreamListenerProtocol starting on 50001
> Feb  7 21:01:21 media media-relay[3339]:  
> [RelayClientProtocol,client]  
> mediaproxy.mediacontrol.StreamListenerProtocol starting on 50002
> Feb  7 21:01:21 media media-relay[3339]:  
> [RelayClientProtocol,client]  
> mediaproxy.mediacontrol.StreamListenerProtocol starting on 50003
> Feb  7 21:01:21 media media-relay[3339]:  
> [RelayClientProtocol,client] Added new stream: (audio)  
> 192.168.1.253:10002 (RTP: Unknown, RTCP: Unknown) <->  
> <IP_MEDIA_RELAY>:50000 <-> <IP_MEDIA_RELAY>:50002 <-> Unknown (RTP:  
> Unknown, RTCP: Unknown)
> Feb  7 21:01:21 media media-relay[3339]:  
> [RelayClientProtocol,client] created new session AmBVR0- 
> hPA1y6f2 at opensips: 1004 at opensips (4g5g2-7QUQV0) --> 08321111 at opensips
> Feb  7 21:01:21 media media-relay[3339]:  
> [RelayClientProtocol,client] updating existing session AmBVR0- 
> hPA1y6f2 at opensips: 1004 at opensips (4g5g2-7QUQV0) --> 08321111 at opensips
> Feb  7 21:01:21 media media-relay[3339]:  
> [RelayClientProtocol,client] Received updated SDP answer
> Feb  7 21:01:21 media media-relay[3339]:  
> [RelayClientProtocol,client] Got initial answer from callee for  
> stream: (audio) 192.168.1.253:10002 (RTP: Unknown, RTCP: Unknown) <- 
> > <IP_MEDIA_RELAY>:50000 <-> <IP_MEDIA_RELAY>:50002 <->  
> <IP_T38MODEM>:10024 (RTP: Unknown, RTCP: Unknown)
> Feb  7 21:01:21 media media-relay[3339]:  
> [mediaproxy.mediacontrol.StreamListenerProtocol (UDP)] Got traffic  
> information for stream: (audio) 192.168.1.253:10002 (RTP: Unknown,  
> RTCP: Unknown) <-> <IP_MEDIA_RELAY>:50000 <-> <IP_MEDIA_RELAY>:50002  
> <-> <IP_T38MODEM>:10024 (RTP: <IP_T38MODEM>:10024, RTCP: Unknown)
> Feb  7 21:01:21 media media-relay[3339]:  
> [mediaproxy.mediacontrol.StreamListenerProtocol (UDP)] Got traffic  
> information for stream: (audio) 192.168.1.253:10002 (RTP:  
> <IP_PUBLIC_PATTON>:10002, RTCP: Unknown) <-> <IP_MEDIA_RELAY>:50000  
> <-> <IP_MEDIA_RELAY>:50002 <-> <IP_T38MODEM>:10024 (RTP:  
> <IP_T38MODEM>:10024, RTCP: Unknown)
> Feb  7 21:01:21 media media-relay[3339]:  
> [mediaproxy.mediacontrol.StreamListenerProtocol (UDP)] Got traffic  
> information for stream: (audio) 192.168.1.253:10002 (RTP:  
> <IP_PUBLIC_PATTON>:10002, RTCP: <IP_PUBLIC_PATTON>:10003) <->  
> <IP_MEDIA_RELAY>:50000 <-> <IP_MEDIA_RELAY>:50002 <-> <IP_T38MODEM>: 
> 10024 (RTP: <IP_T38MODEM>:10024, RTCP: Unknown)
>
> <snip>

Thanks for the extensive log information. For some reason your  
OpenSIPS does not send the re-INVITE and the resulting 200 OK to the  
dispatcher. You can see above that the dispatcher only sends two  
"update" commands to the relay, one for the initial INVITE and the 200  
OK. I'm suspecting that your OpenSIPS config is at fault. Does the  
OpenSIPS log provide you with a clue as to why it does not send the  
contents of the re-INVITE to the dispatcher?

Ruud Klaver
AG Projects