How IPO respond to jumbo frames and/or fragmented packets for SIP messages

[LegoTajkun]

Hi,
could not find any detains at Avaya DOCs for handling at IPO for:
- jumbo frames
- fragmented packets
for SIP messages.

Did somebody have any info from doc or from real life


APDS - Avaya Midmarket Solutions
AIPS - Avaya IP Office™ Platform
ACSS - Avaya IP Office™ Platform

 

[janni78]

If you use TCP it shouldn't be an issue, with UDP anything after 1500 characters will be ignored.

Usually safer to use TCP, some devices like when connecting to SM adds a lot of SIP-headers.
Also have a SIP provider that can sends larger SIP messages if the other party is using the same provider since they just pass-through what they get.

"Trying is the first step to failure..." - Homer

 

[LegoTajkun]

thank you janni78.
What about fragmented packets? I would say that those are also ignored by IPO - in some cases one provider sent sip invite in udp fragmented packets but non was shown in monitor app.

APDS - Avaya Midmarket Solutions
AIPS - Avaya IP Office™ Platform
ACSS - Avaya IP Office™ Platform

 

[janni78]

It doesn't seem to handle it with UDP, in that case you need to use TCP.

"Trying is the first step to failure..." - Homer