Russ,
Response inline.
--- Russ Daigle <[EMAIL PROTECTED]> wrote:
> Thanks for your response.
>
> Remember, in my scenario the UAC died. Therefore,
> it will not be
> having any timers that expire nor will it send any
> CANCELs.
> Therefore, it is completely dependent on the proxy B
> or UAS C to
> clean up. (And please no responses about UAC
> solutions to this
> problem, because the whole point is to test
> proxy/UAS scenarios with
> somewhat flaky UACs. It "dies" because it is
> suppose to!:)
In real world, both UAC and UAS shall start
ringing/alerting timer so that it can clear the call.
In your case, UAS (and/or stateful proxy) shall
terminate the call on that timer expiry.
You can imagine what happen if UAS dies. In that case,
timer at UAC shall help terminating the call.
Therefore, if UAC dies then UAS shall not be ringing
forever and vice-versa.
> I can imagine that a UAS can be implemented to just
> let the phone
> ring and ring and ring. Is there anywhere in any
> RFC that indicates
> UAS's or proxies should terminate an incoming call
> if it isn't
> answered within a certain time?
As far as I know, RFC3261 does not talk much about the
state machine(and timer) of UAC, UAS or Proxy core.
Though, it(RFC3261) describes Transaction state
machine in sec 17.
> Thinking of analog phones, as long as
> the caller doesn't hang up and the callee doesn't
> have answering-
> machine/voicemail, the phone will keep ringing and
> ringing and
> ringing at the callee.
No, that's not true. Even in PSTN also, PSTN
Exchnage(both calling side and called side) starts
Alerting timer. On expiry of that timer, call is
terminated.
> So... I am definitely encountering an indefinite
> 486 busy response
> with a couple different SIP phones (and an analog
> phone connected to
> a cisco gateway). This 486 never clears up, unless
> the phone is
> answered (and hung up).
I shall be really surprised if you say that you are
hearing ringtone indefinitely. I would expect cisco
gateway to release this call after alert timeout.
However, if analog phone is kept offhook then it can
not receive incoming call and it shall be considered
as busy. This may be the reason why cisco gateway is
giving 486 for your case. If you hangup then it shall
be able to receive incoming call.
> Would you expect a transaction stateful proxy would
> cancel a call if
> it rings for so long without being answered? I wish
> the answer was
> yes, but I suspect the answer is that typical UAS
> and proxy will just
> let the phone continue ringing.... hence anybody
> else calling will
> encounter a 486 busy.
>
> This perhaps is more of a testing problem, than
> real-world problem.
> However, my situation is a test-setup, hence is a
> real-world problem
> for me.
>
> Nonetheless, for automation testing, I really wish
> there was a way
> to have the UAS or proxy clear up the line in an
> automatable manner.
>
> -Russ
>
__________________________________________________________
Yahoo! India Answers: Share what you know. Learn something new
http://in.answers.yahoo.com/
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
