[asterisk-dev] chan_sip SIP Authentication

Philipp Kempgen philipp.kempgen at amooma.de
Wed Jan 28 06:45:34 CST 2009

Johansson Olle E schrieb:
> The problem arises since you use phone numbers as identifiers for the  
> users. This is not a good thing (TM) and should be avoided. The  
> dialplan is where you route phone numbers. Devices

Or users ...

> should have device  
> names that you address in the dialplan on the extension that is  
> supposed to connect to one or several devices.

While that is very clear in traditional telephony it's not in
VoIP. SIP URI are by no means limited to numeric usernames

So what would you recommend as the proper SIP way:

123 => {
Isn't it the SIP registrar and also the network stack that
should figure out where that SIP user/device actually lives?

philipp => {
There's no need for numeric extensions in SIP (and Jabber for that

123 => {
This is what you'd prefer I think.

Unfortunately Asterisk does not support multiple SIP registrations
(resources in Jabber terms).

So what would be the proper way to implement something like
the following in Asterisk:
alias => {
	# dials
	# XMPP/philipp/work and
	# XMPP/philipp/home
	# according to my personal preference

Or should the dialplan contain (via an AGI script for example)
my personal preference provided it's my home PBX:
alias => {
	# resp.

> If we go ahead and change matching order, I'm afraid it will break  
> backwards compatibility and stop many systems from working properly.  
> We don't want that.

Definitely not. But as long as it's configurable and off by default
it doesn't break backwards compatibility.

   Philipp Kempgen

AMOOCON 2009, May 4-5, Rostock / Germany   ->  http://www.amoocon.de
Asterisk: http://the-asterisk-book.com - http://das-asterisk-buch.de
AMOOMA GmbH - Bachstr. 126 - 56566 Neuwied  ->  http://www.amooma.de
Geschäftsführer: Stefan Wintermeyer, Handelsregister: Neuwied B14998

More information about the asterisk-dev mailing list