I have an rtp stream that I can capture and see with gstreamer:
gst-launch-1.0 udpsrc caps = "application/x-rtp, media=(string)video, clock-rate=(int)90000, encoding-name=(string)VP8, payload=(int)96" port=10035 ! rtpvp8depay ! decodebin ! xvimagesink sync=false
I would like to build an sdp file for VLC app to see the same video. I tried this, but it doesn't do the job:
v=0
o=- 0 0 IN IP4 127.0.0.1
s=No Name
c=IN IP4 127.0.0.1
t=0 0
m=video 10035 RTP/AVP 96
b=AS:1000
a=rtpmap:120 VP8/90000
a=fmtp:96 packetization-mode=1
v=0
o=- 0 0 IN IP4 127.0.0.1
s=No Name
c=IN IP4 127.0.0.1
t=0 0
m=video 10035 RTP/AVP 96
b=AS:1000
a=rtpmap:**120** VP8/90000
a=fmtp:96 packetization-mode=1
i think is -> a=rtpmap:96 VP8/90000
Related
In my Ubuntu 18.04, I am receiving video from an IP camera and transmitting the video to a rtsp server using gscam in ROS melodic. Here is the code for the gscam nodelet in the launch file:
<node pkg="nodelet" type="nodelet"
name="nodelet_manager" args="manager"
output="screen"/>
<node pkg="nodelet" type="nodelet"
name="$(arg cam_name)"
args="load gscam/GSCamNodelet nodelet_manager"
output="screen">
<param name="camera_name" value="$(arg cam_name)"/>
<param name="camera_info_url" value="$(arg camera_info_url)"/>
<param name="frame_id" value="$(arg cam_name)"/>
<param name="sync_sink" value="true" />
<param name="use_gst_timestamps" value="true" />
<param name="gst_clock_type" value="0" /> <!-- GST_CLOCK_TYPE_REALTIME -->
<param name="reopen_on_eof" value="true" />
<!-- choose appropriate gstreamer pipeline -->
<param name="gscam_config"
value="gst-launch-1.0 rtspsrc location=$(arg rtsp_stream) latency=$(arg latency) ! decodebin
! videoconvert ! video/x-raw,format=RGB" />
<remap from="camera/image_raw" to="$(arg cam_name)/image_raw" />
</node>
Now, I would like to measure the received and dropped frame rate from the camera and from my research I have found that there is a gstreamer element fpsdisplay for this purpose.
If I try this launch operation from console :gst-launch-1.0 rtspsrc location=rtsp://192.168.17.168:553/stream latency=400 ! decodebin ! videoconvert ! fpsdisplaysink, then it displays the frame rate on a pooped up window but if I want to use fpsdisplay in the pipeline in the above gscam nodelet in the launch file like this:
<param name="gscam_config"
value="gst-launch-1.0 rtspsrc location=$(arg rtsp_stream) latency=$(arg latency) ! fpsdisplaysink ! decodebin ! videoconvert !
video/x-raw,format=RGB" />
then it does not work, no topics are published.
Through the documentations, I could not understand how to combine fpsdisplaysink in the gscam pipeline.
How then this element has to be combined with the pipeline?
Or, if it is not clearly possible to get the received frame rate through fpsdisplaysink then how it can be done?
My main goal is not to show the fps on the screen but to get those values and then publish them as a ROS topic.
Thanks!
Getting TLS connect() error: [code=70006]: Not found (PJ_ENOTFOUND) with pjsua(2) with my program and pjsip integrated. The error does not seem to describe what is actually wrong. What's actually going on?? What's not found?
The following is true:
Same code works on Windows
Same program will work on the Mac developed (both El Capitan and Mojave dev machines)
Same program throws the full error below on another Mac when packaged in single .app
Server (songbird.sip.server, not actual server name) is reachable, Asterisk PBX, does not show any connexion attempts in the SIP debug, can ping from device
No firewall is active on the Mac devices
2019-09-26, 13:59:38.184699: <debug> (0x0000700002164000) [PJSIP] pjsua_acc.c Acc 0: setting registration..
2019-09-26, 13:59:38.186322: <debug> (0x0000700002164000) [PJSIP] tlsc0x7f90d706d428 TLS client transport created
2019-09-26, 13:59:38.186473: <debug> (0x0000700002164000) [PJSIP] tlsc0x7f90d706d428 TLS transport 192.168.86.95:62615 is connecting to songbird.sip.server:5061...
2019-09-26, 13:59:38.186550: <debug> (0x0000700002164000) [PJSIP] pjsua_acc.c Contact for acc 0 updated: <sip:2e8f04b6-dc64-4fdf-8e8b-5e034246df4d#192.168.86.95:62615;transport=TLS;ob>;reg-id=1;+sip.instance="<urn:uuid:00000000-0000-0000-0000-000062a2dee5>"
2019-09-26, 13:59:38.188984: <debug> (0x0000700002164000) [PJSIP] pjsua_core.c TX 774 bytes Request msg REGISTER/cseq=36644 (tdta0x7f90d58018a8) to TLS www.xxx.yyy.zzz:5061:
REGISTER sip:songbird.sip.server SIP/2.0
Via: SIP/2.0/TLS 192.168.86.95:62615;rport;branch=z9hG4bKPjB75FE879-DFF6-4FC2-AA8A-C1A89D5E2496;alias
Route: <sip:songbird.sip.server;transport=tls;lr>
Max-Forwards: 70
From: <sip:2e8f04b6-dc64-4fdf-8e8b-5e034246df4d#songbird.sip.server>;tag=9FBBCCE5-7560-4737-B33E-4FFEE66BEC8C
To: <sip:2e8f04b6-dc64-4fdf-8e8b-5e034246df4d#songbird.sip.server>
Call-ID: C8D621A4-E35F-4D18-9373-9BC10CE1DC02
CSeq: 36644 REGISTER
Supported: outbound, path
Contact: <sip:2e8f04b6-dc64-4fdf-8e8b-5e034246df4d#192.168.86.95:62615;transport=TLS;ob>;reg-id=1;+sip.instance="<urn:uuid:00000000-0000-0000-0000-000062a2dee5>"
Expires: 300
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Content-Length: 0
--end msg--
2019-09-26, 13:59:38.189086: <debug> (0x0000700002164000) [PJSIP] pjsua_acc.c Acc 0: Registration sent
2019-09-26, 13:59:38.201446: <info> (0x0000700002164000) [PJSIP] tlsc0x7f90d706d428 TLS connect() error: [code=70006]: Not found (PJ_ENOTFOUND)
2019-09-26, 13:59:38.201536: <info> (0x0000700002164000) [PJSIP] tsx0x7f90d78038a8 Temporary failure in sending Request msg REGISTER/cseq=36644 (tdta0x7f90d58018a8), will try next server: Not found (PJ_ENOTFOUND)
2019-09-26, 13:59:38.201614: <debug> (0x0000700002164000) [PJSIP] pjsua_core.c TX 774 bytes Request msg REGISTER/cseq=36644 (tdta0x7f90d58018a8) to TLS www.xxx.yyy.zzz:5061:
REGISTER sip:songbird.sip.server SIP/2.0
Via: SIP/2.0/TLS 192.168.86.95:62615;rport;branch=z9hG4bKPjB75FE879-DFF6-4FC2-AA8A-C1A89D5E2496;alias
Route: <sip:songbird.sip.server;transport=tls;lr>
Max-Forwards: 70
From: <sip:2e8f04b6-dc64-4fdf-8e8b-5e034246df4d#songbird.sip.server>;tag=9FBBCCE5-7560-4737-B33E-4FFEE66BEC8C
To: <sip:2e8f04b6-dc64-4fdf-8e8b-5e034246df4d#songbird.sip.server>
Call-ID: C8D621A4-E35F-4D18-9373-9BC10CE1DC02
CSeq: 36644 REGISTER
Supported: outbound, path
Contact: <sip:2e8f04b6-dc64-4fdf-8e8b-5e034246df4d#192.168.86.95:62615;transport=TLS;ob>;reg-id=1;+sip.instance="<urn:uuid:00000000-0000-0000-0000-000062a2dee5>"
Expires: 300
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Content-Length: 0
--end msg--
2019-09-26, 13:59:38.201729: <debug> (0x0000700002164000) [PJSIP] pjsua_acc.c Disconnected notification for transport tlsc0x7f90d706d428
2019-09-26, 13:59:38.201781: <debug> (0x0000700002164000) [PJSIP] sip_transport.c Transport tlsc0x7f90d706d428 shutting down, force=0
2019-09-26, 13:59:38.201839: <debug> (0x0000700002164000) [PJSIP] pjsua_acc.c Scheduling re-registration retry for acc 0 in 309 seconds..
2019-09-26, 13:59:38.201891: <info> (0x0000700002164000) [PJSIP] tsx0x7f90d78038a8 Failed to send Request msg REGISTER/cseq=36644 (tdta0x7f90d58018a8)! err=70006 (Not found (PJ_ENOTFOUND))
2019-09-26, 13:59:38.201928: <warn> (0x0000700002164000) [PJSIP] pjsua_acc.c SIP registration failed, status=503 (Not found (PJ_ENOTFOUND))
2019-09-26, 13:59:38.201957: <debug> (0x0000700002164000) [PJSIP] pjsua_acc.c Scheduling re-registration retry for acc 0 in 306 seconds..
2019-09-26, 13:59:38.202053: <debug> (0x0000700002164000) [PJSIP] tlsc0x7f90d706d428 TLS transport destroyed with reason 70006: Not found (PJ_ENOTFOUND)
Are you using gnuTLS for your TLS backend? If so, the error correspond to GNUTLS_E_NO_CERTIFICATE_FOUND. Perhaps you could check your cerificate setup?
I have an ova template. 6 network interfaces are defined in it, named net0, net1, net2, net3, net4, net5. The type of all of them is VMXNET3.
When I deploy this ova template to ESXi6.0/5.5 server, one of steps is to configure the mapping from network name (net0, net1, ..., net5) to existing networks on ESXi server (like vlan500, vlan501, ..., vlan505), like:
net0 -> vlan500
net1 -> vlan501
... ...
net5 -> vlan505
After the VM instance powers on, in the VM instance, there are 6 eth network interfaces: eth0, eth1, ..., eth5.
I expect the order of ethX inside VM should be same as the order of adapters outside VM like:
eth0 -> net0 -> vlan500
eth1 -> net1 -> vlan501
... ...
eth5 -> net5 -> vlan505
But I find I get this by checking the MAC addresses:
eth0 -> net0 -> vlan500
eth1 -> net4 -> vlan504 <= mismatch
eth2 -> net1 -> vlan501 <= mismatch
eth3 -> net5 -> vlan505 <= mismatch
eth4 -> net2 -> vlan502 <= mismatch
eth5 -> net3 -> vlan503 <= mismatch
Can you please help to point out how to resolve this issue?
Thanks in advance!
The ovf xml is like following:
125 <Item>
126 <rasd:AddressOnParent>7</rasd:AddressOnParent>
127 <rasd:AutomaticAllocation>true</rasd:AutomaticAllocation>
128 <rasd:Connection>NET0</rasd:Connection>
129 <rasd:Description>VmxNet3 ethernet adapter on "NET0"</rasd:Description>
130 <rasd:ElementName>Ethernet 1</rasd:ElementName>
131 <rasd:InstanceID>10</rasd:InstanceID>
132 <rasd:ResourceSubType>VmxNet3</rasd:ResourceSubType>
133 <rasd:ResourceType>10</rasd:ResourceType>
134 <vmw:Config ovf:required="false" vmw:key="slotInfo.pciSlotNumber" vmw:value="32" />
135 <vmw:Config ovf:required="false" vmw:key="wakeOnLanEnabled" vmw:value="true" />
136 </Item>
137 <Item>
138 <rasd:AddressOnParent>8</rasd:AddressOnParent>
139 <rasd:AutomaticAllocation>true</rasd:AutomaticAllocation>
140 <rasd:Connection>NET1</rasd:Connection>
141 <rasd:Description>VmxNet3 ethernet adapter on "NET1"</rasd:Description>
142 <rasd:ElementName>Ethernet 2</rasd:ElementName>
143 <rasd:InstanceID>11</rasd:InstanceID>
144 <rasd:ResourceSubType>VmxNet3</rasd:ResourceSubType>
145 <rasd:ResourceType>10</rasd:ResourceType>
146 <vmw:Config ovf:required="false" vmw:key="slotInfo.pciSlotNumber" vmw:value="33" />
147 <vmw:Config ovf:required="false" vmw:key="wakeOnLanEnabled" vmw:value="true" />
148 </Item>
149 <Item>
150 <rasd:AddressOnParent>9</rasd:AddressOnParent>
151 <rasd:AutomaticAllocation>true</rasd:AutomaticAllocation>
152 <rasd:Connection>NET2</rasd:Connection>
153 <rasd:Description>VmxNet3 ethernet adapter on "NET2"</rasd:Description>
154 <rasd:ElementName>Ethernet 3</rasd:ElementName>
155 <rasd:InstanceID>12</rasd:InstanceID>
156 <rasd:ResourceSubType>VmxNet3</rasd:ResourceSubType>
157 <rasd:ResourceType>10</rasd:ResourceType>
158 <vmw:Config ovf:required="false" vmw:key="slotInfo.pciSlotNumber" vmw:value="34" />
159 <vmw:Config ovf:required="false" vmw:key="wakeOnLanEnabled" vmw:value="true" />
160 </Item>
161 <Item>
162 <rasd:AddressOnParent>10</rasd:AddressOnParent>
163 <rasd:AutomaticAllocation>true</rasd:AutomaticAllocation>
164 <rasd:Connection>NET3</rasd:Connection>
165 <rasd:Description>VmxNet3 ethernet adapter on "NET3"</rasd:Description>
166 <rasd:ElementName>Ethernet 4</rasd:ElementName>
167 <rasd:InstanceID>13</rasd:InstanceID>
168 <rasd:ResourceSubType>VmxNet3</rasd:ResourceSubType>
169 <rasd:ResourceType>10</rasd:ResourceType>
170 <vmw:Config ovf:required="false" vmw:key="slotInfo.pciSlotNumber" vmw:value="35" />
171 <vmw:Config ovf:required="false" vmw:key="wakeOnLanEnabled" vmw:value="true" />
172 </Item>
173 <Item>
174 <rasd:AddressOnParent>11</rasd:AddressOnParent>
175 <rasd:AutomaticAllocation>true</rasd:AutomaticAllocation>
176 <rasd:Connection>NET4</rasd:Connection>
177 <rasd:Description>VmxNet3 ethernet adapter on "NET4"</rasd:Description>
178 <rasd:ElementName>Ethernet 5</rasd:ElementName>
179 <rasd:InstanceID>14</rasd:InstanceID>
180 <rasd:ResourceSubType>VmxNet3</rasd:ResourceSubType>
181 <rasd:ResourceType>10</rasd:ResourceType>
182 <vmw:Config ovf:required="false" vmw:key="slotInfo.pciSlotNumber" vmw:value="36" />
183 <vmw:Config ovf:required="false" vmw:key="wakeOnLanEnabled" vmw:value="true" />
184 </Item>
185 <Item>
186 <rasd:AddressOnParent>12</rasd:AddressOnParent>
187 <rasd:AutomaticAllocation>true</rasd:AutomaticAllocation>
188 <rasd:Connection>NET5</rasd:Connection>
189 <rasd:Description>VmxNet3 ethernet adapter on "NET5"</rasd:Description>
190 <rasd:ElementName>Ethernet 6</rasd:ElementName>
191 <rasd:InstanceID>15</rasd:InstanceID>
192 <rasd:ResourceSubType>VmxNet3</rasd:ResourceSubType>
193 <rasd:ResourceType>10</rasd:ResourceType>
194 <vmw:Config ovf:required="false" vmw:key="slotInfo.pciSlotNumber" vmw:value="37" />
195 <vmw:Config ovf:required="false" vmw:key="wakeOnLanEnabled" vmw:value="true" />
196 </Item>
I guess that Linux is the OS inside the VM.
I'm not Linux administrator but recently I've try to resolve something similar to your problem with my colegue. In our situation NIC that was eth0 becomes eth1 after deployment. It was because eth(x) name was assigned by MAC address of NIC. And MAC address is allways different after deploying ovf template (if you deploy that template to the same environment then it have to change to avoid conflicts; if environment is different - then first segments in MAC address are different by default). I'm not linux administrator so I'm not sure that always (in every distribution) is the same mapping NIC->eth(x) policy.
So you have to check how OS maps NIC to eth(x) names. If there is any way to make mapping based on PCI position then you can do it, because that information is in ovf file. If mapping is done ONLY based on MAC address then it will be impossible to map correctly, because MAC address is not written to ovf file.
The issue isn't vmware, it's your vm. When you clone a vm, or if your ova wasn't properly prepped, eth0 won't be usable because the mac adress is in the /etc/sysconfig/network-scripts/ifcfg-eth0 script as well as in the /etc/udev/rules.d/70-persistent-net.rules file. You have 2 choices.
Change the mac in both the 70-persistent-net.rules and ifcfg-eth0 to match your new mac
Delete the 70-persistent-net.rules and remove the HWADDR from the ifcfg-eth0
After a reboot, you should have eth0 working again.
We have a bunch of CXF web services running in weblogic 10.3.0.0.
In sporadic situations, it looks like the network layer is not able to read the XML stream and weblogic server is throwing
the following error. Our service consumers are saying that they are receiving the XML stream or read time out exceptions sporadically. Application log is showing java.net.SocketException.
Also service consumers are saying that if they submit the same request
again, they receive the proper response without any issues.
Following is the log for the issues. This log is from weblogic's managed server (not application log) Also, I pasted below the header details for successful calls.
####<May 3, 2012 6:21:44 PM CDT> <Error> <HTTP> <xxxxxxxx.yyyyyyyy.com> <server2> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1336087304531> <BEA-101108> <[weblogic.servlet.internal.WebAppServletContext#58320dc6 - appName: 'webservice-aa-bb-1', name: 'webservice-aaa', context-path: '/webservice-aaa', spec-version: 'null'] Unsupported encoding: "utf-8";action="" specified.
java.io.UnsupportedEncodingException: Unsupported Encoding utf-8";action="
at weblogic.servlet.internal.ServletRequestImpl.setCharacterEncoding(ServletRequestImpl.java:428)
at weblogic.servlet.internal.ServletRequestImpl.initRequestEncoding(ServletRequestImpl.java:1115)
at weblogic.servlet.internal.ServletRequestImpl.getCharacterEncoding(ServletRequestImpl.java:451)
at org.apache.cxf.transport.http.HttpServletRequestSnapshot.<init>(HttpServletRequestSnapshot.java:69)
at org.apache.cxf.transport.http.AbstractHTTPDestination$1.cacheInput(AbstractHTTPDestination.java:245)
at org.apache.cxf.transport.http.AbstractHTTPDestination.cacheInput(AbstractHTTPDestination.java:441)
at org.apache.cxf.transport.http.AbstractHTTPDestination.flushHeaders(AbstractHTTPDestination.java:453)
at org.apache.cxf.transport.http.AbstractHTTPDestination.flushHeaders(AbstractHTTPDestination.java:446)
at org.apache.cxf.transport.http.AbstractHTTPDestination$WrappedOutputStream.onFirstWrite(AbstractHTTPDestination.java:589)
at org.apache.cxf.io.AbstractWrappedOutputStream.write(AbstractWrappedOutputStream.java:42)
at org.apache.cxf.io.CacheAndWriteOutputStream.write(CacheAndWriteOutputStream.java:68)
at com.ctc.wstx.io.UTF8Writer.flush(UTF8Writer.java:96)
at com.ctc.wstx.sw.BufferingXmlWriter.flush(BufferingXmlWriter.java:214)
at com.ctc.wstx.sw.BufferingXmlWriter.close(BufferingXmlWriter.java:194)
at com.ctc.wstx.sw.BaseStreamWriter.finishDocument(BaseStreamWriter.java:1685)
at com.ctc.wstx.sw.BaseStreamWriter.writeEndDocument(BaseStreamWriter.java:585)
at org.apache.cxf.binding.soap.interceptor.SoapOutInterceptor$SoapOutEndingInterceptor.handleMessage(SoapOutInterceptor.java:282)
at org.apache.cxf.binding.soap.interceptor.SoapOutInterceptor$SoapOutEndingInterceptor.handleMessage(SoapOutInterceptor.java:270)
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263)
at org.apache.cxf.interceptor.AbstractFaultChainInitiatorObserver.onMessage(AbstractFaultChainInitiatorObserver.java:104)
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:323)
at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:118)
at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:208)
at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:205)
at org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:113)
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:184)
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:107)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:163)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3498)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Following is the header details in our debug logs. This header has reponded successful response. I could not catch the header for unsuccessful service requests.
[________,[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)']:D: 03 18:01:41.417: ResponseTimeInInterceptor.handleMessage: HTTP Header :::::: Accept : application/soap+xml, multipart/related, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
[________,[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)']:D: 03 18:01:41.418: ResponseTimeInInterceptor.handleMessage: HTTP Header :::::: X-dynaTrace : FW0;-705664711;1266;3;964372818;3656;2
[________,[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)']:D: 03 18:01:41.418: ResponseTimeInInterceptor.handleMessage: HTTP Header :::::: User-Agent : Jakarta Commons-HttpClient/3.1
[________,[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)']:D: 03 18:01:41.418: ResponseTimeInInterceptor.handleMessage: HTTP Header :::::: Host : abcd.efg.hjk.com
[________,[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)']:D: 03 18:01:41.418: ResponseTimeInInterceptor.handleMessage: HTTP Header :::::: Content-Length : 496
[________,[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)']:D: 03 18:01:41.419: ResponseTimeInInterceptor.handleMessage: HTTP Header :::::: Content-Type : application/soap+xml;charset="utf-8";action=""
Thanks in Advance.
In your DOMAIN_HOME under bin directory, you should have a file called setDomain.env
Edit the file to add the below line, so that Weblogic will support the encoding
JAVA_OPTIONS="${JAVA_OPTIONS} -Dfile.encoding=utf8"
I am using the pjproject1.6 and I could send the sip packets through the sip packets to the proxy server and the rtp packets or not pass through the server. Hence the voice could not be heard on both sides.
I have checked in proxy server, rtp proxy is running and when proxy server sends 200 Ok, the SDP packets from PJSIP includes the IP address of the proxy server.
Still the sound/media are not transmitted to both PJMedia client and reciever.
I have tested the same scenario with the yate client, audio/media is heard both on the sender and reciever.
Is there any other config/code change that should taken care from PJSIP?
Kindly find the below log trace for the packets that are transmitted/recived from the server
Packet sent to server
INVITE sip:yyyyy#x.x.x.x:5060 SIP/2.0
Via: SIP/2.0/UDP 10.122.15.112:2370;branch=z9hG4bK8b9359940aa1224a09cd8cfa27959d48;rport
Max-Forwards: 70
From: ;tag=a604814d1290cc805caf160bdccb9390^M
To:
Call-ID: 1002437405#x.x.x.x-b2b_1
CSeq: 201 INVITE
Contact: Anonymous
Expires: 300
User-Agent: Sippy B2BUA (RADIUS)
cisco-GUID: 1368145855-893785068-3325200664-2859798416
h323-conf-id: 1368145855-893785068-3325200664-2859798416
Content-Length: 383
Content-Type: application/sdp
v=0
o=- 1290749418547 1290749418547 IN IP4 10.122.15.112
s=SIP Call
c=IN IP4 10.122.15.112
t=0 0
m=audio 33564 RTP/AVP 8 11 98 98 101
a=rtpmap:8 PCMA/8000
a=rtpmap:11 L16/8000
a=rtpmap:98 iLBC/8000
a=fmtp:98 mode=20
a=rtpmap:98 iLBC/8000
a=fmtp:98 mode=30
a=rtpmap:101 telephone-event/8000
a=ptime:30
a=nortpproxy:yes
Packet from x.x.x.x:5060
SIP/2.0 200 OK
CSeq: 201 INVITE
Via: SIP/2.0/UDP 10.122.15.112:2370;branch=z9hG4bK8b9359940aa1224a09cd8cfa27959d48;rport
From: ;tag=a604814d1290cc805caf160bdccb9390
Call-ID: 1002437405#213.146.168.52-b2b_1
To: ;tag=2711361009342964732656241
Contact:
Content-Type: application/sdp
Content-Length: 250
v=0
o=VoipSwitch 7240 7240 IN IP4 x.x.x.x
s=VoipSIP
i=Audio Session
c=IN IP4 x.x.x.x
t=0 0
m=audio 6240 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv