Perhaps you could configure an outbound proxy in the ws/wss signaling?  So it sends traffic to X domain/realm but goes to actual true remote proxy endpoint?

On Mon, Feb 27, 2017 at 11:04 PM, Jade SZ <jitterbuffer@gmail.com> wrote:
Hi Team,

Question:

Just wanted to clarify regarding SIP URI in webrtc (over sip) connection.

e.g. if we have a scenario where Kamailio is hosted with websocket support. Websocket URI is used to send packets to to wss/ws address and the SIP URI goes with it. I have tested it with any SIP URI including any domain and it works if I authenticate that domain, regardless that domain is real or not.

// client side SIP URI config
var configuration = {
  uri     : 'sip:alice@example.com',
};

Can we use any central domain for sip uri similar to realm concept and send traffic to multiple kamailio servers through websocket LB.

dummy.domain - for ws/wss SIP URI

kamailio-a.domain.com
kamailio-b.domain.com

Thanks in advance. 


Regards,
Jade

_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users




--
Sincerely,
Brandon Armstead
CTO / CRYY.com