Hi, rport is defined in RFC 3581 and besides that no unknown parameter in any header field should break the normal call processing of a SIP device (except the Require header maybe).
Regards Nils Ohlmeier On Wednesday 14 July 2004 15:45, Markus Hofmann wrote: > Hi Akshai, > > in the Via header is a parameter "rport". I have never heard something > about this parameter. > > Maybe this is the reason. > > Greeting > > Markus > > "Giacomo Vacca" <[EMAIL PROTECTED]> schrieb am 14.07.04 14:08:30: > > Akshai, > > I think that analize the 200 OK message isn't enough. You have to look > > also the INVITE message. If the caller doesnt send the ACK, probably it > > received a 200 OK with some miss or bad-specified header. Also compare > > tags, and try changing the position of some important header (like Via). > > Does the caller send a BYE after the called answered with that 200 OK or > > simply ignor it? Also investigate for RTP troubles. > > Giacomo > > > > -----Messaggio originale----- > > Da: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] Per conto di Akshai > > Parthasarathy > > Inviato: luned� 12 luglio 2004 12.36 > > A: [EMAIL PROTECTED] > > Oggetto: [Sip-implementors] ACK generation in SIP > > > > Hi, > > I am a student working on SIP. I was experimenting with 2 clients, and a > > server that I am working on. > > > > Do you have any idea why the following ok message does not generate an > > ack at the client who intiated the call? > > The message has reached its destination (ie. the caller) from the logs. > > > > RECEIVE TIME: 531703718 > > RECEIVE << 198.202.188.44:5070 > > SIP/2.0 200 Ok > > From: "Shootist" <sip:[EMAIL PROTECTED]>;tag=1738152086 > > To: "Shootme" <sip:[EMAIL PROTECTED]:5060>;tag=36158188 > > Contact: <sip:[EMAIL PROTECTED]:5060> > > Call-ID: [EMAIL PROTECTED] > > CSeq: 13066 INVITE > > Server: SIPphone release 1103a > > Content-Type: application/sdp > > Via: SIP/2.0/UDP > > 198.202.189.120:5060;rport;branch=z9hG4bK6B476672AB524263B0B0751BB7800A8 > > 2 > > Content-Length: 259 > > > > v=0 > > o=Shootme 261980734 262003156 IN IP4 206.236.134.137 s=SIPphone c=IN IP4 > > 206.236.134.137 t=0 0 m=audio 8000 RTP/AVP 0 98 97 101 a=rtpmap:0 > > pcmu/8000 a=rtpmap:98 iLBC/8000 > > a=rtpmap:97 speex/8000 > > a=rtpmap:101 telephone-event/8000 > > a=fmtp:101 0-15 > > > > Thank you, > > Akshai > > > > > > _______________________________________________ > > Sip-implementors mailing list > > [EMAIL PROTECTED] > > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > > > > > > _______________________________________________ > > Sip-implementors mailing list > > [EMAIL PROTECTED] > > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > > _______________________________________________________ > WEB.DE Video-Mail - Sagen Sie mehr mit bewegten Bildern > Informationen unter: http://freemail.web.de/?mc=021199 > > > _______________________________________________ > Sip-implementors mailing list > [EMAIL PROTECTED] > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
