Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Routing rule based on called user is provisioned or not #22

Open
GoogleCodeExporter opened this issue Apr 1, 2015 · 2 comments
Open

Routing rule based on called user is provisioned or not #22

GoogleCodeExporter opened this issue Apr 1, 2015 · 2 comments
Labels
auto-migrated Priority-Medium Roadmap-Issue Type-Enhancement Version-1.0.0.ALPHA2

Comments

@GoogleCodeExporter
Copy link 

If called user is provisioned, user is customer of operator and SMSC initiates 
Mt module

If not, may be SMSC can route to different ESME which can act as aggregator and 
has connection to different operator's SMSC

Original issue reported on code.google.com by [email protected] on 6 Aug 2012 at 2:59
@GoogleCodeExporter
Copy link
Author

Original comment by [email protected] on 6 Aug 2012 at 2:59

@GoogleCodeExporter
Copy link
Author

Original comment by [email protected] on 6 Aug 2012 at 3:09

  • Added labels: Roadmap-Issue, Type-Enhancement
  • Removed labels: Type-Defect

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-Medium Roadmap-Issue Type-Enhancement Version-1.0.0.ALPHA2
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter