> 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/
>