On Tue, Oct 20, 2009 at 11:07 PM, Maksim Karpenko
<mkarpenko1...@gmail.com>wrote:
> Hi!
>
> If it doesn't bother you could you give me few advice concerning SIPp?
>
Sure.
> If I correctly understood, there are two ways of running SIPp: using
> standart scenario file with options in the command line or using own
> scenario where a large part of options is already written. Is it so?
No. The thing that you call standard scenario is just the same as an
external scenario. It just happens that it is embedded inside SIPp. You can
even dump them:
sipp -sd uac
> If yes, then what can be the reason why the standart scenario (uac) doesn't
> work properly? Every time I run SIPp with -sn uac I get error
>
> Unable to send UDP message, errno = 1 (Operation not permitted).
>>
>
> When I run my own uac scenario SIPp receives 200-reply from asterisk for 6
> times and does not send acknowledgement, so the test fails. I've tried to
> make test calls to sip-phone and to isdn-phone connected via PRI to local
> exchange in the office. Result was the same. CLI says
>
> [Oct 20 17:00:07] WARNING[1422]: chan_sip.c:1981 retrans_pkt: Maximum
>> retries exceeded on transmission 1.14688.127.0....@sipp.call.id for seqno
>> 1 (Critical Response) -- See
>> doc/sip-retransmit.txt.
>> [Oct 20 17:00:07] WARNING[1422]: chan_sip.c:2003 retrans_pkt: Hanging up
>> call 1.14688.127.0....@sipp.call.id - no reply to our critical packet
>> (see doc/sip-retransmit.txt).
>>
>
> I've read that in many cases it's a problem with NAT or firewall but
> asterisk server, sip-phone and PC with running SIPp are in the same LAN. And
> one more fact disturbs me: IP-adress in call-id 127.0.0.1. As for me, there
> is something wrong.
>
How are you calling sipp?
What is your complete command-line in both cases?
I checked your previous post again and I can see you called sipp this way:
sipp -sf /home/apollyon/my_uac.xml 10.0.0.154 -r 1 -m 1 -d 3000 -trace_err
-trace_msg
Actually, I always set the local ip address and local port to be used like
this:
sipp -i local_ip -p local_port -sf my_uac.xml -r 1 -m1 destination_address
Please try like the above and see if things change.
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users
