Outgoing Number Issue

Genom88 · Post by **Genom88** » Fri Nov 30, 2012 8:11 am

1. Brekeke Product Name and Version:

Brekeke SIP Server
2.4.3.0/286

2. Java version:
Java Standard Edition 6 Update 11 (build 1.6.0_11-b03)

3. OS type and the version:
Windows XP Prof.
Service Pack 3

4. UA (phone), gateway or other hardware/software involved:
X-Lite / Snom phones, Dialer (Server 2003), ...

5. Your problem:

First of all - Sorry for my bad English:

After my access to the company, the following problem appeared by my predecessor changes: We are sending out our Headnumber the extension and after the extension a “192”, for example:

Headnumber Ext ???

01 400 40 30 214 192

That’s the only Problem, we can Receive Call without Problems (snom phones) we can Call out without Issues (except the wrong Number). Well he’s taking an IP Address, but I don’t know why…

The story:

I entered the Company in March 15. 2012

We had a Major crash short before 2012 (around December 2011) with our Old Servers, that was the Reason why we virtualized everything Server-based on the new HP Server. The only thing is not virtualized is our Dialer Server from “Company XY”. We also had a Firewall crash between the Beginning Year of 2012 and my accession – also the guild of my forerunner.

So my big Problem is – I tried to find out where the Issue is comming from, but I didn’t come to a Solution and I tried probably everything. I just know that the Issue appeared short before the forerunner was walking away, that means around feb-march 2012. I just also thought that this could be a Firewall Issue, but i didn’t found a solution here neither. Fact is that everything worked correct for 2 years – now I don’t really know what my forerunner changed, but it seems like that he made a lot of bullshit.

Here the Facts:

Dialer Server:

Here is everything correct – talked with the responsible Company + Remote Sessions.

Firewall (Sonicwall):

Dialer:

RTP, H323, SIP, UDP port 5060, needed UDP Ports and TCP Ports are opened up – packed in a service Group and placed in the NAT Policy.

Brekek SIP:

TCP/UPD Port 5060, and also UDP 10000-10999

VOIP Settings on SonicWALL:

H.323 Settings, SIP Settings and consistent NAT not enabled.

SIP Server:

IP Address is static…

Dialup Plan

Code: Select all

1	special rule 9	$request=^INVITE
To=sip:120@	To=sip:120@192.168.XX.XX

Code: Select all

2	special rule 8	$request=^INVITE
To=sip:123@	To=sip:123@192.168.XX.XX

Code: Select all

9				
10	IP_PBX	$request=^INVITE
To=sip:(0.+)@	To=sip:%1@192.168.XX.XX

Yea well... i can’t really find a solution and i took a look at many things, without success. The only things I got left are: Firewall Firmware Update – because our current Firmware is pretty old. Or Maybe setting up a new SIP on a Physical Machine… with a newer Version of Brekeke SIP.

I hope you can Help me with that Issue, because i´m kinda burned out with it.

Thanks for your Help in advance.

[/code]

hope · Post by **hope** » Fri Nov 30, 2012 10:56 am

can you describe more about problem details?
what calls have problem?
what problem calls behave like?
what are you expecting the calls should work like?

Genom88 · Post by **Genom88** » Fri Nov 30, 2012 12:13 pm

can you describe more about problem details?

We have only Problems with the outgoing calls, the incoming Calls work fine.We are reachable from outside, if people call our Headnumber with OR without extension. If we call out we got the Issue that our Number is not Displayed Correctly. That also means if one of our Project Managers is calling a Mobile/fixed Line, he will be displayed as (for example ext 210):

01 400 40 31 210 192

That has to cause, that the recipient – if he´s calling back, will not reach the Proj. Manager because that Number does not exist and automatically get redirected to our reception. It’s possible to reach the extension if they dial it manually, but it´s embarrassing to tell this every single Person and harms our Company.

In short Words: The Number presentation is incorrect if we call out. “192” is not Part of our Number.

what calls have problem?

The Problem appears on every outgoing Call. We are a Market institute and having Interviewers which using X-lite for the daily Work. The Internal Members got VOIP Phones (snom). In both cases we send out the 192 at the End of the Telephone Number.

what problem calls behave like?

Like mentioned above: If we call out (no matter which Device we are using), the recipient will get our Head Number including the wrong Number at the End (192).

Examples:

Interviewer calls a Mobile, the Number will appear like this: 900 400 40 31 192
(900 is the ext. from our Interviewers)

Internal Employee calls a Mobile/Fixed Line: 400 40 31 214 192
(214 is the ext. from the VOIP Phone)

How the Number should be displayed, if I call from a VOIP phone : 400 40 31 214

what are you expecting the calls should work like?

The Number presentation should be correct. The 192 should not be part of the Number.
[/u]

