The INVITE likely has a different call-id than the register. You should
split the scenario into two halves, one that REGISTERS and one that
handles the INVITE message.
Charles
[EMAIL PROTECTED] wrote on 07/17/2007 07:24:38 AM:
> Hi,
>
> I am trying to simulate a scenario where SIPp is acting as Server.
> SIPp should simulate the behaviour
> 1) REGISTER msg is received.
> 2) 200 OK for REGISTER msg is send.
> 3) INVITE msg is received.
> 4) 180 Ringing for INVITE msg is send
> 5) 200 OK for INVITE msg is send
>
> Steps 1 and 2 are working fine. But when INVITE msg is received by
> SIPp server , it gives error "Aborting call on unexpected message,
> while expecting 'REGISTER', received 'INVITE'"
>
> Plz find the attachments for
> 1) Scenario xml file
> branchs.xml
> 2) logs file
> branchs_1388_errors.log
>
> Thanks
> -Atul
>
> [image removed]
>
> [attachment "branchs.xml" deleted by Charles P Wright/Watson/IBM]
> [attachment "branchs_1388_errors.log" deleted by Charles P
Wright/Watson/IBM]
>
-------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Sipp-users mailing list
> Sipp-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sipp-users
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users
