2 Jan 2007 15:33
Re: Accounting using dialog and sst module
Do you know any UA which support SST timers?
On 1/2/07, Ron Winacott <ronw-nIlK2fN7gY0WhyVFc8JwjA@public.gmane.org> wrote:
On Tuesday 02 January 2007 9:00 am, Asterisk Expert wrote:
> Hello Ron,
> Thanks for your response. Now I'm able to start and destroy dialog
> properly. But I guess dialog timer is reset when openser receives "Update"
> message. I looked in dialog and sst module codes and found that they rely
> on UA to send "Update" message periodically to keep the dialog active. I
> dont think it is good idea to rely on clients as all clients may not be
> sending "UPDATE" messages after call is established. Correct me if I'm
> wrong. Also I think that I may have to change source code of dialog or sst
> to send bye if any UA is broken and can't send "Bye" in case of dialog
> timeout.
But waiting and acting on UPDATE/re-INVITE is what SST (RFC-4028) is all
about. The SST module is an implementation of the RFC for a SIP proxy. One of
the clients in the dialog must support timers (SST) and the module will
figure out who does and request SST timers (UPDATE/RE-INVITE) from that UAC
if nether UAC want to use timers.
As for the proxy sending a BYE on a timed out SST/dialog, this is against the
RFC. A proxy can't inject a SIP message into the conversation like that.
Also, there is the technical issue that nether the SST or dialog module
track/save enough information (as far as routing goes) to send the BYE.
The SST module is for statefull proxy servers to allow them to free up locally
held resources when a dialog times out without having a default dialog time
out value of 24 hours, and causing one of the UAC's to "ping" the signal path
to let everyone on it know the conversation is still on.
Without one side supporting timers (SST) I would suggest you do not use SST
for any kind of accounting information because as per the RFC, one side must
support timers/SST for it to work.
ronw
--
Ron Winacott - SOMA Networks, Inc.
Work: 1-416-348-1580 - ronw-nIlK2fN7gY0WhyVFc8JwjA@public.gmane.org
---
Programming today is a race between software engineers striving to build
bigger and better idiot-proof programs, and the Universe trying to produce
bigger and better idiots. So far, the Universe is winning
- Unknown
--
Regards
Asterisk Expert
<div> <p>Do you know any UA which support SST timers?<br><br></p> <div> <span class="gmail_quote">On 1/2/07, Ron Winacott <<a href="mailto:ronw@...">ronw@...</a>> wrote:</span> <blockquote class="gmail_quote">On Tuesday 02 January 2007 9:00 am, Asterisk Expert wrote:<br>> Hello Ron,<br>> Thanks for your response. Now I'm able to start and destroy dialog <br>> properly. But I guess dialog timer is reset when openser receives "Update"<br>> message. I looked in dialog and sst module codes and found that they rely<br>> on UA to send "Update" message periodically to keep the dialog active. I <br>> dont think it is good idea to rely on clients as all clients may not be<br>> sending "UPDATE" messages after call is established. Correct me if I'm<br>> wrong. Also I think that I may have to change source code of dialog or sst <br>> to send bye if any UA is broken and can't send "Bye" in case of dialog<br>> timeout.<br><br>But waiting and acting on UPDATE/re-INVITE is what SST (RFC-4028) is all<br>about. The SST module is an implementation of the RFC for a SIP proxy. One of <br>the clients in the dialog must support timers (SST) and the module will<br>figure out who does and request SST timers (UPDATE/RE-INVITE) from that UAC<br>if nether UAC want to use timers.<br><br>As for the proxy sending a BYE on a timed out SST/dialog, this is against the <br>RFC. A proxy can't inject a SIP message into the conversation like that.<br>Also, there is the technical issue that nether the SST or dialog module<br>track/save enough information (as far as routing goes) to send the BYE. <br><br>The SST module is for statefull proxy servers to allow them to free up locally<br>held resources when a dialog times out without having a default dialog time<br>out value of 24 hours, and causing one of the UAC's to "ping" the signal path <br>to let everyone on it know the conversation is still on.<br><br>Without one side supporting timers (SST) I would suggest you do not use SST<br>for any kind of accounting information because as per the RFC, one side must <br>support timers/SST for it to work.<br><br>ronw<br><br>--<br>Ron Winacott - SOMA Networks, Inc.<br>Work: 1-416-348-1580 - <a href="mailto:ronw@...">ronw@...</a><br><br>---<br>Programming today is a race between software engineers striving to build <br>bigger and better idiot-proof programs, and the Universe trying to produce<br>bigger and better idiots. So far, the Universe is winning<br> - Unknown<br> </blockquote> </div> <br><br clear="all"><br>-- <br>Regards<br>Asterisk Expert </div>
RSS Feed