PBXes (http://www1.pbxes.com/forum/index.php)
- English (http://www1.pbxes.com/forum/board.php?boardid=16)
-- Bugs (http://www1.pbxes.com/forum/board.php?boardid=24)
--- RE: Weird routing on secondary call (http://www1.pbxes.com/forum/threadid.php?threadid=1216231890)

Weird routing on secondary call

Hi,

I tried the following sequence:

1. Called a regular number on my Nokia E51;
2. Put the first call on hold;
3. Added a new Internet call (to a PSTN destination) via PBXes.

The Internet call wasn't routed properly -- it just kept heading to the "pbxes.org" trunk (over and over) according to the Call Monitor. If the number in #3 is called directly (not via an additional call), it routes properly.

If anyone from PBXes wants to check my logs, it starts from 2008-07-17 01:45:16 (GMT+0800) to 01:48:01. An example of correct routing is at 01:48:02.

In order to be certain of what you mean and avoid a misinterpretation, I will ask a couple of questions clarifying this call scenario.

On step (1) by the expression "regular number" do you mean a call on the GSM network?

On step (3) if you dial the number of the SIP call, without previously having the 1st call on hold, does the call route properly on PBXes using the correct Outbound Route?

Hi. Yes to both.

That is indeed strange, but we will need some recent calls during a period when traffic is low in your account, in order to figure it out.

Ok, I've unregistered the only client for now, and I'm pretty sure there won't be any traffic. Please let me know when it's ok to register again.

"Weirdness" starts at 2008-07-18 09:02:41 GMT+0800, to a 0291xxxxx number called via PBXes, with a GSM call on hold. Correct routing of the same number from the same client (Nokia E51 SIP) but as the primary call is at 09:03:35.

I'd already stopped the calls, but the incorrect routing to "pbxes.org" kept on going and going until 09:08:12, even surviving a "Submit & Start".

BTW, the caller id of the weird routing is aibrado-xxxx, not the "... SIP <xxxx>" (xxxx = extension) of the correct routing.

I have looked into this, and I can confirm the strange routing issue.

In order to troubleshoot this further, I deleted the 0|N. from the Custom Dial Patterns of the philippines Outbound Route, and added a Test Route with just your 0291xxxxx test number in its' Custom Dial Patterns, restricted only to the 2539 extension.

Send a few calls to the 0291xxxxx test number number from the 2539 extension, and provide me with their time-stamps as well as their routing behavior.

I followed the same sequence (GSM, hold, 0291xxxxx via PBXes), and this time it worked! There's a single call at 2008-07-19 16:32:08 GMT+0800 (caller id 0063920xxxxxxx) and the destination phone rang.

A direct call (no hold) via PBXes is at 16:40:50. It also worked.

So I guess the problem is the processing of the 0|N. pattern... Would you like me to try with the +63 and 0063 patterns?

Great. Now add this +63[2-8]xxxxxxx. for fixed lines, this +639[01279]xxxxxxxx for mobile numbers on the Test Route, and try a couple of calls.

RE: Weird routing on secondary call

I rewrote the rules to not have an outgoing trunk prefix and used these instead:

Trunk:
0063+0|N.
00++|Z.

Outgoing route: (starts with)
+63
0063
0N

Seems to work fine.