On Tue, Jan 10, 2012 at 4:00 PM, raojlist <raojl...@163.com> 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. > I need handle the OPTIONS message, because if i do not process it,the > agent peer will display ‘Unreachabled’ status in asterisk（1.4.2) cli > console. > > > ---------------------------- > <recv response="100" optional="true"></recv> > <recv response="200" ></recv> > <label id= "1" /> > > <recv request="OPTIONS" crlf="true" rrs="true" timeout="10000" > ontimeout="1"></recv> > <send> > 2012-01-10 > ------------------------------ > raojlist > ------------------------------ > *发件人：* mayamatakeshi > *发送时间：* 2012-01-10 14:41:45 > *收件人：* raojlist > *抄送：* sipp-users > *主题：* Re: [Sipp-users] some question about sipp handle OPTIONS(102) > message. > > > On Tue, Jan 10, 2012 at 3:21 PM, raojlist <raojl...@163.com> wrote: > >> ** >> hello every body. >> >> i want to batch register into asterisk (v 1.4.2) in use sipp (v 3.2). >> but when coming OPTIONS message from asterisk, the sipp can not handle it. >> >> >> Options__________________________________________________________________________________________________________________________ >> OPTIONS sip:3007@10.8.103.216:5060 SIP/2.0 >> Via: SIP/2.0/UDP 10.8.103.254:5060;branch=z9hG4bK36df69a8;rport >> From: "Unknown" <sip:Unknown@10.8.103.254:5060>;tag=as3a872d19 >> To: <sip:3007@10.8.103.216:5060> >> Contact: <sip:Unknown@10.8.103.254> >> Call-ID: 149396b64ce3ff4824d9a91d4adb6865@10.8.103.254:5060 >> CSeq: 102 OPTIONS >> User-Agent: HOLLYUC PBX >> Max-Forwards: 70 >> Date: Thu, 23 Sep 2010 06:17:44 GMT >> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY >> Supported: replaces >> Content-Length: 0 >> >> my reg.xml >> ------------------------------------------------ >> <?xml version="1.0" encoding="ISO-8859-1" ?> >> <scenario name="Basic Sipstone UAC"> >> <send retrans="1000"> >> <![CDATA[ >> REGISTER sip:[field0]@[remote_ip]:[remote_port] SIP/2.0 >> Via: SIP/2.0/[transport] [local_ip]:[local_port] >> Contact: <sip:[field0]@[local_ip]:[local_port]> >> Max-Forwards: 70 >> From: "[field0]"<sip:[field0]@[local_ip]:[local_port]>;tag=[call_number] >> To: "[field0]"<sip:[field0]@[remote_ip]:[remote_port]> >> Call-ID: [call_id] >> CSeq: 1 REGISTER >> Expires: 3600 >> Content-Length: 0 >> >> >> ]]> >> </send> >> <recv response="100" ></recv> >> <recv response="401" auth="true"></recv> >> <send retrans="500"> >> <![CDATA[ >> >> REGISTER sip:[remote_ip] SIP/2.0 >> Via: SIP/2.0/[transport] [local_ip]:[local_port] >> Max-Forwards: 70 >> Contact: <sip:[field0]@[local_ip]:[local_port]> >> To: "[field0]"<sip:[field0]@[remote_ip]> >> From: "[field0]"<sip:[field0]@[remote_ip]:[local_port]>;tag=[call_number] >> Call-ID: [call_id] >> CSeq: 2 REGISTER >> Expires: 3600 >> [field1] >> Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REFER,NOTIFY,MESSAGE,SUBSCRIBE,INFO >> Content-Length: 0 >> ]]> >> </send> >> <recv response="100" optional="true"></recv> >> <recv response="200" optional="true"></recv> >> <label id= "1" /> >> *<recv request="102" timeout="10000" ontimeout="1"></recv>* >> > > request="102" will wait for a request named 102 and not OPTIONS, so you > should use request="OPTIONS". But actually, you don't need to wait for it > as it will be handled by sipp as an out-of-call message. > http://sipp.sourceforge.net/doc/reference.html#UAC+Out-of-call+Messages > So just remove the above line. > > regards, > takeshi >
<<Catch2.jpg>>
------------------------------------------------------------------------------ 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
