Voximplant integration. #259
Comments
|
Dear @0bhat, |
|
|
Hope this helps |
|
|
|
I got it working too, but now the problem is this user never seems to get logged it even when Voximplant is sending the calls to the logged in user: Just keeps ringing: |
|
I think this is the missing link: Where can I set these variables from the openfire? |
|
If I edit the pade/classes/jigasi/sip-communicator.properties file manually, on plugin reload, the file gets overwritten to old version again. |
|
That is a general issue with plugins. A plugin jar file is a ZIP file. You can edit it directly or extract/edit/compress again. |
|
I don't think that will fix it, cause that file is being edited by the plugin on the startup. |
|
The file is generated by Like in the other Wrappers, we may to have some more business logic here. @0bhat : For a test, you may revoke the write right on this file for the OpenFire JVB user and edit the required changes e.g. as root user. With your feedback we then may change the source code that will generate the file. |
|
Perfect, let me try to edit it and see if I can implement something to give users a way to add their custom properties. |
|
You may take a look at code of the starters for JiCoFo and JVB to get an idea. First thing is to introduce properties that are taken from the Openfire registry. This may be edited at the Admin UI at Server|Server properties. If the needs are stabilized, In a second step they should appear on the corrensponding UI page in an appropriate way. If I understand it right, we e.g. need the possibility to provide an individual account ID. |
The properties file is updated with openfire generated values. Any property not yet supported by ofmeet will not be over-written. If you have time to work on this, you should add a tab for VoxImplant like I did with FreeSWITCH |
Sorry, I miss this on my (to) short look at the code. |
|
This doesn't seem to work even with all the right headers from the Voximplant. The Jigasi is not sending the call to the right room as pointed in the header. |
|
I am sure you know that X-Room-Name is not the default name for the SIP header value in Jitis and that has to be changed in sip-communicator.properties. Confirm that ofmeet has not messed up the value. |
|
Hi, Yes I have changed it in the
|
|
Unfortunately, I kept the default name when testing with FreeSWITCH. Could you use modify Voximplant to use the default just to confirm issue is not something else? |
|
Can you tell me the default name here, please? |
|
Jitsi-Conference-Room |
|
Doesn't seem to work with that header either: The Jigasi user is not even getting logged in when the call is transferred to SIP by Voximplant: |
How do you expect it to work if the jigasi user is not logged in? I think you should fix that first
|
|
I think that's where the problem is, jigasi user is always offline for me. |
|
things look fine: and here too: but still the user never logs in. |
|
even when I allow the anonymous login, the jigasi user is not getting created. |
|
All I can say is that when debugging, your log file is your best friend 👍 |
|
Hello, Thanks for info in this thread. I have set up a SIP gateway on server. SIP GW connection is OKI but jigasi user does not connect. |
You might need to open port 5222 as jigasi maybe using TLS which requires full FQDN for your XMPP server |
|
Dele, I will fix DNS issue & settings tomorow so TLS Xmpp connectivity should work with proper DNS SRV records. BTW do i need a _sip._udp SRV record ? does it make sense to add it ? |
I don't think so. I did not ned it for pade.chat |
|
@0bhat Try to restart instance after a FW change, check if problem is gone. |
|
I am closing this issue now. I have added ability to change SIP header name and also to use the correct local IP address
|
|
This is my spec: |
Cool :) I will rebuild latest plugin version and try it |
I have confirmed that TLS is not used. Just plain TCP on port 5222. make sure correct Ip address is used in org.jitsi.jigasi.xmpp.acc.SERVER_ADDRESS |
This is mine, almost similar except OpenJDK, which ubuntu version are you using ? |
|
Ubuntu 20.4, let me see if I can fix it |
|
Thanks for your support @deleolajide and @ClaudeStabile |
|
@0bhat OS is not the problem i run on kernels 3.x on CentOS or 5.4 on latest Ubuntu and both works the same. |
|
Still couldn't fix this issue I have set up FreeSWITCH too same issue, the user won't pick up the call and just hangs up: |
It is not going to work until your jigasi user can login ok. Try new version 1.3.2 |
|
I'm using 1.3.2, I'm just studying logs, but I guess they won't help. |
|
What's the output of |
|
|
From this, PID 12716 -- the JVM of JiGaSi -- is up on Is this an IPv6/v4 issue? You may try to add |
|
No I have made freeswitch run on 5080 |
|
Don't understand your answer. |
|
No it's contacting at 5080 |
|
FreeSwitch is making call to the 1000 SIP account, just my Jigasi user won't wake up:
|
|
I'm not familiar with SIP, but you confuse me: This are settings for JiGaSi to contact and register at the SIP server. But you show a log of FreeSWITCH trying and fail contact JiGaSi at I also can't connect to |
|
I'm confused too about this one. |
|
|
With my limited knowledge of SIP, Did you try to connect to by any other tool to |
|
@0bhat I have found what was the problem, why my jigasi user was not connected. It was because port 5060 was already busy. Jigasi needs port 5060 to be allocated netstat -an | grep 5060 Hope this helps |
Yes Jigasi is using it for me but still no help. |
|
I do not have 5060 in used for my openfire instances |
|
Jigasi on my side is using port 5060 to receive the SIP calls. When I call to the user logged in the Jigasi it rings port 5060. |
|
Got is working finally, just re-installed everything. |
|
@0bhat I had the same phenomenon. After a complete restart of dockers & FW then it works. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have created a Voximplant app and the user and following is my config in the Gate Way to Sip:
This doesn't seem to work:
Any suggestion on this?
The text was updated successfully, but these errors were encountered: