Hi!
I need some help regarding the connection of Linkus Mobile Client on our Yeastar S100
Linkus client on mobile can login to Linkus Server and make calls on LAN IP Phone but when you answer the call there is no Audio.
Any idea about this issue?
Thanks Guys!
S100 Firmware Version is 30.7.0.27
Linkus Server Version is up to date
Linkus Mobile Client is up to date
Here's a pcap log for reference thanks.
------------------------
BYE sip:873@10.0.200.5:5060 SIP/2.0
Via: SIP/2.0/UDP 10.0.200.171:5060;branch=z9hG4bK-852d2fa7
From: "Ed" <sip:871@10.0.200.5>;tag=a0da2a31b344f743o0
To: "873" <sip:873@10.0.200.5>;tag=ed8b8dcd-7045-4cd4-9736-ed0eb7ae1120
Call-ID: 677bbf49-6c9ea50b@10.0.200.171
CSeq: 103 BYE
Max-Forwards: 70
Authorization: Digest username="871",realm="YSAsterisk",nonce="1547012422/248e03d37f3665ee33460c284257808d",uri="sip:873@10.0.200.5:5060",algorithm=MD5,response="ccf30465e59fbe7e5dd5b8d1277047a4",opaque="6ce884355b96b804",qop=auth,nc=00000002,cnonce="f868946a"
User-Agent: Cisco/SPA525G2-7.4.7
Content-Length: 0
U‰5\t{ € € @U9¢‘tôµIñá E`r><@ @V.
È
È«ÄÄ^ŒÀSIP/2.0 200 OK
Via: SIP/2.0/UDP 10.0.200.171:5060;received=10.0.200.171;branch=z9hG4bK-852d2fa7
Call-ID: 677bbf49-6c9ea50b@10.0.200.171
From: "Ed" <sip:871@10.0.200.5>;tag=a0da2a31b344f743o0
To: "873" <sip:873@10.0.200.5>;tag=ed8b8dcd-7045-4cd4-9736-ed0eb7ae1120
CSeq: 103 BYE
Server: Yeastar S100-30.7.0.27
Content-Length: 0
U‰5\ŽŒ õ õ IûBôµIñá E`炇@ @V5
È
ƒäÄ ÓTBBYE sip:873@10.0.131.228:5152;linkus SIP/2.0
Via: SIP/2.0/UDP 10.0.200.5:5060;rport;branch=z9hG4bKPj9d92a46d-1da3-4e43-a849-0dd88bf62341
From: "Jozen" <sip:871@10.0.200.5>;tag=36044081-ce1f-498f-ab2b-f47be2d70752
To: <sip:873@10.0.131.228;linkus>;tag=60ecb255-6a8a-4df9-bbf1-bb0781591d4c
Call-ID: 7bcc5787-04d5-4c5b-8dca-f05e19f827d5
CSeq: 22858 BYE
Reason: Q.850;cause=16
Max-Forwards: 70
User-Agent: Yeastar S100-30.7.0.27
Content-Length: 0
U‰5\¡ ¢ ¢ ôµIñá IûB E ”Û£@ ?þË
Ċ
È Ä€ôBSIP/2.0 200 OK
Via: SIP/2.0/UDP 10.0.200.5:5060;rport=5060;received=10.0.200.5;branch=z9hG4bKPj9d92a46d-1da3-4e43-a849-0dd88bf62341
Call-ID: 7bcc5787-04d5-4c5b-8dca-f05e19f827d5
From: "Jozen" <sip:871@10.0.200.5>;tag=36044081-ce1f-498f-ab2b-f47be2d70752
To: <sip:873@10.0.131.228;linkus>;tag=60ecb255-6a8a-4df9-bbf1-bb0781591d4c
CSeq: 22858 BYE
Content-Length: 0
The pcap is not complete as the Contact and Connection headers are missing. These are the critical ones as they tell the receiving device what IP and port to use when communicating back to the other end. Do the capture from the S100 and post the file.
Thanks Larry
Linkus to Linkus extension is working fine but for Linkus to IP Phone there is no audio.
please send the pcap file so I can use the tools to analyze.
Here's the pcap tar file
https://drive.google.com/open?id=1Syv-WjYbxW-84OWGf3tl7tr2d38NXa20
Can you show a screen shot of the linkus settings and the SIP NAT settings?
What I see is that the 525 and the Spbx are on 1 subnet and the Linkus is on another,
Here's the setup of Linkus and SIP NAT
The SIP session seems fine and the S20 receive both IP phone and Linkus's RTP stream. See below screenshot:
Try call from Linkus to Linkus and see if the voice works fine or not. If Linkus call to Linkus works fine, it probably caused by the DSP hardware issue. Get system logs and post here to confirm. (It is better to reboot the device and get the system logs, in order to make sure the hardware logs will not be over wrote)
Hi Oscar
Linkus to Linkus voice is working fine.
Linkus to IP Phone the RTP is not connecting
Here's the screenshot of Linkus to Linkus Call
I will also post the system logs
Thanks
Hey Oscar, the trace is not fine. you are correct in that the PBX is receiving the streams, but the PBX is not transcoding and relaying the stream from one device to the other. So, you assumption about the DSP may very well be correct.
Can you reach voice mail (*2 default) on the S20 from Linkus and hear the prompts? Can you call another extension from Linkus and leave a voice mail and then retreive same by hearing the voice.
From the screen shot, it appears that the expectation is that the there is no external communication expected with any device which would include the use of SIP providers, unless there is an on-premise SBC. Is this correct?
Hello Larry
From Linkus, I can reach the voice mail on the PBX but there is no audio.
Also from Linkus leaving a voice mail to IP Phone extension, its not working and there is no record of the voice mail
As an aside, what codecs are set in the SIP settings? I am going to assume that ilbc is enabled, as otherwise the PBX should have responded with a 488 response, but just to be safe, please check. Also, can you confirm the firmware version of the pbx and also see if the Linkus app is up to date?
I assume you can get to Voice mail from the Cisco and hear the voice?
Larry, yes, the PBX is not transcoding and relaying the stream from one device to the other.
As I know, there is a DSP inside the PBX, which used to encode and decode the iLbc. I have one customer that has similar issue and finally, with Yeastar support team's help, they confirm it is the DSP issue. But we need the system logs to confirm.
Jozen, do you work with a Yeastar distributor or Yeastar directly as a distributor? I would suggest you to try with another S PBX, if you have. : )
Or I would suggest you to submit a ticket and ask Yeastar support team to confirm it is hardware issue or not.
Hi Guys,
Yes Larry ilbc codec is enabled, Voice Mail is working fine in IP Phone extension
Here's the information of our PBX
Yeastar S100 Firmware Version is 30.7.0.27
Linkus Server Version is up to date
Linkus Mobile Client is up to date
I still not contact the local distributor regarding this issue Oscar, I think the device was purchased abroad.
here's the link for system logs.
https://drive.google.com/open?id=1-Eh4o6Te4xjyma_RzK2ptHZh8TwDQddH
Thanks Guys.
Unfortunately, there is not hardware logs inside the system logs.
Can you try login via SSH and get dmesg logs?
See here for the guide how to login SSH:
After you login successfully, execute command dmesg
After that, save the logs into a file and post a download link here.
See the last part of the dmesg message, the USB 2 is disconnect many times, I believe there is issue with the DSP hardware. I can confirm this is an hardware problem.
Hi Guys,
I coordinate with Yeastar support regarding this issue and they confirmed that the problem is indeed the onboard DSP Module of the device.
Thanks.
Unified Communications
