Linphone debugging information

Source: Internet
Author: User
Tags linphone

[Email protected]: ~ Linphonec-v-D 6
Info: No logfile, logging to stdout
Ortp-message-oRTP-0.20.0 initialized.
Ortp-message-assigning PCMU/8000 payload type number 0
Ortp-message-assigning GSM/8000 payload type Number 3
Ortp-message-assigning PCMA/8000 payload type number 8
Ortp-message-assigning speex/8000 payload type number 110
Ortp-message-assigning speex/16000 payload type Number 111
Ortp-message-assigning speex/32000 payload type number 112
Ortp-message-assigning telephone-event/8000 payload type number 101
Ortp-message-assigning g722/8000 payload type Number 9
Ortp-message-assigning h263/90000 payload type number 34
Ortp-message-assigning theora/90000 payload type number 97
Ortp-message-assigning H263-1998/90000 payload type number 98
Ortp-message-assigning MP4V-ES/90000 payload type number 99
Ortp-message-assigning h264/90000 payload type Number 102
Ortp-message-assigning Vp8/90000 payload type number 103
Ortp-message-assigning X-snow/90000 payload type number 96
Ortp-message-assigning ilbc/8000 payload type number 100
Ortp-message-assigning AMR/8000 payload type Number 104
Ortp-message-assigning AMR-WB/16000 payload type Number 105
Ortp-message-assigning 1015/8000 payload type number 106
Ortp-message-assigning G726-16/8000 payload type number 107
Ortp-message-assigning G726-24/8000 payload type number 108
Ortp-message-assigning G726-32/8000 payload type Number 109
Ortp-message-assigning G726-40/8000 payload type Number 113
Ortp-message-assigning AAL2-G726-16/8000 payload type number 114
Ortp-message-assigning AAL2-G726-24/8000 payload type Number 115
Ortp-message-assigning AAL2-G726-32/8000 payload type Number 116
Ortp-message-assigning AAL2-G726-40/8000 payload type number 117
Ortp-message-assigning Silk/8000 payload type number 118
Ortp-message-assigning Silk/12000 payload type number 119
Ortp-message-assigning Silk/16000 payload type Number 120
Ortp-message-assigning Silk/24000 payload type Number 121
Ortp-message-assigning g729/8000 payload type number 18
Ortp-message-Mediastreamer2 2.8.2 (GIT: Unknown) starting.
Ortp-message-registering all Soundcard handlers
Ortp-message-card 'alsa: Default device' added
ALSA lib Conf. C: 4630 :( snd_config_expand) unknown parameters 0
ALSA lib control. C: 882 :( snd_ctl_open_noupdate) invalid CTL default: 0
Ortp-warning-cocould not attach mixer to card: invalid argument
Ortp-message-card 'alsa: pcm051 audio 'added
ALSA lib Conf. C: 4630 :( snd_config_expand) unknown parameters 1
ALSA lib control. C: 882 :( snd_ctl_open_noupdate) invalid CTL default: 1
Ortp-warning-cocould not attach mixer to card: invalid argument
ALSA lib pcm_dmix.c: 1018 :( snd_pcm_dmix_open) unable to open slave
Ortp-message-card 'alsa: USB 2.0 Pc camera 'added
Ortp-message-card 'oss:/dev/DSPs 'added
Ortp-message-card 'oss:/dev/dsp1 'added
Ortp-message-registering all webcam handlers
Ortp-message-Webcam v4l2:/dev/video0 added
Ortp-message-Webcam staticimage: static picture added
Ortp-message-loading MS plugins FRON [/home/elinux/Linphone/armbuild/lib/mediastreamer/plugins]
Ortp-message-cannot open directory/home/elinux/Linphone/armbuild/lib/mediastreamer/plugins: no such file or directory
Ortp-message-ms_init () done
Ortp-message-cannot open directory/home/elinux/Linphone/armbuild/lib/liblinphone/plugins: no such file or directory
Ortp-message-linphone_core_set_playback_gain_db (): no active call.
Ortp-message-adding new codec L16/44100 with fmtp
Ortp-message-getaddrinfo returned the following addresses:
The ortp-message-0.0.0.0 port 5060
Ortp-error-exosip: cannot bind socket node: 0.0.0.0 family: 2 address already in use
Ortp-error-exosip: cannot bind on port: 5060
Ortp-warning-cocould not start UDP Transport on port 5060, maybe this port is already used.
Warning: cocould not start UDP Transport on port 5060, maybe this port is already used.
Ready
Linphonec> ortp-message-new local IP address is 192.168.18.202
Ortp-message-network state is now [Up]
Ortp-message-getaddrinfo returned the following addresses:
The ortp-message-0.0.0.0 port 5060
Ortp-error-exosip: cannot bind socket node: 0.0.0.0 family: 2 address already in use
Ortp-error-exosip: cannot bind on port: 5060
Ortp-warning-cocould not start UDP Transport on port 5060, maybe this port is already used.
Warning: cocould not start UDP Transport on port 5060, maybe this port is already used.
Linphonec> ortp-message-setting video size 352x288
Ortp-message-driver is uvcvideo
Ortp-message-v4l2: Trying 352x288
Ortp-message-v4lv2: yuv420p choosen
Ortp-message-size of webcam delivered pictures is 352x288
Ortp-message-video_out_init
Ortp-message-video size set to 352x288
Ortp-message-video size set to 352x288
Ortp-message-ms_filter_link: msv4l2capture: 0x0000e8, 0 --> mspixconv: 0x49388, 0
Ortp-message-ms_filter_link: mspixconv: 0x49388, 0 --> msvideoout: 0x4f970, 0
Ortp-message-Initialize SDL video
Ortp-message-msv4l2_thread (starting)
Ortp-message-V4L2 video capture started.
Ortp-message-video driver: fbcon
Ortp-message-HW surface available (2400 K memory)
Ortp-message-SDL surface created in hardware
Ortp-message-number of planes: 3
Ortp-message-352 x 288 YUV overlay created: hw_accel = 0, pitches = 352,176,176
Ortp-message-planes = 0x46d00008 0x46d18c08 0x46d1ef08 101376 25344
Ortp-warning-SDL window show/hide not implemented
Ortp-warning-sdl_get_native_window_id not implemented
Ortp-message-captured mean FPS = 26.164288, expected = 29.969999
Ortp-message-captured mean FPS = 27.875790, expected = 29.969999
Ortp-message-captured mean FPS = 23.137396, expected = 29.969999
Ortp-message-captured mean FPS = 26.512047, expected = 29.969999
Ortp-message-captured mean FPS = 26.777443, expected = 29.969999
Ortp-message-captured mean FPS = 22.266455, expected = 29.969999
Ortp-message-captured mean FPS = 24.645529, expected = 29.969999
Ortp-message-captured mean FPS = 26.164782, expected = 29.969999
Ortp-message-captured mean FPS = 21.469557, expected = 29.969999
Ortp-message-captured mean FPS = 23.748100, expected = 29.969999
Ortp-message-captured mean FPS = 25.813494, expected = 29.969999
Ortp-message-captured mean FPS = 27.365429, expected = 29.969999
Ortp-message-captured mean FPS = 21.513132, expected = 29.969999
Ortp-message-captured mean FPS = 23.089275, expected = 29.969999
Ortp-message-captured mean FPS = 25.596851, expected = 29.969999
Ortp-message-captured mean FPS = 26.847204, expected = 29.969999

