On 4/11/11 6:53 PM, George Niculae wrote:
maybe the + is ignored, and if you send itsip:+17652320315 it will match a
> 17652320315 in the users.
>
Check etc/sipxpbx/fallbackrules.xml, userPattern and transform/user
value for your rule, maybe this will give you a hint
_______________________________________________
it does look like SOMETHING, somewhere is ignoring the +, so a sip
invite to sip:+17652320315 does end up at a user with 7652320315 in as
an alias.
patterns that try to match + (or \+) seem to be ignored.
with the growing importance of E.164 numbering for international itsp's,
this may be a major issue soon.
example:
you send 56(*) to an itsp. do they assume since its 10 digits, it
should route to us?
clearly if we send 156* it should.
sending the + first, signifies that what comes after is a country code,
so there is no ambiguity.
for us, yes, just put the 1.
for international, yes, put 00 or 01.
or, see about what type of support is needed for e.164 numbering.
I can't seem to figure out how to OUTPULSE the +1. but am working on it.
--
Michael Scheidell, CTO
o: 561-999-5000
d: 561-948-2259
ISN: 1259*1300
>*| *SECNAP Network Security Corporation
* Best Intrusion Prevention Product, Networks Product Guide
* Certified SNORT Integrator
* Hot Company Award, World Executive Alliance
* Best in Email Security, 2010 Network Products Guide
* King of Spam Filters, SC Magazine
______________________________________________________________________
This email has been scanned and certified safe by SpammerTrap(r).
For Information please see http://www.secnap.com/products/spammertrap/
______________________________________________________________________
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/
