Calling Feature

[MurhafSousli]

closes #65

[MurhafSousli]

@ifoche I think I have located the problem, I tried the following URIs:

wss://dev.eyeseetea.com
wss://dev.eyeseetea.com:8443
wss://dev.eyeseetea.com:80
wss://dev.eyeseetea.com:8080

ws://dev.eyeseetea.com
ws://dev.eyeseetea.com:8443
ws://dev.eyeseetea.com:80
ws://dev.eyeseetea.com:8080

All these responded with 403 error immediately. However, when I used wss://dev.eyeseetea.com:5060 I didn't get the same error, the app showed connecting and after a while I get handshake timed out error. Basically, our Kamailio server didn't respond with anything on 5060

---

Using the guys' app settings worked, I am able to connect to their kamailo server successfully

[ifoche]

@tokland can you help @MurhafSousli with this? Maybe we could setup a meeting to talk about this?

[tokland]

CSipSimple uses the port 5060 (no TLS), wss was untested. I've set up a real certificate for dev.eyeseetea.com (let's encrypt) and use it in kamailio, now I see this in the Chrome console:

SIP/2.0 200 OK
Via: SIP/2.0/AUTO u57ihl7f6p5h.invalid;branch=z9hG4bK4850048;rport=53562;received=185.26.139.89
To: <sip:1@dev.eyeseetea.com>;tag=cfe2a596ee411df91ca0a89ee67a9faa.6cc3

Using: wss://dev.eyeseetea.com:8443

@MurhafSousli can you test if it works now as expected?

[MurhafSousli]

@tokland It worked 👍

[MurhafSousli]

@tokland Can we have the following fields in sip in logged in response

{
   // ...
   "sip": {
        "host": "wss://dev.eyeseetea.com:8443",
        "authorization_user": "1",
        "password": "USER_PASSWORD",
        "domain": "dev.eyeseetea.com"
    }
}

Once user is logged in, SIP will initialize with these values

[ifoche]

Hi @MurhafSousli, I think it shouldn't be necessary.

• I've just changed the host to "dev.eyeseetea.com". With that, you can build the actual host by including wss:// at the beginning and :8443 at the end
• We're using the phoneNumber as the authorization_user.
• The password is exactly the same from the user, as we're doing the login against kamailio
• The domain you can just use by default what's returned in host by now. And later we can think if it worth the pain to change the property from "host" to "domain" in the WS

Can you confirm that you can proceed with that?

[MurhafSousli]

Hi @ifoche

• The current host has the port 5060 at the end which does not work for our Kamailio server
• Currently the app stores the encoded token for the username & password (which is used in every request), but not the password as string

If there is no time for this then its fine, I can find a workaround to get it to work

[ifoche]

Hi @MurhafSousli,

that's why I said "I've just changed the host". I deleted that 5060. Maybe your API's client is caching the previous result? Otherwise you shouldn't see the port.

Re your second point I guess it's possible to store the password also as a string to use it as part of the SIP configuration? Do you think it's very difficult?

[MurhafSousli]

@ifoche Ok 👍 That will do. No, it is not difficult

[MurhafSousli]

@ifoche @tokland Hey guys, I am getting this error on accepting an incoming call The error seems to be related to Kamailio, but I am not sure! are you familiar with this?