SIP Videocall To DS-KB8113-IME1(B)

Joshua Parker Ruehlig

Young grasshopper
Jul 22, 2016
31
0
Hello,
I was able to connect this doorbell directly to my Asterisk PBX; I do not own an indoor station. Upon a doorbell button press, I successfully get a video call, with video/audio preview only my Linphone App.

Now, I was hoping to be able to videocall the doorbell from my Linphone App, and view the camera feed with 2-way audio. Calling the doorbell does work, the doorbell automatically answers and I can use 2-way audio. But no video is presented just a black screen. I'm not sure if this use case (videocall from phone to doorbell) is expected to work?
 
asterisk can't decode video from one format to another. Only one video codec must be agreed on on each side
H265 - ok

96 this is the transmission of keystrokes in inband format. Not dtmf
 
Ok, I will try to figure out how to use wireshark and will post the logs in a 1-2 days.

I have dmtf_mode = info (SIP INFO), which I think means it is not inband.
Also I only have ulaw, alaw, and h264 enabled in Asterisk. Linphone will provide more codecs, but I believe the codecs are paired down before the actual RTP packets are sent.

I was referring to the line below, with type 96. There are hundreds of them that are received by Asterisk, but never sent out.
If the same doorbell calls my phone, via doorbell button, the packets with type 96 are received, then properly sent to my Linphone App.

res_rtp_asterisk.c: Got RTP packet from 192.168.3.92:9856 (type 96, seq 019741, ts 1304229808, len 000280)

My current theory is Asterisk has a bug related to recvonly / sendonly, where it thinks that channel (video) is on hold. I need to analyze the logs between a working vs non-working call and see if the recvonly / sendonly lines make sense, or if Asterisk is making a mistake when the Linphone App calls the doorbell.