Re: CallSignalHandlerNumber

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> > > But I can imagine that average dialing phase (from setup to altering -
> > > PDD)
> >
> > Are you sure NOW that this is what PDD stands for? ;)
> >
> > > would be longer with CallSignalHandlerNumber=1. Another situation when
> >
> > Why? I can't see any relation. We process Setup and return. How can this
> > influent the time between Setup sent and Alerting received?
>
> It does not matter how do we define PDD. If we assume it is time between
> the Setup sent from calling party and ringback tone -

As we agreed early this year ;) we may be getting RBT just after we've send 
Setup to the calling party with FastStarts in it. So RBT and PDD is not 
affected in this case.

> CallSignalHandlerNumber can affect PDD. Every time Setup is received it has
> to wait until messages received from sockets that are earlier on the socket
> select list are processed. The same is with Alerting, CallProceeding and
> other Q.931 messages.

OK, I see your point... CallSignalHandlerNumber hits performance, agree. But 
do I need more performance than I have with one ProxyHandleThread?... 
Everithing depends on what you expect from a setup. I'm happy with one - 
ProxyH(0) - thread.

Andrey.



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
List: Openh323gk-users@lists.sourceforge.net
Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549
Homepage: http://www.gnugk.org/

[Index of Archives]     [SIP]     [Open H.323]     [Gnu Gatekeeper]     [Asterisk PBX]     [ISDN Cause Codes]     [Yosemite News]

  Powered by Linux