outgoing calls

I've got on top a "blocked number" list...
then I've got provider X having only 19x0 in the dialpattern;
then I have Provider Y with 69xxxxxx in the dial pattern;
and then I have Provider Z with xx.

Now Why does pbxes go to provider Y when I call 00398187800xx?

RE: outgoing calls

When seeking help please check "Allow independent moderators to see your call log & configuration data for support purposes (readonly, no passwords)" in your personal data.

thnx for looking into it ..i've [x] the option...

More outbound routing issues

I have several outbound routes defined on my PBX if I have the following route entries entrires (mixed with others):

0 provider A
1203222XXXX

1 Provider B
1203XXXXXXX

2 Provider C
1XXXXXXXXXX


the first entry seems to work, if I dial 12032222222.

The second entry is ignord and often passed along to the third outbound route, when I dial 12033331111. I have confirmed this many times over the last few months, and twice in the last 2 days. In fact the second third and fourth entries are quite often ignored if the dialed number fits a more general dial plan that is defined later. Only the first "0" seems to be used in most cases.

This does not seem to applyif all dial plans are specific for instance if I say

0 Provider A
1206XXXXXXX

1 Provider B
1509XXXXXXX

2 Provider C
1503XXXXXXX

this last example makes outbound routing mponunds more difficult, and you often must use a catch all later such as 1XXXXXXXXXX anyway, which returns you to the first example.

This post has been edited 2 time(s), it was last edited by i-p on 08.08.2006 at 13:11.

I notice the 0032+Nxxxxxx is ignored when the following line has xx.
i've removed xx. from the "trunks" section...
now it has
0032xxxxxx (for that equipment that allready has removed the 0)
0032+Nxxxxxxx (for adding countrycode&remove trailing 0)

RE: More outbound routing issues

@supernettel
Yiannis tried to reproduce your findings on his PBX but could not. We currently believe that your problem is related to the fact that your routing tables are extremely long. Just one of your dial patterns is 150+ pages long.

WAS 150 pages long when you looked at it, however the problem existed way before introducing that. In fact I saw the routing as fairly basic when I first encountered the problem. Please look for my past posts on this topic

BTW, my complex routing is now being handled elswere (in the same San Diego data center), and it works wonderfully.

I had tried to reproduce it for Yiannis on another PBX with no luck, however they were all supernettel trunks and that may have had something to do with it as well.

problem with outgoing calls

My ATA is registered with pbxes.org as a SIP extension.

I set a simple Outbound route with just one SIP trunk and rule XX. The trunk is set to a SIP provider sipnet.ru
This provider uses 7 digit usenames/IDs on its network.

The incoming calls via this provider work fine.

When making outgoing calls, I see strange behavior:
if I dial a 7-digits number, it works ok and I can reach another sipnet.ru user. If I dial a long distance number in the format prescribed by the provider, I get a message "All circuits are busy now, please try your call again".

Now, if I register my ATA directly with the provider and try to dial the exact same long distance number, it works ok

This post has been edited 1 time(s), it was last edited by ryb on 02.10.2006 at 00:50.

Hi rybshik,

When you login to your PBXes account, does the URL start as www2.pbxes.com or not?

Does the behaviour you described, only happened today or it has been going on for a while?

What kind of ATA have you registered as an extension?

Zitat:

Originally posted by Diafora Hi rybshik, When you login to your PBXes account, does the URL start as www2.pbxes.com or not? Does the behaviour you described, only happened today or it has been going on for a while? What kind of ATA have you registered as an extension?

Yes, it starts as www2.pbxes.com. I have Sipura 3000 at home and Grandstream GXP2000 in office.

I have been a PBXes user for a couple of days only. If I use the above mentioned provider (sipnet.ru) for my outbound routing, I still cannot make outgoing PBXes calls.

I tried two more providers for my out-bound routing. Gizmo project (sipphone.com) and vbuzzer. Gizmo project seems to work seamlessly. Vbuzzer works, too, but appears to send some extra digits after the dialed number which may confuse automatic phone attendants (if any).

Speaking of sipnet.ru, I know that it is a very SIP-friendly provider. For example, they accept (and let forward, too) SIP URI calls.

If you have time, could you please use my sipnet.ru account to test how it works with PBXes.
My account information with spinet.ru is as follows:
Username/ID "rybshik_4"
Password: will send by email/PM
SIP proxy: "sipnet.ru"

To make a test call, you can dial 74952235555 without any other prefixes. This a phone number of Russian Airlines automated information system

This post has been edited 6 time(s), it was last edited by ryb on 03.10.2006 at 00:58.

RE: outgoing calls

Finally we found an error processing routing tables of more than 10 routes. This was fixed today.