Askozia Forums
May 17, 2012, 02:43:12 pm *
Welcome, Guest. Please login or register.

Login with username, password and session length
 
   Home   Help Search Login Register  
Pages: [1]
  Print  
Author Topic: Multiple accounts on the same provider  (Read 723 times)
Scapal
Full Member
***

Karma: 4
Posts: 58



View Profile
« on: January 10, 2011, 10:48:17 am »

Hi,

I have multiple accounts on the same provider infrastructure, I mean the same SIP server.
In fact I have even two providers using the same underlying VoIP infrastructure (3starsnet.com and nomado.eu).

The problem is that for any incoming call, they will all be matched only based on their IP address, hence only the incoming call routing rules of the first provider configured in Askozia are used.

As a workaround I put all the incoming routing in the first provider but this isn't very clean.
Shouldn't the incoming contexts for multiple account sharing the same remote server IP be merged ? Does it make sense for SIP providers to have a distinct incoming routing at all?

Cheers,
Pascal
Logged
giovanni.v
Hero Member
*****

Karma: 53
Posts: 670


View Profile
« Reply #1 on: January 10, 2011, 03:24:41 pm »

The problem is that for any incoming call, they will all be matched only based on their IP address, hence only the incoming call routing rules of the first provider configured in Askozia are used.

Unfortunately, according to the configuration, this is the way Asterisk works. From the Asterisk source example sip configuration file:
;------- Naming devices ------------------------------------------------------
;
; When naming devices, make sure you understand how Asterisk matches calls
; that come in.
;   1. Asterisk checks the SIP From: address username and matches against
;      names of devices with type=user
;      The name is the text between square brackets [name]
;   2. Asterisk checks the From: addres and matches the list of devices
;      with a type=peer
;   3. Asterisk checks the IP address (and port number) that the INVITE
;      was sent from and matches against any devices with type=peer
;
; Don't mix extensions with the names of the devices. Devices need a unique
; name. The device name is *not* used as phone numbers. Phone numbers are
; anything you declare as an extension in the dialplan (extensions.conf).


In Askozia the third option apply because no device match usernames, as the latest documentation suggests.

There are some workarounds:
1) Add match_auth_username=yes to manual attributes in the advanced sip configuration. I think there are very little changes... probably don't work.

2) Append a device matching the From: address to sip.conf using the dev panel; to do that simply copy the device created for the provider exactly as is and paste it changing only the unique [device name] to match the From: field.
Logged
Scapal
Full Member
***

Karma: 4
Posts: 58



View Profile
« Reply #2 on: January 11, 2011, 07:01:17 pm »

Yes, I now this is the way Asterisk works, hence my suggestion to merge the incoming contexts of SIP providers sharing the same IP address, so Askozia could accommodate with how Asterisk handles them.
 
I would make more sense, wouldn't it?
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!
Page created in 0.09 seconds with 19 queries.