Horizontal scaling, that is what I am looking for webrtc over sip. Also by
giving 1 SIP URI to webrtc client.
Regarding - "Why not do UA -> kamailio 1 -> kamailio 2 or kamailio 3?"
Because I want the UA to be configured to wss which can load-balance to
multiple kamailio servers. Avoiding single p
Why not do UA -> kamailio 1 -> kamailio 2 or kamailio 3?
Not quite sure on what you are trying to achieve. Think of the request uri
as the current destined address/hop if no outbound proxy host is specified
as otherwise.
On Tue, Feb 28, 2017 at 12:41 AM Jade SZ wrote:
> Thanks for the reply. J
Thanks for the reply. Just to be clear is the above mentioned idea
conceptually wrong? so here is a detail of scenario
All UA's are over websockets.
UA --wss--> HAProxy ws-> (Identical Kamailio Servers - SIP1 and
SIP2 for now)
ofcourse if a peer is registered on SIP1, SIP2 routes cal
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 wrote:
> Hi Team,
>
> Question:
>
> Just wanted to clarify regarding SIP URI in webrtc (over sip)
