[asterisk-users] DUNDI / regcontext

[Watkins, Bradley]

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?
 
Regards,
- Brad

________________________________

From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Simon
Woodhead
Sent: Monday, July 17, 2006 5:53 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] DUNDI / regcontext


Thanks for the reply Brad.

The relevant section of sip.conf was posted:

[general]
regcontext=sipregistration

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. 

Simon


On 7/16/06, Watkins, Bradley <Bradley.Watkins at compuware.com> wrote: 

	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.
	
	Regards,
	- Brad
	
	________________________________
	
	From: asterisk-users-bounces at lists.digium.com on behalf of Simon
Woodhead
	Sent: Sat 7/15/2006 5:59 PM
	To: asterisk-users at lists.digium.com
	Subject: [asterisk-users] DUNDI / regcontext
	
	
	
	Hi folks,
	
	I've been having a go at getting DUNDI working this evening to
enable
	users to register to any Asterisk box and to look them up from
another. 
	The DUNDI part works just great (very impressed), as does the
subsequent
	joining of calls between the two servers but I'm struggling with
	regcontext and would be grateful for any input.
	
	sip.conf includes: 
	
	[general]
	regcontext=sipregistration
	
	When a user registers, I get the "Added extension 'XXXXXX'
priority 1 to
	sipregistration" message. However, 'show dialplan' does not show
the
	extension and a DUNDI lookup does not return it. The
sipregistration 
	context has been auto-created but is empty. If I manually create
the
	sipregistration context and add the NoOp extension, then
everything
	works as expected.
	
	I've tried this across multiple boxes, each running different
versions 
	right up to the latest stable but the behaviour is the same. It
is also
	the same with both SIP and IAX registrations and doesn't make a
	difference if the peer is defined in the .conf file or Realtime.
They do
	all have identical configurations though so I suspect there
might be
	something in our setup which is conflicting.
	
	Any input gratefully received.
	
	All the best,
	Simon
	
	
	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. 
	
	
	_______________________________________________
	--Bandwidth and Colocation provided by Easynews.com --
	
	asterisk-users mailing list
	To UNSUBSCRIBE or update options visit: 
	   http://lists.digium.com/mailman/listinfo/asterisk-users
	
	
	
	


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. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20060717/119f0dad/attachment.htm