2012/1/10 raojlist <raojl...@163.com>
> **
>
> 2012-01-10 15:15:20:867 1326179720.867330: Discarding message which
> can't be mapped to a known SIPp call:
> OPTIONS sip:3007@10.8.103.216:5060 SIP/2.0
> Via: SIP/2.0/UDP 10.8.103.254:5060;branch=z9hG4bK0f27650b;rport
> From: "Unknown" <sip:Unknown@10.8.103.254:5060>;tag=as1e37f103
> To: <sip:3007@10.8.103.216:5060>
> Contact: <sip:Unknown@10.8.103.254>
> Call-ID: 003e344d599cf73a555321ef1bed3a21@10.8.103.254:5060
> CSeq: 102 OPTIONS
> User-Agent: HOLLYUC PBX
> Max-Forwards: 70
> Date: Thu, 23 Sep 2010 07:14:57 GMT
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
> Supported: replaces
> Content-Length: 0
>
> I actually never used ooc scenario.
I tried now and confirmed the message is not handled by the ooc scenario.
So i am not sure if this never worked or if it got broken in the latest
SIPp that I have built from source.
You could try this alternative:
http://permalink.gmane.org/gmane.comp.telephony.sipp.user/5769
------------------------------------------------------------------------------
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
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users
