MTU Size Problem

[LJDirk]

Hello at all,

Setup:

Home private Lan with ACW (Avaya Communicator for Windows) will be connect to the IPO Server Edition 9.1 over an SBC in the Customers DMZ. SBC with all Settings for Remoteworker are set proberly. One-X Mobile can connect right with SIP and Presents. Also Relaying Ports 9443, 5222 & 5223 how seen in the SIP Register Message / wrote in the Docu. Using TLS.

SIP Register will be done, but no Presentsserver is aviable (tell the ACW).

Make Wireshark and see, the attached Messesage if transfering Information over Port 9443 from Source IP xxx.xxx.xxx.5 (that´s the Customers Firewall)

Now i think it´s a MTU Problem in Firewall, but Customer don´t want to change the MTU Size at the moment. Now the Question: can i reduce the MTU Size at IPO SE Site? Thinking default is 1500?!?
The Connection from Customers LAN (Routing over SBC) will be made without any Problems. All Services are aviable on ACW.



Obviously it is of eminent relevance, that I this, what you celeprate, not optimally effective assume, since the integrate of you in the communicative system as code related terms with me no explosive associations in mental-empirical reproduction process of the mind.

 

[kyle555]

is your xmpp domain the same as the inside/outside fqdn?
do you have a DNS entry for the xmpp service advertising it's port?

if you turn up logging in the portal, somewhere in the log files you should see yourself coming in IF you got everything right but mtu. Can't see why Communicator to the IPO service for SIP would work but XMPP to a different service on the same box wouldn't because of MTU.

 

[LJDirk]

Yes, XMPP ist overall the same (only Primary Server installed). Using Split-DNS. From external DNS-A is pointing to the public xxx.xxx.xxx.5 IP from the Firewall.

I think the Port will be provided thrue the SIP Regitration. No DNS-SRV Query will be done from ACW - don´t see it in Wireshark, only DNS-A.

Obviously it is of eminent relevance, that I this, what you celeprate, not optimally effective assume, since the integrate of you in the communicative system as code related terms with me no explosive associations in mental-empirical reproduction process of the mind.

 

[kyle555]

well, you know what you could try...

Wireshark from your PC, and "tshark -i eth0 port 9443 -w /tmp/9443traffic.pcap" on the server edition and see what the MTU is on the inside to the IPO server to compare the size.

I did see a support article saying Avaya's never tested changing MTU on a server edition so you might be on your own there if that's the case.

 

[LJDirk]

at the moment i wouldn´t it try. Only evidence gather with the customer to weigh the advantages and disadvantages and then to make a decision.
I read out: there´s no official Way to change it.

Will be calling the Customer and see, what the LOGs from the Firwall say and than we´ll see... Thanks a lot and nice Weekend.

Obviously it is of eminent relevance, that I this, what you celeprate, not optimally effective assume, since the integrate of you in the communicative system as code related terms with me no explosive associations in mental-empirical reproduction process of the mind.