Cannot ping sip Proxy?

[killmasta93]

Hi,
I was wondering if someone could help me out?

So Before i was running an old version of elastix and wanted to upgrade it. So instead I bought me a new disk and put a clean install of elastix. Everything is working well added the IVR extensions and trunk GSM works fine. But now the issue is the sip proxy from the VOIP provider Not sure why I cannot ping which therefore wont wonk the trunk. Whats soo funny is that i screen shot everything so i could copy the trunk detail exactly the same everything.

So i was thinking it was my VOIP provider i called and they said everything was fine. So i put in the old disk and the trunk was working again. So Im not sure why or how its not working on my new disk?

This is my config for my trunk settings

type=friend
context=from-trunk
canreinvite=no
nat=no
host=172.17.179.166
dtfmode=rfc2833
disallow=all
allow=ulaw&alaw&gsm&g729
qualify=yes
insecure=yes

Thank you

 

[Bob1]

killmaster93,

First of all, thanks for providing enough detail to make an educated guess, it really helps. My answer might be wrong, but at least it may be in the right direction.

Whilst you screen shot everything, I suspect (like most of us), you have forgotten non-gui changes that you may have done in the past.

On your new machine, can you perform traceroutes to
1) a device on the 192.168.1.x network
2) The 172.17.179.166 address

Could you also provide a screen shot of your current routes on the Elastix box.

At a guess at the moment
1) Your VSP does not allow you ping their Server and you are on the wrong track
or
2) You are missing the routes for the 172.17.179.x network as your default gateway is set to 192.168.1.254

If you find your routes are the issue, I don't need screenshots....

Regards

Bob

 

[killmasta93]

Hi Bob,
Thank you for the reply, As the previous Elastix was working well I did not set up it the previous IT did and they never really gave me nothing to go on. What instead i did i screen shotted everything and copy exactly the same in the networking config. Im not really sure when you mean current routes on the Elastix box as in the network settings?

Well on the /etc/sysconfig/network-scripts the ifcfg-eth0

I added the screen shots from the old elastix and the new elastix config

my VOIP provider does allow to ping because on the old elastix which is on another disk works while when i put in the new disk that has the new elastix same config everything wont let me ping the sip proxy im guessing im missing something.

Thank you

 

[Bob1]

Killamasta,

With the news that you took over the system, means that it is more likely that you are missing the route.

You have two network cards - that is fine, you can configure has many as you want, however you can only have one default gateway (which in your case is the 192.168.1.254). What this means is that all traffic (unless you have specific route) will go to this card (unless the network address you are trying to reach is within the subnet of the other card(s). Naturally your ISP Trunk will also try and reach its destination via this Gateway (which is most likely impossible via this Internet connection).

Now the address 172.17.179.166 is not part of the subnet of the second card you have in the system, so a hard route is needed to tell it how to get to that address (which is via the second card).

So you need to add a route to tell it what interface to go out for that particular traffic.

At the Linux prompt on the old Elastix box type

route -n

This should show you if you have any routes in place

post this

For your benefit do the same on the new Elastix box - you should find they differ



If you need to add a route, I recommend that you do a search on the following words in Google

centos route add

and also more information is here
https://access.redhat.com/documentation ... lt_Gateway

You will need to setup persistent routes and if you check the old Elastix box, under /etc/sysconfig/network-scripts, you will probably find a file called route-eth0 or route-eth1 etc......

Hope this helps...

Regards

Bob

 

[killmasta93]

Hi,
Thank you so much i needed to add this

route add -net 172.17.179.166 netmask 255.255.255.255 gw 172.22.102.161 dev eth0

But that everything is working but when i restart or halt it erases the route? Any idea to have it permanent?


Thank you again so much

 

[Bob1]

Killamasta,

Glad you are on your way....

You need to add the route to the route file

/etc/sysconfig/network-scripts/route-eth0 or eth1

Have a look at Centos route persistent in Google and there are plenty of guides....

Regards

Bob

 

[killmasta93]

Thank you so much this is how i got it working to help others
first add this

route add -net 172.17.179.166 netmask 255.255.255.255 gw 172.22.146.89 dev eth1

then

# vim /etc/sysconfig/network-scripts/route-eth1

edit like this depending on your proxy settings that your VOIP provider gives

see picture then save it by doing ctrl+c then shift then the :wq

and reboot you can verify with route -n

Thank you again