Issue 149 in restcomm: Number identification based on R-URI

[rest...@googlecode.com]

Status: New
Owner: ----

New issue 149 by nicolas....@gmail.com: Number identification based on R-URI
http://code.google.com/p/restcomm/issues/detail?id=149

Detailed information about the new feature request

1. What motivated the request:

If number in R-URI has been previously rewritten by a proxy in front of
Mobicents, restcomm will return a 404 not found because it will try to
match number in "To" header, instead of number it R-URI.

2. Link to related public forum or mailing list discussion:

https://groups.google.com/forum/?fromgroups=#!topic/restcomm/-3kXGPUow_M

3. Describe functionality and API (if applicable)

A new parameter in config file could allow to configure this behaviour (ie:
match numbers on R-URI or on "To" header)

[rest...@googlecode.com]

Updates:
Labels: Version-1.0.0.FINAL

Comment #1 on issue 149 by quintana...@gmail.com: Number identification

based on R-URI
http://code.google.com/p/restcomm/issues/detail?id=149

(No comment was entered for this change.)

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[rest...@googlecode.com]

Updates:
Labels: -Version-1.0.0.FINAL TelScale-6.1.0.GA

Comment #2 on issue 149 by quintana...@gmail.com: Number identification

[rest...@googlecode.com]

Updates:
Status: Done
Owner: quintana...@gmail.com

Comment #3 on issue 149 by quintana...@gmail.com: Number identification