<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2912" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=720292910-17072006><FONT face=Arial
color=#0000ff size=2>So you are relying on the behavior of regexten to default
to peer name? Is that what you are expecting? And if so, could you
test with a statically defined extension for the per-peer regexten
parameter?</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=720292910-17072006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=720292910-17072006><FONT face=Arial
color=#0000ff size=2>Regards,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=720292910-17072006><FONT face=Arial
color=#0000ff size=2>- Brad</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> asterisk-users-bounces@lists.digium.com
[mailto:asterisk-users-bounces@lists.digium.com] <B>On Behalf Of </B>Simon
Woodhead<BR><B>Sent:</B> Monday, July 17, 2006 5:53 AM<BR><B>To:</B> Asterisk
Users Mailing List - Non-Commercial Discussion<BR><B>Subject:</B> Re:
[asterisk-users] DUNDI / regcontext<BR></FONT><BR></DIV>
<DIV></DIV>Thanks for the reply Brad.<BR><BR>The relevant section of sip.conf
was posted:<BR><BR>[general]<BR>regcontext=sipregistration<BR><BR>If you mean
extensions.conf, I wasn't creating the extension in there other than for
testing. RegContext correctly creates the context on registration but does not
create the extension. If I create the extension manually, the DUNDi lookup works
just fine. <BR><BR>Simon<BR><BR>
<DIV><SPAN class=gmail_quote>On 7/16/06, <B class=gmail_sendername>Watkins,
Bradley</B> <<A
href="mailto:Bradley.Watkins@compuware.com">Bradley.Watkins@compuware.com</A>>
wrote:</SPAN>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">Could
you possibly put up the relevant section(s) of your sip.conf? It
sounds like the DUNDi portion is set up properly, and obviously it's not going
to find an extension that doesn't exist.<BR><BR>Regards,<BR>-
Brad<BR><BR>________________________________<BR><BR>From: <A
href="mailto:asterisk-users-bounces@lists.digium.com">asterisk-users-bounces@lists.digium.com</A>
on behalf of Simon Woodhead<BR>Sent: Sat 7/15/2006 5:59 PM<BR>To: <A
href="mailto:asterisk-users@lists.digium.com">asterisk-users@lists.digium.com</A><BR>Subject:
[asterisk-users] DUNDI / regcontext<BR><BR><BR><BR>Hi folks,<BR><BR>I've been
having a go at getting DUNDI working this evening to enable<BR>users to
register to any Asterisk box and to look them up from another. <BR>The DUNDI
part works just great (very impressed), as does the subsequent<BR>joining of
calls between the two servers but I'm struggling with<BR>regcontext and would
be grateful for any input.<BR><BR>sip.conf includes:
<BR><BR>[general]<BR>regcontext=sipregistration<BR><BR>When a user registers,
I get the "Added extension 'XXXXXX' priority 1 to<BR>sipregistration" message.
However, 'show dialplan' does not show the<BR>extension and a DUNDI lookup
does not return it. The sipregistration <BR>context has been auto-created but
is empty. If I manually create the<BR>sipregistration context and add the NoOp
extension, then everything<BR>works as expected.<BR><BR>I've tried this across
multiple boxes, each running different versions <BR>right up to the latest
stable but the behaviour is the same. It is also<BR>the same with both SIP and
IAX registrations and doesn't make a<BR>difference if the peer is defined in
the .conf file or Realtime. They do<BR>all have identical configurations
though so I suspect there might be<BR>something in our setup which is
conflicting.<BR><BR>Any input gratefully received.<BR><BR>All the
best,<BR>Simon<BR><BR><BR>The contents of this e-mail are intended for the
named addressee only. It contains information that may be confidential. Unless
you are the named addressee or an authorized designee, you may not copy or use
it, or disclose it to anyone else. If you received it in error please notify
us immediately and then destroy it.
<BR><BR><BR>_______________________________________________<BR>--Bandwidth and
Colocation provided by <A href="http://Easynews.com">Easynews.com</A>
--<BR><BR>asterisk-users mailing list<BR>To UNSUBSCRIBE or update options
visit: <BR> <A
href="http://lists.digium.com/mailman/listinfo/asterisk-users">http://lists.digium.com/mailman/listinfo/asterisk-users</A><BR><BR><BR><BR></BLOCKQUOTE></DIV><BR>The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. </BODY></HTML>