Open aduggirala28 opened 7 years ago
@aduggirala28 registration indeed fails, but doesn't seem to be because of wrong credentials; instead it seems to timeout somehow. But how do you know that the credentials are right? Do you have an account in cloud.restcomm.com? If so have you checked if there is a client called user_name
(or whatever you use to REGISTER from restcomm-web-sdk)
Yes, I do have an account on cloud.restcomm.com. Yes the caller is a client on cloud.restcomm and the callee is number linked with an RVD app.
@aduggirala28 if you are using the sample code, can you try it without registration, like we illustrate here and call for example +1235@cloud.restcomm.com. Does that work?
I'm facing the same issue after changing restcomm to use SSL instead of plain HTTP. btw, I'm using CentOS 7, Restcomm-JBoss-AS7-8.7.1.25, a self signed certificate (instructed here) and I have defined my hostname in restcomm.conf as well.
Here are my browser logs :
2018-02-09 20:46:01.258 ERROR PrivateJainSipClientConnector:processSipRegisterResponse(): SIP registration failed:403 [object Object]
Stack trace:
at commonLog (https://192.168.x.x:8443/olympus/resources/assets/WebRTComm.63fcb1db625e783e.js:4950:10)
at console.error (https://192.168.x.x:8443/olympus/resources/assets/WebRTComm.63fcb1db625e783e.js:5023:4)
at PrivateJainSipClientConnector.processSipRegisterResponse (https://192.168.x.x:8443/olympus/resources/assets/WebRTComm.63fcb1db625e783e.js:1821:12)
at PrivateJainSipClientConnector.processResponse (https://192.168.x.x:8443/olympus/resources/assets/WebRTComm.63fcb1db625e783e.js:1646:9)
at EventScanner.deliverEvent (https://192.168.x.x:8443/olympus/resources/assets/jain-sip.cb5c2df41b743fd3.js:29648:25)
at SipProviderImpl.handleEvent (https://192.168.x.x:8443/olympus/resources/assets/jain-sip.cb5c2df41b743fd3.js:30884:27)
at DialogFilter.processResponseargu3 (https://192.168.x.x:8443/olympus/resources/assets/jain-sip.cb5c2df41b743fd3.js:30376:17)
at DialogFilter.processResponse (https://192.168.x.x:8443/olympus/resources/assets/jain-sip.cb5c2df41b743fd3.js:30234:14)
at SIPClientTransaction.nonInviteClientTransaction (https://192.168.x.x:8443/olympus/resources/assets/jain-sip.cb5c2df41b743fd3.js:28101:32)
at SIPClientTransaction.processResponseargu3 (https://192.168.x.x:8443/olympus/resources/assets/jain-sip.cb5c2df41b743fd3.js:28071:18)
commonLog @ WebRTComm.63fcb1db625e783e.js:4991
WebRTComm.63fcb1db625e783e.js:4991 2018-02-09 20:46:01.258 ERROR WebRTCommClient:onPrivateClientConnectorOpenErrorEvent():error:undefined
Stack trace:
at commonLog (https://192.168.x.x:8443/olympus/resources/assets/WebRTComm.63fcb1db625e783e.js:4950:10)
at console.error (https://192.168.x.x:8443/olympus/resources/assets/WebRTComm.63fcb1db625e783e.js:5023:4)
at WebRTCommClient.onPrivateClientConnectorOpenErrorEvent (https://192.168.x.x:8443/olympus/resources/assets/WebRTComm.63fcb1db625e783e.js:4819:10)
at PrivateJainSipClientConnector.processSipRegisterResponse (https://192.168.x.x:8443/olympus/resources/assets/WebRTComm.63fcb1db625e783e.js:1823:25)
at PrivateJainSipClientConnector.processResponse (https://192.168.x.x:8443/olympus/resources/assets/WebRTComm.63fcb1db625e783e.js:1646:9)
at EventScanner.deliverEvent (https://192.168.x.x:8443/olympus/resources/assets/jain-sip.cb5c2df41b743fd3.js:29648:25)
at SipProviderImpl.handleEvent (https://192.168.x.x:8443/olympus/resources/assets/jain-sip.cb5c2df41b743fd3.js:30884:27)
at DialogFilter.processResponseargu3 (https://192.168.x.x:8443/olympus/resources/assets/jain-sip.cb5c2df41b743fd3.js:30376:17)
at DialogFilter.processResponse (https://192.168.x.x:8443/olympus/resources/assets/jain-sip.cb5c2df41b743fd3.js:30234:14)
at SIPClientTransaction.nonInviteClientTransaction (https://192.168.x:8443/olympus/resources/assets/jain-sip.cb5c2df41b743fd3.js:28101:32)
@atsakiridis
I think it could be useful if I add some server side DEBUG level logs as well, clearing out my issue :
06:24:34,351 DEBUG [gov.nist.javax.sip.stack.NioTcpMessageProcessor] (RestComm-akka.actor.default-dispatcher-39) Connected. lets set WRITE ops.
06:24:34,352 DEBUG [org.mobicents.servlet.sip.message.TransactionApplicationData] (MSS-Executor-Thread-3) cleaning up the application data org.mobicents.servlet.sip.message.TransactionApplicationData@9b15c3f
06:24:34,352 DEBUG [gov.nist.javax.sip.stack.NioTcpMessageProcessor] (RestComm-akka.actor.default-dispatcher-39) Waking up selector thread
06:24:34,352 DEBUG [org.mobicents.servlet.sip.core.session.SipSessionImpl] (MSS-Executor-Thread-3) cleanDialogInformation null
06:24:34,352 DEBUG [org.mobicents.servlet.sip.core.session.SipSessionImpl] (MSS-Executor-Thread-3) cleanDialogInformation terminate false
06:24:34,352 DEBUG [gov.nist.javax.sip.stack.NioTcpMessageProcessor] (NioSelector-WSS-192.168.x.x/5083) null selectedKeys
06:24:34,352 DEBUG [org.mobicents.servlet.sip.core.session.SipApplicationSessionImpl] (MSS-Executor-Thread-3) Before Semaphore released for sipApplicationSession=4d01c13b;RestComm semaphore=java.util.concurrent.Semaphore@5b1f3111[Permits = 0]
06:24:34,352 INFO [gov.nist.javax.sip.stack.SIPTransactionStack] (RestComm-akka.actor.default-dispatcher-39) <message
from="192.168.x.x:5083"
to="192.168.x.y:1860"
time="1536067474350"
isSender="true"
transactionId="z9hg4bk-393132-3f05db1d3a873c992e25d956a255e45c"
callId="1536067474225"
firstLine="SIP/2.0 403 Forbidden"
>
<![CDATA[SIP/2.0 403 Forbidden
To: <sip:myuser@192.168.x.x>;tag=84305530_3d67b3b4_57a5b08a_4d01c13b
Via: SIP/2.0/WSS 192.168.x.y:1860;branch=z9hG4bK-393132-3f05db1d3a873c992e25d956a255e45c;rport=1860;received=192.168.x.y
CSeq: 2 REGISTER
Call-ID: 1536067474225
From: <sip:myuser@192.168.x.x>;tag=1536067474226
Server: Restcomm 8.4.0-227
Content-Length: 0
]]>
</message>
A bizarre resolution for my problem: Guys, after changing the RestComm connectivity mode to SSL, strangely you need to delete all the clients you had defined in the system before and recreate them again (Changing client's password doesn't suffice here, you need to explicitly delete the client). A bit disappointed of RestComm team neither mentioned this in any doc nor fixed the problem in the code (It literally took 48 hours of my time, going back and force among docs and forums). but thanks anyways for a great free communication platform.
Hi Majid,
I have the same error on registration am receiving 403 and am not using SSL. can you please let me know what am doing wrong 👍
this is my configuration:
>>>>>> Restcomm.conf <<<<<<<
NET_INTERFACE='ens160' PRIVATE_IP='192.168.153.174' SUBNET_MASK='255.255.255.0' NETWORK='192.168.153.1' BROADCAST_ADDRESS='182.168.153.255'
STATIC_ADDRESS=''
RESTCOMM_HOSTNAME='OldUbuntu'
advanced.conf <<<<<<<
SECURESSL=FALSE TRUSTSTORE_FILE='inmokey.jks' #File should be located at $RESTCOMM_HOME/standalone/configuration folder. Provide just the name of the trustore file. TRUSTSTORE_PASSWORD='password' #Password for the trustore file TRUSTSTORE_ALIAS='inmo' #The certificate alias
SSL_PROTOCOLS=''
SSL_CIPHER_SUITES=''
DISABLE_HTTP='true' #Control HTTP connector behavior. Values, TRUE=HTTP connector will be disable, FALSE=HTTP Connector will be active, REDIRECT= http -> https redirection will be enabled (For CLI RestAPI requests when redirect is active https needs to be used).
SSL_MODE='allowall' #Values allowall=allow self-signed certificates, strict=don't allow self signed certificates. If SECURESSL=SELF set to "allowall" automaticaly.
Am using hostname as you can see but when i wanna register my client i do it this way:
99199:192.168.153.174:5060 UDP/TCP
i tried with hostname but no luck
99199:OldUbuntu:5060 UDP/TCP
Br
I have the SIP registration error while doing the tutorial at http://docs.telestax.com/restcomm-client-web-sdk-quick-start/ . I have given my own login credentials.The credentials are right as I am able to login with them at cloud.restcomm.com. I am trying to call from the a restcomm client to a SIP number linked to an app I designed using the RVD. The hello world demo also produces the same errors. Thank you. Given below are the errors/logs in my browser console.