Issue initializing some mrcp clients when many clients are started together

[hsb]

Hi,
     I started some mrcp clients. These clients have default settings. Most of the clients get started and send the requests to mrcp server and receive the replies. Whereas some clients just stop at the initiation stage. Following is the output on the such clients

12:45:31:732725 [NOTICE] UniMRCP Client [1.0.0]
12:45:31:732964 [INFO]   APR [1.4.2]
12:45:31:732988 [NOTICE] Create MRCP Client
12:45:31:733077 [NOTICE] Open Config File [./conf/mrcpclient.xml]
12:45:31:733441 [DEBUG]  Loading Properties
12:45:31:733453 [DEBUG]  Loading Element <ip>
12:45:31:733461 [DEBUG]  Detecting IP Address
12:45:31:747592 [INFO]   Set Property ip:<IP_ADDRESS_OF_CLIENT>
12:45:31:747649 [INFO]   Register Codec [PCMU]
12:45:31:747661 [INFO]   Register Codec [PCMA]
12:45:31:747672 [INFO]   Register Codec [L16]
12:45:31:747680 [DEBUG]  Loading Components
12:45:31:747692 [DEBUG]  Loading Resources
12:45:31:747718 [NOTICE] Register Resource [speechrecog]
12:45:31:747728 [INFO]   Register Resource Factory
12:45:31:747738 [DEBUG]  Loading SofiaSIP Agent <SIP-Agent-1>
12:45:31:747746 [DEBUG]  Loading Element <sip-port>
12:45:31:747761 [DEBUG]  Loading Element <sip-transport>
12:45:31:747770 [DEBUG]  Loading Element <ua-name>
12:45:31:747777 [DEBUG]  Loading Element <sdp-origin>
12:45:31:747795 [NOTICE] Create SofiaSIP Agent [SIP-Agent-1] [1.12.10devel] sip:<IP address of the client:port><IP_ADDRESS_OF_CLIENT>:8081;transport=udp
12:45:31:747804 [INFO]   Register Signaling Agent [SIP-Agent-1]
12:45:31:747817 [DEBUG]  Loading UniRTSP Agent <RTSP-Agent-1>
12:45:31:747825 [DEBUG]  Loading Element <max-connection-count>
12:45:31:747834 [DEBUG]  Loading Element <sdp-origin>
12:45:31:747845 [DEBUG]  Create RTSP Client [100]
12:45:31:747914 [NOTICE] Create UniRTSP Agent [RTSP-Agent-1] [100]
12:45:31:747924 [INFO]   Register Signaling Agent [RTSP-Agent-1]
12:45:31:747934 [DEBUG]  Loading MRCPv2 Agent <MRCPv2-Agent-1>
12:45:31:747945 [DEBUG]  Loading Element <max-connection-count>
12:45:31:747953 [DEBUG]  Loading Element <offer-new-connection>
12:45:31:747964 [DEBUG]  Loading Element <rx-buffer-size>
12:45:31:747972 [DEBUG]  Loading Element <tx-buffer-size>
12:45:31:747981 [NOTICE] Create MRCPv2 Agent [MRCPv2-Agent-1] [100]
12:45:31:748011 [INFO]   Register Connection Agent [MRCPv2-Agent-1]
12:45:31:748023 [DEBUG]  Loading Media Engine <Media-Engine-1>
12:45:31:748031 [DEBUG]  Loading Element <realtime-rate>
12:45:31:748039 [NOTICE] Create Media Engine [Media-Engine-1]
12:45:31:748050 [INFO]   Register Media Engine [Media-Engine-1]
12:45:31:748060 [DEBUG]  Loading RTP Factory <RTP-Factory-1>
12:45:31:748068 [DEBUG]  Loading Element <rtp-port-min>
12:45:31:748075 [DEBUG]  Loading Element <rtp-port-max>
12:45:31:748084 [NOTICE] Create RTP Termination Factory <IP_ADDRESS_OF_CLIENT>:[4000,5000]
12:45:31:748092 [INFO]   Register RTP Termination Factory [RTP-Factory-1]
12:45:31:748101 [DEBUG]  Loading Settings
12:45:31:748110 [DEBUG]  Loading RTP Settings <RTP-Settings-1>
12:45:31:748117 [DEBUG]  Loading Element <jitter-buffer>
12:45:31:748124 [DEBUG]  Loading Jitter Buffer Settings
12:45:31:748131 [DEBUG]  Loading Element <playout-delay>
12:45:31:748138 [DEBUG]  Loading Element <max-playout-delay>
12:45:31:748146 [DEBUG]  Loading Element <ptime>
12:45:31:748153 [DEBUG]  Loading Element <codecs>
12:45:31:748170 [DEBUG]  Loading Element <rtcp>
12:45:31:748178 [INFO]   Register RTP Settings [RTP-Settings-1]
12:45:31:748187 [INFO]   Enter Directory [./conf/client-profiles]
12:45:31:748255 [NOTICE] Open Config File [./conf/client-profiles/mrcp.xml]
12:45:31:759402 [DEBUG]  Loading Settings
12:45:31:759446 [DEBUG]  Loading SIP Settings <UniMRCP-SIP-Settings>
12:45:31:759455 [DEBUG]  Loading Element <server-port>
12:45:31:759467 [INFO]   Create SIP Settings <IP_ADDRESS_OF_CLIENT>:8060
12:45:31:759475 [INFO]   Register Signaling Settings [UniMRCP-SIP-Settings]
12:45:31:759486 [DEBUG]  Loading RTSP Settings <UniMRCP-RTSP-Settings>
12:45:31:759494 [DEBUG]  Loading Element <server-port>
12:45:31:759501 [DEBUG]  Loading Element <resource-location>
12:45:31:759520 [DEBUG]  Loading Element <resource-map>
12:45:31:759528 [DEBUG]  Loading Resource Map
12:45:31:759536 [DEBUG]  Loading Param speechrecog:speechrecognizer
12:45:31:759544 [INFO]   Create RTSP Settings <IP_ADDRESS_OF_CLIENT>:1554
12:45:31:759552 [INFO]   Register Signaling Settings [UniMRCP-RTSP-Settings]
12:45:31:759560 [DEBUG]  Loading Profiles
12:45:31:759568 [DEBUG]  Loading MRCPv2 Profile <uni2>
12:45:31:759575 [DEBUG]  Loading Element <sip-uac>
12:45:31:759583 [DEBUG]  Loading Element <mrcpv2-uac>
12:45:31:759590 [DEBUG]  Loading Element <media-engine>
12:45:31:759599 [DEBUG]  Loading Element <rtp-factory>
12:45:31:759606 [DEBUG]  Loading Element <sip-settings>
12:45:31:759614 [DEBUG]  Loading Element <rtp-settings>
12:45:31:759623 [NOTICE] Create MRCPv2 Profile [uni2]
12:45:31:759630 [INFO]   Register Profile [uni2]
12:45:31:759639 [DEBUG]  Loading MRCPv1 Profile <uni1>
12:45:31:759646 [DEBUG]  Loading Element <rtsp-uac>
12:45:31:759653 [DEBUG]  Loading Element <media-engine>
12:45:31:759660 [DEBUG]  Loading Element <rtp-factory>
12:45:31:759667 [DEBUG]  Loading Element <rtsp-settings>
12:45:31:759676 [DEBUG]  Loading Element <rtp-settings>
12:45:31:759683 [NOTICE] Create MRCPv1 Profile [uni1]
12:45:31:759690 [INFO]   Register Profile [uni1]
12:45:31:759730 [INFO]   Leave Directory [./conf/client-profiles]
12:45:31:759742 [NOTICE] Create Application
12:45:31:759749 [INFO]   Register Application [recog]
12:45:31:759787 [INFO]   Start Task [Framework Agent]
12:45:31:759912 [INFO]   Start Task [MRCP Client]
12:45:31:778108 [DEBUG]  Task Started [Framework Agent]
12:45:31:778158 [NOTICE] Run Demo Framework
12:45:31:778167 [DEBUG]  Wait for Messages [Framework Agent]
12:45:31:778193 [INFO]   Start Task [SIP-Agent-1]
12:45:31:778307 [INFO]   Start Task [RTSP-Agent-1]
12:45:31:778421 [INFO]   Start Task [MRCPv2-Agent-1]
12:45:31:778478 [INFO]   Start Task [Media-Engine-1]
12:45:31:778592 [DEBUG]  Task Started [Media-Engine-1]
12:45:31:778606 [DEBUG]  Signal Message to [MRCP Client] [0;1]
12:45:31:778617 [DEBUG]  Wait for Messages [MRCP Client]
12:45:31:778625 [DEBUG]  Process Message [MRCP Client] [0;1]
12:45:31:778643 [DEBUG]  Wait for Messages [MRCP Client]
12:45:31:793269 [DEBUG]  Task Started [RTSP-Agent-1]
12:45:31:793315 [DEBUG]  Signal Message to [MRCP Client] [0;1]
12:45:31:793343 [DEBUG]  Wait for Messages [RTSP-Agent-1]
12:45:31:793368 [DEBUG]  Process Message [MRCP Client] [0;1]
12:45:31:793380 [DEBUG]  Wait for Messages [MRCP Client]
12:45:31:793404 [DEBUG]  Task Started [MRCPv2-Agent-1]
12:45:31:793421 [DEBUG]  Signal Message to [MRCP Client] [0;1]
12:45:31:793433 [DEBUG]  Wait for Messages [MRCPv2-Agent-1]
12:45:31:793445 [DEBUG]  Process Message [MRCP Client] [0;1]
12:45:31:793454 [DEBUG]  Wait for Messages [MRCP Client]
12:45:31:813894 [DEBUG]  Task Started [SIP-Agent-1]
12:45:31:813947 [DEBUG]  Signal Message to [MRCP Client] [0;1]
12:45:31:813968 [DEBUG]  Task Terminated [SIP-Agent-1]
12:45:31:814166 [DEBUG]  Process Message [MRCP Client] [0;1]
12:45:31:814180 [DEBUG]  Task Started [MRCP Client]
12:45:31:814188 [NOTICE] MRCP Client Started
12:45:31:814201 [DEBUG]  Wait for Messages [MRCP Client]
12:45:31:814306 [DEBUG]  Signal Message to [Framework Agent] [1;1]
12:45:31:814364 [DEBUG]  Process Message [Framework Agent] [1;1]
12:45:31:814378 [NOTICE] Run Demo Application Scenario [recog]
12:45:31:814415 [NOTICE] Create MRCP Handle 0x8472318 [uni2]
12:45:31:814438 [INFO]   Create Channel 0x8472318 <new>
12:45:31:814452 [DEBUG]  Signal Message to [MRCP Client] [4;0]
12:45:31:814463 [DEBUG]  Wait for Messages [Framework Agent]
12:45:31:814477 [DEBUG]  Process Message [MRCP Client] [4;0]
12:45:31:814486 [INFO]   Receive App Request 0x8472318 <new> [2]
12:45:31:814503 [INFO]   Add MRCP Handle 0x8472318 <new>
12:45:31:814512 [DEBUG]  Dispatch App Request 0x8472318 <new> [2]
12:45:31:814585 [DEBUG]  Signal Message to [MRCPv2-Agent-1] [1;0]
12:45:31:814613 [NOTICE] Add Control Channel 0x8472318 <new@speechrecog>
12:45:31:814627 [DEBUG]  Add Media Termination 0x8472318 <new@media-tm>
12:45:31:814639 [DEBUG]  Add Media Termination 0x8472318 <new@rtp-tm>
12:45:31:814648 [DEBUG]  Signal Message to [Media-Engine-1] [1;0]
12:45:31:814657 [DEBUG]  Wait for Messages [MRCP Client]
12:45:31:814712 [DEBUG]  Process Poller Wakeup [MRCPv2-Agent-1]
12:45:31:814724 [DEBUG]  Process Message [MRCPv2-Agent-1] [1;0]
12:45:31:814736 [DEBUG]  Signal Message to [MRCP Client] [2;0]
12:45:31:814749 [DEBUG]  Wait for Messages [MRCPv2-Agent-1]
12:45:31:814764 [DEBUG]  Process Message [MRCP Client] [2;0]
12:45:31:814773 [DEBUG]  Control Channel Added 0x8472318 <new@speechrecog>
12:45:31:814781 [DEBUG]  Wait for Messages [MRCP Client]
12:45:31:823571 [DEBUG]  Process Message [Media-Engine-1] [1;0]
12:45:31:823620 [DEBUG]  Add Media Context 0x8472318
12:45:31:823913 [DEBUG]  Process Message [MRCP Client] [3;0]
12:45:31:823931 [DEBUG]  Media Termination Added 0x8472318 <new@media-tm>
12:45:31:823942 [DEBUG]  Media Termination Added 0x8472318 <new@rtp-tm>
12:45:31:823953 [INFO]   Send Offer 0x8472318 <new> [c:1 a:1 v:0] to <IP_ADDRESS_OF_CLIENT>:8060
12:45:31:824007 [INFO]   Local SDP 0x8472318 <new>
v=0
o=UniMRCPClient 0 0 IN IP4 <IP_ADDRESS_OF_CLIENT>
s=-
c=IN IP4 <IP_ADDRESS_OF_CLIENT>
t=0 0
m=application 9 TCP/MRCPv2 1
a=setup:active
a=connection:new
a=resource:speechrecog
a=cmid:1
m=audio 4000 RTP/AVP 0 8 96 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:96 L16/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendonly
a=ptime:20
a=mid:1

