Questions from a confused newboy

[SY]

PBX documentation provides a lot of information. Did you read it?

You may use network protocol analyzers (like a Wireshark) to check what is coming(outgoing) to(from) your host.

 

[SY]

PBX documentation provides a lot of information. Did you read it?

You may use network protocol analyzers (like a Wireshark) to check what is coming(outgoing) to(from) your host.

 

[ryan]

PBX documentation provides a lot of information. Did you read it?

You may use network protocol analyzers (like a Wireshark) to check what is coming(outgoing) to(from) your host.

LOL - read the manual that many times in the last 48 hours I could quote it now

Ah well.

 

[SY]

PBX documentation provides a lot of information. Did you read it?

You may use network protocol analyzers (like a Wireshark) to check what is coming(outgoing) to(from) your host.

LOL - read the manual that many times in the last 48 hours I could quote it now

Ah well.

What about Wireshark capture?

 

[ryan]

PBX documentation provides a lot of information. Did you read it?

You may use network protocol analyzers (like a Wireshark) to check what is coming(outgoing) to(from) your host.

LOL - read the manual that many times in the last 48 hours I could quote it now

Ah well.

What about Wireshark capture?

To be honest, if the suggestions from the gurus here don't work I cannot see what a ethereal trace would say that they haven't.

It was worth a punt but I guess its not to be

Thanks to everyone for the suggestions.

 

[ryan]

Just a quick thought, does it matter what your ethernet adapter name is?
As my system is sat on a VPS, the ethernet adapter is called vznet0.
Just wondered if 3CX looks for certain ethernet names etc

ry

 

[SY]

PBX documentation provides a lot of information. Did you read it?

You may use network protocol analyzers (like a Wireshark) to check what is coming(outgoing) to(from) your host.

LOL - read the manual that many times in the last 48 hours I could quote it now

Ah well.

What about Wireshark capture?

To be honest, if the suggestions from the gurus here don't work I cannot see what a ethereal trace would say that they haven't.

It was worth a punt but I guess its not to be

Thanks to everyone for the suggestions.

Ethereal will provide raw network data and there we will see, what was delivered and what was not.

Regards

 

[tjabaut]

Sy,

Thanks for the props, but I am a little confused about ports 7000-?

According to the documentation these are only for the system to communicate with VoIP gateways. The purpose of SIP is to setup dynamica channels once a call is registered, so I am still of the belief that it is using ports 9000+ (default; I tend to use industry standard range of 10000-20000).

In past, looking at packet captures I still see ports in my predefined range even for LOCAL calls. I will have to take a look again, but that has been my understanding.

Ryan, SY is correct. A packet capture will speak volumes as to what is going on between you and your VPS. That is truly the only way to isolate the problem. This is not specific to 3CX, but rather is a by product of the enitre SIP protocol. We as network engineers have use protocol analyzers for years as it is the ONLY way to determine what is going on at the packet level.

Sy, correct me if I am wrong, but Ryan also should not be exposing port 5482 the Medai Server. He should instead be using Port is external. CORRECT? I do not see any value in exposing more ports than necessary. As I have previously stated, my job as a Security Consultant always has me looking into Attack Surfaces, and I have to have a real justification to open any ports. Mine are not open and things work fine.

 

[ryan]

I have installed ethereal locally so will have a play later......if I remember how to use it!!

 

[ryan]

On the back of that - I dropped the firewall on the VPS quickly and the problems remained so I guess its my end that has the problem

 

[tjabaut]

Is it possible that your ISP is filtering SIP traffic?

 

[ryan]

Is it possible that your ISP is filtering SIP traffic?

Nope, I can use voip using some of the commercial outfits like voiptalk etc.

I have just had another play and this is popping up in the logs:

[MS105000] Call(58) Ext.101: No RTP packets were received on 00000058@:remoteAddr=62.31.86.139:5063,extAddr=77.74.198.156:9016,localAddr=0.0.0.0:9016

So I see the stun server picks up my external IP (62.31.xx.xx) and the IP of the server (77.74.xx.xx), but what is the 0.0.0.0 on the end?

I tried running Wireshark on the server but because its a virtual ethernet device, wireshark doesn't pick it up

Again I apologise for the problems I keep throwing here, but like I said, this software is cracking so I would like to get it going

Ry

 

[SY]

Is it possible that your ISP is filtering SIP traffic?

Nope, I can use voip using some of the commercial outfits like voiptalk etc.

I have just had another play and this is popping up in the logs:

