Re: [Sipp-users] Aborting call on unexpected message

[Tincho y. <sa...@gm...>]

Ok Bradley. You're right!

Thanks all!

2009/8/18 Bradley, Todd <tod...@po...>:
> Let's go through a simple troubleshooting exercise that will hopefully
> help:
>
> 1) "How can I know the cause of the failed calls?"  Well, there are only
> two user agents (pieces of software) in this network.  One is SIPp and
> the other is Asterisk.  So that narrows things down.  Sounds like we
> need to find out what each of those applications thinks is going wrong.
>
> 2) "Is it the connection?"  Well, if there were Layer 0 or Layer 1
> problems, we'd see much more catastrophic issues.  And the fact that
> SIPp is telling you that there was an "unexpected message" means that
> packets are getting through, right?
>
> 3) "Is it my LAN?"  Again, your LAN must be working, or you wouldn't get
> any message back from Asterisk, would you?
>
> 4) "How can I know?"  Use your troubleshooting skills to eliminate
> things that aren't causing the problem, then gather more information
> about things that are causing it.  In this case, since you know that
> Asterisk is sending a "603 Declined" message, you should gather more
> information about what that means and why Asterisk would send it.
>
> Did you try googling "asterisk 603 declined"?  I don't know anything
> about Asterisk, but that's where I'd start.  Then I'd look at the system
> logs for Asterisk.  No doubt the Asterisk developers built in a logging
> system, and log messages are probably printed when someting bad happens,
> such as whatever causes a 603 Declined error.
>
> Is this your first time trying to diagnose problems on a TCP/IP network,
> or with SIP specifically?  It sounds like you're not trying the most
> basic troubleshooting techniques.
>
>
> Cheers,
> Todd.
>
> ps.  When I did the Google search I suggested above, I found that all of
> the first page of search results seem to be relevant.  The first one
> sounds particularly promising since it's from a site called "Asterisk
> Guru".
>
>
>> -----Original Message-----
>> From: Tincho ylm [mailto:sa...@gm...]
>> Sent: Tuesday, August 18, 2009 8:42 AM
>> To: sip...@li...
>> Subject: [Sipp-users] Aborting call on unexpected message
>>
>> Hi all.
>>
>> I have received this message a couple times (all depends of
>> the number of simultaneous calls). By example: If I try 100
>> calls and 8 simultaneous, I get this message fifty times:
>>
>> Aborting call on unexpected message for Call-Id '80-19001@UAC-IP':
>> while expecting '180' (index 2), received 'SIP/2.0 603 Declined
>> Via: SIP/2.0/UDP UAC-IP:5061;branch=z9hG4bK-19001-80-0;received=UAC-IP
>> From: sipp <sip:sipp@UAC-IP:5061>;tag=80
>> To: sut <sip:1234@ASTERIX-IP8:5060>;tag=as4fc7680d
>> Call-ID: 80-19001@UAC-IP
>> CSeq: 1 INVITE
>> User-Agent: Asterisk PBX
>> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
>> Supported: replaces
>> Contact: <sip:1234@ASTERIX-IP>
>> Content-Length: 0
>>
>> But, If I try 100 calls and 10 simultaneous, I get the same
>> message 69th times. I'm using a 1 Mb internet connection.
>>
>> How can I know the cause of the failed calls? I mean, is the
>> connection? is my LAN? is the Asterisk? How can I know?
>>
>> Thanks all!
>>
>> --------------------------------------------------------------
>> ----------------
>> Let Crystal Reports handle the reporting - Free Crystal
>> Reports 2008 30-Day trial. Simplify your report design,
>> integration and deployment - and focus on what you do best,
>> core application coding. Discover what's new with Crystal
>> Reports now.  http://p.sf.net/sfu/bobj-july
>> _______________________________________________
>> Sipp-users mailing list
>> Sip...@li...
>> https://lists.sourceforge.net/lists/listinfo/sipp-users
>>
>