Invalid SIP Packet when upgrade to latest version

1. Brekeke Product Name and version:

SIP Server Standard, Version 2.3.7.4

2. Java version:

1.6.0_14

3. OS type and the version:

Ubuntu 8.10 LTS

4. UA (phone), gateway or other hardware/software involved:

n/a

5. Select your network pattern from http://www.brekeke-sip.com/bbs/network/ ... terns.html :

n/a

6. Your problem:

We are running SIP Server Standard version 2.2.7.8 on another machine and we are trying to upgrade it to version 2.3.7.4 on a separate machine. All installation and configuration went fine and are exactly the same but when making calls the call is dropped as soon as is answered by the other site. On the CDR's we see "Invalid SIP packet" as a result.

what kind of SIP client are you using?

can you paste the SIP packet you got "Invalid SIP packet" message?

what kind of SIP client are you using?

For this test I am using eyeBeam and I have tried G711 and G729 codecs. With the same softphone and same configuration on the previous version of SIP Server (2.3.7.4) everything works fine.

can you paste the SIP packet you got "Invalid SIP packet" message?

The "Invalid SIP packet" is shown under result column when viewing the Calls from the SIP Server. When capturing the packets on the SIP Server, I do not see it in the SIP messages.

I'm using eyeBeam without any issue..
Which version of eyeBeam are you using??
Mine is 1.5.20 (54437).. I think it is the latest version.

Are you using any DialPlan rule?

I have eyeBeam version 1.5.20 build 54436

I have deleted the latest version of SIP Server and I have installed version 2.2.7.8 (as the one I have on the other machine) and now tests are successful. I will stay with the old one as I have to finish with migration and be VERY VERY careful on any future upgrade.

Do you have any DialPlan rule?
If so, it will be a cause of the issue..


Also, is there a firewall between the eyeBeam and the SIP Server??

I am also experiencing the same problem in v2.3.7.4/286. Occasionally, calls don't complete or get hung-up on immediately. On another server which is IDENTICALLY CONFIGURED we are running v2.3.6.0/286 and everything works absolutely perfectly.

How do we get Brekeke to fix v2.3.7.4????

Hi

Can you put your packet trace at http://pcapr.net/ ?