This is applied as revision 536.
It would be great if we had a nice string structure throughout the code so
that we could handle non-null terminated strings both on send and receive
for all types of messages; but this is a good start.
Charles
Andy Aicken [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
09/09/2008 07:04 PM
To
'darshan b n' [EMAIL PROTECTED], sipp-users@lists.sourceforge.net
cc
Subject
Re: [Sipp-users] SIP-I message format in sipp
Hi Darshan,
I created a patch for handling SIP-I messages, as the current message
handling in SIPp treats everything as a string so doesn?t handle ISUP
message bodies that contain a binary \x00. This ends up being treated as a
string termination resulting in message gets truncated.
The patch is available at:
https://sourceforge.net/tracker/?func=detailatid=637566aid=1965508group_id=104305
It needs more rigorous testing but worked ok for me with the type of
functionality I was using.
Regards
Andy
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of darshan b n
Sent: 04 September 2008 12:30
To: sipp-users@lists.sourceforge.net
Subject: [Sipp-users] SIP-I message format in sipp
Hi all ,
i want know how to create a SIP-I message in sipp please respond with a
sample message format
Thanks
darshan
On 04/09/2008, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Send Sipp-users mailing list submissions to
sipp-users@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/sipp-users
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than Re: Contents of Sipp-users digest...
Today's Topics:
1. Re: Force source IP source Port at IP layer (Klaus Darilion)
2. sipp remote (RTP) port handling (Jan Rudinsk?)
--
Message: 1
Date: Thu, 04 Sep 2008 10:05:02 +0200
From: Klaus Darilion [EMAIL PROTECTED]
Subject: Re: [Sipp-users] Force source IP source Port at IP layer
To: Cyrille OLIVIER [EMAIL PROTECTED]
Cc: sipp-users@lists.sourceforge.net
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
FYI: If you want to change the src IP you can also use this patch:
https://sourceforge.net/tracker/?func=detailatid=637566aid=1823593group_id=104305
klaus
Cyrille OLIVIER schrieb:
Dear sipp-users,
Again, I asked my requests about SIPp client using TCP:
Is it possible to force sipp to use specific IP source Port source, at
IP layer, for send messages when TCP with single socket (option '-t
t1' used) ?
I tried many things:
-bind_local: seems unuseful.
-i x.x.x.x -p options: it's only for some SIP headers but not
for IP packet header.
send -source_ip=x.x.x.x -source_port= for INVITE message
look for this subject in mailing list archives
...
Currently, I don't know which other workaround or things to do :(
I would really appreciate any help about that
Thanks a lot,
BR,
Cyrille
Discutez gratuitement avec vos amis en vid?o ! T?l?chargez Messenger,
c'est gratuit ! http://www.windowslive.fr/majmessenger.asp
-
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
___
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users
--
Message: 2
Date: Thu, 04 Sep 2008 12:32:12 +0200
From: Jan Rudinsk? [EMAIL PROTECTED]
Subject: [Sipp-users] sipp remote (RTP) port handling
To: sipp-users@lists.sourceforge.net
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=iso-8859-2
Hi,
I'm using SIPp to generate a call with RTP media. Media are sent to
remote side, recorded and sent back.
However SIPp sends media to a different remote port than offered by the
remote side.
SIPp: SIP INVITE with SDP m=audio 6000 RTP/AVP 0
Remote: 200 OK with SDP m=audio 18436 RTP/AVP 0 101
SIP:RTP incoming on 6000(OK)
Remote: RTP incoming on 1843(instead of 18436)
Attached: scenario graph, packet capture
Does anyone know the solution?
Thank you,
JaR
--
Ing. Jan Rudinsky
Czech Technical University in Prague
Cesnet z.s.p.o.
RD Centre (RDC) for Mobile Applications
[EMAIL PROTECTED
