[asterisk-dev] chan_sip SIP Authentication
jesusr at voztele.com
Wed Jan 28 09:02:54 CST 2009
>>> This implements a way to
>>> - register with SIp services
>>> - get the call back
>>> - match the proper peer, even if you have five accounts, we will
>>> the proper peer
>>> - send the call to the called number (to: header), not using a
>>> exten that overrides.
>> ahh. It took us many yours to tell vendors that To-based routing is
> Oh yes, it is. In theory you should never do that, but...
> But if you register for a service, the request URI is whatever
> you register with and can't really be used for any routing decisions
> in a b2bua.
> For a simple phone, it doesnt matter. Registration for a trunk service
> doesn't really work,
> which might be a design flaw in SIP.
> How on earth do you get the requested number without checking To: or
Please, can you explain a little bit more why you need To: or RPID for
routing decisions? I don't fully understand it :-/
Furthermore, To header is for destination and is always present but
RPID/PAI makes reference to source information and you don't know if
they will exist.
More information about the asterisk-dev