On Tue, Mar 23, 2010 at 9:02 AM, JOLY, ROBERT (ROBERT) <[email protected]> wrote: > > >> >> We have few doubts regarding Slow Start (or late media) >> support on SIPX for which we need your views. >> >> >> >> As per observation, SIPX does not support SLOW START i.e. if >> it receives INVITE message without SDP in the first request, >> it would reject with "500 Server Internal Error". There are >> few Avaya's CS1000 scenarios such as "No Hold Conference", >> "MobileX Hand off" and "MobileX RGA support" in which CS1000 >> would send out INVITE message without SDP (Slow Start case, >> where SDP would present in the 'ACK' to '200 OK' from far >> end) and this is rejected by SIPX. > > The sipX SIP routing core does not care about "slow start" or "fast start". > If you see 500 Server Internal Error, it must be generated by the UAS that is > the target of the call. Please be a lot more specific about the failing > scenario so that we can identify the endpoints in play.
If a dialog forming INVITE without SDP is sent to sipxbridge it will return 400 error. (at least it should return a 400 error). The first reason is that sipxbridge is a B2BUA and not just a UA and hence does not as such support an a-priori known codec set. Second, there is no ITSP-driven use case for forwarding the INVITE (no SDP) to the ITSP. Bharath : If you have such a use case, please open up a JIRA issue with a clear description of the call flow. > > >> >> >> This scenario is also tested generically by sending out >> INVITE without SDP using "Sip tool" and SIPX rejected it with >> "500 Internal Server Error". >> >> >> >> Can you please confirm if SIPX does not support Slow Start >> scenarios? As per initial investigations, we understand that >> this would require considerable changes to be done on SIPX >> end to support Slow Start. Please provide your views and if >> there is any reason behind lack of Slow Start support on SIPX. >> >> >> >> Thanks a lot for your time. >> >> >> >> Regards >> >> Bharath >> >> Please do not print this email unless it is absolutely necessary. >> >> The information contained in this electronic message and any >> attachments to this message are intended for the exclusive >> use of the addressee(s) and may contain proprietary, >> confidential or privileged information. If you are not the >> intended recipient, you should not disseminate, distribute or >> copy this e-mail. Please notify the sender immediately and >> destroy all copies of this message and any attachments. >> >> WARNING: Computer viruses can be transmitted via email. The >> recipient should check this email and any attachments for the >> presence of viruses. The company accepts no liability for any >> damage caused by any virus transmitted by this email. >> >> www.wipro.com >> >> > _______________________________________________ > sipx-dev mailing list [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev > sipXecs IP PBX -- http://www.sipfoundry.org/ > -- M. Ranganathan _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
