> http://track.sipfoundry.org/browse/XX-6961, we need > sipXbridge to add a signed X-Sipx-Authidentity header to TLS > calls it presents to the proxy, containing the appropriate > special trusted peer user id configured for that connection. > I am trying to understand what the relationship is here. > Does it make sense to add the peer user id into each > itsp-account section of sipxbridge.xml, as follows? > > <itsp-account> > <itsp-proxy-domain>othertrusteddomain.com</itsp-proxy-domain> > <itsp-proxy-address>othertrusteddomain.com</itsp-proxy-address> > <peer-user>~~peer~othertrusteddomain.com</peer-user> > > How many of these special peer users do we expect to have? > just one (in which case we have one ~~peer~trusteddomain > special user) or one per "peer system configured" (in which > case we have something like > ~~peer~<peer>). Any other suggestions for xml tag name or sipx user > id?
I'd say that peers should be on a per ITSP account basis. Also, two distinct TSP accounts should be allowed to use the same peer. bob _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
