Timeout to wait for Request Cancelled SIP message

1. Brekeke Product Name and version:
BSS, 2.4.8.6

2. Java version:
1.6.0_25

3. OS type and the version:
linux centos 5.5

4. UA (phone), gateway or other hardware/software involved:
doesn't matter

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

6. Your problem:
Refering to http://www.brekeke-sip.com/bbs/viewtopi ... ght=#24112 where timeout commands were introduced, my question is if there is any timeout command to wait for Request Cancelled once CANCEL message was fired.

(BSS) ----- INVITE ------> (terminator)
(BSS) <----- Trying ------ (terminator)
(BSS) <----- Session Progress ------ (terminator)
... and here the question...
(BSS) ----- CANCEL -----> (terminator)
(BSS) <----- OK ----- (terminator)
no Request Cancelled sent from (terminator)

is there any way to tear down the connection.

Thanks in advance.

create dial plan rule for the call and there is &net.sip.timeout.ringing in deploy patterns variables

Hi

hope wrote:create dial plan rule for the call and there is &net.sip.timeout.ringing in deploy patterns variables

i have it implemented in Advanced Configuration for 50000 ms, but it does not do the trick.

Does not work even if you set 50000 at [Ringing Timeout (ms)] in the [Configuration]->[SIP] page?

Nope it does not work at all.

(BSS) ----- CANCEL -----> (terminator)
(BSS) <----- OK ----- (terminator)
Those two messages are connected with: CANCELing the request and in almost the same time OK which says that sb has pick up the phone.

If there is no Request Cancelled sent from terminator BSS should tear down this attempt once timeout is reached.

Does your "OK" means "200 OK" for INVITE?
I supposed it is "200 OK" for CANCEL..


In your situation, the session is not closed with the Ringing Timeout because it has been accepted!

For closing the session, the UAC may need to send BYE after it receives "200 OK". Or the UAS may need to send BYE after it receives CANCEL.