Closed GoogleCodeExporter closed 8 years ago
Are you using a bluetooth headset?
Original comment by eofs...@gmail.com
on 26 May 2010 at 2:09
No, usb headset
Original comment by jasenko....@gmail.com
on 26 May 2010 at 11:00
Could you please attach a crash report? It’s in ~/Library/Logs/CrashReporter.
Available via Finder or
Console.app.
Original comment by eofs...@gmail.com
on 30 May 2010 at 11:31
Yesterday I had the same problem: every call resulted in a crash. But today I'm
unable to reproduce this error
because instead of the crash every interaction with the sip server results in
the following error message:
"Message too long (PJSIP_EMSGTOOLONG)"
Original comment by ja...@php4you.de
on 31 May 2010 at 11:42
Attachments:
[deleted comment]
foxx@jbbr.net, is ICE enabled?
Original comment by eofs...@gmail.com
on 31 May 2010 at 12:06
Yes, it was enabled. I disabled it and now the crash is back. I added the crash
report and the Telephone.log file.
Original comment by ja...@php4you.de
on 31 May 2010 at 12:14
Attachments:
foxx@jbbr.net, are you using a USB headset?
Original comment by eofs...@gmail.com
on 31 May 2010 at 12:20
No. I have a USB sound card plugged in but for Telephone I'm using the build in
macbook microphone and
output.
Now I disabled DNS SRV, saved, restarted telephone and suddenly everything
works well. I even tried call
transfer and holding - perfect!
Than I reenabled DNS SRV, saved, restarted telephone and everything still works
fine... Don't know what the
problem was but when it appears again I will write here again.
But ICE support would be fine - With ICE I was able to call through a UMTS
provider NAT - At least I think that
ICE was responsible for this.
Thank you for your great application!
Original comment by ja...@php4you.de
on 31 May 2010 at 12:29
You can still try it with ICE. Maybe it’s just some temporary error. Or does
it always work for you with the
previous version?
Original comment by eofs...@gmail.com
on 31 May 2010 at 10:28
With the previous version I never had any crashs or message too long errors -
Sometimes some little bugs, for
example that I didn't heard anything or something like this but restarting
telephone always fixed these temporary
bugs. I always had ICE and DNS SRV enabled.
Now with 0.15 when enabling ICE I get the message too long error and when
disabling it works (or crashs, but I'm
unable to reproduce these crashes again)
Original comment by ja...@php4you.de
on 31 May 2010 at 10:53
foxx@jbbr.net, could you please send me the log with the “too long” error?
But before that, please increase the
log level. Run the following command in Terminal when Telephone isn’t
launched. And don’t forget to quit
Telephone before sending the file.
defaults write com.tlphn.Telephone LogLevel -integer 4
Original comment by eofs...@gmail.com
on 31 May 2010 at 10:59
ok
Original comment by ja...@php4you.de
on 31 May 2010 at 11:08
Attachments:
foxx@jbbr.net, could you please send me the same, but from Telephone 0.14.3?
You can send it to me directly
(eofster@gmail.com) with or without anonymizing.
Original comment by eofs...@gmail.com
on 31 May 2010 at 11:19
done.
For me the logs looks like in my case 0.14.3 isn't using STUN but ICE instead
and 0.15 has problems with ICE and
uses STUN when ICE is disabled.
Original comment by ja...@php4you.de
on 31 May 2010 at 11:35
I think “Message too long” started to happen in 0.15 because of this.
Telephone 0.15 uses pjproject-1.6. pjproject1.6 adds additional fields to the
SIP messages. Combined with all features enabled (STUN, ICE), the size of
outgoing SIP packets sometimes exceeds pjproject’s own limit. I will increase
that limit in the next update, but for now you have two options. You can use
Telephone 0.14.3 or you can disable ICE.
Original comment by eofs...@gmail.com
on 12 Jun 2010 at 4:07
PJSIP_MAX_PKT_LEN was increased in pjsip itself. Telephone 0.15.1 will be
linked against pjsip >= 1.8.5 where this is already solved.
Original comment by eofs...@gmail.com
on 5 Dec 2010 at 3:15
Fixed with 0.15.1 release.
Original comment by eofs...@gmail.com
on 13 Dec 2010 at 11:40
Original issue reported on code.google.com by
jasenko....@gmail.com
on 26 May 2010 at 12:27