Re: reuse callID by proxy
Lebing Xie <[email protected]>
| Newsgroups | gmane.comp.voip.nist-sip |
|---|---|
| Organization | Fraunhofer FOKUS Berlin |
| Message-ID | <1164306233.5499.119.camel@localhost> |
Hi, all About the Proxy, my problem is that I want to host multiple Proxy applications above same SIP Stack, what happens: mes0 - Proxy1 -mes1- Proxy2 - mes2 - Proxy2 - mes3 -> out ---------------------------------------------------------- JAIN SIP Stack mes1,2 are sending back to same stack (e.g to localhost:5060), three proxy application will be triggert in turn. All 4 messages have same from-tag/to-tag/CallID, so: 1. How to implement a Proxy? So I can clone a message and send it on a ClientTransaction. Is there 1 or 2 dialog? I think only 1, for the dialog ID is same (callid+fromtag, to tag is null here), getNewClientTransaction will copy the dialog also. 2. The CT and ST have also the same cloned branchID, so could it be a problem? I am thinking build a layer between Stack and applications, but seemed this layer should implement all the SIP state machine, simulating a real SIP stack:((( urs Lebing On Fri, 2006-09-29 at 14:53 +0200, Jeroen van Bemmel wrote: > Lebing, > > If you are implementing a 'normal' proxy, the Call-ID needs to remain the > same. If you are implementing a B2BUA, it should be changed. The S-CSCF > won't care either way, as it cannot tell whether it was changed or not. > > Regards, > > Jeroen > > ----- Original Message ----- > From: "Lebing Xie" <[email protected]> > To: "sip mailing" <[email protected]> > Sent: Wednesday, September 27, 2006 1:12 PM > Subject: [nist-sip] reuse callID by proxy > > > > Hallo, > > > > I am working on a sip proxy based on JAIN Stack 1.2, can the cloned and > > proxyed initial request use the same call-id as the originating one? I > > do not think it can and should not, for a proxy is implemented as a > > B2BUA(or not?) > > > > But if other parties on single path (e.g S-CSCF) need to check the > > callID for some kind of business logic, a changed callid could break it. > > So any idea about it? > > > > urs Lebing > > _______________________________________________ > > nist-sip mailing list > > [email protected] > > http://www-x.antd.nist.gov/mailman/listinfo/nist-sip >