The problem is because NOTIFY has a different call-id from the REGISTER
message sent by SIPP. SIPP has a limitation that the call-id must be same in
a scenario.
I will suggest 3 possible solutions
1. If the NOTIFY can be received on a different port by SIPP (if not then go
to step2) then run two sipp instances in parallel
sipp <other options> -sf register.xml
sipp <other options> -sf notify_answer.xml
2. Run two sipp scripts one by one like
sipp <other options> -sf register.xml && sipp <other options> -sf
notify_answer.xml
3. Use the /// feature in call-id if possible
>From the SIPP documentation:
A call_id identifies a call and is generated by SIPp for each new call. *In
client mode, it is mandatory to use the value generated by SIPp in the
"Call-ID" header.* Otherwise, SIPp will not recognise the answer to the
message sent as being part of an existing call.
Note: [call_id] can be pre-pended with an arbitrary string using '///'.
Example: Call-ID: ABCDEFGHIJ///[call_id] - it will still be recognized by
SIPp as part of the same call.
Regards
Pandu
On 11/1/07, Jeverson Deggerone <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I am trying to setup a registration scenario but our sip
> application server does send a notify after the registration steps has been
> finish, but sipp is unable to recognize the notify because our sip server is
> not totally complaint according RFC. Is there any way to workaround it? I
> want sipp answer 200 ok in any case even if the notify is not RFC complaint.
>
>
>
>
>
> ------------------------------ Scenario Screen -------- [1-9]: Change
> Screen --
> Call-rate(length) Port Total-time Total-calls Remote-host
> 1.0(0 ms)/1.000s 5060 7.70 s 1 172.30.57.102:5060(UDP)
>
> Call limit reached (-m 1), 0.695 s period 4 ms scheduler resolution
> 1 calls (limit 1) Peak was 1 calls, after 1 s
> 0 Running, 1 Paused, 0 Woken up
> 4 out-of-call msg (discarded)
> 1 open sockets
>
> Messages Retrans Timeout
> Unexpected-Msg
> REGISTER ----------> 1 0 0
> 401 <---------- 1 0 0
> REGISTER ----------> 1 0 0
> 200 <---------- 1 0 0
> NOTIFY <---------- 0 0 0
> 200 ----------> 0 0 0
> ------------------------------ Test Terminated
> --------------------------------
>
>
> ----------------------------- Statistics Screen ------- [1-9]: Change
> Screen --
> Start Time | 2007-11-01 13:00:20
> Last Reset Time | 2007-11-01 13:00:27
> Current Time | 2007-11-01 13:00:28
>
> -------------------------+---------------------------+--------------------------
> Counter Name | Periodic value | Cumulative value
> -------------------------+---------------------------+--------------------------
>
> Elapsed Time | 00:00:00:698 | 00:00:07:758
> Call Rate | 0.000 cps | 0.129 cps
> -------------------------+---------------------------+--------------------------
>
> Incoming call created | 0 | 0
> OutGoing call created | 0 | 1
> Total Call created | | 1
> Current Call | 1 |
>
> -------------------------+---------------------------+--------------------------
> Successful call | 0 | 0
> Failed call | 0 | 0
>
> -------------------------+---------------------------+--------------------------
> Call Length | 00:00:00:000 | 00:00:00:000
> ------------------------------ Test Terminated
> --------------------------------
>
> 2007-11-01 13:00:25: Discarding message which can't be mapped to a known
> SIPp call:
> NOTIFY sip:[EMAIL PROTECTED] SIP/2.0
> From: < sip:[EMAIL PROTECTED]>
> To: <sip:[EMAIL PROTECTED]>
> Via: SIP/2.0/UDP 172.30.57.102:5060
> Max-Forwards: 70
> CSeq: 2173 NOTIFY
> Allow: REGISTER, INVITE, ACK, BYE, CANCEL, NOTIFY, REFER
> Contact: <sip:[EMAIL PROTECTED]:5060>
> Call-ID: 8148193911-95937732293911-11-9215663022
> Event: message-summary
> Subscription-State:active
> Content-Type: application/simple-message-summary
> Content-Length: 24
>
> please find bellow
>
> --
> Jeverson Deggerone
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Sipp-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/sipp-users
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
