Ekiga registration: Not Acceptable
Brought to you by:
krunalhire
Originally created by: os...@valdez-bicard.com.sv
What steps will reproduce the problem?
1.Enter or edit Ekiga username and password in CSipSimple
2.Hit Save button
3.Accounts screen shows "Error al registrar - Not acceptable" next to Ekiga icon
What is the expected output? What do you see instead?
Expected: "Registered" - Instead: "Error al registrar - Not acceptable"
What version of the product are you using? On what operating system?
0.03-01 [r1108] on Android 2.3.4
Please provide any additional information below.
Phone is a Samsung Galaxy S2 (GT-I9100)
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: r3gis...@gmail.com
Did you manually disable stun server?
It could also be because ekiga stun server is down. You can maybe try another public one. For example stun.ippi.fr
In fact you get this problem because ekiga does not allow to register with a private ip.
Normally stun is there to know your public IP in public network.
this operation is not really linked to the provider, that's why you can try with the stun server of another provider. By default the ekiga wizard setup ekiga stun server because of the fact ekiga restrict register to public IP. But possible that there is currently a problem on this server.
Normally if the stun resolution goes well ekiga will not cry anymore
Status: WrongConfig
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: os...@valdez-bicard.com.sv
STUN is enabled, and there are three STUN servers configured: stun.ekiga.net,stun.ippi.fr,stun.counterpath.com
This last one (stun.counterpath.com) seems to be added automatically at the end of the list whenever a server is added to it.
I configured a PC on the same LAN with the same username/password, and it registered correctly.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: os...@valdez-bicard.com.sv
stun.counterpath.com does not respond to pings. Is it somehow hardwired, making CSipSimple dependent on it?
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: r3gis...@gmail.com
The stun server of ekiga is DNS alias for another stun servers. So maybe sometimes it load balance on invalid one. And indeed seems that there is some problem with counterpath's one.
So try to remove all but the one of ippi.
By default to make things easier for users stun.counterpath.com is added (many users doesn't know what stun is about and I want to simplify their life as much as possible ;) ).
Then if there is a setup from a different wizard the stun server of the wizard will be inserted in the list.
Normally the sip stack behind csipsimple should try all stun server configured but I'm not sure if it goes well in all error cases (maybe a dns error on one of the stun server can completely break stun things).
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: os...@valdez-bicard.com.sv
I've tried leaving only stun.ekiga.net or stun.ippi.fr, and in both cases I get the "Error al registrar - Not acceptable" message :(
Any other tips?
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: r3gis...@gmail.com
Well weird.
Can you try to collect some logs. See HowToCollectLogs wiki page.
Maybe something in logs can give us a clue about why ekiga does not allow registration :)
Thx
Status: Need-Details
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: r3gis...@gmail.com
For the record on the issue list after private mails ;) : to be linked to issue 345.
The problem was that a first account did a register to a local account previously to the one to ekiga. As consequence, pjsip detected its public ip to be the one of the phone in the LAN area and did the registration using this IP.
The clean way to solve this kind of issue is the one proposed in issue 345.
However it should be possible to try to workaround by disabling contact rewrite feature on first account (maybe need to force contact header on this account)
Maybe reordering account priority could help for first registration too, but I do not advise this method cause could be broken in next registration.
Mergedinto: 345
Status: Duplicate
Related
Tickets:
#345