Re: [Ekiga-list] Problems incoming calls.

[Bas Driessen <bas driessen xobas com>]

On Sat, 2009-02-14 at 23:06 +1000, Bas Driessen wrote:
>      On Sat, 2009-02-14 at 11:38 +0100, Damien Sandras wrote: 
> > Le samedi 14 février 2009 à 10:48 +1000, Bas Driessen a écrit :
> > > Hello,
> > > 
> > > I am using Ekiga 3.0.2 on Fedora 10 x86_64 (64 bit). I have a VoIP
> > > account with my internet provider and I have setup Ekiga to use that
> > > and that all works fine. However, within a couple of minutes, the
> > > incoming calls do not work anymore. It goes straight to the voice
> > > mail. If I de-register and register again, all works again for a
> > > minute or 2 and then same problem. Outgoing calls are fine and stable.
> > > 
> > > What can be a possible cause and/or what can I do to further
> > > investigate. To eliminate the fact that it is not a
> > > router/infrastructure etc issue, I have tested with Twinkle. This
> > > package seems stable both incoming as outgoing. So the issue appears
> > > to be with Ekiga.
> > > 
> > > How can I see how I am registered in Ekiga? I want to see something
> > > like this: <sip:012345678 192 168 1 44>;q=0.500;expires=360. As
> > > outgoing calls still work, registration must perhaps get confused
> > > somehow and change to something like:
> > > <sip:012345678-ksfjklfj 192 168 1 44>;q=0.500;expires=360 (I am only
> > > guessing) meaning that I am still connected to a sip server, but not
> > > linked anymore to the incoming number.
> > > 
> > > Any ideas/tips/hints/solutions are appreciated.
> >
> > Perhaps the NAT binding on the router is closed.
> >
> > We send a 'probe' every 10 seconds to keep it alive. 
> >
> > Perhaps you could try sending a probe every 3 seconds. To change this,
> > you can edit the following key :
> > /apps/ekiga/protocols/sip/binding_timeout
> > using gconftool or gconf-editor. 
> >
> > Do not edit the config files manually, it won't work.
> >     
>      
>     Thanks Damien. Tried that, but it did not work unfortunately.  Fedora release ekiga-3.0.2-2.fc10 update yesterday. Updated and also no change.
>     
>     Is it possible that the problem is on the provider site? If so, which value/setting should I ask them to set/use?
>     
>     Anything else in Ekiga I can set. Proxy for instance? Can I edit STUN settings in Ekiga? Any other ideas?
>     
>     Thanks again.
>     

Can the following be an issue? It looks to me it is retrying something 3 times and then give up? (note, I have changed my real SIP number for a dummy number for obvious privacy reasons)


2009/02/14 23:57:15.447	 10:59.032	 Housekeeper:0x3ef66950	SIP	Starting PUBLISH for offline retry
2009/02/14 23:57:15.447	 10:59.032	 Housekeeper:0x3ef66950	SIP	Expiry time for PUBLISH set to 500 seconds.
2009/02/14 23:57:15.515	 10:59.100	 Housekeeper:0x3ef66950	SIP	Transaction remote address is udp$203.2.134.1:5060
2009/02/14 23:57:15.515	 10:59.100	 Housekeeper:0x3ef66950	SIP	Sending PDU PUBLISH sip:012345678 sip internode on net (881 bytes) to: rem=udp$203.2.134.1:5060,local=udp$59.167.214.42:5060,if=192.168.1.14%br0
2009/02/14 23:57:15.516	 10:59.101	 Housekeeper:0x3ef66950	SIP	Expiry time for PUBLISH set to 500 seconds.
2009/02/14 23:57:15.553	 10:59.138	 Housekeeper:0x3ef66950	SIP	Transaction remote address is udp$203.2.134.1:5060
2009/02/14 23:57:15.553	 10:59.138	 Housekeeper:0x3ef66950	SIP	Sending PDU PUBLISH sip:012345678 sip internode on net (881 bytes) to: rem=udp$203.2.134.1:5060,local=udp$192.168.122.1:5060,if=192.168.122.1%virbr0
2009/02/14 23:57:15.592	 10:59.177	Opal Liste...0x3ef25950	OpalUDP	Binding to interface: 59.167.214.42:5060
2009/02/14 23:57:15.592	 10:59.177	Opal Liste...0x3ef25950	SIP	No Content-Length present from udp$203.2.134.1:5060<if=udp$59.167.214.42:5060>, reading till end of datagram/stream.
2009/02/14 23:57:15.592	 10:59.177	Opal Liste...0x3ef25950	SIP	PDU 405  Method Not Allowed received: rem=udp$203.2.134.1:5060,local=udp$59.167.214.42:5060,if=192.168.1.14%br0
2009/02/14 23:57:15.593	 10:59.178	Opal Liste...0x3ef25950	SIP	Transaction 39 PUBLISH completed.
2009/02/14 23:57:15.593	 10:59.178	Opal Liste...0x3ef25950	Opal	Transport clean up on termination
2009/02/14 23:57:15.947	 10:59.532	 Housekeeper:0x3ef66950	SIP	Transaction 40 PUBLISH timeout, making retry 1
2009/02/14 23:57:15.948	 10:59.533	 Housekeeper:0x3ef66950	SIP	Sending PDU PUBLISH sip:012345678 sip internode on net (881 bytes) to: rem=udp$203.2.134.1:5060,local=udp$192.168.122.1:5060,if=192.168.122.1%virbr0
2009/02/14 23:57:16.594	 11:00.179	 Housekeeper:0x3ef66950	SIP	Set state Terminated_Success for transaction 39 PUBLISH
2009/02/14 23:57:16.947	 11:00.532	 Housekeeper:0x3ef66950	SIP	Transaction 40 PUBLISH timeout, making retry 2
2009/02/14 23:57:16.948	 11:00.533	 Housekeeper:0x3ef66950	SIP	Sending PDU PUBLISH sip:012345678 sip internode on net (881 bytes) to: rem=udp$203.2.134.1:5060,local=udp$192.168.122.1:5060,if=192.168.122.1%virbr0
2009/02/14 23:57:18.948	 11:02.533	 Housekeeper:0x3ef66950	SIP	Transaction 40 PUBLISH timeout, making retry 3
2009/02/14 23:57:18.948	 11:02.533	 Housekeeper:0x3ef66950	SIP	Sending PDU PUBLISH sip:012345678 sip internode on net (881 bytes) to: rem=udp$203.2.134.1:5060,local=udp$192.168.122.1:5060,if=192.168.122.1%virbr0
2009/02/14 23:57:21.447	 11:05.032	 Housekeeper:0x3ef66950	SIP	Set state Terminated_Timeout for transaction 40 PUBLISH

Thanks,
Bas.