Re: [TIProtocol-askcisco] TIP on TP Server Info Inquiry

[David B. (dbenham) <db...@ci...>]

Have whomever is accessing the TelePresence Server following the instructions on page 75 and continuing on pages 77-79.   Although this document is for  TelePresence Server 2.2 (the version being usied 2.1), the wording is only slightly different but is essentially the same instruction/configuration.
http://www.cisco.com/en/US/docs/telepresence/infrastructure/ts/user_guide/Cisco_TelePresence_Server_2-2_Product_user_guide.pdf

When configuring the endpoint, the “Address” field should be the dial-out URI; i.e. the address the TelePresence Server would dial out to reach your endpoint.  However, you are dialling into the TelePresence Server so you also need to configure one or more of the “Call-in match parameters” under “Configuration” for this endpoint.  We recommend configuring the “E.164” parameter: this should be the SIP username of the endpoint (i.e. the section of the URI before the @ sign); in your pcap file your endpoint is  seevogh@158.197.28.58:5060 so the E.164 should be set to “seevogh” (without the quotes).  

TelePresence Server version 2.1 will advertise mpeg4-generic in its SDP if matching a preconfigured CTS so you can use that to check the above configuration is successful.

Page 142 refers to CTS endpoints only and can be ignored in this case.

Thomas

----------------------------
David,

I have no direct access to tanberg located in USA, but can find out this settings.
To be sure what need to be add there. Should be there our endpoint sip adress or only legacy cisco cts 500 up to cts 3210 which is mention on page 142?

Martin.

> -----Original Message-----
> From: martin harcar [mailto:mar...@ev...]
> Sent: Wednesday, February 08, 2012 5:24 AM
> To: David Benham (dbenham)
> Cc: tip...@li...
> Subject: Re: [TIProtocol-askcisco] TIP on TP Server Info Inquiry
> Importance: High
> 
> David,
> 
> Thanks for your reply.
> Our goal is to be TIP compatible with cisco devices.
> Firstly we want to achieve successful TIP communication between our
> tool(endpoint) and TANDBERG Telepresence Server 8710 which as I found
> that is compatible with TIP.
> What we did are follows:
> Make sip call with these settings:
> m=audio ${A_PORT} RTP/AVP 96 9 0 101
> b=TIAS:128000
> a=rtpmap:96 mpeg4-generic/48000
> a=fmtp:96
> profile-level-
> id=16;streamtype=5;mode=AAChbr;config=B98C00;sizeLength=13;indexLeng
> th=3;indexDeltaLength=3;constantDuration=480
> a=rtpmap:9 G722/8000
> a=rtpmap:0 PCMU/8000
> a=rtpmap:101 telephone-event/8000
> m=video ${V_PORT} RTP/AVP 112
> b=AS:4096
> b=TIAS:4096000
> a=sendrecv
> a=rtpmap:112 H264/90000
> a=fmtp:112 profile-level-id=4d0028;packetization-mode=1
> 
> Than did TIP negotiation on video port+1(64181 in this case) using
> libTIP.
> Here is what we get from TANDBERG Telepresence Server 8710:
> v=0
> o=CODIAN 1328705765 1328705765 IN IP4 150.199.99.228
> s=-
> i=TANDBERG Telepresence Server 8710 v2.1(1.37)
> c=IN IP4 150.199.99.228
> b=AS:1920
> t=0 0
> m=audio 51732 RTP/AVP 96 9 0 101
> a=rtpmap:96 MP4A-LATM/90000
> a=fmtp:96 profile-level-id=24;object=23;bitrate=64000
> a=rtpmap:9 G722/8000
> a=rtpmap:0 PCMU/8000/1
> a=rtpmap:101 telephone-event/8000
> a=fmtp:101 0-15
> a=sendrecv
> m=video 64180 RTP/AVP 112
> b=AS:1920
> a=rtpmap:112 H264/90000
> a=fmtp:112 profile-level-id=42e016;max-mbps=108000;max-fs=3600
> a=sendrecv
> 
> but we never received any TIP packets from TANDBERG Telepresence Server
> 8710 and immediately after SIP call we get h264 hd720 black video with
> 30fps.
> 
> Maybe I miss something and did it wrong way.
> In attachment is pcap file with communication between our endpoint and
> Tandberg which should be helpful.
> IP adress of our endpoint: 158.197.28.58
> IP adress of tandberg: 150.199.99.228
> 
> Hope it will be helpful to identify what is wrong in our setup.
> Regards
> Martin.
> 
> On Tue, 2012-02-07 at 10:20 -0800, David Benham (dbenham) wrote:
> > Martin
> > Since your question is specific to Cisco's TIP implementation, you should
> send your questions to the  open source project mail specific to asking Cisco
> questions ...
> >
> >          Email:   tip...@li...
> >   Archives:
> http://sourceforge.net/mailarchive/forum.php?forum_name=tiprotocol-
> askcisco
> >
> > Please respond with further detail about your configuration and release
> numbers (endpoints, UCM, TP Server inclusive) used.
> >
> > If you have followed the profile instructions to interop with a CTS 1.7 or
> earlier, meeting all the restricted video details, you will need to pre-
> configure your endpoint on the TP Server's 'add an endpoint' as a "Cisco CTS
> / Legacy Cisco CTS" per pages 75 or 142 on the user guide (see URL).
> >
> http://www.cisco.com/en/US/docs/telepresence/infrastructure/ts/user_gu
> ide/Cisco_TelePresence_Server_2-2_Product_user_guide.pdf
> > If you have yet done that, do so and try again.
> >
> >
> > > -----Original Message-----
> > > From: martin harcar [mailto:mar...@ev...]
> > > Sent: Friday, February 03, 2012 5:50 AM
> > > To: tip...@im...
> > > Subject: IMTC TIP Info Inquiry
> > >
> > > Hi.
> > >
> > > I am trying to make a SIP call to TANDBERG Telepresence Server 8710
> > > follow the rules in TIP documentations. I was able to get HD video but
> > > did not receive any TIP rtcp packet.
> > > Is some specific port used for TIP negotiation?
> > > I did TIP negotiation on local receive audio/video and remote receive
> > > audio/video ports get from sip call. Than I try to use ports+1 on both
> > > side. In both cases I did not receive any TIP rtcp packets.
> > > I am using for tip negotiation open source TIP library and tested it
> > > between my two endpoints and works OK.
> > >
> > > Thanks for any answer.
> > > Regards
> > > Martin.
> >