24 apr 2012 kl. 16:04 skrev Daniel-Constantin Mierla:
Hello,
On 4/24/12 3:55 PM, Olle E. Johansson wrote:
24 apr 2012 kl. 14:27 skrev Daniel-Constantin Mierla:
Hello,
thanks, I found that as well, but I didn't wanted to believe is no update to it in regard to sip client behavior. A phone replying with such generic code is really misleading for such case . So I searched further in 4xx class, base rfc and other extensions, and could not find anything.
You propably want to add a reason header or something to explain for the poor guy running wireshark. The error code is not all.
I would do if I was developing the hard/softphone. So I was actually wondering how to detect such situation based on the reply received in the proxy.
Btw, what Asterisk/Sems does in this situation (just for the developers of such end points here :-) ), any special hint-header added?
No for Asterisk. It should, really.
/O