Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • J jami-client-gnome
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 89
    • Issues 89
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • savoirfairelinux
  • jami-client-gnome
  • Issues
  • #699

Closed
Open
Created Dec 19, 2017 by RingBot@RingBotOwner

SIP registration: "invalid" with no reason why

Issue generated from Tuleap's migration script. Originally submitted by: szotsaki (szotsaki)

It's not possible to register to SIP provider StuntCalls. With Ekiga and Zoiper Android it works. Gnome client just gives back the "invalid" state, but there is no error message at all what could go wrong. Please, enhance the error reporting.

Console message:

(gnome-ring:30900): Gtk-CRITICAL \*\*: gtk\_widget\_destroy: assertion 'GTK\_IS\_WIDGET (widget)' failed   
  
(gnome-ring:30900): Gtk-CRITICAL \*\*: gtk\_widget\_destroy: assertion 'GTK\_IS\_WIDGET (widget)' failed   
  
(gnome-ring:30900): Gtk-CRITICAL \*\*: gtk\_widget\_destroy: assertion 'GTK\_IS\_WIDGET (widget)' failed   
  
(gnome-ring:30900): Gtk-CRITICAL \*\*: gtk\_widget\_destroy: assertion 'GTK\_IS\_WIDGET (widget)' failed  
  
07:43:03.036  sip\_resolve.c  Starting async DNS SRV query: target=\_sip.\_udp.sip.stuntcalls.com, transport=UDP, port=0   
07:43:03.036 \_sip.\_udp.sip.  Starting async DNS SRV query\_job: target=\_sip.\_udp.sip.stuntcalls.com:5060   
07:43:03.036     resolver.c  Nameserver 127.0.0.1:53 state changed Active --> Probing   
07:43:03.036     resolver.c  Nameserver 0.0.0.0:0 state changed Bad --> Probing   
07:43:03.036     resolver.c  Nameserver 208.67.222.222:53 state changed Active --> Probing   
07:43:03.037     resolver.c  Transmitting 46 bytes to NS 2 (208.67.222.222:53): DNS SRV query for \_sip.\_udp.sip.stuntcalls.com: Success   
07:43:03.037     resolver.c  Transmitting 46 bytes to NS 0 (127.0.0.1:53): DNS SRV query for \_sip.\_udp.sip.stuntcalls.com: Success   
07:43:03.037     resolver.c  Transmitting 46 bytes to NS 1 (0.0.0.0:0): DNS SRV query for \_sip.\_udp.sip.stuntcalls.com: Invalid argument   
07:43:03.067     resolver.c  Received 121 bytes DNS response from 208.67.222.222:53   
07:43:03.067     resolver.c  Nameserver 208.67.222.222:53 state changed Probing --> Active   
07:43:03.067 \_sip.\_udp.sip.  DNS SRV resolution failed for \_sip.\_udp.sip.stuntcalls.com: DNS "Name Error" (PJLIB\_UTIL\_EDNS\_NXDOMAIN)   
07:43:03.067 \_sip.\_udp.sip.  DNS SRV resolution failed for \_sip.\_udp.sip.stuntcalls.com, trying resolving A/AAAA record for sip.stuntcalls.com   
07:43:03.067 \_sip.\_udp.sip.  Starting async DNS A query\_job for sip.stuntcalls.com   
07:43:03.067     resolver.c  Transmitting 36 bytes to NS 2 (208.67.222.222:53): DNS A query for sip.stuntcalls.com: Success   
07:43:03.067     resolver.c  Transmitting 36 bytes to NS 0 (127.0.0.1:53): DNS A query for sip.stuntcalls.com: Success   
07:43:03.067     resolver.c  Transmitting 36 bytes to NS 1 (0.0.0.0:0): DNS A query for sip.stuntcalls.com: Invalid argument   
07:43:03.067     resolver.c  Transmitting 36 bytes to NS 2 (208.67.222.222:53): DNS AAAA query for sip.stuntcalls.com: Success   
07:43:03.067     resolver.c  Transmitting 36 bytes to NS 0 (127.0.0.1:53): DNS AAAA query for sip.stuntcalls.com: Success   
07:43:03.067     resolver.c  Transmitting 36 bytes to NS 1 (0.0.0.0:0): DNS AAAA query for sip.stuntcalls.com: Invalid argument   
07:43:03.088     resolver.c  Received 121 bytes DNS response from 127.0.0.1:53   
07:43:03.088     resolver.c  Nameserver 127.0.0.1:53 state changed Probing --> Active   
07:43:03.088     resolver.c  DNS response from 127.0.0.1:53 id=11 discarded   
07:43:03.098     resolver.c  Received 52 bytes DNS response from 208.67.222.222:53   
07:43:03.098     resolver.c  Nameserver 208.67.222.222:53 state changed Active --> Active   
07:43:03.098 \_sip.\_udp.sip.  DNS A for sip.stuntcalls.com: 77.72.169.131   
07:43:03.108     resolver.c  Received 111 bytes DNS response from 208.67.222.222:53   
07:43:03.108     resolver.c  Nameserver 208.67.222.222:53 state changed Active --> Active   
07:43:03.108 \_sip.\_udp.sip.  Server resolution complete, 1 server entry(s) found   
07:43:03.124     resolver.c  Received 111 bytes DNS response from 127.0.0.1:53   
07:43:03.124     resolver.c  Nameserver 127.0.0.1:53 state changed Active --> Active   
07:43:03.124     resolver.c  DNS response from 127.0.0.1:53 id=13 discarded   
07:43:03.134     resolver.c  Received 52 bytes DNS response from 127.0.0.1:53   
07:43:03.134     resolver.c  Nameserver 127.0.0.1:53 state changed Active --> Active   
07:43:03.134     resolver.c  DNS response from 127.0.0.1:53 id=12 discarded  

* Environment:
openSUSE Tumbleweed, x64, Gnome Ring client

Assignee
Assign to
Time tracking