I have created two endpoints:
- 1000 (normal sip client) with auth (username=1000) and transport protocol udp
- 1001 (webrtc client) with auth (username=1001) and transport protocol wss
This configuration works OK and webrtc client connects to 1001 and non webrtc connects to 1000.
No lets say that this is the same agent that would like to have the same user name/psw (1000) and will be able to connect using both different protocols. So when 1000 connects over webrtc, endpoint containing transport=transport_wss with all other webrtc settings will be selected, otherwise udp endpoint will be selected.
I have played with different configuration but was not able to make this working. If I set same auth for both endpoints, I can see that webrtc client connects to udp endpoint what will obviously not work.
It looks like that transport configuration has no influence in endpoint selection!
The only solution I see is using identify_by header and then adding some specific header in webrtc client. I haven’t tested this, but it is also far from being clean solution.
thanks in advance