Hi Vaclav, The INVITE from the Interconnect to the SEMS-SBC contains one c= line (only the IP of the Interconnect), while the INVITE from the SEMS-SBC to the customer equipment contains two c=lines (one with IP of SEMS for RTP-relaying and the second c=line with the IP of the Interconnect). If i cannot relay T.38 to my natted devices, the rtprelay-function of SEMS is useless (at least for usecases containing fax). In that particular setup (which will be replaced with IMS anyway) i tried to avoid using other RTP-Relaying functions on my Kamailio, such as RTPProxy,org or ngcp-mediaproxy-ng.
Thanks, Carsten 2012/11/21 Vaclav Kubart <[email protected]>: > Hello Carsten, > outgoing initial INVITE contains only one c= line? > > I would say that the re-INVITE is correct. At the time of writing the code > there > was no support for relaying "udptl" protocol (not sure how about now) so I > did a > workaround there to pass the "udptl" directly (no relaying for it, so put > original > IP in c= line related to the m= line) > > Vaclav > > On St, lis 21, 2012 at 12:50:02 +0100, Carsten Bock wrote: >> Hi, >> >> i just noticed the following. I have a SEMS running as a SBC with the >> following >> config settings: >> >> ## RTP relay >> # enable RTP relaying (bridging): >> enable_rtprelay=yes >> # force symmetric RTP (start with passive mode): >> rtprelay_force_symmetric_rtp=yes >> # use symmetric RTP indication from P-MsgFlags flag 2 >> #rtprelay_msgflags_symmetric_rtp=yes >> >> I use latest SEMS 1.5 from git, without any changes. >> It works fine until i do a Re-INVITE (e.g. for T.38). The outgoing Re-INVITE >> contains suddenly two c= lines?!? >> >> This looks like a bug to me. >> >> Kind regards, >> Carsten >> >> Incoming Re-INVITE for T.38: >> >> INVITE sip:84.252.101.20:5060 SIP/2.0 >> Max-Forwards: 28 >> Via: SIP/2.0/UDP 84.252.101.17;branch=z9hG4bKb4c1.a6add533.0 >> Via: SIP/2.0/UDP 84.252.101.12;branch=z9hG4bKb4c1.e8e4e867.0 >> Via: SIP/2.0/UDP 109.239.50.67:5061;rport=5061;branch=z9hG4bKb4c1.e8fa5fe6.0 >> Via: SIP/2.0/UDP 109.239.50.66:5080;branch=z9hG4bKF8glJakk;rport=5080 >> From: sip:[email protected];tag=3A06855E-50ACBBA8000F05B6-28C25700 >> To: "+4989200011252" <sip:[email protected]>;tag= >> 46E2A8C2-50ACBBA8000ED1E9-737F7700 >> CSeq: 14 INVITE >> Call-ID: 1B02101F-50ACBBA8000ED1EC-737F7700 >> Contact: <sip:[email protected]:5080> >> Supported: timer >> Session-Expires: 120 >> Min-SE: 90 >> Content-Type: application/sdp >> Content-Length: 571 >> >> v=0 >> o=- 12682033 12682038 IN IP4 87.234.1.225 >> s=call >> c=IN IP4 87.234.1.225 >> t=0 0 >> m=image 23634 udptl t38 >> a=sendrecv >> a=T38FaxVersion:0 >> a=T38MaxBitRate:14400 >> a=T38FaxRateManagement:transferredTCF >> a=T38FaxUdpEC:t38UDPRedundancy >> a=direction:both >> m=audio 23636 RTP/AVP 8 102 0 127 101 >> a=rtpmap:8 PCMA/8000 >> a=rtpmap:102 PCMA/8000 >> a=rtpmap:0 PCMU/8000 >> a=rtpmap:127 PCMU/8000 >> a=rtpmap:101 telephone-event/8000 >> a=fmtp:101 0-15 >> a=sendrecv >> a=gpmd:102 vbd=yes >> a=gpmd:127 vbd=yes >> a=ptime:20 >> a=silenceSupp:off - - - - >> a=ecan:fb on - >> a=X-fax >> a=direction:both >> >> Outgoing Re-INVITE: >> >> INVITE sip:[email protected]:61025 SIP/2.0 >> Via: SIP/2.0/UDP 84.252.101.20;branch=z9hG4bKfZo1oa8u;rport >> From: >> <sip:[email protected]>;tag=27B7E6A1-50ACBBA8000ECFED-783EE700 >> To: "+4989200011252" <sip:[email protected]>;tag=92b7a18884 >> CSeq: 10 INVITE >> Call-ID: 5119d5fe762347de >> Contact: <sip:[email protected]:5060> >> Route: <sip:84.252.101.17;lr=on;ftag=92b7a18884;did=b3f.e62da602;ngv= >> NWU2YnxpNDk8ZDVjMDMzPzRCAnssZnMweGovPz1kLXk5Z1s->, >> <sip:84.252.101.12;lr=on;nat >> =yes> >> Supported: timer >> Session-Expires: 120 >> Min-SE: 90 >> Content-Type: application/sdp >> Content-Length: 595 >> >> v=0 >> o=- 12682033 12682034 IN IP4 87.234.1.225 >> s=call >> c=IN IP4 84.252.101.20 >> t=0 0 >> m=image 23634 udptl t38 >> c=IN IP4 87.234.1.225 >> a=sendrecv >> a=T38FaxVersion:0 >> a=T38MaxBitRate:14400 >> a=T38FaxRateManagement:transferredTCF >> a=T38FaxUdpEC:t38UDPRedundancy >> a=direction:both >> m=audio 35006 RTP/AVP 8 103 0 127 101 >> a=rtpmap:8 PCMA/8000 >> a=rtpmap:103 PCMA/8000 >> a=rtpmap:0 PCMU/8000 >> a=rtpmap:127 PCMU/8000 >> a=rtpmap:101 telephone-event/8000 >> a=fmtp:101 0-15 >> a=sendrecv >> a=gpmd:103 vbd=yes >> a=gpmd:127 vbd=yes >> a=ptime:20 >> a=silenceSupp:off - - - - >> a=ecan:fb on - >> a=X-fax >> a=direction:both >> >> -- >> Carsten Bock >> CEO (Geschäftsführer) >> >> ng-voice GmbH >> Schomburgstr. 80 >> D-22767 Hamburg / Germany >> >> http://www.ng-voice.com >> mailto:[email protected] >> >> Office +49 40 34927219 >> Fax +49 40 34927220 >> >> Sitz der Gesellschaft: Hamburg >> Registergericht: Amtsgericht Hamburg, HRB 120189 >> Geschäftsführer: Carsten Bock >> Ust-ID: DE279344284 >> >> Hier finden Sie unsere handelsrechtlichen Pflichtangaben: >> http://www.ng-voice.com/imprint/ > >> _______________________________________________ >> Semsdev mailing list >> [email protected] >> http://lists.iptel.org/mailman/listinfo/semsdev > -- Carsten Bock CEO (Geschäftsführer) ng-voice GmbH Schomburgstr. 80 D-22767 Hamburg / Germany http://www.ng-voice.com mailto:[email protected] Office +49 40 34927219 Fax +49 40 34927220 Sitz der Gesellschaft: Hamburg Registergericht: Amtsgericht Hamburg, HRB 120189 Geschäftsführer: Carsten Bock Ust-ID: DE279344284 Hier finden Sie unsere handelsrechtlichen Pflichtangaben: http://www.ng-voice.com/imprint/ _______________________________________________ Semsdev mailing list [email protected] http://lists.iptel.org/mailman/listinfo/semsdev
