I'm trying to configure Jigasi for testing, and am having some problems
when it comes to connecting to a SIP registrar.
I've tried ekiga, and linphone so far.
LinPhone bombs out on the initial connection:
newState=RegistrationState=Registering; reasonCode=-1; reason=null]
2018-03-30 17:44:17.524 INFO: 
Gettting source address for /10.2.0.22 -> sip3.li
2018-03-30 17:44:17.890 SEVERE: 
Unable to create a via header for port 5060
javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
Using Ekiga gets further, but ends up failing with:
2018-03-30 18:28:15.971 INFO: 
org.jitsi.jigasi.AbstractGateway.registrationStateChanged().120 REG STATE
CHANGE ProtocolProviderServiceSipImpl(firstname.lastname@example.org (SIP)) ->
newState=RegistrationState=Connection Failed; reasonCode=-1;
reason=Received an error while trying to register. Server returned
It looks like the SIP code corresponds to:
"606 Not AcceptableThe user's agent was contacted successfully but some
aspects of the session description such as the requested media, bandwidth,
or addressing style were not acceptable."
Is this an issue maybe with trying to use Jigasi behind a NAT (AWS)?
At this point I don't really care what the registrar is.. I just want to
Is there a known SIP provider that other people are using that they know
will just work?
Or is there some other configuration that is needed for AWS that would make
my Ekiga account not bomb out?
- Jason Thomas.