302 moved temporarily message

1. Brekeke Product Name and version:

2. Java version:

3. OS type and the version:

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

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

6. Your problem:

There is a problem when using the Call Forward on No Reply function of our VoIP board. It seem that BBS is modifying the contact in 302 moved temporarily message which is causing this problem. Is there any solution to this?

Thanks.

I know this.. and it was fixed in the latest version..
let's try new one.

Actually, my old version just got expired yesterday. I tried the new one today and now it's not working under any condition(unconditional, busy, no reply) !!

Is there any settings on BSS that I need to change?

Thanks.

Here is the Ethereal log

No. Time Source Destination Protocol Info
1 0.000000 192.168.1.7 192.168.1.157 SIP/SDP Request: INVITE sip:501@192.168.1.157, with session description
2 0.000746 192.168.1.157 192.168.1.7 SIP Status: 100 Trying
3 0.002136 192.168.1.157 192.168.1.5 SIP/SDP Request: INVITE sip:501@192.168.1.5:5060;transport=udp, with session description
4 0.035024 192.168.1.5 192.168.1.157 SIP Status: 302 Moved Temporarily
5 0.035507 192.168.1.157 192.168.1.7 SIP Status: 302 Moved Temporarily
6 0.040426 192.168.1.7 192.168.1.157 SIP Request: ACK sip:501@192.168.1.157
7 0.042737 192.168.1.157 192.168.1.5 SIP Request: ACK sip:501@192.168.1.5:5060;transport=udp
8 0.044186 192.168.1.7 192.168.1.5 SIP/SDP Request: INVITE sip:702@192.168.1.5, with session description
9 0.072449 192.168.1.5 192.168.1.7 SIP Status: 404 Not Found
10 0.080386 192.168.1.7 192.168.1.5 SIP Request: ACK sip:702@192.168.1.5

8 0.044186 192.168.1.7 192.168.1.5 SIP/SDP Request: INVITE sip:702@192.168.1.5, with session description
9 0.072449 192.168.1.5 192.168.1.7 SIP Status: 404 Not Found
10 0.080386 192.168.1.7 192.168.1.5 SIP Request: ACK sip:702@192.168.1.5

The log seems 192.168.1.7 sent the INVITE to 702@192.168.1.5 without SIP Server and 192.168.1.5 returned 404 (Not Found).
Is 702@192.168.1.5 active?

701 and 702 are associate with 192.168.1.7
501 is associate with 192.168.1.5

The INVITE should be sent to 702@192.168.1.7.

Can I see the response packet 302 which came from 192.168.1.5?

Is this what you're looking for?
Can I upload any files on this forum?

No. Time Source Destination Protocol Info
4 0.035024 192.168.1.5 192.168.1.157 SIP Status: 302 Moved Temporarily

Frame 4 (417 bytes on wire, 417 bytes captured)
Ethernet II, Src: 38:c7:44:71:59:05 (38:c7:44:71:59:05), Dst: Dell_00:0b:98 (00:12:3f:00:0b:98)
Internet Protocol, Src: 192.168.1.5 (192.168.1.5), Dst: 192.168.1.157 (192.168.1.157)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)
Session Initiation Protocol
Status-Line: SIP/2.0 302 Moved Temporarily
Status-Code: 302
Resent Packet: False
Message Header
Via: SIP/2.0/UDP 192.168.1.157:5060;branch=z9hG4bK76adac9bef1-936fb44-64080692
Via: SIP/2.0/UDP 192.168.1.7:5060;branch=z9hG4bK387509189;rport=5060
From: "TC7-1" <sip:701@192.168.1.157>;tag=0-404044530
SIP Display info: "TC7-1"
SIP from address: sip:701@192.168.1.157
SIP tag: 0-404044530
To: <sip:501@192.168.1.157>
SIP to address: sip:501@192.168.1.157
Call-ID: 32503690602141367580@192.168.1.7
CSeq: 6 INVITE
Contact: sip:702@192.168.1.5
Contact Binding: sip:702@192.168.1.5
URI: sip:702@192.168.1.5\r
SIP contact address: sip:702@192.168.1.5\r
Content-Length: 0

No. Time Source Destination Protocol Info
5 0.035507 192.168.1.157 192.168.1.7 SIP Status: 302 Moved Temporarily

Frame 5 (337 bytes on wire, 337 bytes captured)
Ethernet II, Src: Dell_00:0b:98 (00:12:3f:00:0b:98), Dst: 38:c7:44:71:59:07 (38:c7:44:71:59:07)
Internet Protocol, Src: 192.168.1.157 (192.168.1.157), Dst: 192.168.1.7 (192.168.1.7)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)
Session Initiation Protocol
Status-Line: SIP/2.0 302 Moved Temporarily
Status-Code: 302
Resent Packet: False
Message Header
Via: SIP/2.0/UDP 192.168.1.7:5060;branch=z9hG4bK387509189;rport=5060
From: "TC7-1" <sip:701@192.168.1.157>;tag=0-404044530
SIP Display info: "TC7-1"
SIP from address: sip:701@192.168.1.157
SIP tag: 0-404044530
To: <sip:501@192.168.1.157>
SIP to address: sip:501@192.168.1.157
Call-ID: 32503690602141367580@192.168.1.7
CSeq: 6 INVITE
Contact: sip:702@192.168.1.5
Contact Binding: sip:702@192.168.1.5
URI: sip:702@192.168.1.5\r
SIP contact address: sip:702@192.168.1.5\r
Content-Length: 0

