Hi, we definetly need a FAQ section on sipp.sourceforge.net.
First of all, your UAC - sipp-scenario uses one Call-ID for the register, the subscribe and the invite dialog. As in RFC3261 stated: "In a new request created by a UAC outside of any dialog, the Call-ID header field MUST be selected by the UAC as a globally unique identifier over space and time unless overridden by method-specificbehavior.", so the behaviour of your UAC is problematic. Well, your proxy does obviously (as most proxies) not care about this, so just keep in mind, that you can come into troubles with this scenario. The reason, why your UAS is not working is clear: SIPp can be run either in UAC-mode (it sends the first message) or in UAS-mode (it receives the first message). In both modes, it parses for the Call-ID and stores this Call-ID (together with CSseq) in a hashtable. Each subsequent message will then be compared, if its Call-ID is already in this hashtable or not. If it is in this hashtable, the message is compared to expected message defined in the XML-call-flow. If it matches, the messages is accepted and counted as valid. If the Call-ID or the CSeq-Number is changing, then the message is dropped. So, your UAS call-Flow looks this way Proxy UAS <--REG---- ---200---> <--SUB---- ---501---> ***New dialog, Call-ID and CSeq change*** ---INV---> <--180---- You have to split your scenario into two files and run SIPp subsequently twice, once, for the registration and the subscribe, and once for the UAS br Michael On 2010-04-16 19:36, ritesh.gu...@bt.com wrote: > Hi, > > > > SIPp –xlite communication working fine > > > > SIPp-SIPp not working ...? > > > > Below is details explanation > > * * > > *Scenario A1- * > > > > Node A Caller > > > > Node B Xlite > > > > > > <send > *REGISTER* </send> > > > > <recv response="200" crlf="true" /> > > > > <send > *SUBSCRIBE *</send> > > > > <recv response="501" crlf="true" /> > > > > <send > *INVITE *</send> > > > > <recv response="486" optional="true" /> > > > > <recv response="180" optional="true"/> > > > > <send> *ACK* </Send> > > > > > > > > > > > > > > This Works Perfectly on Node B xLite is able to receive call. Working Good. > > > > > > *Scenario B2- * > > > > Node A Caller > > > > Node B Receiver > > > > > > <send > *REGISTER* </send> > > > > <recv response="200" crlf="true" /> > > > > <send > *SUBSCRIBE *</send> > > > > <recv response="501" crlf="true" /> > > > > <send > *INVITE *</send> > > > > <recv response="486" optional="true" /> > > > > <recv response="180" optional="true"/> > > > > <send> *ACK* </Send> > > > > > > > > <send > *REGISTER* </send> > > > > <recv response="200" crlf="true" /> > > > > <send > *SUBSCRIBE *</send> > > > > <recv response="501" crlf="true" /> > > > > <recv request="*INVITE*"> > > </recv> > > > > <send> > > <![CDATA[ > > > > SIP/2.0 180 Ringing > > [last_Via:] > > [last_From:] > > [last_To:];tag=[call_number] > > [last_Call-ID:] > > [last_CSeq:] > > Contact: <sip:[local_ip]:[local_port];transport=[transport]> > > Content-Length: 0 > > > > ]]> > > </send> > > > > Scenario B2- on > Node B side does not work.. > > Node B - got error on during Invite receive here is error: > > Discarding message which can't be mapped to a known SIPp call: INVITE sip > > > > Any clue or suggestion what could be the reason ? > > Thanks in advance > > > > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > > > > _______________________________________________ > Sipp-users mailing list > Sipp-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/sipp-users ------------------------------------------------------------------------------ _______________________________________________ Sipp-users mailing list Sipp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sipp-users
