2012/1/10 mayamatakeshi <[email protected]>
>
>
> On Tue, Jan 10, 2012 at 4:00 PM, raojlist <[email protected]> wrote:
>
>> **
>> thanks first,
>>
>> I get your advice and use request="OPTIONS", but the sipp can not
>> handle the OPTIONS message.
>>
>
> Yes, I just explained that request="102" would not work.
> But request="OPTIONS" will not work either because this is an out-of-call
> message. So you should just remove the line and let SIPp respond with "200
> OK" to it.
> As explained in the SIPp doc, it should be responding with "200 OK" for
> any out-of-call messages.
> So if this is not happening, maybe you are using and old version of SIPp.
>
But if SIPp is sending the "200 OK" response but Asterisk doesn't like it,
then you can pass the uas scenario to be used using option
-oocsf (as mentioned in the doc).
So that you could reply for example returning a header like "
Accept: application/sdp"
------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create
new or port existing apps to sell to consumers worldwide. Explore the
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