As you can see, the 192.168.1.5 sent the response 302 including "Contact: sip:702@192.168.1.5" and SIP Server forwarded it to the 192.168.1.7.

In this result, the 192.168.1.7 sent the second INVITE to "sip:702@192.168.1.5".

But your first log seems the 192.168.1.5 rejected the second INVITE by the response 404...

I think the 192.168.1.5 should accept the second INVITE..

501 is on board 192.168.1.5
701,702 is on board 192.168.1.7

So the way it should work is that
1. 701@192.168.1.7 INVITE 501@192.168.1.5
2. 501@192.168.1.5 Moved Temporarily to 702@192.168.1.7
3. 701@192.168.1.7 INVITE 702@192.168.1.7

Right now Step 3 becomes 701@192.168.1.7 INVITE 702@192.168.1.5
I don't understand why the IP address has been modified.

This is what supposed to happen: (v2.0.7.2)

No. Time Source Destination Protocol Info
1 0.000000 192.168.1.7 192.168.1.157 SIP/SDP Request: INVITE sip:501@192.168.1.157, with session description
2 0.000744 192.168.1.157 192.168.1.7 SIP Status: 100 Trying
3 0.010074 192.168.1.157 192.168.1.5 SIP/SDP Request: INVITE sip:501@192.168.1.5:5060;transport=udp, with session description
4 0.033120 192.168.1.5 192.168.1.157 SIP Status: 302 Moved Temporarily
5 0.041333 192.168.1.157 192.168.1.7 SIP Status: 302 Moved Temporarily
6 0.060434 192.168.1.7 192.168.1.157 SIP Request: ACK sip:501@192.168.1.157
7 0.061060 192.168.1.157 192.168.1.5 SIP Request: ACK sip:501@192.168.1.5:5060;transport=udp
8 0.064204 192.168.1.7 192.168.1.157 SIP/SDP Request: INVITE sip:702@192.168.1.157:5060, with session description
9 0.064828 192.168.1.157 192.168.1.7 SIP Status: 100 Trying
10 0.066868 192.168.1.157 192.168.1.7 SIP/SDP Request: INVITE sip:702@192.168.1.7:5060;transport=udp, with session description
11 0.114538 192.168.1.7 192.168.1.157 SIP Status: 100 Trying
12 0.119125 192.168.1.7 192.168.1.157 SIP Status: 180 Ringing
13 0.119602 192.168.1.157 192.168.1.7 SIP Status: 180 Ringing
14 3.536630 192.168.1.7 192.168.1.157 SIP Request: CANCEL sip:702@192.168.1.157:5060
15 3.537475 192.168.1.157 192.168.1.7 SIP Status: 200 OK
16 3.537622 192.168.1.157 192.168.1.7 SIP Request: CANCEL sip:702@192.168.1.7:5060;transport=udp
17 3.583810 192.168.1.7 192.168.1.157 SIP Status: 200 Ok
18 3.587968 192.168.1.7 192.168.1.157 SIP Status: 487 Request Cancelled
19 3.588415 192.168.1.157 192.168.1.7 SIP Status: 487 Request Cancelled
20 3.610137 192.168.1.7 192.168.1.157 SIP Request: ACK sip:702@192.168.1.157:5060
21 3.610664 192.168.1.157 192.168.1.7 SIP Request: ACK sip:702@192.168.1.7:5060;transport=udp

No. Time Source Destination Protocol Info
5 0.035507 192.168.1.157 192.168.1.7 SIP Status: 302 Moved Temporarily

Frame 5 (337 bytes on wire, 337 bytes captured)
Ethernet II, Src: Dell_00:0b:98 (00:12:3f:00:0b:98), Dst: 38:c7:44:71:59:07 (38:c7:44:71:59:07)
Internet Protocol, Src: 192.168.1.157 (192.168.1.157), Dst: 192.168.1.7 (192.168.1.7)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)
Session Initiation Protocol
Status-Line: SIP/2.0 302 Moved Temporarily
Status-Code: 302
Resent Packet: False
Message Header
Via: SIP/2.0/UDP 192.168.1.7:5060;branch=z9hG4bK387509189;rport=5060
From: "TC7-1" <sip:701@192.168.1.157>;tag=0-404044530
SIP Display info: "TC7-1"
SIP from address: sip:701@192.168.1.157
SIP tag: 0-404044530
To: <sip:501@192.168.1.157>
SIP to address: sip:501@192.168.1.157
Call-ID: 32503690602141367580@192.168.1.7
CSeq: 6 INVITE
Contact: sip:702@192.168.1.5
Contact Binding: sip:702@192.168.1.5
URI: sip:702@192.168.1.5\r
SIP contact address: sip:702@192.168.1.5\r
Content-Length: 0

Comparing the working (v.2.0.7.2) and not working case (v.2.1.6.2),
we can see that for 302 Moved Temporarily,
v.2.0.7.2 re-writes the sip contact as 702@192.168.1.157, while
v.2.1.6.2 re-writes the sip contact as 702@192.168.1.5.

How do I keep it the correct way, as in v.2.0.7.2, where the INVITE is sent to BSS first.