Hi Tristan,

I'm now using the build from last night

ii  sflphone-client-gnome                  1.2.0-rc20121213~ppa1~precise
        GNOME client for SFLphone
ii  sflphone-common                        1.2.0-rc20121213~ppa1~precise
        SIP and IAX2 compatible softphone - Core

I notice that there is only a single sflphoned udp socket listening on port
5060 this time (no second socket on port 60592 like before) and that it is
bound to address 0.0.0.0 to listen on all interfaces as opposed to the
192.168.1.1 address.

udp        0      0 0.0.0.0:5060            0.0.0.0:*
    13694/sflphoned
unix  2      [ ]         DGRAM                    226381   13694/sflphoned

unix  3      [ ]         STREAM     CONNECTED     225859
13687/sflphone-clie
unix  3      [ ]         STREAM     CONNECTED     225786   13694/sflphoned

unix  3      [ ]         STREAM     CONNECTED     225783   13694/sflphoned

unix  3      [ ]         STREAM     CONNECTED     224893   13694/sflphoned

unix  3      [ ]         STREAM     CONNECTED     224247
13687/sflphone-clie
unix  3      [ ]         STREAM     CONNECTED     224246
13687/sflphone-clie
unix  3      [ ]         STREAM     CONNECTED     224245
13687/sflphone-clie
unix  3      [ ]         STREAM     CONNECTED     222794
13687/sflphone-clie

I notice that if I get disconnected from wireless, I get the following in
/var/log/syslog and then the sflphoned stops running and exits:

Dec 14 10:15:20 jlynch-Vostro-3350 sflphoned: networkmanager.cpp:49:tid
59200:#011Network state changed: unknown
Dec 14 10:15:20 jlynch-Vostro-3350 sflphoned: networkmanager.cpp:54:tid
59200:#011Properties changed:
Dec 14 10:15:20 jlynch-Vostro-3350 sflphoned: networkmanager.cpp:57:tid
59200:#011ActiveConnections
Dec 14 10:15:20 jlynch-Vostro-3350 sflphoned: networkmanager.cpp:57:tid
59200:#011State
Dec 14 10:15:20 jlynch-Vostro-3350 sflphoned: sipvoiplink.cpp:2016:tid
59200:#011Could not register account Account:1354718606 with error 503
Dec 14 10:15:20 jlynch-Vostro-3350 sflphoned: sipaccount.cpp:653:tid
59200:#011UserAgent: VoipLinkException occured: Unable to send account
registration request
Dec 14 10:15:40 jlynch-Vostro-3350 sflphoned: sipvoiplink.cpp:2016:tid
39744:#011Could not register account Account:1354718606 with error 503
Dec 14 10:15:40 jlynch-Vostro-3350 sflphoned: sipvoiplink.cpp:2000:tid
39744:#011Could not register account Account:1354718606 with error 400


Dec 14 10:28:26 jlynch-Vostro-3350 sflphoned: networkmanager.cpp:49:tid
5952:#011Network state changed: unknown
Dec 14 10:28:26 jlynch-Vostro-3350 sflphoned: networkmanager.cpp:54:tid
5952:#011Properties changed:
Dec 14 10:28:26 jlynch-Vostro-3350 sflphoned: networkmanager.cpp:57:tid
5952:#011ActiveConnections
Dec 14 10:28:26 jlynch-Vostro-3350 sflphoned: networkmanager.cpp:57:tid
5952:#011State
Dec 14 10:28:26 jlynch-Vostro-3350 sflphoned: sipvoiplink.cpp:2016:tid
5952:#011Could not register account Account:1354718606 with error 503
Dec 14 10:28:26 jlynch-Vostro-3350 sflphoned: sipaccount.cpp:653:tid
5952:#011UserAgent: VoipLinkException occured: Unable to send account
registration request
Dec 14 10:29:12 jlynch-Vostro-3350 sflphoned: sipvoiplink.cpp:2016:tid
52032:#011Could not register account Account:1354718606 with error 503
Dec 14 10:29:12 jlynch-Vostro-3350 sflphoned: sipvoiplink.cpp:2000:tid
52032:#011Could not register account Account:1354718606 with error 400
Dec 14 10:29:14 jlynch-Vostro-3350 sflphoned: sipvoiplink.cpp:2016:tid
52032:#011Could not register account Account:1354718606 with error 503
Dec 14 10:29:14 jlynch-Vostro-3350 sflphoned: sipvoiplink.cpp:2000:tid
52032:#011Could not register account Account:1354718606 with error 400