Linphonec> ortp-message-captured mean FPS = 23.517830, expected = 29.969999
Ortp-message-captured mean FPS = 25.243301, expected = 29.969999
Ortp-message-captured mean FPS = 26.842932, expected = 29.969999
Ortp-message-captured mean FPS = 27.930450, expected = 29.969999
Ortp-message-captured mean FPS = 23.791159, expected = 29.969999
Linphonec> ortp-message-captured mean FPS = 25.035530, expected = 29.969999
Ortp-message-captured mean FPS = 26.779442, expected = 29.969999
Ortp-message-captured mean FPS = 24.263119, expected = 29.969999
Ortp-message-captured mean FPS = 24.977747, expected = 29.969999
Ortp-message-captured mean FPS = 26.210056, expected = 29.969999
Ortp-message-captured mean FPS = 22.829041, expected = 29.969999
Ortp-message-captured mean FPS = 20.100039, expected = 29.969999
Ortp-message-captured mean FPS = 26.524433, expected = 29.969999
Ortp-message-captured mean FPS = 26.210079, expected = 29.969999
Ortp-message-captured mean FPS = 22.297983, expected = 29.969999
Ortp-message-captured mean FPS = 24.536579, expected = 29.969999
Ortp-message-captured mean FPS = 26.067451, expected = 29.969999
Ortp-message-captured mean FPS = 26.977785, expected = 29.969999
^ Cterminating...
A ortp-message-msv4l2_thread exited.
Ortp-message-msv4l2 thread has joined.
Ortp-message-ms_filter_unlink: msv4l2capture: 0x0000e8, 0 --> mspixconv: 0x49388, 0
Ortp-message-ms_filter_unlink: mspixconv: 0x49388, 0 --> msvideoout: 0x4f970, 0
Ortp-message-freeing overlay
Ortp-message-freeing Surface
Ortp-message-WD Fred
Ortp-warning-SDL window show/hide not implemented
Ortp-message-video msticker thread exiting

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.