Maxim, Nowadays it returns directly what the RTPProxy Error codes, but it's really a good idea create an Object and group the errors by type! great idea!
I asked for the list of possible error codes to document it better, and in the next step we can create a better error handling and reporting with objects, types, messages, etc. Best regards, Antonio Anderson Souza Voice Technology http://www.antonioams.com On Sat, Jun 12, 2010 at 2:05 PM, Maxim Sobolev <[email protected]>wrote: > On 6/9/2010 6:06 AM, Antonio Anderson Souza wrote: > >> 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. >> > > I wonder how do you use those. Just passing it to the caller? Perhaps it > would be better to return few unified classes of errors (i.e. no resources, > syntax error, session not found) and also provide detailed human-readable > error message with each error. What do you think? > > > 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