12:45:31:824047 [DEBUG]  Wait for Messages [MRCP Client]

---------------------------------------------------------------------------------------------------
It happens when I run many clients. Could anyone please let me know the solution to avoid such situation

[frank.of...@caseris.de]

Hi,

> I started some mrcp clients. These clients have default
> settings. Most of the clients get started and send the requests to
> mrcp server and receive the replies. Whereas some clients just stop
> at the initiation stage. Following is the output on the such clients
>

You should look up my (Frank Offermanns) previous posts. I asked this
question a few months (or about a year) ago.
As far as I remember each client must have some of his ports unique for
himself.
The answer which Arsen gave to me is of course more precise and should
completely answer your question.

Best regards,
Frank Offermanns

[hsb]

Thanks Frank for the input. I tried using different folders for clients, each containing unique values for RTP and SIP. However at the run time, I am not sure why some clients pick up the RTP ports which are being used by other clients. Because of this, both the clients stop. Is there a solution for this? Or am I doing somethign wrong here?

Client 1
00:8060
14:43:57:383885 [INFO]   Local SDP 0x9d50318 <new>
v=0
o=UniMRCPClient 0 0 IN IP4 192.168.1.100
s=-
c=IN IP4 192.168.1.100

t=0 0
m=application 9 TCP/MRCPv2 1
a=setup:active
a=connection:new
a=resource:speechrecog
a=cmid:1

