Re: [Sip-implementors] Need Information on SIP Contact Headerparameters wlsscid and sipappsessionid
Adding Sipappsessionid is one way to making sure that all subsequent in-dialog request reaches to same sip-servlet-host which has originally sent this request. In case of cluster approach this is quite common. If sip-servlet-host does add this then it has to replicate SAS to all other such hosts, which makes cluster set-up inefficient. No idea about wlsscid. Thanks, -Original Message- From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of kranthi kolluru Sent: Wednesday, July 29, 2009 6:00 PM To: sip-implementors@lists.cs.columbia.edu Subject: [Sip-implementors] Need Information on SIP Contact Headerparameters wlsscid and sipappsessionid Hi We are using OCCAS Web Logic server to deploy our application. The content header information has fields wlsscid sipappsessionid which are coming as default. Want to understand more how when these fields are getting populated and their significance. Please find the message snippet below Via: SIP/2.0/TCP 10.68.20.101:5067;wlsscid=d09c87074527;branch=z9hG4bK6f882d53b3f7e95ef23452ec3412ab76;received=10.68.20.104 Via: SIP/2.0/UDP 10.48.27.197:5090;branch=z9hG4bK_IMSCA0500514.000_51c3d4c797ac2666f8b9fddc1bd7534c01;lskpmc=S05 Via: SIP/2.0/TCP 10.48.27.197:5070;branch=z9hG4bK_IMSCA0500514.000_32e277815bbabf5de92486514f1e4ad3;lskpmc=P07 Via: SIP/2.0/UDP 10.68.20.101:5168;branch=z9hG4bKnashds8 Record-Route: sip:10.68.20.101:5067;wlsscid=d09c87074527;lr;sipappsessionid=app-5u4nn0gjyl4j;wlssrrd=out Record-Route: sip:i...@scscf.ims2.mlab:5090;routing_id=775a4689c391524586728ff1f57883f6;lskpmc=S05;lr;interface=bcc;tid=51c3d4c797ac2666f8b9fddc1bd7534c01 Record-Route: sip:pcscf.ims2.mlab:5070;routing_id=pcscf_a_side;lskpmc=P07;lr The OCCAS server configured with below SIP parameters: enable-local-dispatch, server-header , server-header-value, globally-routable-uri Enable local dispatch Enable a server%2 ___ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors ___ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
Re: [Sip-implementors] Need Information on SIP Contact Headerparameters wlsscid and sipappsessionid
Hi , We are using OCCAS Web Logic server to deploy our application. The content header information has fields wlsscid sipappsessionid which are coming as default. Want to understand more how when these fields are getting populated and their significance. if we set the Enable-local-dispatch value as true will it effect the contact header information. We have the size limitation on the header information and hence trying for the options to remove wlsscid sipappsessionid sip parameters from the contact header. Can somebody please confirm that by using the standalone application in OCCAS is there any provision of surpressing the parameters wlsscid and sipappsession from the contact header ? Currently as we are not using cluster mode please update Thanks, Kranthi ___ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
Re: [Sip-implementors] Need Information on SIP Contact Headerparameters wlsscid and sipappsessionid
Hi The wlsscid sipappsessionid parameters are Weblogic SIP server parameters. wlsscid - Identifies the cluster ID of the cluster that originated the SIP message during a software upgrade. The sideways forwarding mechanism uses this attribute to ensure that messages are delivered to a compatible cluster. apsessionid - Used with the SipApplicationSession.encodeURI method to store the session ID. Reference - Table 1-4 http://download.oracle.com/docs/cd/E13153_01/wlcp/wlss40/notes/new.html#whatsnew regards Abhishek Dhammawat Aricent -Original Message- From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of kranthi kolluru Sent: Wednesday, July 29, 2009 6:00 PM To: sip-implementors@lists.cs.columbia.edu Subject: [Sip-implementors] Need Information on SIP Contact Headerparameters wlsscid and sipappsessionid Hi We are using OCCAS Web Logic server to deploy our application. The content header information has fields wlsscid sipappsessionid which are coming as default. Want to understand more how when these fields are getting populated and their significance. Please find the message snippet below Via: SIP/2.0/TCP 10.68.20.101:5067;wlsscid=d09c87074527;branch=z9hG4bK6f882d53b3f7e95ef23452ec3412ab76;received=10.68.20.104 Via: SIP/2.0/UDP 10.48.27.197:5090;branch=z9hG4bK_IMSCA0500514.000_51c3d4c797ac2666f8b9fddc1bd7534c01;lskpmc=S05 Via: SIP/2.0/TCP 10.48.27.197:5070;branch=z9hG4bK_IMSCA0500514.000_32e277815bbabf5de92486514f1e4ad3;lskpmc=P07 Via: SIP/2.0/UDP 10.68.20.101:5168;branch=z9hG4bKnashds8 Record-Route: sip:10.68.20.101:5067;wlsscid=d09c87074527;lr;sipappsessionid=app-5u4nn0gjyl4j;wlssrrd=out Record-Route: sip:i...@scscf.ims2.mlab:5090;routing_id=775a4689c391524586728ff1f57883f6;lskpmc=S05;lr;interface=bcc;tid=51c3d4c797ac2666f8b9fddc1bd7534c01 Record-Route: sip:pcscf.ims2.mlab:5070;routing_id=pcscf_a_side;lskpmc=P07;lr The OCCAS server configured with below SIP parameters: enable-local-dispatch, server-header , server-header-value, globally-routable-uri Enable local dispatch Enable a server%2 ___ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error,please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus. ___ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
