We recently migrated to Session Manager 6.3 from an old version 5.2 SES. We have SIP endpoints that we need to establish calls to that are registered to SM. I believe I read somewhere that in SM 6.3 the SIP stack was increased to add some Avaya proprietary stuff, stuff we don't need in our environment. I see packets being fragmented coming out of the SM because the SIP INVITE is larger than the 1500 byte MTU of the Linux server.
I am looking for a way to strip out some of the unnecessary stuff in Session Manager to try to reduce the packet size.
Mostly we are able to connect anyway but we have a few sites that are connected via satellite. On these sites the INVITE never makes to the SIP endpoint. I have tried setting "Support Request History" to N on the SIP trunk in CM but that didn't seem to have any effect.
I don't think I can simply adjust the MTU in SM since in the newer versions we don't have root access. I'm not sure that would help anyway since the network will probably need to fragment the packet anyway farther down stream.
Any assistance is greatly appreciated.
I am looking for a way to strip out some of the unnecessary stuff in Session Manager to try to reduce the packet size.
Mostly we are able to connect anyway but we have a few sites that are connected via satellite. On these sites the INVITE never makes to the SIP endpoint. I have tried setting "Support Request History" to N on the SIP trunk in CM but that didn't seem to have any effect.
I don't think I can simply adjust the MTU in SM since in the newer versions we don't have root access. I'm not sure that would help anyway since the network will probably need to fragment the packet anyway farther down stream.
Any assistance is greatly appreciated.