Anil,
Make sure that your REGISTER and INVITE have the same Call-ID. If you
need to have two different call-id's you can use /// to prefix them with
something. For example: Call-ID: FOO///[EMAIL PROTECTED] and Call-ID:
BAR///[EMAIL PROTECTED] should be treated as the same Call-ID by SIPp.
Charles
[EMAIL PROTECTED] wrote on 03/13/2007 10:22:38 AM:
> Hi,
>
> I am running a single call that has the following call scenario:
>
> SIPa SIPb
> ------REGISTER---->
> <---200 OK ----------
> -----INVITE------------>
> <-----180 Ringing----
> <-----200 OK-----------
>
> When I run the scenario with sipa.xml and sipb.xml on 2 different
machines,
> SIPb receives REGISTER and sends 200 OK. SIPa sends INVITE to SIPb,
> but SIPp on SIPb machine prints the following log:
>
> Aborting call on unexpected message for Call-ID '109771157-2561':
> while expecting 'REGISTER', received 'INVITE'......
>
> When SIPb is expecting INVITE according to the call flow(after
> sending 200 OK), then why
> is the application throwing error on REGISTER. Please help me on
> this scenario.
> (This is just one call, not in retransmission mode)
>
> This is on SIPp v1.1-TLS-PCAP, version 20061124 version.
>
> XML file SIPb.xml
>
> ==============================================
> <?xml version="1.0" encoding="ISO-8859-1" ?>
> <!DOCTYPE scenario SYSTEM "sipp.dtd">
> <scenario name="SIPa to SIPb">
>
> <recv request="REGISTER" crlf="true">
> </recv>
>
> <send>
> <