Bug#365588: Configuration

[Santiago Garcia Mantinan]

> I use Nikotel to call to POTS.

I don't know this service, could it be that nikotel is hanging your call
because of a problem with a firewall or nat device?

I suffered similar problems with another provider calling it through an
asterisk server, the asterisk server was redirecting the RTP traffic from
the provider to my twinkle and the firewall was cutting that, so the call
was muted after a while, I solved this on asterisk by changing the default
setting of ...
;canreinvite=yes                ; allow RTP voice traffic to bypass Asterisk

Anyway, I would check the firewall's logs if I were you just in case...

> My audio setting in twinkle are:
> ALSA: default: Default device
> for ring tone, speaker and microphone.
> play period size is 128, capture period size is 32.

Twinkle doesn't recommend to use the default device for capture (mic), in
fact I tried to set up mine like that and it could not open the mic (I think
I could do it before, but anyway). I'd try to select the alsa device you
want for mic and if you suspect it can be an audio problem (I'd say it is
not but who knows?) even try with the alsa oss emulation. I used to have
problems with alsa when using it for the mic, but using alsa oss emulation
for the mic worked ok.

> ALSA device list:
>   #0: Intel ICH6 with STAC9752,53 at 0xdfebfe00, irq 201
>   #1: Intel ICH6 Modem at 0xee00, irq 177

I don't know this driver personally maybe somebody with this driver can make
some tests to see if they see similar problems?

I think it would be good if you could try twinkle against some other SIP
service, you can even set up your own service (I use my own asterisk server
for testing purposes) to test with it.

Regards...
-- 
Manty/BestiaTester -> http://manty.net