0

Strange problem with Cisco CP-8845-3PCC and Yeastar S50

P. Hubert

January 10, 2021 15:08

None

Follow

Hi All,

I Hope someone can help me with a strange problem. I recently buy a Cisco CP-8845-3PCC Phone as a replacement for the CP-7970G. The problem was, working from home; don't wanna have 2 phone's on my desk. The CP-7970G only could connect to 1 PBX, and for that reason I had an extra Linksys SPA942 on my desk with the lines from work. In the living room I have a SPA962 with 2 home lines, 1 work line, both work fine.

The technical details:

At Home: RasPBX (with 2 lines)
At Work: Yeastar S50 (Multiple lines) (I have 2 at home extension)
Cisco CP-8845-3PCC (Firmware: 11-3-2MPP0001) (Have try all versions) (Multiplatform you can compare it with the SPA series with web interface).

VPN site to site Connection between home and work, at work I have permission to the Voip Lan to connect to the Yeastar. At home I have a seperate VLAN for all Voip. Everything works fine, I can call with both SPA942 and 962 accept the CP-8845-3PCC.

I have followed the instructions of:
https://support.yeastar.com/hc/en-us/articles/115000305848-Manually-Register-Cisco-SPA-Series-IP-Phone-to-Yeastar-S-Series-VoIP-PBX

All phones have the same settings (accept the 8845 have more than the older ones but leave it to default.) I only work with IPv4, disabled IPv6 on the phone.

On the Cisco CP-8845-3PCC all the lines register, 2 from home, 2 from work. People can call me from work, from outside, no problem, but I can't call out with the work lines. The home lines work perfectly but the work lines doesn't.

-All phones same network permissions at home
-All SPAxxx phones work perfectly, local and tru VPN s2s to work
-The CP-8845-3PCC register (green LED)
-The CP-8845-3PCC can receive incoming calls from work (tru VPN), with voice both directions, perfect quality. 
-The CP-8845-3PCC work lines doesn't work If I want to call out, not to an extension at work or a mobile phone.
-The CP-8845-3PCC works perfect with home extensions
-If I apply the dialplan of Yealink "[x.]" or the one from the SPA962/42 both doesn't work If I want to call out.

Am I missing something? Can anyone help me, thank you!

• Facebook
• Twitter
• LinkedIn

5 comments

• 0
  
  Larry Neblett January 13, 2021 13:23

  When calling out, have you taken a capture at the PBX to ensure that the PBX is seeing the stream and to validate the data within the stream? 

• 0
  
  P. Hubert January 14, 2021 22:07

  Hi Larry,

  Thank you for your answer. With all do respect, how can I do that? The thing is, the phone can be receive incoming calls but if I want to call the line stay's dead. With a (home) raspbx and external extension of a provider it works. Is there maybe a parameter in the Yeastar I need to enable of set? Already set the extension to allow remote registration, allow the firewall and allow multiple registrations (3).

  Paul

• 0
  
  P. Hubert January 14, 2021 22:11

  Other question to all who are reading this post. If anyone have connect with succes a CP-88xx-3PCC Cisco phone to any of the S-series Yeastar, have you ad or changed some parameters in the EXT or SIP other than in the manual for the SPA-series?

  Thank you very much!

• 0
  
  Larry Neblett January 14, 2021 22:47

  Well, each system may be somewhat different so what happens on one system is of little consequence as it apparently isn't working on the S-PBX. I do not understand what is meant by the line stays dead. Does this mean that when you lift the receiver there is no dial tone?

   

  Do a network capture, look in maintenance and the manual. As you have only provided what the issue is and none of the settings, it pretty hard to suggest what setting may be needed when none of them are known. 

   

  As you have indicated that some are seemingly on a VPN, did you add the local subnet of the VPN side into the NAT section of the PBX?

• 0
  
  P. Hubert January 20, 2021 16:17

  Hi Larry, 

  Thank you for you're thinking with me to solve the problem. I have delete some posts because the problem is solved. After a post on the Cisco community the problem was solved within 15 minutes. 

  Solution: Disable all unused codecs if using UDP.

  Kind regards,

  Paul