Also when I resume from suspend mode, i sometimes see the socket still in
netstat and then other times both the client and daemon were somehow
terminated and nothing in /var/log/syslog

Regards
Jonathan

On 13 December 2012 19:56, Tristan Matthews <
[email protected]> wrote:

> Hi Jonathan,
>
> ----- Original Message -----
> > From: "Jonathan Lynch" <[email protected]>
> > To: "Tristan Matthews" <[email protected]>,
> [email protected]
> > Sent: Wednesday, December 12, 2012 2:01:14 PM
> > Subject: Re: [SFLphone] sflphone registration issues
> >
> >
> > Hi Tristan,
> >
> >
> > Some more info regarding the sockets from netstat
> >
> >
> > Before suspend
> >
> >
> > sudo netstat -alnp | grep sfl
> >
> > udp 0 0 192.168.1.1:5060 0.0.0.0:* 22472/sflphoned
> > udp 0 0 192.168.1.1:60592 0.0.0.0:* 22472/sflphoned
> > unix 2 [ ] DGRAM 1551793 22472/sflphoned
> > unix 3 [ ] STREAM CONNECTED 1545608 22844/sflphone-clie
> > unix 3 [ ] STREAM CONNECTED 1545509 22844/sflphone-clie
> > unix 3 [ ] STREAM CONNECTED 1542654 22844/sflphone-clie
> > unix 3 [ ] STREAM CONNECTED 1543451 22844/sflphone-clie
> > unix 3 [ ] STREAM CONNECTED 1543450 22844/sflphone-clie
> > unix 3 [ ] STREAM CONNECTED 1544488 22844/sflphone-clie
> > unix 3 [ ] STREAM CONNECTED 1493140 22472/sflphoned
> > unix 3 [ ] STREAM CONNECTED 1493134 22472/sflphoned
> > unix 3 [ ] STREAM CONNECTED 1491398 22472/sflphoned
> >
> >
> > After resume (all sflphoned sockets dont seem to be connected
> > anymore).
> >
> >
> >
> >
> >
> > sudo netstat -alnp | grep sfl
> > unix 3 [ ] STREAM CONNECTED 1545608 22844/sflphone-clie
> > unix 3 [ ] STREAM CONNECTED 1545509 22844/sflphone-clie
> > unix 3 [ ] STREAM CONNECTED 1542654 22844/sflphone-clie
> > unix 3 [ ] STREAM CONNECTED 1543451 22844/sflphone-clie
> > unix 3 [ ] STREAM CONNECTED 1543450 22844/sflphone-clie
> > unix 3 [ ] STREAM CONNECTED 1544488 22844/sflphone-clie
>
> This should be fixed in master, could you try the
> https://launchpad.net/~savoirfairelinux/+archive/sflphone-nightly ppa
> as of tomorrow and confirm?
>
> Best,
> Tristan
>
> >
> >
> >
> > What I did was edit -> accounts -> edit account -> (make no changes)
> > -> apply
> > and I see "Registered. Server returned "OK" (200) at the bottom of
> > the accounts menu and I can make calls again.
> >
> >
> > or else I just killed the client and the daemon to get it working
> > again.
> >
> >
> > Regards
> > Jonathan
> >
> >
> >
> > On 12 December 2012 13:39, Jonathan Lynch < [email protected]
> > > wrote:
> >
> >
> > Hi Tristan,
> >
> >
> > What I did was edit -> accounts -> edit account -> (make no changes)
> > -> apply
> > and I see "Registered. Server returned "OK" (200) at the bottom of
> > the accounts menu and I can make calls again.
> >
> >
> > or else I just killed the client and the daemon to get it working
> > again.
> >
> >
> > Thanks
> > Jonathan
> >
> >
> >
> >
> > On 12 December 2012 12:48, Tristan Matthews <
> > [email protected] > wrote:
> >
> >
> > Hi Jonathan,
> >
> >
> > ----- Original Message -----
> > > From: "Jonathan Lynch" < [email protected] >
> > > To: [email protected]
> > > Sent: Wednesday, December 12, 2012 9:51:52 AM
> > > Subject: [SFLphone] sflphone registration issues
> > >
> > >
> > >
> > >
> > > Hi,
> > >
> > >
> > > I connect to a work asterix SIP server and experience registration
> > > issues on resumption after suspending my laptop.
> > > I'm running Ubuntu 12.04 with version 1.2.0 of sflphone installed
> > >
> > >
> > > ii sflphone-client-gnome 1.2.0~ppa1~precise GNOME client for
> > > SFLphone
> > >
> > > ii sflphone-common 1.2.0~ppa1~precise SIP and IAX2 compatible
> > > softphone - Core
> > >
> > >
> > > The output from syslog is included below. From the source code I
> > > see
> > > that the error codes correspond to the following
> > >
> > >
> > >
> > >
> > > PJSIP_SC_BAD_REQUEST = 400
> > >
> > >
> > > PJSIP_SC_REQUEST_TIMEOUT = 408
> > >
> > >
> > > PJSIP_SC_SERVICE_UNAVAILABLE = 503
> > >
> > >
> > >
> > > Any Ideas how to resolve these issues?
> >
> > Thanks for all the detailed info, I've created a bug report here to
> > track the problem:
> > https://projects.savoirfairelinux.com/issues/18494
> >
> > This is definitely a bug, I'm guessing that SFLphone needs to reopen
> > its SIP socket in this case.
> > As a temporary workaround, if you unregister and register your
> > account, are you able to make calls
> > or does it stay in the same state?
> >
> > Best,
> > Tristan
> >
> >
> >
> > >
> > > Thanks
> > > Jonathan
> > >
> > >
> > > ------------
> > >
> > >
> > > Dec 11 13:29:35 sflphoned: managerimpl.cpp:351: Could not hang up
> > > call, call not valid
> > > Dec 11 13:29:45 sflphoned: sdp.cpp:89: Could not find rtpmap
> > > attribute
> > >
> > >
> > > Dec 11 16:55:37 sflphoned: networkmanager.cpp:49: Network state
> > > changed: unknown
> > > Dec 11 16:55:37 sflphoned: networkmanager.cpp:54: Properties
> > > changed:
> > > Dec 11 16:55:37 sflphoned: networkmanager.cpp:57: ActiveConnections
> > > Dec 11 16:55:37 sflphoned: networkmanager.cpp:57: State
> > > Dec 11 16:55:37 sflphoned: sipvoiplink.cpp:1914: Could not register
> > > account Account:1354718606 with error 503
> > > Dec 11 16:55:37 sflphoned: sipaccount.cpp:652: UserAgent:
> > > VoipLinkException occured: Unable to send account registration
> > > request
> > > Dec 11 16:55:40 sflphoned: sipvoiplink.cpp:1914: Could not register
> > > account Account:1354718606 with error 503
> > > Dec 11 16:55:40 sflphoned: sipvoiplink.cpp:1898: Could not register
> > > account Account:1354718606 with error 400
> > >
> > >
> > > Dec 12 00:40:43 sflphoned: networkmanager.cpp:49: Network state
> > > changed: unknown
> > > Dec 12 00:40:43 sflphoned: networkmanager.cpp:49: Network state
> > > changed: unknown
> > > Dec 12 00:40:43 sflphoned: networkmanager.cpp:54: Properties
> > > changed:
> > > Dec 12 00:40:43 sflphoned: networkmanager.cpp:57: ActiveConnections
> > > Dec 12 00:40:43 sflphoned: networkmanager.cpp:57: State
> > > Dec 12 00:40:43 sflphoned: sipvoiplink.cpp:1914: Could not register
> > > account Account:1354718606 with error 503
> > > Dec 12 00:40:43 sflphoned: sipaccount.cpp:652: UserAgent:
> > > VoipLinkException occured: Unable to send account registration
> > > request
> > > Dec 12 00:40:43 sflphoned: networkmanager.cpp:54: Properties
> > > changed:
> > > Dec 12 00:40:43 sflphoned: networkmanager.cpp:57: ActiveConnections
> > > Dec 12 00:40:43 sflphoned: sipvoiplink.cpp:1914: Could not register
> > > account Account:1354718606 with error 503
> > > Dec 12 00:40:43 sflphoned: sipaccount.cpp:652: UserAgent:
> > > VoipLinkException occured: Unable to send account registration
> > > request
> > > Dec 12 00:40:44 sflphoned: networkmanager.cpp:49: Network state
> > > changed: unknown
> > > Dec 12 00:40:44 sflphoned: networkmanager.cpp:54: Properties
> > > changed:
> > > Dec 12 00:40:44 sflphoned: networkmanager.cpp:57: ActiveConnections
> > > Dec 12 00:40:44 sflphoned: networkmanager.cpp:57: State
> > > Dec 12 00:40:44 sflphoned: sipvoiplink.cpp:1914: Could not register
> > > account Account:1354718606 with error 503
> > > Dec 12 00:40:44 sflphoned: sipaccount.cpp:652: UserAgent:
> > > VoipLinkException occured: Unable to send account registration
> > > request
> > > Dec 12 00:40:44 sflphoned: networkmanager.cpp:54: Properties
> > > changed:
> > > Dec 12 00:40:44 sflphoned: networkmanager.cpp:57: ActiveConnections
> > > Dec 12 00:40:44 sflphoned: sipvoiplink.cpp:1914: Could not register
> > > account Account:1354718606 with error 503
> > > Dec 12 00:40:44 sflphoned: sipaccount.cpp:652: UserAgent:
> > > VoipLinkException occured: Unable to send account registration
> > > request
> > > Dec 12 00:40:46 sflphoned: networkmanager.cpp:49: Network state
> > > changed: unknown
> > > Dec 12 00:40:46 sflphoned: networkmanager.cpp:54: Properties
> > > changed:
> > > Dec 12 00:40:46 sflphoned: networkmanager.cpp:57: State
> > > Dec 12 00:41:21 sflphoned: sipvoiplink.cpp:1927: Could not register
> > > account Account:1354718606 with error 408
> > > Dec 12 00:41:22 sflphoned: networkmanager.cpp:49: Network state
> > > changed: unknown
> > > Dec 12 00:41:22 sflphoned: networkmanager.cpp:54: Properties
> > > changed:
> > > Dec 12 00:41:22 sflphoned: networkmanager.cpp:57: ActiveConnections
> > > Dec 12 00:41:22 sflphoned: networkmanager.cpp:57: State
> > > Dec 12 00:41:22 sflphoned: sipvoiplink.cpp:1914: Could not register
> > > account Account:1354718606 with error 503
> > > Dec 12 00:41:22 sflphoned: sipaccount.cpp:652: UserAgent:
> > > VoipLinkException occured: Unable to send account registration
> > > request
> > > Dec 12 00:41:22 sflphoned: networkmanager.cpp:49: Network state
> > > changed: unknown
> > > Dec 12 00:41:22 sflphoned: networkmanager.cpp:54: Properties
> > > changed:
> > > Dec 12 00:41:22 sflphoned: networkmanager.cpp:57: ActiveConnections
> > > Dec 12 00:41:22 sflphoned: networkmanager.cpp:57: State
> > > Dec 12 00:41:22 sflphoned: sipvoiplink.cpp:1914: Could not register
> > > account Account:1354718606 with error 503
> > > Dec 12 00:41:22 sflphoned: sipaccount.cpp:652: UserAgent:
> > > VoipLinkException occured: Unable to send account registration
> > > request
> > > Dec 12 00:41:22 sflphoned: networkmanager.cpp:54: Properties
> > > changed:
> > > Dec 12 00:41:22 sflphoned: networkmanager.cpp:57: ActiveConnections
> > > Dec 12 00:41:22 sflphoned: sipvoiplink.cpp:1914: Could not register
> > > account Account:1354718606 with error 503
> > > Dec 12 00:41:22 sflphoned: sipaccount.cpp:652: UserAgent:
> > > VoipLinkException occured: Unable to send account registration
> > > request
> > > Dec 12 00:41:23 sflphoned: sipvoiplink.cpp:1914: Could not register
> > > account Account:1354718606 with error 503
> > > Dec 12 00:41:23 sflphoned: sipvoiplink.cpp:1914: Could not register
> > > account Account:1354718606 with error 503
> > >
> > >
> > > _______________________________________________
> > > SFLphone mailing list
> > > [email protected]
> > > http://lists.savoirfairelinux.net/mailman/listinfo/sflphone
> > >
> >
> > --
> >
> > Tristan Matthews
> > Développeur de logiciels libres
> > [email protected]
> > Ligne directe: 514-276-5468 poste 190
> >
> > Fax : 514-276-5465
> > 7275 Saint Urbain
> > Bureau 200
> > Montréal, QC, H2R 2Y5
> >
> >
> >
> >
>
> --
>
> Tristan Matthews
> Développeur de logiciels libres
> [email protected]
> Ligne directe: 514-276-5468 poste 190
>
> Fax : 514-276-5465
> 7275 Saint Urbain
> Bureau 200
> Montréal, QC, H2R 2Y5
>
>
_______________________________________________
SFLphone mailing list
[email protected]
http://lists.savoirfairelinux.net/mailman/listinfo/sflphone

Reply via email to