W52P over IPsec VPN

[Novais]

We have a W52P that i am wanting to connect to a remote yeastar PBX and the 2 sites have an established IPSec site to site VPN. I can log into the PBX from the remote site and everything appears to be communicating but I am unable to register the W52P to the Yeastar. We have several other T46S phones on the same site as the Yeastar which are working great.

I have tried some basic troubleshooting but without any success. The logs only show the following...

SUA <3+error > [000] [Server0]: try reg again after (30) s

Any suggestions?

[Karl_Yealink]

Please help us to capture the PCAP/syslog/config.bin files from W52P and T46S.
We can check more from them.
You can know the method from the FAQ below.
FAQ: http://support.yealink.com/faq/faqInfo?id=313

[Novais]

Here are the logs from the 2 phones. The zip file is he T46S phone.

[Karl_Yealink]

Please help us to capture the files one more time, it don't contain useful information.
And we also need files from W52P

[Novais]

Here are the syslog files from the W52P. Not sure what other files you are looking for...

[Karl_Yealink]

(02-14-2017 05:21 PM)Novais Wrote:  Here are the syslog files from the W52P. Not sure what other files you are looking for...

Still need config.bin file, you can access phone->configuratoin-> Export or Import Configuration, then export the configuration file.

Meantime, if possible, please help us to capture the log and config.bin file from T4S phone

[jolouis]

(02-14-2017 05:21 PM)Novais Wrote:  Here are the syslog files from the W52P. Not sure what other files you are looking for...

Have you checked all the basics first? You said you can log into the Yeastar from the remote site, but what is the VPN structure? i.e. is the remote site a different subnet/network than the main one, and have you confirmed all the proper routing is in place on both sites for the traffic to work properly? I believe you log shows the W52P is getting it's config through the RPS service, have you confirmed using the web interface on the W52P that the server information is in fact correct for the location you are at? (i.e. you said you can log into the Yeastar from the remote site... are you using the same IP to log in as the W52P is using to try and register?)

Try doing a packet capture on both sides of the VPN and see if:
A) your W52P traffic is in fact making it to the Yeastar network,
B) The Yeastar is sending any kind of response onto the Yeastar network
C) If it is sending a response, does it make it over the VPN to the W52P network?

There are any number of firewall and routing configuration problems that could cause your issue, you need to narrow it down much further in order to figure this one out.