BYE requests are not answered correctly

1. Brekeke Product Name and version:

2. Java version:

3. OS type and the version: Win2003 SP2

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

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

6. Your problem:
A BYE request is received from the other end (Global IP somewhere on the Internet). When this is received I aspect the SIP Server to forward this to the UA (SW-phone is located on same hardware as SIP server) so that the UA can reply with 200 OK and the call will be ended. But this never happends. What happends is that a BYE request is sent back to to other end. This goes on until until there is an timeout but the SW-phoen keeps sending RTP packets.

Any idea on whats causing this?

Kind regards,

Fredrik

What is the ITSP?

Can you give us information about the template questions
1. 2. and 4.

Hi,

Sorry about missing infromation. My first post here...

1. Brekeke Product Name and version: SIP Server 2.0.7.2

2. Java version: 1.6.0.02

3. OS type and the version: Win2003 SP2

4. UA (phone), gateway or other hardware/software involved:
UA is eyeBeam 1.5, Intertex Surfinbird firewall. UA is located on the same machine as SIP server.

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

Can you paste the BYE packet (both receiving and sending) here?

Hi,
Thanks for your answer. I don't know how to post a trace file here so I just copy the contents of the packets.

These packets are sent about 10 times in each direction. Finally a timeout ends the BYE requests.

6 21.071521 194.0.210.200 88.131.46.219 SIP Request: BYE sip:02073367100@88.131.46.219:5060
Record-Route: <sip:194.0.210.200;lr=on;ftag=as4e13cc18>
Via: SIP/2.0/UDP 194.0.210.200;branch=z9hG4bKbb0d.ddeec274.0
Via: SIP/2.0/UDP 194.0.210.133:5060;branch=z9hG4bK335b5048;rport=5060
Route: <sip:194.0.210.200;lr=on;ftag=0c048b33>,<sip:88.131.46.219:5060;lr>
From: "0046709931762"<sip:0046709931762@194.0.210.200>;tag=as4e13cc18
To: "Local SIP Proxy"<sip:02073367100@88.131.46.219>;tag=0c048b33
Call-ID: NzJmOTA1ZTdlYWEwODBjYjU3NDdmYmE1NWU1MGMwMGE.
CSeq: 102 BYE
User-Agent: Simwood SIP CLuster
Max-Forwards: 18
Content-Length: 0



7 21.072516 88.131.46.219 194.0.210.200 SIP Request: BYE sip:02073367100@127.0.0.1:27178
Record-Route: <sip:88.131.46.219:5060;lr>
Record-Route: <sip:194.0.210.200;lr=on;ftag=as4e13cc18>
Via: SIP/2.0/UDP 88.131.46.219:5060;branch=z9hG4bK19a61b2604949bd9.3
Via: SIP/2.0/UDP 194.0.210.200;branch=z9hG4bKbb0d.ddeec274.0
Via: SIP/2.0/UDP 194.0.210.133:5060;branch=z9hG4bK335b5048;rport=5060
Route: <sip:194.0.210.200;lr=on;ftag=0c048b33>
Route: <sip:88.131.46.219:5060;lr>
From: "0046709931762"<sip:0046709931762@127.0.0.1>;tag=as4e13cc18
To: "Local SIP Proxy"<sip:02073367100@127.0.0.1>;tag=0c048b33
Call-ID: NzJmOTA1ZTdlYWEwODBjYjU3NDdmYmE1NWU1MGMwMGE.
CSeq: 102 BYE
User-Agent: Simwood SIP CLuster
Max-Forwards: 17
Content-Length: 0

Do ACK packets have any problem?

I think the Route: headers were not correct.
Can you ask about this thing to your ITSP?