Hi,
you must use the placeholder [call_id] instead of your self-defined
Call-ID--Header:
http://sipp.sourceforge.net/doc/reference.html#Structure+of+client+(UAC+like)+XML+scenarios
--
A call_id identifies a call and is generated by SIPp for each new call.
In
Can you send us the xml-scenario and the -trace_msg - Logfile?
br
Michael
On 2010-04-20 08:20, Himanshu Rawat wrote:
Hi Michael,
I made sample Subscribe/Notify XML scenario and getting below error in
sipp error log files. Error log files shows me 200 response received but
with below
Thanks Michale.
Tried and worked though with some errors. Will get back if not
resolved + more Questions.
Cheers,
Rawat
On Fri, Apr 16, 2010 at 17:46, Michael Hirschbichler
s...@hirschbichler.biz wrote:
Well, this is not tricky, just
send
SUBSCRIBE...
/send
recv response=200/recv
Hi Guys,
Can anyone tell me on how to write a simple customized
Subscribe/Notify Call scenario.
Subscribe needs to be send to voice mail server ( which i already have).
-- SUBSCRIBE ( to my voice mail server which will process it )
-- 200
[ 50ms] Pause
--
Well, this is not tricky, just
send
SUBSCRIBE...
/send
recv response=200/recv
recv request=NOTIFY/recv
send
200 OK ...
/send
For the SIP-messages, just start the SIP-client of your choice and
record the messages with wireshark
br
Michael
On 2010-04-16 13:55, Himanshu Rawat wrote:
Hi
