Hi Takeshi,
Thanks for your response.
In your script, i am not able to understand when second time INVITE received,
after parsing,if its call hold, then it will go to label id=reply_to_hold, else
label-id=reinvite_not_received, but in that script, after parsing, why you are
sending 200 ok instead of directly going to label-id=reply_to_hold, i am not
able to understand.
can you pls kindly explain...
And when i put ur script, its showing me the error like
"next jump, "reply_to_hold" is not a valid integer!"
Regards
manasi
On Thu, 14 Apr 2011 16:39:02 +0530 wrote
>
On Thu, Apr 14, 2011 at 4:36 PM, manasi wrote:
Hi
i am using sipp for call hold scenerio. here i am using x-lite as uac and sipp
as uas.
here i want to implement the logic, when x-lite press hold button, my sipp will
receive invite and it will parse the msg field (c=0.0.0.0 || a=sendonly || c &
a field), if it matches with any of the field, then go for sending 200 ok with
c=0.0.0.0 or a= recvonly, if it did not receive INVITE from x-lite, then close
the call by sendind BYE.
I had written a script for a similar test.
I have adapted according to the above.
regards,
takeshi
------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve
application availability and disaster protection. Learn more about boosting
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