[MS105000] Call(58) Ext.101: No RTP packets were received on 00000058@:remoteAddr=62.31.86.139:5063,extAddr=77.74.198.156:9016,localAddr=0.0.0.0:9016

So I see the stun server picks up my external IP (62.31.xx.xx) and the IP of the server (77.74.xx.xx), but what is the 0.0.0.0 on the end?

I tried running Wireshark on the server but because its a virtual ethernet device, wireshark doesn't pick it up

Again I apologise for the problems I keep throwing here, but like I said, this software is cracking so I would like to get it going

Ry

Log just provide you information:
No packets was received from address 62.31.86.139:5063 on address 77.74.198.156:9016 that is address of PBX receiver. Your connection is not local, so you don't need to pay attention on localAddr=0.0.0.0:9016.
For local connections local address will be specified but external will be 0.0.0.0.

possible reasons:
1. Firewall can blocks traffic (it may happen on any router (hop)). There are three parts of path:
a) from extension to its gateway(62.31.86.139),
b) from 62.31.86.139 to 77.74.198.156
c) from 77.74.198.156 and your server host.

2. NAT translation is incompatible with RTP traffic on server side network.

It was a reason why I asked you to analyze traffic on the server host.

Regards

 

[ryan]

Thanks for all the tips.
I have definately narrowed it down to my router - stuck my softphone PC into the DMZ on my router and the sound came through fine and dandy.

Could anyone tell me what ports should be open on my home router (Netgear WGR614v6) so 2 softphones on my home network can connect and use the PBX?

Many thanks again (honest I will shut up in a bit ) - at least at this rate with all the things I have written down during the last week I may be able to help others one day

 

[SY]

Thanks for all the tips.
I have definately narrowed it down to my router - stuck my softphone PC into the DMZ on my router and the sound came through fine and dandy.

Could anyone tell me what ports should be open on my home router (Netgear WGR614v6) so 2 softphones on my home network can connect and use the PBX?

Many thanks again (honest I will shut up in a bit ) - at least at this rate with all the things I have written down during the last week I may be able to help others one day

I'm glad to hear that we found a problem. Please specify your router model.

Thanks

 

[ryan]

Not as happy as I am
The router is a Netgear WGR614v6.

Slowly narrowing it down further - when using the 3CX phone software, there is no where to specify the RTP ports to use for each client.

Fired up X-Lite and I can now specify ports per client which seems to work in the logs.

Only thing thats not working is X-Lite is sending my local address and not the WAN address, but thats not 3CX problem

Getting there - I can only apologise for the postings I have made over the last few days. Hopefully I will get there tonight!!!

Ryan

 

[SY]

Not as happy as I am
The router is a Netgear WGR614v6.

Slowly narrowing it down further - when using the 3CX phone software, there is no where to specify the RTP ports to use for each client.

Fired up X-Lite and I can now specify ports per client which seems to work in the logs.

Only thing thats not working is X-Lite is sending my local address and not the WAN address, but thats not 3CX problem

Getting there - I can only apologise for the postings I have made over the last few days. Hopefully I will get there tonight!!!

Ryan

What do you mean, "there is no where to specify the RTP ports to use for each client."? Please describe what do you expect form such ability and which kind of information you plan to put there?

Thanks

 

[ryan]

As I found out last night its my stupid router causing the problems - it allows the setup of the call but the RTP ports don't come back through the router to set up the audio bit.

On X-Lite there is a part of the config where you specify a port range to use so I can put rules in the firewall to forward those ports to the right X-Lite phone.

Image is below:

Image Removed (Broken link. Please upload through the forum)

All I need to do now is get the STUN bit going on X-Lite and I am laughing!
At this rate I will be a guru soon

 

[ryan]

Its actually working!
My router, supplied by my ISP (also a telecomms supplier) appeared to have a hacked firmware put on by them. I couldn't upgrade the firmware due to the ISP locking down so went and bough a new one - now working a treat.

So, thanks to my dodgy router I thought there was a fault with my router and with the softphone and in fact they had all been configured perfectly.

Thanks to everyone here for the hints and tips - at least I can now help out!

Ryan

 

[nb]

ts actually working!
My router, supplied by my ISP (also a telecomms supplier) appeared to have a hacked firmware put on by them. I couldn't upgrade the firmware due to the ISP locking down so went and bought a new one - now working a treat.

Ryan - For information purposes - so you could not find a way to open ports 9000 to desired amount inbound on your local router? Im afraid that there are other people who have this restriction on their routers - something which is out of their control - right??