m=audio 4027 RTP/AVP 0 8 96 101

a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:96 L16/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendonly
a=ptime:20
a=mid:1

14:43:57:383924 [DEBUG]  Wait for Messages [MRCP Client]
*************************************************************
Client 2
00:8060
14:43:57:329313 [INFO]   Local SDP 0x824e8c0 <new>
v=0
o=UniMRCPClient 0 0 IN IP4 192.168.1.100
s=-
c=IN IP4 192.168.1.100

t=0 0
m=application 9 TCP/MRCPv2 1
a=setup:active
a=connection:new
a=resource:speechrecog
a=cmid:1

m=audio 4027 RTP/AVP 0 8 96 101

a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:96 L16/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendonly
a=ptime:20
a=mid:1

Thanks,
hsb

[Francais Francaise]

My guess is that since you are using ASR and the local SDP ports are unused, Sofia SIP may have decided to save some valuable port numbers and use the same port values for the ports which will not receive any UDP messages. However, this theory is not consistent with the requirement of having unique RTCP ports (RTCP ports value are 1 higher that the value of the respective RTP ports). RTCP messages flow in both directions, unlike caller's utterances which go only from the client to server. 

 

I will ask Arsen.

 

--
You received this message because you are subscribed to the Google Groups "UniMRCP" group.

To view this discussion on the web visit https://groups.google.com/d/msg/unimrcp/-/ZUZSRDl0dnVlNUVK.

To post to this group, send email to uni...@googlegroups.com.
To unsubscribe from this group, send email to unimrcp+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/unimrcp?hl=en.

[frank.of...@caseris.de]

Hello,

you should really read my previous posts and Arsens answers, since I had a
similar problem.
I can't tell you more - unfortunately I would have to look up it myself
since I don't remember it completly.

Best regards,
Frank Offermanns

[Francais Francaise]

Here is the link:

 

https://groups.google.com/forum/#!searchin/unimrcp/Frank$20Offermanns/unimrcp/s7O6AFTBq3Y/7AaOYABT8W4J

--
You received this message because you are subscribed to the Google Groups "UniMRCP" group.