Re: [reSIProcate] resiprocate-devel Digest, Vol 33, Issue 25
Hello,
Any one knows how to use DNS to resolve this domain name into IP Address by
using resiprocate API?
which api is called ?
thanks!
------------------
fancy_xiao
2007-01-29
-------------------------------------------------------------
发件人：resiprocate-devel-request
发送日期：2007-01-19 05:27:00
收件人：resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
抄送：
主题：resiprocate-devel Digest, Vol 33, Issue 25
Send resiprocate-devel mailing list submissions to
resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
or, via email, send a message with subject or body 'help' to
resiprocate-devel-request@xxxxxxxxxxxxxxxxxxxx
You can reach the person managing the list at
resiprocate-devel-owner@xxxxxxxxxxxxxxxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of resiprocate-devel digest..."
Today's Topics:
1. Re: Session destroyed while in OnTerminated(..)
(Kovar, William (Bill))
2. Re: Session destroyed while in OnTerminated(..) (Scott Godin)
------------------------------------------------------------
From: "Kovar, William \(Bill\)" <bkovar@xxxxxxxxx>
To: "Scott Godin" <slgodin@xxxxxxxxxxxx>
<resiprocate-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [reSIProcate] Session destroyed while in OnTerminated(..)
Date: Thu18 Jan 2007 16:08:44 -0500
Scott,
You may have mis-understood me. I have an app thread that
controls/monitors one of N UAs, each running on their own DumThread but
sharing a single StackThread. Use of a single Stack thread across
multiple Dums is accomplished by adding user based switching in
MessageFilterRule. Works quite nicely for phone numbers, actually!!
In no situation does one Dum thread (UA) ever make a call on another Dum
thread. I don't do that kind of thread hopping.
What I am doing, which I believe is solvable with DumCommand, is this:
At the App thread, when I decide which UA to control, I directly call
session->end() from the App thread causing the problem I described,
namely, if OnTerminated() runs too long, the 200 OK response to the BYE
blows away the session/Dialog/etc.
So my question is: Will the use of DumCommand in this instance, from my
App thread, directed at a specific Dum thread, fix the sequence
problem??
Bill Kovar
bkovar@xxxxxxxxx
Avaya, Inc.
(732) 852-2609
_____
From: Scott Godin [mailto:slgodin@xxxxxxxxxxxx]
Sent: Thursday, January 18, 2007 3:56 PM
To: Kovar, William (Bill); resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [reSIProcate] Session destroyed while in
OnTerminated(..)
It is not legal to have multiple dum threads. All calls to
dum->process and the dum api's must be run from the same thread, or must
be protected.
http://www.resiprocate.org/DUM_Threading
From: Kovar, William (Bill) [mailto:bkovar@xxxxxxxxx]
Sent: Thursday, January 18, 2007 3:20 PM
To: Scott Godin; resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [reSIProcate] Session destroyed while in
OnTerminated(..)
I run 2 dums, 1 SipStack in my B2B, each using DumThread (2) and
the same StackThread(1).
So my calling session->end() from outside of the Dum thread is
causing this sequencing problem??
And posting the session->end() using DumCommand will get around
this sequencing problem??
Bill Kovar
bkovar@xxxxxxxxx
Avaya, Inc.
(732) 852-2609
_____
From: Scott Godin [mailto:slgodin@xxxxxxxxxxxx]
Sent: Thursday, January 18, 2007 2:17 PM
To: Kovar, William (Bill);
resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [reSIProcate] Session destroyed while in
OnTerminated(..)
It seems that you may have multiple dum threads running.
Dum should only be running in one thread. With dum running in one
thread - nothing else in dum happens until you return from the
onTerminated callback.
The 15ms delay you are seeing is likely due to some
problem in your process loop.
Scott
From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxxx
[mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxxx] On Behalf Of
Kovar, William (Bill)
Sent: Wednesday, January 17, 2007 6:08 PM
To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: [reSIProcate] Session destroyed while in
OnTerminated(..)
All,
I'm sure this is not new information but I am wondering
what, if anything could/will be done to the following problem regarding
OnTerminated() callback.
When one sends an BYE with InviteSessionHandle->end()
the following happens:
1. The BYE msg is built and put on the Fifo ready to be
sent on the wire
2. the session is transitioned to IsTerminating()
3. The onTerminated() callback is fired.
If system load causes a slowdown, it quite easy to be
manipulating the session in OnTerminated() and the AppDialog,
AppdialogSet and InviteSession all get destroyed before exiting the
callback. This happens when the BYE gets a 200 OK answer and the session
is torn down.
It seems that there is a window of ~15ms before the BYE
msg is sent out. What's controlling this time?
Any suggestions how to get around this issue or if the
session will be kept around longer than the receipt of the 200 OK on the
BYE. Any forseeable changes to DUM?
Bill Kovar
bkovar@xxxxxxxxx
Avaya, Inc.
(732) 852-2609
------------------------------------------------------------
------------------------------------------------------------
From: "Scott Godin" <slgodin@xxxxxxxxxxxx>
To: "Kovar, William \(Bill\)" <bkovar@xxxxxxxxx>
Subject: Re: [reSIProcate] Session destroyed while in OnTerminated(..)
Date: Thu18 Jan 2007 16:26:10 -0500
Bill,
It the threading model was valid, then Dum should not be able to process
the 200 response while you are in your onTerminated callback. The
process loop should be blocked. How do you ensure that messages such as
BYE and their responses are routed to the same dum thread that created
the dialog by using the message filter rules?
Scott
From: Kovar, William (Bill) [mailto:bkovar@xxxxxxxxx]
Sent: Thursday, January 18, 2007 4:09 PM
To: Scott Godin; resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [reSIProcate] Session destroyed while in OnTerminated(..)
Scott,
You may have mis-understood me. I have an app thread that
controls/monitors one of N UAs, each running on their own DumThread but
sharing a single StackThread. Use of a single Stack thread across
multiple Dums is accomplished by adding user based switching in
MessageFilterRule. Works quite nicely for phone numbers, actually!!
In no situation does one Dum thread (UA) ever make a call on another Dum
thread. I don't do that kind of thread hopping.
What I am doing, which I believe is solvable with DumCommand, is this:
At the App thread, when I decide which UA to control, I directly call
session->end() from the App thread causing the problem I described,
namely, if OnTerminated() runs too long, the 200 OK response to the BYE
blows away the session/Dialog/etc.
So my question is: Will the use of DumCommand in this instance, from my
App thread, directed at a specific Dum thread, fix the sequence
problem??
Bill Kovar
bkovar@xxxxxxxxx
Avaya, Inc.
(732) 852-2609
________________________________
From: Scott Godin [mailto:slgodin@xxxxxxxxxxxx]
Sent: Thursday, January 18, 2007 3:56 PM
To: Kovar, William (Bill); resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [reSIProcate] Session destroyed while in
OnTerminated(..)
It is not legal to have multiple dum threads. All calls to
dum->process and the dum api's must be run from the same thread, or must
be protected.
http://www.resiprocate.org/DUM_Threading
From: Kovar, William (Bill) [mailto:bkovar@xxxxxxxxx]
Sent: Thursday, January 18, 2007 3:20 PM
To: Scott Godin; resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [reSIProcate] Session destroyed while in
OnTerminated(..)
I run 2 dums, 1 SipStack in my B2B, each using DumThread (2) and
the same StackThread(1).
So my calling session->end() from outside of the Dum thread is
causing this sequencing problem??
And posting the session->end() using DumCommand will get around
this sequencing problem??
Bill Kovar
bkovar@xxxxxxxxx
Avaya, Inc.
(732) 852-2609
________________________________
From: Scott Godin [mailto:slgodin@xxxxxxxxxxxx]
Sent: Thursday, January 18, 2007 2:17 PM
To: Kovar, William (Bill);
resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [reSIProcate] Session destroyed while in
OnTerminated(..)
It seems that you may have multiple dum threads running.
Dum should only be running in one thread. With dum running in one
thread - nothing else in dum happens until you return from the
onTerminated callback.
The 15ms delay you are seeing is likely due to some
problem in your process loop.
Scott
From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxxx
[mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxxx] On Behalf Of
Kovar, William (Bill)
Sent: Wednesday, January 17, 2007 6:08 PM
To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: [reSIProcate] Session destroyed while in
OnTerminated(..)
All,
I'm sure this is not new information but I am wondering
what, if anything could/will be done to the following problem regarding
OnTerminated() callback.
When one sends an BYE with InviteSessionHandle->end()
the following happens:
1. The BYE msg is built and put on the Fifo ready to be
sent on the wire
2. the session is transitioned to IsTerminating()
3. The onTerminated() callback is fired.
If system load causes a slowdown, it quite easy to be
manipulating the session in OnTerminated() and the AppDialog,
AppdialogSet and InviteSession all get destroyed before exiting the
callback. This happens when the BYE gets a 200 OK answer and the session
is torn down.
It seems that there is a window of ~15ms before the BYE
msg is sent out. What's controlling this time?
Any suggestions how to get around this issue or if the
session will be kept around longer than the receipt of the 200 OK on the
BYE. Any forseeable changes to DUM?
Bill Kovar
bkovar@xxxxxxxxx
Avaya, Inc.
(732) 852-2609
------------------------------------------------------------
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
https://list.resiprocate.org/mailman/listinfo/resiprocate-devel