[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sr-users
Subject:    Re: [SR-Users] Kamailio network edge for registration and rtp pass-through
From:       "JR Richardson" <jmr.richardson () gmail ! com>
Date:       2013-10-29 12:47:23
Message-ID: 000c01ced4a5$03bd8f10$0b38ad30$ () gmail ! com
[Download RAW message or body]

Date: Fri, 25 Oct 2013 17:48:13 -0400
From: Fred Posner <fred@palner.com>
To: "Kamailio (SER) - Users Mailing List"
	<sr-users@lists.sip-router.org>
Cc: SR-Users <sr-users@lists.sip-router.org>
Subject: Re: [SR-Users] Kamailio network edge for registration and rtp
	pass-through
Message-ID: <6D231DE3-5BED-4601-A097-5A79CEF452F0@palner.com>
Content-Type: text/plain;	charset=us-ascii

Do you need the registration be local to the asterisk? 

I would have all the asterisks send calls to the Kamailio.

You can have a lookup on endpoint outbound to decide which asterisk should
handle the outbound call for that did. 

Also a lookup for incoming DIDs, etc. 

---Fred 


> On Oct 25, 2013, at 5:43 PM, Jr Richardson <jmr.richardson@gmail.com>
wrote:
> 
> Hi All,
> 
> Starting a new project, roll your own SBC, not a full SBC, just need some
minor functionality.  I'm interested in deploying Kamailio as a edge device
on a VSP for single entry point for hosted PBX's, Asterisk based.  I had
some wonderful and informative conversations at Astricon 2013, several folks
assuring me Kamailio w/rtpproxy was the tool for the job, so this is a
follow up to delve more into details.
> 
> I've been researching configs, topology, modules needed, ect...  Most of
the examples I'm reading about for this scenario are spreading the
registrations across many PBX's without distinction.  One concept I'm
struggling with is having a specific phone register to a specific PBX.
> 
> phone-customer-A-x101><internet><kamailio><PBX-customer-A-x101
> phone-customer-B-x101><internet><kamailio><PBX-customer-B-x101
> phone-customer-C-x101><internet><kamailio><PBX-customer-B-x101
> 
> I could add a unique identifier to some part of the registration of each
phone like 'custA-101@kamailio_server', custB-101@kamailio_server, ect.
What I'm not clear on is when the request comes to kamailio, where would I
identify what PBX the phone should register to and how to re-write the
'custA-101@kamailio_server' to '101@custA-pbx' and forward to the correct
PBX and ensure rtp flows through kamailio.
> 
> Could this function be derived using dbaliases or possibly using
dispatcher with group number for each customer PBX?
> 
> So assuming I can get the registrations to work properly, would standard
invite for calling just work or would I also have to have specific config in
place to ensure an invite from customer A phone also reaches the correct
customer A PBX?
> 
> A point in the right direction?
> 
> Thanks.
> 
> JR

I would like kamailio to be transparent in the process, i.e. phones register
locally to their respective PBX.

Thanks.

JR


_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
[prev in list] [next in list] [prev in thread] [next in thread]