Mark Gertsvolf wrote:
Scott Lawrence wrote:
I still don't understand what problem the configuration you
describe in the issue is for, Mark - why have 3 accounts when
you can only make outgoing calls on one of them?
Hi Scott,
The case of 3 accounts, where you can only use one for outgoing calls
was just an example.
In real life I have seen at least two applications of multiple ITSP
accounts per ITSP/domain:
1. Some carriers/ITSPs provide different service plans, which differ in
price, calling restrictions (active calls per subscription), quality of
service, etc. The customer may decide to subscribe to multiple service
plans and use them selectively for subset of calls. Typically each
subscription is mapped into a single ITSP SIP account.
For instance: VOIP.MS allows one customer to create multiple SIP
accounts. Each account has a number of individual settings including
quality of service setting (premium vs. basic). The QoS setting impacts
outgoing call routing and guarantees better call completion rate and
premium voice quality for premium plan at a higher per-minute call rate
than basic.
Customer can use 2 VOIP.MS accounts - one with premium plan and one with
basic. The customer then sets the dial plan such that some calls are
made using account with higher quality. For instance CEO can dial prefix
8 for premium calls, while all other employees dial prefix 9 for basic
call service. Using permissions dial plan with prefix 8 can be
restricted to a few PBX users.
Another example: Skype S4S allows customers to create multiple SIP
profiles. Each profile maps into one SIP account. The profile has its
own billing, call records and the following options:
- channel subscriptions (i.e. virtual channels or DS0s), which limit the
number of simultaneous calls. Subscriptions can be purchased on a
monthly basis in increments of one.
- DID (online number)
- CallerID - all outgoing calls made using this profile will appear with
CallerID configurable by the customer and enforced/set by Skype. Skype
validates the authenticity of the CallerID prior to using it.
- A list of Skype IDs associated with the PBX, such that when one of the
skypeID is called from Skype application the call is routed to the PBX.
A customer can create one SIP profile for sales and another one for
support. Expected sales call volume is low, so sales profile has 3
channel subscriptions, which allow 3 simultaneous calls. Sales has a
dedicated DID number. When sales person calls out the sales DID is used
as a CLID. Sales profile may have its own credit with auto-refill.
Expected support call volume is high and support SIP profile has 10
channel subscriptions. Support has its own DID, which is set as a
CallerID for outgoing calls. Credit for outgoing calls is set for
support account independently of the sales profile and has no
auto-refill to limit the credit for outgoing calls. Skype maintains CDR
records per profile.
2. Some carriers allow customers to purchase virtual DID phone numbers
in different area codes (rate centers). Assuming customer has DIDs in
Ottawa and Montreal. When the customer makes a call to Ottawa he/she
wants the Ottawa number to be used as a CallerId while if a call is made
to Montreal the Montreal number should be used. At least two large
carriers we deal with relay responsibility to support this feature to
the PBX.
With sipXecs this requirement can be supported in the following way:
create two SIP trunk gateways and set the CLID override in each one of
the accounts to be Montreal and Ottawa number respectively. The create
two dial plan rules one to call Ottawa (pattern: 1613+(7 digits)) and
the second to Montreal (pattern: 1514+(7 digits))
This way calls to Ottawa are made with Ottawa DID and to Montreal with
Montreal DID.
Cheers,
Mark.
Couple of issues related to this topic:
XX-668 <http://track.sipfoundry.org/browse/XX-668> (which was a new
feature request to support multiple SIP trunks from the same ITSP provider)
XX-4785 <http://track.sipfoundry.org/browse/XX-4785> (the caller ID is
not applied correctly for outgoing calls when multiple SIP trunks of the
same ITSP provider are configured)
Thanks,
Chaitra
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/
