Re: [GnomeMeeting-devel-list] Can't register to Digisip

From: Damien Sandras <dsandras seconix com>
To: GnomeMeeting development mailing list <gnomemeeting-devel-list gnome org>
Subject: Re: [GnomeMeeting-devel-list] Can't register to Digisip
Date: Wed, 07 Dec 2005 12:52:24 +0100
Hello,

Can you try again tomorrow with the new gnomemeeting version?
I have fixed something while eating my sandwich that will at least
prevent it to stay in the "Registering" state in your case :)


Le mercredi 07 décembre 2005 à 11:40 +0100, cooky hey shacknet nu a
écrit :
> Hello! I was recommended to bring this issue to the
> gnomemeeting-devel-list, even though it is also kind of a support
> request.
> I have subscribed to a pc<->phone service called Digisip, but I haven't
> managed to register yet. I hope to get some simple assistance from the
> GM community. This is how I try to set up the account in yesterday's
> gnomemeeting-opal snapshot:
> 
>   * Registrar:   proxy.digisip.net
>   * Realm/Domain:   I don't know what this is, but I set it to
> proxy.digisip.net as well. Maybe this is where the problem lies.
>   * Username:   A five digit number that I have recieved as "account ID"
>   * Password
>   * Registration timeout:   120 (which is apparently the minimum
> allowed)
> 
> When I try to register by clicking on the "L" checkbox, it changes
> status to "registering". But nothing happens, even after some 10
> minutes. It's not possible to uncheck the checkbox. Even next time I
> start gnomemeeting, when I open the account manager, it will say
> "registering" and show a timeglass mouse pointer. Is this a bug?
> If I change the username to something bogus, I will at least see a
> "registration failed" message immediately.
> Thanks in advance! Debug output follows:
> /Eric
> 
> 
> 2005/12/07 10:44:54.031   0:00.563                 gnomemeeting Detected
> audio plugins: ALSA,OSS
> 2005/12/07 10:44:54.036   0:00.567                 gnomemeeting Detected
> video plugins: Picture,V4L
> 2005/12/07 10:44:54.049   0:00.580                 gnomemeeting Detected
> audio plugins: ALSA,OSS
> 2005/12/07 10:44:54.063   0:00.594                 gnomemeeting Detected
> video plugins: Picture,V4L
> 2005/12/07 10:44:54.489   0:01.021                 gnomemeeting Detected
> the following audio input devices: VIA 8235,USB Device
> 0x46d:0x8b2,Default with plugin ALSA
> 2005/12/07 10:44:54.501   0:01.033                 gnomemeeting Detected
> the following audio output devices: VIA 8235,Default with plugin ALSA
> 2005/12/07 10:44:54.502   0:01.033                 gnomemeeting Detected
> the following video input devices: Logitech QuickCam Pro 4000 with
> plugin V4L
> 2005/12/07 10:44:54.513   0:01.044                 gnomemeeting Detected
> the following audio input devices: VIA 8235,USB Device
> 0x46d:0x8b2,Default with plugin ALSA
> 2005/12/07 10:44:54.535   0:01.066                 gnomemeeting Detected
> the following audio output devices: VIA 8235,Default with plugin ALSA
> 2005/12/07 10:44:54.548   0:01.079                 gnomemeeting Detected
> the following video input devices: Logitech QuickCam Pro 4000 with
> plugin V4L
> 2005/12/07 10:44:55.410   0:01.941                 gnomemeeting
> GnomeMeeting version 1.9.0
> 2005/12/07 10:44:55.411   0:01.942                 gnomemeeting OPAL
> version unknown
> 2005/12/07 10:44:55.424   0:01.956                 gnomemeeting PWLIB
> version 1.9.2
> 2005/12/07 10:44:55.425   0:01.956                 gnomemeeting GNOME
> support enabled
> 2005/12/07 10:44:55.444   0:01.975                 gnomemeeting
> Fullscreen support enabled
> 2005/12/07 10:44:55.445   0:01.976                 gnomemeeting DBUS
> support disabled
> 2005/12/07 10:44:55.483   0:02.014                 gnomemeeting Set TCP
> port range to 3000030010
> 2005/12/07 10:44:55.484   0:02.015                 gnomemeeting Set RTP
> port range to 50005016
> 2005/12/07 10:44:55.500   0:02.031                 gnomemeeting Set UDP
> port range to 50605100
> 2005/12/07 10:44:55.514   0:02.058                 gnomemeeting OpalEP
> Created endpoint: h323
> 2005/12/07 10:44:55.528   0:02.075                 gnomemeeting H323
> Created endpoint.
> 2005/12/07 10:44:55.560   0:02.091                 gnomemeeting OpalMan
> Added route "pc:.*=h323:<da>"
> 2005/12/07 10:44:55.561   0:02.092                 gnomemeeting OpalEP
> Created endpoint: sip
> 2005/12/07 10:44:55.576   0:02.119                 gnomemeeting SIP
> Created endpoint.
> 2005/12/07 10:44:55.607   0:02.138                 gnomemeeting OpalMan
> Added route "pc:.*=sip:<da>"
> 2005/12/07 10:44:55.608   0:02.139                 gnomemeeting OpalEP
> Created endpoint: pc
> 2005/12/07 10:44:55.679   0:02.210                 gnomemeeting PCSS
> Created PC sound system endpoint.
> 2005/12/07 10:44:55.680   0:02.211                 gnomemeeting OpalMan
> Added route "h323:.*=pc:<da>"
> 2005/12/07 10:44:55.695   0:02.226                 gnomemeeting OpalMan
> Added route "sip:.*=pc:<da>"
> 2005/12/07 10:44:56.115   0:02.646        Opal Listener:89c0130 Listen
> Started listening thread on tcp$85.228.79.57:1720
> 2005/12/07 10:44:56.115   0:02.646        Opal Listener:89c0130 Listen
> Waiting on socket accept on tcp$85.228.79.57:1720
> 2005/12/07 10:44:56.131   0:02.662        Opal Listener:89c0da8 Listen
> Started listening thread on udp$85.228.79.57:5060
> 2005/12/07 10:44:56.146   0:02.677        Opal Listener:89c0da8 Listen
> Waiting on UDP packet on udp$85.228.79.57:5060
> 2005/12/07 10:48:49.616   3:56.147      GMAccounts...r:08a18c78 OpalUDP
> Binding to interface: 85.228.79.57:32820
> 2005/12/07 10:48:49.619   3:56.150      GMAccounts...r:08a18c78 SIP
> Created transport udp$0.0.0.0<if=udp$85.228.79.57:32820>
> 2005/12/07 10:48:49.658   3:56.189      GMAccounts...r:08a18c78 OpalUDP
> Started connect to 82.209.165.194:5060
> 2005/12/07 10:48:49.660   3:56.205      GMAccounts...r:08a18c78 OpalUDP
> Connect on pre-bound interface: 85.228.79.57
> 2005/12/07 10:48:49.676   3:56.223      GMAccounts...r:08a18c78 SIP
> Created Transport for Registrar udp$82.209.165.194:5060<if=udp
> $85.228.79.57:5061>
> 2005/12/07 10:48:49.721   3:56.252        SIP Transport:8a1d278 SIP
> Read thread started.
> 2005/12/07 10:48:49.721   3:56.252        SIP Transport:8a1d278 SIP
> Waiting for PDU on udp$82.209.165.194:5060<if=udp$85.228.79.57:5061>
> 2005/12/07 10:48:49.755   3:56.286      GMAccounts...r:08a18c78 SIP
> Sending PDU on udp$82.209.165.194:5060<if=udp$85.228.79.57:5061>
> REGISTER sip:proxy.digisip.net SIP/2.0
> CSeq: 1 REGISTER
> Via: SIP/2.0/UDP
> 85.228.79.57:5061;branch=z9hG4bK20432c56-7465-da11-986c-000ea67d7128;rport
> User-Agent: GnomeMeeting/1.9.0
> From:
> <sip:##### proxy digisip net>;tag=9a522a56-7465-da11-986c-000ea67d7128
> Call-ID:
> 3a251c56-7465-da11-986c-000ea67d7128 c-394fe455 09-237-73746f34 cust bredbandsbolaget se
> To: <sip:##### proxy digisip net>
> Contact: <sip:##### 85 228 79 57:5060;transport=udp>
> Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, REGISTER, SUBSCRIBE, NOTIFY,
> REFER, MESSAGE
> Expires: 120
> Content-Length: 0
> Max-Forwards: 70
> 
> 
> 2005/12/07 10:48:49.793   3:56.324        SIP Transport:8a1d278 SIP
> PDU Received on udp$82.209.165.194:5060<if=udp$85.228.79.57:5061>
> SIP/2.0 100 Trying
> CSeq: 1 REGISTER
> Via: SIP/2.0/UDP
> 85.228.79.57:5061;branch=z9hG4bK20432c56-7465-da11-986c-000ea67d7128;rport=5061
> Server: Sip EXpress router (0.9.3 (i386/linux))
> From:
> <sip:##### proxy digisip net>;tag=9a522a56-7465-da11-986c-000ea67d7128
> Call-ID:
> 3a251c56-7465-da11-986c-000ea67d7128 c-394fe455 09-237-73746f34 cust bredbandsbolaget se
> To: <sip:##### proxy digisip net>
> Warning: 392 82.209.165.194:5060 "Noisy feedback tells:  pid=31386
> req_src_ip=85.228.79.57 req_src_port=5061 in_uri=sip:proxy.digisip.net
> out_uri=sip:proxy.digisip.net via_cnt==1"
> Content-Length: 0
> 
> 
> 2005/12/07 10:48:49.839   3:56.382        SIP Transport:8a1d278 SIP
> Transaction 1 REGISTER proceeding.
> 2005/12/07 10:48:49.852   3:56.396        SIP Transport:8a1d278 OpalUDP
> Ended connect, selecting 85.228.79.57:5061
> 2005/12/07 10:48:49.867   3:56.411        SIP Transport:8a1d278 SIP
> Waiting for PDU on udp$82.209.165.194:5060<if=udp$85.228.79.57:5061>
> 2005/12/07 10:48:49.882   3:56.430        SIP Transport:8a1d278 SIP
> PDU Received on udp$82.209.165.194:5060<if=udp$85.228.79.57:5061>
> SIP/2.0 401 Unauthorized
> CSeq: 1 REGISTER
> Via: SIP/2.0/UDP
> 85.228.79.57:5061;branch=z9hG4bK20432c56-7465-da11-986c-000ea67d7128;rport=5061
> Server: Sip EXpress router (0.9.3 (i386/linux))
> From:
> <sip:##### proxy digisip net>;tag=9a522a56-7465-da11-986c-000ea67d7128
> Call-ID:
> 3a251c56-7465-da11-986c-000ea67d7128 c-394fe455 09-237-73746f34 cust bredbandsbolaget se
> To:
> <sip:##### proxy digisip net>;tag=9d0c2f86226119ed3517373c02465a4b.1fe6
> Warning: 392 82.209.165.194:5060 "Noisy feedback tells:  pid=31386
> req_src_ip=85.228.79.57 req_src_port=5061 in_uri=sip:proxy.digisip.net
> out_uri=sip:proxy.digisip.net via_cnt==1"
> Content-Length: 0
> WWW-Authenticate: Digest realm="proxy.digisip.net",
> nonce="4396b0ea4e9fd9d86e891168a31d451862c1cc75"
> 
> 
> 2005/12/07 10:48:49.944   3:56.498        SIP Transport:8a1d278 SIP
> Transaction 1 REGISTER completed.
> 2005/12/07 10:48:49.968   3:56.512        SIP Transport:8a1d278 SIP
> Received Authentication Required response
> 2005/12/07 10:48:49.999   3:56.531        SIP Transport:8a1d278 SIP
> Adding authentication information
> 2005/12/07 10:48:50.002   3:56.545        SIP Transport:8a1d278 SIP
> Sending PDU on udp$82.209.165.194:5060<if=udp$85.228.79.57:5061>
> REGISTER sip:proxy.digisip.net SIP/2.0
> CSeq: 2 REGISTER
> Via: SIP/2.0/UDP
> 85.228.79.57:5061;branch=z9hG4bK8eb45656-7465-da11-986c-000ea67d7128;rport
> User-Agent: GnomeMeeting/1.9.0
> Authorization: Digest username="#####", realm="proxy.digisip.net",
> nonce="4396b0ea4e9fd9d86e891168a31d451862c1cc75",
> uri="sip:proxy.digisip.net",
> response="42ff48391a4bbf2ef197fbdb102071ff", algorithm=md5
> From:
> <sip:##### proxy digisip net>;tag=7a665456-7465-da11-986c-000ea67d7128
> Call-ID:
> 3a251c56-7465-da11-986c-000ea67d7128 c-394fe455 09-237-73746f34 cust bredbandsbolaget se
> To: <sip:##### proxy digisip net>
> Contact: <sip:##### 85 228 79 57:5060;transport=udp>
> Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, REGISTER, SUBSCRIBE, NOTIFY,
> REFER, MESSAGE
> Expires: 120
> Content-Length: 0
> Max-Forwards: 70
> 
> 
> 2005/12/07 10:48:50.016   3:56.585        SIP Transport:8a1d278 SIP
> Waiting for PDU on udp$82.209.165.194:5060<if=udp$85.228.79.57:5061>
> 2005/12/07 10:48:50.056   3:56.602        SIP Transport:8a1d278 SIP
> PDU Received on udp$82.209.165.194:5060<if=udp$85.228.79.57:5061>
> SIP/2.0 100 Trying
> CSeq: 2 REGISTER
> Via: SIP/2.0/UDP
> 85.228.79.57:5061;branch=z9hG4bK8eb45656-7465-da11-986c-000ea67d7128;rport=5061
> Server: Sip EXpress router (0.9.3 (i386/linux))
> From:
> <sip:##### proxy digisip net>;tag=7a665456-7465-da11-986c-000ea67d7128
> Call-ID:
> 3a251c56-7465-da11-986c-000ea67d7128 c-394fe455 09-237-73746f34 cust bredbandsbolaget se
> To: <sip:##### proxy digisip net>
> Warning: 392 82.209.165.194:5060 "Noisy feedback tells:  pid=31383
> req_src_ip=85.228.79.57 req_src_port=5061 in_uri=sip:proxy.digisip.net
> out_uri=sip:proxy.digisip.net via_cnt==1"
> Content-Length: 0
> 
> 
> 2005/12/07 10:48:50.109   3:56.663        SIP Transport:8a1d278 SIP
> Transaction 2 REGISTER proceeding.
> 2005/12/07 10:48:50.133   3:56.677        SIP Transport:8a1d278 SIP
> Waiting for PDU on udp$82.209.165.194:5060<if=udp$85.228.79.57:5061>
> 2005/12/07 10:48:50.147   3:56.694        SIP Transport:8a1d278 SIP
> PDU Received on udp$82.209.165.194:5060<if=udp$85.228.79.57:5061>
> SIP/2.0 401 Unauthorized
> CSeq: 2 REGISTER
> Via: SIP/2.0/UDP
> 85.228.79.57:5061;branch=z9hG4bK8eb45656-7465-da11-986c-000ea67d7128;rport=5061
> Server: Sip EXpress router (0.9.3 (i386/linux))
> From:
> <sip:##### proxy digisip net>;tag=7a665456-7465-da11-986c-000ea67d7128
> Call-ID:
> 3a251c56-7465-da11-986c-000ea67d7128 c-394fe455 09-237-73746f34 cust bredbandsbolaget se
> To:
> <sip:##### proxy digisip net>;tag=9d0c2f86226119ed3517373c02465a4b.f467
> Warning: 392 82.209.165.194:5060 "Noisy feedback tells:  pid=31383
> req_src_ip=85.228.79.57 req_src_port=5061 in_uri=sip:proxy.digisip.net
> out_uri=sip:proxy.digisip.net via_cnt==1"
> Content-Length: 0
> 
> 
> 2005/12/07 10:48:50.204   3:56.754        SIP Transport:8a1d278 SIP
> Transaction 2 REGISTER completed.
> 2005/12/07 10:48:50.225   3:56.774        SIP Transport:8a1d278 SIP
> Received Authentication Required response
> 2005/12/07 10:48:50.244   3:56.775        SIP Transport:8a1d278 SIP
> Unknown authentication type
> 2005/12/07 10:48:50.245   3:56.792        SIP Transport:8a1d278 SIP
> Waiting for PDU on udp$82.209.165.194:5060<if=udp$85.228.79.57:5061>
> 2005/12/07 10:48:51.016   3:57.547                  Housekeeper SIP
> Set state Terminated_Success for transaction 1 REGISTER
> 2005/12/07 10:48:51.245   3:57.776                  Housekeeper SIP
> Set state Terminated_Success for transaction 2 REGISTER
> 
> 
> _______________________________________________
> Gnomemeeting-devel-list mailing list
> Gnomemeeting-devel-list gnome org
> http://mail.gnome.org/mailman/listinfo/gnomemeeting-devel-list
-- 
 _      Damien Sandras
(o-     
//\     GnomeMeeting: http://www.gnomemeeting.org/
v_/_    FOSDEM 2006 : http://www.fosdem.org
        SIP Phone   : sip:dsandras gnomemeeting net 
                      sip:600000 gnomemeeting net
Follow-Ups:
- Re: [GnomeMeeting-devel-list] Can't register to Digisip
  - From: cooky
References:
- [GnomeMeeting-devel-list] Can't register to Digisip
  - From: cooky
[Date Prev][Date Next] [Thread Prev][Thread Next] [Thread Index] [Date Index] [Author Index]