Re: [reSIProcate-users] a question about dialog of dum

[Scott Godin <sgodin@xxxxxxxxxxxxxxx>]

>i don't really agree that "DialogSet's are keyed off of call id and from tag"
>it think it should be "DialogSet's are keyed off of call id and local
>tag"  if  the "DialogSetId::DialogSetId(const SipMessage& msg)" is
>true.

[Scott]  Yes, I agree, you are right. : )

2010/10/19 吴振宇 <ssosun@xxxxxxxxx>

i don't really agree that "DialogSet's are keyed off of call id and from tag"
it think it should be "DialogSet's are keyed off of call id and local
tag"  if  the "DialogSetId::DialogSetId(const SipMessage& msg)" is
true.
yestoday,i test that sending a invite but not really,and then i use
setFromExternal() to it ,force it to
DialogUsageManager::processRequest ,then i got two dialogset.
so i get that a almost same invite request but one from out
(isExternal) and one from tu.the dialogsetid should be different,then
it will create two dialog.
the thing above is my question,now i get it and i have to say my
_expression_ is so bad.
在 2010年10月19日 下午9:58，Scott Godin <sgodin@xxxxxxxxxxxxxxx> 写道：

> I don't really understand what you are asking.  If any of the following are
> different, then they will be distinct dialogs:  to tag, from tag, call id.
>  DialogSet's are keyed off of call id and from tag.
> Scott
>
> 2010/10/18 吴振宇 <ssosun@xxxxxxxxx>
>>
>> the transactionid which has been said is in order to say that the
>> invite can be transmited to the dum beacause the invite we sent and
>> the invite we received are not in a transaction.
>>
>> "A dialog is identified by a call identifier, local tag, and a remote
>> tag.  "from rfc3261
>>
>> the dialogsetid of the invite we sent is combination of call-id and
>> from tag(local tag)
>> the dialogsetid of the invite we recieved is combination of call-id
>> and to tag which we will create one(remote tag).then the dialogsetids
>> are different  or not?and dialogsets aredifferent or not?and dialogs
>> are different or not?
>>
>>
>> ps:in processRequest of dialoguagemanager there is
>> findDialogSet(DialogSetId(request))
>>
>> 在 2010年10月18日 下午9:18，Scott Godin <sgodin@xxxxxxxxxxxxxxx> 写道：
>> > The DUM layer does not look at the transaction id's - it identifies
>> > dialogs
>> > by Call id, and tags only - so it will not see these as separate
>> > dialogs.
>> > Scott
>> >
>> > 2010/10/18 吴振宇 <ssosun@xxxxxxxxx>
>> >>
>> >> i know TransactionState can be distinguished,i want to know the two
>> >> invite
>> >> will be in a dialog or two?
>> >> sending invite request can create a dialogset only.receive a invite
>> >> request will create a dialog.
>> >> if we send a 200 to the invite request we received,then we receive  a
>> >> almost same 200(top via dif from we sent) for the invite we sending.
>> >> now how much dialog we have ?
>> >>
>> >> in another word:
>> >> send a invite :
>> >> from tag=A(local tag)
>> >> to tag = B(remote tag)
>> >> call-ID = C
>> >>
>> >>
>> >> receive a invite:
>> >>
>> >> form tag=A(remote tag)
>> >> to tag=B(local tag)
>> >> call-ID=C
>> >>
>> >> will be how many dialog?
>> >> one or two?
>> >> 在 2010年10月18日 下午5:19，highering <highering@xxxxxxx> 写道：
>> >> > yes，he can.
>> >> > TransactionId was built from via when via exist.
>> >> > TransactionState::process->SipMessage::getTransactionId
>> >> >
>> >> >
>> >> > At 2010-10-18 15:56:12，"吴振宇" <ssosun@xxxxxxxxx> wrote:
>> >> >>hi all:
>> >> >>i have a question about dum:
>> >> >>after sending a invite(a) request using dum,we rec a invite almost
>> >> >> the
>> >> >>same with we sent,except the top via. in another word,the same
>> >> >>call-ID,same from tag.can the dum distinguish them to two dialogs?
>> >> >>_______________________________________________
>> >> >>resiprocate-users mailing list
>> >> >>resiprocate-users@xxxxxxxxxxxxxxx
>> >> >>List Archive: http://list.resiprocate.org/archive/resiprocate-users/
>> >> >
>> >> >
>> >> >
>> >> _______________________________________________
>> >> resiprocate-users mailing list
>> >> resiprocate-users@xxxxxxxxxxxxxxx
>> >> List Archive: http://list.resiprocate.org/archive/resiprocate-users/
>> >
>
>
_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/