This content has been marked as final. Show 5 replies
Here is an explanation of these parameters:
The 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.
sipappsessionid is the id of the sip application session; used with encodeURI and some other mechanisms
You can find an explanation on these custom params here:
Look for Table 1-4 WebLogic SIP Server Parameters
Regarding restricting size of headers:
RFC 3261 does not have any restriction on the size of any header in any SIP message. Other implementations having restrictions are not adhering to the RFC, imho.
Having said that, to reduce the size of header you could use the compact config option, however that will only compact the header name ie, From: will f:
You will get some saving but that wont be significant.
We identified the relative available attributes which could probably affect the contact header information as below:
3. from the transport web page it is found that we can disble the sideways forwarding by removing the network-access from config.xml - will this supress the wlsscid insertion? and from where we can disbale this?
By enabling this Options will the Wlsscid insertion can be avoided ?.Please update.
currently the configuration is standalone with cluster diabled...but the wlsscid is populating, please provide instructions which parameters need to be modified to avoid this insertion
Edited by: user8388560 on Aug 11, 2009 2:55 AM
Edited by: user8388560 on Aug 11, 2009 3:00 AM