hope · Post by **hope** » Mon Dec 03, 2012 11:35 pm

when the call is talking, and go to brekeke server "active sessions" and click on the call, go to session details,
- what dial plan rule name is in "rule" field for the problem call?
- paste the rule here
- and run wireshark to capture packets at Brekeke server of the problem call, and check the INVITE sent from brekeke to destination,
what is from header like?

Genom88 · Post by **Genom88** » Mon Dec 10, 2012 8:57 am

hope wrote:when the call is talking, and go to brekeke server "active sessions" and click on the call, go to session details,
- what dial plan rule name is in "rule" field for the problem call?
- paste the rule here
- and run wireshark to capture packets at Brekeke server of the problem call, and check the INVITE sent from brekeke to destination, what is from header like?

Tested with extension 214:
Our SIP Server is 105
Our Dialer Server is 100

Rule: IP_PBX

IP_PBX:

$request=^INVITE
To=sip:(0.+)@

To=sip:%1@192.168.1.100

Wireshark capture:

From: "214" <sip:214@192.168.1.105>;tag=o793ntzgx7
SIP Display info: "214"
SIP from address: sip:214@192.168.1.105

hope · Post by **hope** » Mon Dec 10, 2012 12:28 pm

Wireshark capture:

From: "214" <sip:214@192.168.1.105>;tag=o793ntzgx7
SIP Display info: "214"
SIP from address: sip:214@192.168.1.105

There is only 214 as display name in the packets
check at dialer server side if there is any setting changed the from header sent from Brekeke server to dialer server

Genom88 · Post by **Genom88** » Fri Dec 14, 2012 2:48 am

hope wrote:
Wireshark capture:

From: "214" <sip:214@192.168.1.105>;tag=o793ntzgx7
SIP Display info: "214"
SIP from address: sip:214@192.168.1.105
There is only 214 as display name in the packets
check at dialer server side if there is any setting changed the from header sent from Brekeke server to dialer server

Hello,

Thats our Config.xml, but i took a look in the Backup from 2010 (when in worked).. nothing changed:

Code: Select all

	
<addressTranslations>
...
<translate address="sip:0*@192.168.1.100" translated="0*"/>
<translate address="0*1921681100" translated="0*"/>
...

Genom88 · Post by **Genom88** » Fri Dec 14, 2012 3:00 am

Another Information:

"The IP address XXX.XXX.XXX.XXX you have entered for this network adapter is already assigned to another adapter"

Fact is that we virtualized the SIP Server to our Server. When I saw this message I just put out the wrong entry from the Regestry, and nothing changed. Some days passed and I decided to make a SIP Server restart – didn’t do that after the change because we had a lot of Interviewers here. Well now comes the funny part: Tried to open the Admintool some seconds
Later = Fatal Error (please reinstall your product).

Could it be that this Issue appears with the non existing configured physical NIC from the old Workstation?

I mean if I plug in the Old archived Workstation in and put the Virtual one on offlinemode we could find out if this is the cause.

Laurie · Post by **Laurie** » Mon Dec 17, 2012 1:00 pm

Genom88,

Which IP-PBX product are you using?

> Thats our Config.xml,...

I think you must talk with the IP-PBX manufacturer because the problem is caused from the IP-PBX.

Laurie · Post by **Laurie** » Mon Dec 17, 2012 1:05 pm

> Could it be that this Issue appears with the non existing configured physical NIC from the old Workstation?

Is it on the Brekeke SIP Server's PC?

You may need to re-activate the product license if you remove/add a NIC.

Genom88 · Post by **Genom88** » Thu Dec 27, 2012 6:45 am

Hello Laurie,

Thanks for the response, i need to test some things when we are in nonoperating state.

Well for fyi: i talked with the IP-PBX Manufacture and they took a look at it, more than once, also when my forerunner was here, they said its not a issue on their side.

But thanks, was a good hint in that case.

Dont care any longer about this Thread for now, i will respond you if i know more. (or atleast if i find a solution i will post it here, wouldnt be bad for a documentation if this problem really appeared with Brekeke SIP).

Thanks and Br

Genom88 · Post by **Genom88** » Thu Mar 07, 2013 3:28 am

Just to let you know what the Issue is:

The Problem was on the Dailer Server. The Translation for sorting the Internal IP out wasn’t working correctly.

An outgoing Call was presented with Number+Ip address because of a Bug in the internal System. That Bug had just one manner: He wasn’t able to translate the interal Server IP to the ISDN.

So he always took the max tel. Number Length (depends on the country) and filled it up with the internal IP Address of Server.

That kina looked like +44 1002030 400 192
Call Number ext. IP

Well the Solution in my Case (because the Host is an external Company) is a complete System Update to a never Version. Well the Version we had is 2 Years old, but I thinks its ok to follow the slogan: never touch a running system… IF the System works.

Br