Maxim, We already faced, and documented those errors codes: *Code* *Command* *Description* *Most common cause* E0 any Syntax error E3 any Unknown command E8 D *(delete)* delete requestest failed: session *CALL_ID*, tags *FROMTAG* /*TOTAG* not found Session timed out in the RTPProxy server. E10 U * (update)* can't bind to the IPv4 port XXXXX: Cannot assign requested address RTPProxy server was bound to an invalid address (-l parameter). The listen address is not verified in the server initialization. But recently in a performance testing in our solution we faced E7, so I'd like to know the meaning of E7 (I guess this is related to not enough File Descriptors), and if it's possible the other possible codes.
Best regards, Antonio Anderson Souza Voice Technology http://www.antonioams.com On Wed, Jun 9, 2010 at 3:33 AM, Maxim Sobolev <[email protected]> wrote: > On 6/8/2010 6:05 PM, Antonio Anderson Souza wrote: > >> We are using the rtpproxy inside our IP-Centrex platform, and we >> developed an Java RTP Proxy Client library [1], I'd like to ask you guys >> where can we find all of the possible error codes because we've >> documented only some that we faced during our tests. >> >> Can someone point me where I can find those error codes and its >> descriptions? >> > > Actually we have never had stable error code API. What do you need it for > exactly? Usually for most commands, we only need 3 possible statuses - > "success", "session lookup failure" and "error". Specific error values are > there mostly for debugging purposes. > > Regards, > -- > Maksym Sobolyev > Sippy Software, Inc. > Internet Telephony (VoIP) Experts > T/F: +1-646-651-1110 > Web: http://www.sippysoft.com > MSN: [email protected] > Skype: SippySoft >
_______________________________________________ Devel mailing list [email protected] http://lists.rtpproxy.org/mailman/listinfo/devel
