On Wed, Nov 30, 2011 at 5:44 AM, Murray Hooper <[email protected]> wrote:
> Sorry, poor description before.****
>
> ** **
>
> I go through normal INVITE uac setup, receive 200 OK, respond with ACK and
> then get unexpected INVITE. What is the best way to handle this?
>
Well, you have to adjust your xml scenario to expect the unexpected INVITE.
Assuming the "unexpected INVITE" is a RE-INVITE, then putting something
like this after the ACK should work:
<recv request="INVITE"/>
<send>
<![CDATA[
SIP/2.0 200 OK
[last_To:]
[last_From:]
[last_Call-ID:]
[last_CSeq:]
[last_Via:]
Content-Length: 0
]]>
</send>
<recv request="ACK"/>
regards,
takeshi
> ****
>
> ** **
>
> *From:* Murray Hooper [mailto:[email protected]]
> *Sent:* Tuesday, November 29, 2011 3:24 PM
> *To:* [email protected]
> *Subject:* [Sipp-users] reINVITE response****
>
> ** **
>
> In uac scenario, currently the uas responds with a reINVITE to my INVITE.
> What is the correct way to handle this in my uac.xml? ****
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure
> contains a definitive record of customers, application performance,
> security threats, fraudulent activity, and more. Splunk takes this
> data and makes sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
> _______________________________________________
> Sipp-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/sipp-users
>
>
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
