Have you tried sending it to a different extension number? I've got the
registrations working on my home server where I register with one number
and have it drop in on a totally different number in the context.
register => 44198:[EMAIL PROTECTED]/200
Aaron
On Wed, 19 Apr 2006, Thomas Winter wrote:
Hi,
[general]
context=Sip_in
register => 1234:[EMAIL PROTECTED]/s
s is the same, it still looks for an extension 1234 in the context Sip_in and
did not use /s
Asterisk is 1.2.7
Am Wednesday 19 April 2006 22:48 schrieb Aaron Daniel:
I'm not gonna say much for the documentation, but I would suggest if you
want to bypass that problem, add /s (or whatever extension) to the
register statement so you know for absolute sure that incoming calls on
the registration will go to the extension that you expect.
Aaron
On Wed, 19 Apr 2006, Thomas Winter wrote:
Hi,
the documentation of sip.conf is telling me this:
;register => 1234:[EMAIL PROTECTED]
;
; This will pass incoming calls to the 's' extension
In reality it jumps to the extension 1234 in the context and not to s
So it is much more complicate to write an proper dialplan.
Is this an bug or is the documentation not up to date?
best regards
Thomas
_______________________________________________
--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
--
Aaron Daniel
Computer Systems Technician
Sam Houston State University
[EMAIL PROTECTED]
(936) 294-4198
_______________________________________________
--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
