| k3b wish
Nov 2 2005 on content K3b |
How about this?
We put a CD in the drive and start a project that will normalize each track, encode for mp3 or ogg, tag the file and put the resulting files into the folder of our choice. Is there an app that already does this? |
|  | | Re: Re: outgoing proxy
Aug 8 2005 on content Twinkle |
I found the source of my confusion. Twinkle erroneously reports in its display area that the outgoing proxy and the registrar are the same. It did in fact send the registration request to the registrar as it should.
I also found two more problems. The first one concerns multiple contacts. When a registration is complete the registrar will report back with the contacts it has for the address of record. Twinkle apparently sees multiple contacts as no contacts and reports that registration failed with "Contact missing". Twinkle is happy if it is the only contact.
The third problem is audio cutoff and premature call release by the far end. I believe this occurs when the 200 OK has two URI's in its record-route. When the UA responds with ACK it should include a route header with the same URI's that were received in record-route. It seems to include only the most recent URI which is the outgoing proxy. The outgoing proxy will forward the ACK to the request URI and not to the next proxy.
I have had success with kphone. Kphone however is short on features and KDE integration. I wish you success with the twinkle project. |
| | | Re: Re: outgoing proxy
Jul 27 2005 on content Twinkle |
The intent is to have the registration request go to the registrar via the outgoing proxy. If the registrar is left blank, twinkle assumes the proxy is the registrar. |
| | | outgoing proxy
Jul 27 2005 on content Twinkle |
The outgoing proxy parameter is ignored. Registration goes directly to registrar. |
| |
Search people
Current visitors
New users
Birthdays
Most active users
Back
|
|
