> Simple Scenario:
> 
>                    SIP
>   CS1000 ------------------SIPX
>    |   |                                |
> setA setB                          setX
> 
> - setA and setB are connected to CS1000 and setX is connected to SIPX.
> 
> Actions:
> ---------
> 1. setA calls setB.
> 2. setA initiates a No Hold Conference to setX.
> 
> This problematic scenario can also be simulated using SIPp 
> tool (without CS1000 and without NHC scenario). Construct a 
> simulated INVITE without SDP using "SIPp tool" and send it 
> across to SIPX, you might be able to observe the results yourself.

I suspect that setX does not support "Slow start" then.  A simple network trace 
would confirm that.


> 
> 
> -----Original Message-----
> From: JOLY, ROBERT (ROBERT) [mailto:[email protected]]
> Sent: Tuesday, March 23, 2010 7:15 PM
> To: Bharath Ramalingam (WT01 - Telecom Equipment); 
> [email protected]
> Subject: RE: SLOW START on SIPX
> 
> > Thanks Joly for your response.
> > 
> > As mentioned earlier, it's a "No Hold Conference" (NHC) 
> scenario from 
> > CS1000 to endpoint connected to SIPX i.e.
> > without putting the present call on hold, conference will 
> initiate. In
> 
> > such case, CS1000 would send out INVITE message without SDP 
> > information and when far end responds with the '200 OK', the SDP 
> > information would be sent in 'ACK' message.
> > But when the far end is SIPX, it rejects the INVITE without 
> SDP with 
> > "500 internal Server Error".
> 
> What do you mean by 'the far end is SIPX'.  You were just 
> explaining that the scenario is between CS1K to an endpoint 
> connected to sipXecs.
> Please describe failing scenario - that would be one where 
> the far-end is a component of sipX, not CS1K or a phone 
> connected to sipX.
> 
> 
> > Our understanding it
> > that this problem happens due to lack of 'slow start' or late media 
> > support on SIPX.
> > 
> > I am not sure if we are missing any configuration for 'slow 
> start' to 
> > be supported on SIPX.
> > 
> > If not without CS1000, this issue can be reproduced by the standard 
> > "SIPp tool" to generate INVITE without SDP to SIPX.
> > We tried using SIPp as well and received "500 Internal 
> Server Error" 
> > from SIPX, after which we understood that this problem 
> could be due to
> 
> > lack of 'slow start'
> > implementation on SIPX. Please see if the attached traces 
> help you to 
> > identify the cause for the problem.
> > 
> > Thanks for your time.
> > 
> > Regards
> > Bharath
> > 
> > -----Original Message-----
> > From: JOLY, ROBERT (ROBERT) [mailto:[email protected]]
> > Sent: Tuesday, March 23, 2010 6:33 PM
> > To: Bharath Ramalingam (WT01 - Telecom Equipment); 
> > [email protected]
> > Subject: RE: SLOW START on SIPX
> > 
> >  
> > 
> > > 
> > > 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.
> > 
> > 
> > >  
> > > 
> > > 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
> > > 
> > > 
> > 
> > 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
> > 
> 
> 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/

Reply via email to