27 Jan
2006
27 Jan
'06
11:56 a.m.
my request goes through many SER servers( more than 5 and in the future it can be much
more ) and each one add headers before forwarding the message. So I prefered not to put
any constraint on SIP request size.
I will check the MTU and my network. but I m not sure that the problem is in the
network because when I send a PING "message" greater than 1500 byte, it is
sent without problem (the message is fragmented and the "more fragment" flag
of the first paquest is set to 1 so at the end we get a complete message).
Regards,
Arek Bekiersz <sip(a)perceval.net> a écrit : Hi,
IMHO it has nothing to do with SER.
I've experienced this before.
Check your MTU, your network and firewalls.
Limit size of SIP message by consume_credentials() and limit number of
codecs used.
--
Regards,
Arek Bekiersz
zaghouani hamdi wrote:
I used both. first UDP then I tried TCP .
*/Andrey Kouprianov /* a écrit :
Are you sending your message through UDP or TCP?
On 1/26/06, zaghouani hamdi wrote:
---------------------------------
Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels
pour appeler la France et l'international.Téléchargez la version beta.
hi,
I m using ser-0.8.14.
i m trying to send a SIP message from an SER server to another
SER server.
The length of this message is greater than 1500
Bytes(around 1600
Bytes) ,
so it is fragmented before being sent.
(in my case it's fragmented to 2 packets.)
then I check the SIP flow using ethereal I found that :
In the IP header of the first packet, the "more fragment" flag is
set to
"0" so at the reception the second
packet is ignored.
And we get at the receiver a SIP message which is not completed
.( we don t
receive all the SIP message).
is it SER who force that the sent message being less than 1500
bytes ?
>
> thinks a lot
>
> Hamdi