|
From: | David Sugar |
Subject: | Re: [Sipwitch-devel] SIPWitch destination router |
Date: | Mon, 22 Apr 2013 14:14:49 -0400 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130402 Thunderbird/17.0.5 |
Sipwitch cares only about a few things. If you claim your "from" uri is assocated with the sipwitch instance, it will ask you to prove you are who you claim through sip authentication. If your a non-local (non-authenticated) user, and the destination is not a local sipwitch endpoint, it will not let you call through it.
Sipwitch is also a forking server, in that if the destination uri can be interpreted as multiple sip destinations or endpoints, it will create an invite for each possible destination, and then connect you to the first one that actually answers.
Connected single domain calling is a special case. This is where you have a series of sipwitch nodes all acting as a single switch for a single uri. In that case sipwitch keeps track of which instance the user assocated with the domain is logged into/registered with. Right now it does it primarily by partitioning the numeric dialing plan, though later shared multicast registry operations will be added.
On 04/05/2013 10:14 AM, liang wrote:
Mr Sugar: From GNU Free Call Announcement, i learned that sip witch is a destination router for sip protocol, and Free Call support publishing of routes to connected peers which builds upon the already routing foundation in sip witch itself. My questions are that : 1. What is the *destination router* in sip witch ,and how to use it? Could you please give the XML configuration. 2. What is the meaning of *publishing of routes to connected peers*through the routing foundation of sip witch? I am looking forward to you replay! Thank you!
dyfet.vcf
Description: Vcard
[Prev in Thread] | Current Thread | [Next in Thread] |