Hi all,
As our requirements scale (number of DIDs, number of users, number of simultaneous calls, etc) it is very apparent that our needs require us to move from a softswitch/pbx application environment onto a Sip Router based platform. While I have been able to run though the documentation and bring online a working OpenSER platform I am still confused about DID handling in the system.
I need to be able to take a series of DIDs that we are being passed from the carrier and forward the call to the end user's switch untouched (i.e. 18005551212@me needs to be passed to 18005551212@customer). I have been reading through aliasing but this does not seem to be what I need (because the customer's switch does not see the original DID). Ideally I need to be able to maintain a large inventory of DIDs and assign them to customers without touching the configuration files when the association is made.
How do I accomplish this? What do I need to add/configure in the system? How do I configure this redirect/mapping/proper terminology correctly?
Thanks in advance, Max
Max,
We are doing this same thing but our method is somewhat of a hack. We effectively use a system call from within the cfg script to lookup the DID in a postgres db. The lookup returns the domain the DID belongs too ( our customer's switch ). We then re-write the RURI and forward the message along using t_relay.
This is a simplification but I think you get the point.
I would also like to know if there is a more 'proper' way to accomplish this lookup.
The difference between what we are doing and what it seems openser was built to do is the lack of registrations. If we implemented registrations then I think we could use the userloc module. Am I right about this?
Is there a better way to implement 'static registrations'?
T.R.
-----Original Message----- From: users-bounces@openser.org [mailto:users-bounces@openser.org] On Behalf Of Max Clark Sent: Monday, July 31, 2006 8:45 PM To: users@openser.org Subject: [Users] DID Handling -> Transitioning from Asterisk/SipX
Hi all,
As our requirements scale (number of DIDs, number of users, number of simultaneous calls, etc) it is very apparent that our needs require us to move from a softswitch/pbx application environment onto a Sip Router based platform. While I have been able to run though the documentation and bring online a working OpenSER platform I am still confused about DID handling in the system.
I need to be able to take a series of DIDs that we are being passed from the carrier and forward the call to the end user's switch untouched (i.e. 18005551212@me needs to be passed to 18005551212@customer). I have been reading through aliasing but this does not seem to be what I need (because the customer's switch does not see the original DID). Ideally I need to be able to maintain a large inventory of DIDs and assign them to customers without touching the configuration files when the association is made.
How do I accomplish this? What do I need to add/configure in the system? How do I configure this redirect/mapping/proper terminology correctly?
Thanks in advance, Max
-- Max Clark http://www.clarksys.com
_______________________________________________ Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Would you mind sharing your openser.cfg file (or the sections specific to this) so I can get a better idea on how to proceed?
Thanks, Max
On 7/31/06, T.R. Missner trmissner@bandwidth.com wrote:
Max,
We are doing this same thing but our method is somewhat of a hack. We effectively use a system call from within the cfg script to lookup the DID in a postgres db. The lookup returns the domain the DID belongs too ( our customer's switch ). We then re-write the RURI and forward the message along using t_relay.
This is a simplification but I think you get the point.
I would also like to know if there is a more 'proper' way to accomplish this lookup.
The difference between what we are doing and what it seems openser was built to do is the lack of registrations. If we implemented registrations then I think we could use the userloc module. Am I right about this?
Is there a better way to implement 'static registrations'?
T.R.
-----Original Message----- From: users-bounces@openser.org [mailto:users-bounces@openser.org] On Behalf Of Max Clark Sent: Monday, July 31, 2006 8:45 PM To: users@openser.org Subject: [Users] DID Handling -> Transitioning from Asterisk/SipX
Hi all,
As our requirements scale (number of DIDs, number of users, number of simultaneous calls, etc) it is very apparent that our needs require us to move from a softswitch/pbx application environment onto a Sip Router based platform. While I have been able to run though the documentation and bring online a working OpenSER platform I am still confused about DID handling in the system.
I need to be able to take a series of DIDs that we are being passed from the carrier and forward the call to the end user's switch untouched (i.e. 18005551212@me needs to be passed to 18005551212@customer). I have been reading through aliasing but this does not seem to be what I need (because the customer's switch does not see the original DID). Ideally I need to be able to maintain a large inventory of DIDs and assign them to customers without touching the configuration files when the association is made.
How do I accomplish this? What do I need to add/configure in the system? How do I configure this redirect/mapping/proper terminology correctly?
Thanks in advance, Max
-- Max Clark http://www.clarksys.com
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
-
Max Clark -
T.R. Missner