|Summary:||ASTERISK-07487: Frontrange's Goldmine 6.7 SIP Client|
|Date Opened:||2006-08-08 12:00:28||Date Closed:||2006-08-21 14:50:03|
|Description:||Hello, have tried working with frontrange on this issue, but they say their sip client is 100% standards compliant, yet their SIP client embedded into their product will not successfully register in a manner that will allow us to use the sip phone to place or recieve calls. The only information I've been able to gather is pasted below:|
Jul 27 10:48:47 DEBUG chan_sip.c: SIP message could not be handled, bad request: firstname.lastname@example.org
Jul 27 12:11:16 DEBUG chan_sip.c: = No match Their Call ID: email@example.com Their Tag 3b77d0 Our tag: as2905cb31
Jul 27 12:11:18 DEBUG chan_sip.c: = Found Their Call ID: firstname.lastname@example.org Their Tag 3b77d0 Our tag: as2905cb31
Jul 27 12:11:18 DEBUG chan_sip.c: SIP message could not be handled, bad request: email@example.com
Jul 27 12:11:20 DEBUG chan_sip.c: = No match Their Call ID: firstname.lastname@example.org Their Tag 3b77d0 Our tag: as2905cb31
Jul 27 12:11:25 DEBUG chan_sip.c: Auto destroying call 'email@example.com'
Is this a bug w/asterisk or is it really Frontrange's product that is causing the error?
Thank you in advance
|Comments:||By: Joshua C. Colp (jcolp) 2006-08-08 12:09:48|
I'll take a page from vechers' book:
I) As per bug guidelines, could you please attach a SIP debug trace illustrating the problem. Please do the following:
1) Prepare test environment (reduce the ammount of unrelated traffic on the server);
2) Make sure your logger.conf has the following line:
console => notice,warning,error,debug
3) restart Asterik.
4) Enable SIP transaction logging with the following CLI commands:
set debug 4
set verbose 4
5) Save complete console log to file and _attach_ said file to the bug.
That way we can see the complete dialog that's going on.
By: Joshua C. Colp (jcolp) 2006-08-08 12:10:38
Also - try the latest Asterisk 1.2 release, 1.2.10 - Thanks!
By: Serge Vecher (serge-v) 2006-08-21 14:49:52
no response from the reporter. Please reopen the issue if you are able to reproduce the problem with latest Asterisk release (1.2.10).