Scott,
please do not take 12345678 as a real life example. I simply invented a
number to explain the issue, not really thinking it would not match in
any of my rule.
Here the real life example
04341856999 works
[email protected] does not work.
But I can prove anything in the form "num...@domain" does not work while
"number" does.
The dial plan you see is almost completely based on the default Italian
dialplan which I proved to work fine with all physical gateways I tested.
The dialplan rule used is "Nazionali". There is no fixed length for the
number. The number could be of any length. 043471417 and 04341856999 are
both valid numbers. The reason why there are 9 rules (not 10) is simple.
00____ is an international call here. 01__ to 09__ are a national call.
There is only one dial rule in sipxconfig that will produce the 9 rules
you saw.
I'm not claiming I want to use [email protected] to place a
call, it is simply what my two phones store in their incoming call list
when they receive a call from sipxbridge. When I'm trying to call back a
missed call it simply doesn't work.
This was not an issue at all when I could enable "Internet Calling"
choosing sipxbridge as the default sbc. Now it's not possible cause
sipxbridge is not in the list anymore.
Thanks again
Alberto
Scott Lawrence ha scritto:
On Thu, 2009-04-30 at 09:04 +0200, Alberto wrote:
I'm currently running sipxecs 4.0 stable and I ran in a simple issue.
I'm perfectly using my ITSP (eutelia) with 2 different accounts (for my
ITSP means 2 different PSTN numbers). I'm able to place and pick up
received calls.
When the I try to recall an inbound call number it simply fails.
Incoming calls routed from sipxecs come from the Internet to my
destination phone with a number like this: [email protected].
This number is what the phone save in the received/missed call list. If
I dial 12345678 the call goes exactly as expected, but if I call
[email protected] fails.
Scott Lawrence wrote:
There's something wrong with your dial plans, I suspect.
Attach the files /etc/sipxpbx/mappingrules.xml
and /etc/sipxpbx/fallbackrules.xml and we may be able to spot the
problem.
Alberto wrote:
thanks for your reply. Attached the files you requested.
Based on those rules, I can't see how dialing 12345678 would work,
unless you've programmed your phones to add a 0 on the front of an 8
digit number.
I strongly recommend _not_ using dial string transformations in any
component of the system except the sipXecs routing rules - having it all
centralized makes it much easier to debug problems.
You have 10 rules that together specify that a '0' followed by any
number of digits is always routed to voip.eutelia.it via your
sipXbridge. Based on your incoming numbers, I'm guessing that 8 digits
is the length of the numbers where you are.
I believe you could replace all 10 of the rules you have with just one
that listed an optional '0' prefix followed by 9 digits, and then sends
the call as 0 followed by the variable digits (that is, if the zero is
dialed, it will be kept - if not it will be added), routed to your ITSP
via the bridge as you have in your existing rules. Because the leading
0 is optional, the numbers the ITSP is sending you will work when used
as a return number.
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
