I'm looking at the way chan_sip.c matches peers (by name or by IP/port)
It may be possible to add an extra discriminator, for example, it could be called "class" [my-proxy-a] host=192.168.100.1 class=group-a dtlsenable=no [my-proxy-b] host=192.168.100.1 class=group-b dtlsenable=yes The proxy then signals the desired class in the request URI, e.g. INVITE sip:[email protected];x-asterisk-class=group-b If no tag is supplied or it doesn't match, it would fall back to a peer with class=<nothing> (ensuring existing behavior is consistent) It appears that this logic can be inserted in most of the places where callbackexten is used as a discriminator for peer selection. Has anybody else already started on anything like this on a branch or in any third-party patch? -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
