-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can Not Send Request to Myself #1
Comments
can you attach the drachtio server log for when it processes that register and response? |
actually, that error does not pertain to the contact header it pertains to the request uri you provided.....where are you trying to send this REGISTER request? A drachtio server wont send a request to itself, in order to prevent loops |
Ok, now I understand, I will try to make changes to register drachtio itself, not redirect, I just need a service like simple-drachtio-registrar but webrtc clients and sip clients can connect at the same time. |
yes, you should be able to do that. Are webrtc clients connecting over wss ? You need to configure the drachtio server listen for both wss and udp. Not totally sure I am following what you want to do though -- you want your app to receive the REGISTERs and act as the registrar? Or you want to forward the REGISTERs on downstream to some other registrar? |
I want my app act as registrar. both sip and webrtc clients register to my app and all media pass through rtpengine. I will take a look at drachtio-server wss configuration thank you. |
here is an example of one of my servers configured for both wss and udp <drachtio>
<!-- udp port to listen on for client connections (default 8022), and shared secret used to authenticate clients -->
<admin port="9022" secret="cymru">127.0.0.1</admin>
<!-- sip configuration -->
<sip>
<contacts>
<contact>sip:162.244.175.143;transport=udp</contact>
<contact>sips:162.244.175.143:4433;transport=wss</contact>
</contacts>
<tls>
<key-file>/etc/letsencrypt/live/tighthead.drachtio.org/privkey.pem</key-file>
<cert-file>/etc/letsencrypt/live/tighthead.drachtio.org/cert.pem</cert-file>
<chain-file>/etc/letsencrypt/live/tighthead.drachtio.org/chain.pem</chain-file> |
in register.js file header.contact is set to sip:user@localhost and there is a note to localhost will be replaced in the drachtio-server but there is a problem I think.
In my setup application, server and rtpengine are all in different servers.
The text was updated successfully, but these errors were encountered: