28 Jul
2005
28 Jul
'05
6:44 a.m.
Hi!
What should happen if the invite_timer expires and there is no failure
route defined?
In my case happens nothing, the phone is still ringing. Shouldn't
openser (CVS) cancel the call and responds with 408?
If I define a failure_route, everything works fine.
regards,
klaus
debuglog:
9(21752) DEBUG: reply relayed. buf=0x81148d0: SIP/2.0 1...,
shmem=0x40606568: SIP/2.0 1
9(21752) reply_received: FR_INV_TIMER = 10
9(21752) DEBUG: add_to_tail_of_timer[1]: 0x40604d7c
9(21752) DEBUG:destroy_avp_list: destroying list (nil)
9(21752) receive_msg: cleaning up
after 10 seconds:
10(21756) DEBUG: timer routine:1,tl=0x40604d7c next=(nil)
10(21756) DEBUG: final_response_handler: transaction silently dropped
(0x40604c50)
10(21756) DEBUG: add_to_tail_of_timer[2]: 0x40604c98
phone is still ringing, some seconds later:
10(21756) DEBUG: timer routine:2,tl=0x40604c98 next=(nil)
10(21756) DEBUG: wait_handler : removing 0x40604c50 from table
10(21756) DEBUG: delete transaction 0x40604c50
10(21756) DEBUG: wait_handler : done
phone is still ringing :-(
28 Jul
28 Jul
7:45 p.m.
Hi Klaus,
that's the effect of the so called feature "noisy_ctimer" added by Jiri
- if there is no interest in getting the final reply (as acc, failure
routes, callbacks, etc), when the timer hits, the transaction will be
silently discarded - the callee phone will keep ringing infinitely until
caller cancels the call.
you can disable this feature by setting the tm param "noisy_ctimer". See
http://www.openser.org/docs/modules/0.9.x/tm.html#AEN173
regards,
bogdan
Klaus Darilion wrote:
Hi!
What should happen if the invite_timer expires and there is no failure
route defined?
In my case happens nothing, the phone is still ringing. Shouldn't
openser (CVS) cancel the call and responds with 408?
If I define a failure_route, everything works fine.
regards,
klaus
debuglog:
9(21752) DEBUG: reply relayed. buf=0x81148d0: SIP/2.0 1...,
shmem=0x40606568: SIP/2.0 1
9(21752) reply_received: FR_INV_TIMER = 10
9(21752) DEBUG: add_to_tail_of_timer[1]: 0x40604d7c
9(21752) DEBUG:destroy_avp_list: destroying list (nil)
9(21752) receive_msg: cleaning up
after 10 seconds:
10(21756) DEBUG: timer routine:1,tl=0x40604d7c next=(nil)
10(21756) DEBUG: final_response_handler: transaction silently dropped
(0x40604c50)
10(21756) DEBUG: add_to_tail_of_timer[2]: 0x40604c98
phone is still ringing, some seconds later:
10(21756) DEBUG: timer routine:2,tl=0x40604c98 next=(nil)
10(21756) DEBUG: wait_handler : removing 0x40604c50 from table
10(21756) DEBUG: delete transaction 0x40604c50
10(21756) DEBUG: wait_handler : done
phone is still ringing :-(
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
9:31 p.m.
Bogdan-Andrei Iancu wrote:
Hi Klaus,
that's the effect of the so called feature "noisy_ctimer" added by Jiri
- if there is no interest in getting the final reply (as acc, failure
routes, callbacks, etc), when the timer hits, the transaction will be
silently discarded - the callee phone will keep ringing infinitely until
caller cancels the call.
What will be discarded? The transaction or the timer event? If the
transaction will be discarded, I guess the CANCEL won't match a
transaction anymore.
klaus
you can disable this feature by setting the tm param "noisy_ctimer". See
http://www.openser.org/docs/modules/0.9.x/tm.html#AEN173
regards,
bogdan
Klaus Darilion wrote:
Hi!
What should happen if the invite_timer expires and there is no failure
route defined?
In my case happens nothing, the phone is still ringing. Shouldn't
openser (CVS) cancel the call and responds with 408?
If I define a failure_route, everything works fine.
regards,
klaus
debuglog:
9(21752) DEBUG: reply relayed. buf=0x81148d0: SIP/2.0 1...,
shmem=0x40606568: SIP/2.0 1
9(21752) reply_received: FR_INV_TIMER = 10
9(21752) DEBUG: add_to_tail_of_timer[1]: 0x40604d7c
9(21752) DEBUG:destroy_avp_list: destroying list (nil)
9(21752) receive_msg: cleaning up
after 10 seconds:
10(21756) DEBUG: timer routine:1,tl=0x40604d7c next=(nil)
10(21756) DEBUG: final_response_handler: transaction silently dropped
(0x40604c50)
10(21756) DEBUG: add_to_tail_of_timer[2]: 0x40604c98
phone is still ringing, some seconds later:
10(21756) DEBUG: timer routine:2,tl=0x40604c98 next=(nil)
10(21756) DEBUG: wait_handler : removing 0x40604c50 from table
10(21756) DEBUG: delete transaction 0x40604c50
10(21756) DEBUG: wait_handler : done
phone is still ringing :-(
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
9:48 p.m.
Klaus Darilion wrote:
Bogdan-Andrei Iancu wrote:
Both the transaction and event are discarded. The CANCEL - since it will
not match any transaction, it must be routed from script in the same way
as the INVITE - that's the reason I do *not* like this "feature".
regards,
bogdan
Hi Klaus,
that's the effect of the so called feature "noisy_ctimer" added by
Jiri - if there is no interest in getting the final reply (as acc,
failure routes, callbacks, etc), when the timer hits, the transaction
will be silently discarded - the callee phone will keep ringing
infinitely until caller cancels the call.
What will be discarded? The transaction or the timer event? If the
transaction will be discarded, I guess the CANCEL won't match a
transaction anymore.
klaus
7127
days inactive
7128
days old
3 comments
2 participants
participants (2)
-
Bogdan-Andrei Iancu -
Klaus Darilion