<html><div style='background-color:'><DIV class=RTE>
<P>>If I recall correctly (and I'm not a BV user), incoming sip calls to <BR>>asterisk do not use all the parameters as one would expect. I think<BR>>Olle posted something in the last month or two that such incoming<BR>>calls attempt to find the first context that matches IP Address (or<BR>>something like that) regardless of other parameters passed.<BR><BR>>The sip.conf.sample file includes the following comment:<BR>>; For incoming calls only. Example: FWD (Free World Dialup)<BR>>; We match on IP address of the proxy for incoming calls<BR>>; since we can not match on username (caller id)<BR><BR>>You might try to find that post and review the exact sequence of<BR>>parameters that asterisk uses for incoming sip calls.</P>
<P>Yes, I know all of that, the problem is asterisk is NOT trying to match anything except the IP from Broadvoiice. So all calls from BV will be cached to the phone number and context of the first BV call. Asterisk will not look at the phone number or context of the other BV number when they come in.</P>
<P>So... Since Asterisk IS GETTING the phone number and context for the first one that rings in, but IS NOT getting the phone number and context for subsequent BV calls and INSTEAD caches and uses the info from the first call, ASTERISK IS BROKEN.</P>
<P>Think about it and I think anyone would agree this is not a good thing (can't send calls to correct destination based on context, can't bill the proper partry for their phone service).</P>
<P>Thanks<BR><BR><BR></P></DIV></div></html>