Menu
▾
▴
Re: [Sipp-users] Problem with the UAS
|
From: Luis F. <lui...@in...> - 2004-07-23 08:28:11
|
Message>Be sure the SIPPp server can pingthe originating
server.
There was no problem pinging the originating server
>Also, SIPp will reply to the server that is
generating the INVITE. If you expect the response to
be sent somehwere else, for example an address in the
contact header, it will not.
Yep, im trying to reply to the generating server.
>Which version did you download ?
I tried both 0.3 and 0.4 and got the same error.
The extrange thing is that if i run it in UAC mode, there is no problem =
contacting the server, but if run it in UAS mode, the packets do not =
reach the server. There is no firewall in between or anything like =
that.
Richard.
-----Original Message-----
From: sip...@li... =
[mailto:sip...@li...] On Behalf Of Luis Flores
Sent: Thursday, July 22, 2004 4:15 PM
To: sip...@li...
Subject: [Sipp-users] Problem with the UAS
Hi,
I have a problem with sipp running the default uas scenario:=20
./sipp -sn uas -trace_msg
When I run other clients and servers to try to contac this client, =
sipp receives the INVITE requests, it sends the 180 and 200 responses, =
but the other clients/servers do not receive this messages for some =
reason.
If I run the default uac scenario or any other uac scenario created =
by myself, there is no problem contacting the other servers and clients, =
the problem appears only when I'm running sipp in the uas mode.
There is only one way in which this works, which is when I run both =
the UAC and the UAS in the same computer using different ports, then =
the UAC sends messages to UAS, it responds and all the conversation is =
carried out normally.
I have not changed any of the configuration files or anything like =
that, i am just running the unzipped files and i downloaded the program =
last week.
Does anyone have any idea why this is happening?
Thanks for everybody's help, i hope i can help you one of this day =
if i become a SIPP expert.
Regards,
Luis.
PS. Here I include the Scenario Screen, and the log of two =
sent-but-not-received messages.
------------------------------ Scenario Screen -------- [1-4]: =
Change Screen --
Port Total-time Total-calls Transport
5060 7623.08 s 24 UDP
0 new calls during 1.000 s period 20 ms scheduler resolution
0 concurrent calls Peak was 1 calls, after 967 =
s
1 open sockets
Messages Retrans Timeout =
Unexpected-Msg
----------> INVITE 2 11 22
<---------- 180 2 11
<---------- 200 2 14 2
----------> ACK E-RTD 0 0 0
----------> BYE 0 0 0
<---------- 200 0 0
[ 4000 ms]
----------------- Traffic Paused - Press [p] again to resume =
------------------
-----------------------------------------------
UDP message send:
SIP/2.0 200 OK^M
Via: SIP/2.0/UDP 193.156.19.79:5060^M
From: PARLAYSCS <sip:MCUServer@193.156.19.79>^M
To: sipp <sip:sipp@193.156.19.31:5060>;tag=3D1^M
Call-ID: 2069227828@193.156.19.79^M
CSeq: 1 INVITE^M
Contact: <sip:193.156.19.31:5060;transport=3DUDP>^M
Content-Type: application/sdp^M
Content-Length: 136^M
^M
v=3D0^M
o=3Duser1 53655765 2353687637 IN IP4 127.0.0.1^M
s=3D-^M
t=3D0 0^M
c=3DIN IP4 127.0.0.1^M
m=3Daudio 10000 RTP/AVP 0^M
a=3Drtpmap:0 PCMU/8000^M
-----------------------------------------------
-----------------------------------------------
UDP message send:
SIP/2.0 200 OK^M
Via: SIP/2.0/UDP 193.156.19.121:5060;branch=3Dfake.1^M
From: User1 <sip:user1@193.156.19.121:5060>;tag=3D1090498754400^M
To: <sip:sipp@193.156.19.31>;tag=3D2^M
Call-ID: 1090498754400@193.156.19.121^M
CSeq: 1109291050 INVITE^M
Contact: <sip:193.156.19.31:5060;transport=3DUDP>^M
Content-Type: application/sdp^M
Content-Length: 136^M
^M
v=3D0^M
o=3Duser1 53655765 2353687637 IN IP4 127.0.0.1^M
s=3D-^M
t=3D0 0^M
c=3DIN IP4 127.0.0.1^M
m=3Daudio 10000 RTP/AVP 0^M
a=3Drtpmap:0 PCMU/8000^M
-----------------------------------------------
|