<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<font size="+1"><font face="monospace">Ah, but is EXTREMELY useful for
people like me who need to know where the call was originally destined
for when it bounces off a Centrex DMS-100 due to call forward no answer
or call busy condition. I can treat it as the DID for the original
number and then send the caller into VM or other location as if it
were the DID actually assigned to me. :)</font></font><br>
<br>
Johansson Olle E wrote:
<blockquote cite="mid:A3B6608A-D00F-4D68-B0E9-C4EAADB3610F@edvina.net"
type="cite">
<pre wrap="">7 nov 2007 kl. 14.26 skrev Tony Mountifield:
</pre>
<blockquote type="cite">
<pre wrap="">Quick question for those who know the innards of chan_sip:
Does chan_sip use the "To:" header of an incoming INVITE request,
for anything other than setting SIP_HEADER(TO) ?
</pre>
</blockquote>
<pre wrap=""><!---->No. Like e-mail software not using the To: header in the actual e-mail.
</pre>
<blockquote type="cite">
<pre wrap="">
As far as I can tell so far, the target extension is taken from the
request URI, i.e. <a class="moz-txt-link-freetext" href="sip:extension@domain">sip:extension@domain</a>, and the target context
is taken from the section in sip.conf that matches the request's
source IP address. Is that correct?
</pre>
</blockquote>
<pre wrap=""><!---->
Or by matching a user section by From: username.
/O
_______________________________________________
--Bandwidth and Colocation Provided by <a class="moz-txt-link-freetext" href="http://www.api-digital.com">http://www.api-digital.com</a>--
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
<a class="moz-txt-link-freetext" href="http://lists.digium.com/mailman/listinfo/asterisk-users">http://lists.digium.com/mailman/listinfo/asterisk-users</a>
</pre>
</blockquote>
</body>
</html>