keehub
commented
2 years ago 2022-04-13 17:19:23.037 [http-nio-18080-exec-9] INFO c.g.iot.vmp.gb28181.transmit.cmd.impl.SIPCommander:357 - 34020000001320000003_34020000001320000003 分配的ZLM为: wvp-media-id [【公网IP】:43260]
2022-04-13 17:19:23.166 [http-nio-18080-exec-9] DEBUG druid.sql.Statement:134 - {conn-10010, pstmt-20033} created. insert into log ( name, type, uri, address, result, timing, username, createTime) values ('开始点播', 'GET', '/api/play/start/34020000001320000003/34020000001320000003', '43.250.106.176', '200 OK', 1454, 'admin', '2022-04-13 17:19:23')
2022-04-13 17:19:23.167 [http-nio-18080-exec-9] DEBUG druid.sql.Statement:134 - {conn-10010, pstmt-20033} Parameters : []
2022-04-13 17:19:23.167 [http-nio-18080-exec-9] DEBUG druid.sql.Statement:134 - {conn-10010, pstmt-20033} Types : []
2022-04-13 17:19:23.169 [http-nio-18080-exec-9] DEBUG druid.sql.Statement:134 - {conn-10010, pstmt-20033} executed. 2.146987 millis. insert into log ( name, type, uri, address, result, timing, username, createTime) values ('开始点播', 'GET', '/api/play/start/34020000001320000003/34020000001320000003', '43.250.106.176', '200 OK', 1454, 'admin', '2022-04-13 17:19:23')
2022-04-13 17:19:23.169 [http-nio-18080-exec-9] DEBUG druid.sql.Statement:134 - {conn-10010, pstmt-20033} closed
2022-04-13 17:19:23.230 [wvp-5] INFO c.g.i.v.g.t.e.r.impl.InviteResponseProcessor:84 - [回复ack] sip:34020000001320000003@175.9.140.239:60735-> 175.9.140.239:60735
2022-04-13 17:19:23.714 [wvp-6] INFO c.g.i.v.g.t.event.request.impl.ByeRequestProcessor:89 - 收到bye, [34020000001320000003/34020000002000000001]
2022-04-13 17:19:23.716 [wvp-6] DEBUG druid.sql.Statement:134 - {conn-10010, pstmt-20034} created. SELECT * FROM device_channel WHERE channelId=?
2022-04-13 17:19:23.716 [wvp-6] DEBUG druid.sql.Statement:134 - {conn-10010, pstmt-20034} Parameters : [34020000001320000003]
2022-04-13 17:19:23.716 [wvp-6] DEBUG druid.sql.Statement:134 - {conn-10010, pstmt-20034} Types : [VARCHAR]
2022-04-13 17:19:23.718 [wvp-6] DEBUG druid.sql.Statement:134 - {conn-10010, pstmt-20034} executed. 1.238913 millis. SELECT * FROM device_channel WHERE channelId=?
2022-04-13 17:19:23.719 [wvp-6] DEBUG druid.sql.Statement:134 - {conn-10010, pstmt-20034} closed
2022-04-13 17:19:23.719 [wvp-6] DEBUG druid.sql.Statement:134 - {conn-10010, pstmt-20035} created. SELECT * FROM device WHERE deviceId = ?
2022-04-13 17:19:23.719 [wvp-6] DEBUG druid.sql.Statement:134 - {conn-10010, pstmt-20035} Parameters : [34020000001320000003]
2022-04-13 17:19:23.720 [wvp-6] DEBUG druid.sql.Statement:134 - {conn-10010, pstmt-20035} Types : [VARCHAR]
2022-04-13 17:19:23.720 [wvp-6] DEBUG druid.sql.Statement:134 - {conn-10010, pstmt-20035} executed. 0.911392 millis. SELECT * FROM device WHERE deviceId = ?
2022-04-13 17:19:23.721 [wvp-6] DEBUG druid.sql.Statement:134 - {conn-10010, pstmt-20035} closed
2022-04-13 17:19:23.722 [wvp-6] DEBUG druid.sql.Statement:134 - {conn-10010, pstmt-20036} created. UPDATE device_channel SET streamId=null WHERE deviceId=? AND channelId=?
2022-04-13 17:19:23.722 [wvp-6] DEBUG druid.sql.Statement:134 - {conn-10010, pstmt-20036} Parameters : [34020000001320000003, 34020000002000000001]
2022-04-13 17:19:23.722 [wvp-6] DEBUG druid.sql.Statement:134 - {conn-10010, pstmt-20036} Types : [VARCHAR, VARCHAR]
2022-04-13 17:19:23.723 [wvp-6] DEBUG druid.sql.Statement:134 - {conn-10010, pstmt-20036} executed. 0.839975 millis. UPDATE device_channel SET streamId=null WHERE deviceId=? AND channelId=?
2022-04-13 17:19:23.723 [wvp-6] DEBUG druid.sql.Statement:134 - {conn-10010, pstmt-20036} closed
2022-04-13 17:19:41.035 [Timer-1] WARN com.genersoft.iot.vmp.service.impl.PlayServiceImpl:244 - 设备点播超时，deviceId：34020000001320000003 ，channelId：34020000001320000003
javax.sip.SipException: Cannot find listening point for transport TCP
at gov.nist.javax.sip.stack.SIPDialog.createRequest(SIPDialog.java:2472)
at gov.nist.javax.sip.stack.SIPDialog.createRequest(SIPDialog.java:2403)
at com.genersoft.iot.vmp.gb28181.transmit.cmd.impl.SIPCommander.streamByeCmd(SIPCommander.java:733)
at com.genersoft.iot.vmp.gb28181.transmit.cmd.impl.SIPCommander.streamByeCmd(SIPCommander.java:677)
at com.genersoft.iot.vmp.service.impl.PlayServiceImpl$1.run(PlayServiceImpl.java:250)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
648540858
slxsyxx
tingmag
zhangdongshun
rainingshining
JinruiWang
realbillwong
HogwartsRico
MrLiuFang
lixiansky
penghui-luna
Zhu168888rui
hnzmxy
dcq123
wildwindyevan
hejinenPrivate
loveworldlovesky
zhuuvzhi
xiaoxuanshiya
yogo-zhangyingzhe
zh176
JQYXQ
9loki
durantgod
Farrahchen
scdn
willianfu
hhhuaang
answer666
Kkmdfuck
wo8335224
yangjun7948
这个地方不知道为什么WVP的代码只接收rtsp类型的on_stream_changed事件。我注释掉之后，就可以接收到国标流RTP的事件了
CXY001
ztluxi
一. 部署环境
二. 部署方式
ZLMediaKit配置文件，点击查看 (/root/zlmediakit/config.ini)
```ini ; auto-generated by mINI class { [api] apiDebug=0 defaultSnap=./www/logo.png secret=035c73f7-bb6b-4889-a715-d9eb2d1925cc snapRoot=./www/snap/ [cluster] origin_url= timeout_sec=15 [ffmpeg] bin=/usr/bin/ffmpeg cmd=%s -fflags nobuffer -i %s -c:a aac -strict -2 -ar 44100 -ab 48k -c:v libx264 -f flv %s log=./ffmpeg/ffmpeg.log restart_sec=0 snap=%s -i %s -y -f mjpeg -t 0.001 %s [general] addMuteAudio=1 continue_push_ms=3000 enableVhost=0 enable_audio=1 flowThreshold=1024 fmp4_demand=0 hls_demand=0 maxStreamWaitMS=15000 mediaServerId=wvp-media-id mergeWriteMS=0 modifyStamp=0 publishToHls=1 publishToMP4=0 resetWhenRePlay=1 rtmp_demand=0 rtsp_demand=0 streamNoneReaderDelayMS=10000 ts_demand=0 unready_frame_cache=100 wait_add_track_ms=3000 wait_track_ready_ms=3000 [hls] broadcastRecordTs=0 deleteDelaySec=0 fileBufSize=65536 filePath=./www segDur=2 segNum=3 segRetain=5 [hook] admin_params=secret=035c73f7-bb6b-4889-a715-d9eb2d1925cc alive_interval=10.0 enable=1 on_flow_report= on_http_access= on_play=http://192.168.0.57:18080/index/hook/on_play on_publish=http://192.168.0.57:18080/index/hook/on_publish on_record_mp4=http://127.0.0.1:18081/api/record/on_record_mp4 on_record_ts= on_rtsp_auth= on_rtsp_realm= on_server_keepalive=http://192.168.0.57:18080/index/hook/on_server_keepalive on_server_started=http://192.168.0.57:18080/index/hook/on_server_started on_shell_login=http://192.168.0.57:18080/index/hook/on_shell_login on_stream_changed=http://192.168.0.57:18080/index/hook/on_stream_changed on_stream_none_reader=http://192.168.0.57:18080/index/hook/on_stream_none_reader on_stream_not_found=http://192.168.0.57:18080/index/hook/on_stream_not_found timeoutSec=20 [http] charSet=utf-8 dirMenu=1 forbidCacheSuffix= keepAliveSecond=30 maxReqSize=40960 notFound=您访问的资源不存在！
wvp-GB28181-pro 配置文件，点击查看 (application.yml，无关敏感配置用***代替了)
```yml spring: # [可选]上传文件大小限制 servlet: multipart: max-file-size: 10MB max-request-size: 100MB # REDIS数据库配置 redis: # [必须修改] Redis服务器IP, REDIS安装在本机的,使用127.0.0.1 host: *** # [必须修改] 端口号 port: *** # [可选] 数据库 DB database: *** # [可选] 访问密码,若你的redis服务器没有设置密码，就不需要用密码去连接 password: # [可选] 超时时间 timeout: 10000 # [可选] jdbc数据库配置, 项目使用sqlite作为数据库，一般不需要配置 # mysql数据源 datasource: type: com.alibaba.druid.pool.DruidDataSource driver-class-name: com.mysql.cj.jdbc.Driver url: jdbc:mysql://***/wvp?useUnicode=true&characterEncoding=UTF8&rewriteBatchedStatements=true&serverTimezone=PRC&useSSL=false username: *** password: *** druid: initialSize: 10 # 连接池初始化连接数 maxActive: 200 # 连接池最大连接数 minIdle: 5 # 连接池最小空闲连接数 maxWait: 60000 # 获取连接时最大等待时间，单位毫秒。配置了maxWait之后，缺省启用公平锁，并发效率会有所下降，如果需要可以通过配置useUnfairLock属性为true使用非公平锁。 keepAlive: true # 连接池中的minIdle数量以内的连接，空闲时间超过minEvictableIdleTimeMillis，则会执行keepAlive操作。 validationQuery: select 1 # 检测连接是否有效sql，要求是查询语句，常用select 'x'。如果validationQuery为null，testOnBorrow、testOnReturn、testWhileIdle都不会起作用。 testWhileIdle: true # 建议配置为true，不影响性能，并且保证安全性。申请连接的时候检测，如果空闲时间大于timeBetweenEvictionRunsMillis，执行validationQuery检测连接是否有效。 testOnBorrow: false # 申请连接时执行validationQuery检测连接是否有效，做了这个配置会降低性能。 testOnReturn: false # 归还连接时执行validationQuery检测连接是否有效，做了这个配置会降低性能。 poolPreparedStatements: false # 是否開啟PSCache，並且指定每個連線上PSCache的大小 timeBetweenEvictionRunsMillis: 60000 # 配置間隔多久才進行一次檢測，檢測需要關閉的空閒連線，單位是毫秒 minEvictableIdleTimeMillis: 300000 # 配置一個連線在池中最小生存的時間，單位是毫秒 filters: stat,wall,slf4j # 配置监控统计拦截的filters，监控统计用的filter:sta, 日志用的filter:log4j, 防御sql注入的filter:wall useGlobalDataSourceStat: true # 合并多个DruidDataSource的监控数据 # 通过connectProperties属性来打开mergeSql功能；慢SQL记录 connectionProperties: druid.stat.mergeSql=true;druid.stat.slowSqlMillis=1000 #stat-view-servlet.url-pattern: /admin/druid/* #[可选] WVP监听的HTTP端口, 网页和接口调用都是这个端口 server: port: 18080 # 作为28181服务器的配置 sip: # [必须修改] 本机的IP ip: 192.168.0.57 # [可选] 28181服务监听的端口 port: 5060 # 根据国标6.1.2中规定，domain宜采用ID统一编码的前十位编码。国标附录D中定义前8位为中心编码（由省级、市级、区级、基层编号组成，参照GB/T 2260-2007） # 后两位为行业编码，定义参照附录D.3 # 3701020049标识山东济南历下区 信息行业接入 # [可选] domain: 3402000000 # [可选] id: 34020000002000000001 # [可选] 默认设备认证密码，后续扩展使用设备单独密码, 移除密码将不进行校验 password: 12345678 #zlm 默认服务器配置 media: id: wvp-media-id # [必须修改] zlm服务器的内网IP ip: 192.168.0.57 # [必须修改] zlm服务器的http.port http-port: 8001 # [可选] zlm服务器的hook.admin_params=secret secret: 035c73f7-bb6b-4889-a715-d9eb2d1925cc # 启用多端口模式, 多端口模式使用端口区分每路流，兼容性更好。 单端口使用流的ssrc区分， 点播超时建议使用多端口测试 rtp: # [可选] 是否启用多端口模式, 开启后会在portRange范围内选择端口用于媒体流传输 enable: true # [可选] 在此范围内选择端口用于媒体流传输, 必须提前在zlm上配置该属性，不然自动配置此属性可能不成功 port-range: 30000,30500 # 端口范围 # [可选] 国标级联在此范围内选择端口发送媒体流, send-port-range: 30000,30500 # 端口范围 # 录像辅助服务， 部署此服务可以实现zlm录像的管理与下载， 0 表示不使用 record-assist-port: 18081 # [可选] 日志配置, 一般不需要改 logging: config: classpath:logback-spring-local.xml # 版本信息， 不需修改 version: version: "@project.version@" description: "@project.description@" artifact-id: "@project.artifactId@" ```配置图片 (https://user-images.githubusercontent.com/41461205/163112767-ca696c6e-dab3-4876-8a6c-5efbb846cc26.png)
三. 界面截图，日志截图
wvp-GB28181-pro日志截图 (https://user-images.githubusercontent.com/41461205/163119165-4462fbef-77b1-44de-ad43-26a3da7f05cc.png)
wvp-GB28181-pro媒体节点 (https://user-images.githubusercontent.com/41461205/163115450-4105bee5-3075-4c58-b9ae-d3baea7e2c13.png)
wvp-GB28181-pro点播收流，超时界面 (https://user-images.githubusercontent.com/41461205/163115957-9236ba52-afd2-4986-836d-1986ede6e3db.png)