Skip to main content
A
Anonymous
August 6, 2014
Answered

Object encoding error; terminating connection on call to pushNewStream method of amg

  • August 6, 2014
  • 1 reply
  • 591 views

Hi,

I am publishing a audio stream from a client with the name: az_34534_c_-1_31972433_23. On the server i receive this stream in the onPublish method and there i try to use legService.pushNewStream method.

It gives me the following error in AMS console:

(first line is the trace i have added in onPublish method followed by the error raised)

---OnPublish-----<>------:  stream az_34534_c_-1_31972433_23 ----push in legId 8879bfee-8ff6-433b-8691-441a89cad833

Object encoding error; terminating connection : rtmp://_defaultRoot_/_defaultVHost_/BPool1/23296

The legId is active and works fine because i could here the other speaker at my side. It is when i push my stream the object encoding error comes.

Is it a encoding issue like AMF3 or AMF0. I use the current default AMF3. I created a sample application, surprisingly, there the pushnewstream worked fine and communication worked. What should i check in case of my main application?

Here are the Logs from the AMG log file(right when pushnewstream is called):

2014-08-06::18:37:41.132    INFO    RTMP    8528    Received onStatus <Success> code <status> classType <StreamCreated> description <> details

2014-08-06::18:37:41.134    INFO    RTMP    8528    Received onStatus <NetStream.Play.Reset> code <status> classType <Playing and resetting az_34534_c_-1_31972433_23.> description <(null)> details

2014-08-06::18:37:41.135    INFO    RTMP    8528    Received onStatus <NetStream.Play.Start> code <status> classType <Started playing az_34534_c_-1_31972433_23.> description <(null)> details

2014-08-06::18:37:41.395    DEBUG    RTMP    8528    Received onStatus <NetConnection.Connect.Closed> code <status> classType <(null)> description <(null)> details

2014-08-06::18:37:41.395    DEBUG    RTMP    9048    connection closed- cleaning up all legService instance

2014-08-06::18:37:41.395    DEBUG    CALLLEG    9048    [LEG ID:15] - State Change EXEC -> HANGUP

2014-08-06::18:37:41.407    DEBUG    CALLLEG    7276    [LEG ID:16] - Bridging Completed for

2014-08-06::18:37:41.407    DEBUG    CALLLEG    7276    [LEG ID:16] - State Change SENDRECV -> HOLD

2014-08-06::18:37:41.407    DEBUG    CALLLEG    7276    [LEG ID:16] - Going For State 5

2014-08-06::18:37:41.407    DEBUG    SIPLEG    7276    [LEG ID:16] - holdHandler called...

2014-08-06::18:37:41.407    DEBUG    CALLLEG    7276    [LEG ID:16] - Call Leg HOLD

2014-08-06::18:37:41.407    ERROR    CORE    7276    [LEG ID:16] - deleting call leg ac93a9aa-b4a2-4df1-9507-c1455da16e62 after being at state 5 for 0 milliseconds

2014-08-06::18:37:41.407    DEBUG    CALLLEG    7276    [LEG ID:16] - Hangup Call (cause 702), from FMSMGCallLeg.cpp:618

2014-08-06::18:37:41.407    INFO    CALLLEG    7276    [LEG ID:16] - Hangup [HOLD] [Crash]

2014-08-06::18:37:41.407    DEBUG    CALLLEG    7276    [LEG ID:16] - Going For State 7

2014-08-06::18:37:41.407    DEBUG    SIPLEG    7276    [LEG ID:16] - hangupHandler called...sipGateway

2014-08-06::18:37:41.407    DEBUG    SIP    7276    [LEG ID:16] - Closing audio RTP session

2014-08-06::18:37:41.407    DEBUG    SIP    7276    [LEG ID:16] - closed audio socket=7416

2014-08-06::18:37:41.407    DEBUG    SIP    7276    [LEG ID:16] - closed video socket=7388

2014-08-06::18:37:41.407    DEBUG    SIP    7276    Removing Call Leg Entry for UUID ac93a9aa-b4a2-4df1-9507-c1455da16e62

2014-08-06::18:37:41.407    DEBUG    SIP    7276    [LEG ID:16] - call reject failed, will try disconnecting it rv=-3

2014-08-06::18:37:41.412    DEBUG    CALLLEG    2440    [LEG ID:15] - Bridging Completed for

2014-08-06::18:37:41.412    DEBUG    CALLLEG    2440    [LEG ID:15] - Hangup Call (cause 702), from FMSMGAppNodesHelper.cpp:1015

2014-08-06::18:37:41.412    DEBUG    CALLLEG    2440    [LEG ID:15] - Putting the other end on hold

2014-08-06::18:37:41.412    DEBUG    CALLLEG    2440    [LEG ID:15] - App  bridge(sip|9900@sipGateway) Returns 0 (next ID:1)

2014-08-06::18:37:41.412    DEBUG    CALLLEG    2440    [LEG ID:15] - Going For State 7

2014-08-06::18:37:41.412    DEBUG    CALLLEG    2440    [LEG ID:15] - Call Leg HANGUP, cause: Crash

2014-08-06::18:37:41.412    INFO    CALLLEG    2440    [LEG ID:15] - CallLeg Ended

2014-08-06::18:37:41.412    DEBUG    CALLLEG    2440    [LEG ID:15] - Cleaning up Leg [HANGUP]

2014-08-06::18:37:41.418    DEBUG    SIP    7276    [LEG ID:16] - Disconnected call for profile=sipGateway

2014-08-06::18:37:41.418    DEBUG    CALLLEG    7276    [LEG ID:16] - Call Leg HANGUP, cause: Crash

2014-08-06::18:37:41.418    INFO    CALLLEG    7276    [LEG ID:16] - CallLeg Ended

2014-08-06::18:37:41.418    DEBUG    CALLLEG    7276    [LEG ID:16] - Cleaning up Leg [HANGUP]

2014-08-06::18:37:41.419    DEBUG    SIP    8568    Callleg disconnect cause is 200

2014-08-06::18:37:42.418    DEBUG    SIPLEG    7276    [LEG ID:16] - deleting sip leg

2014-08-06::18:37:42.418    DEBUG    SIP    7276    [LEG ID:16] - Closing audio RTP session

Thanks,

Sahil.

This topic has been closed for replies.
Correct answer

Issue- AMG does not receive metadata embedded live streams. Once I removed the meta data injection scenario worked fine and there was no Object encoding error.

I was using stream.send("@setDataFrame","onMetaData", metaData);

But still I would like to ask experts, why is it so and how to fix it?

Thanks

Sahil.

1 reply

A
Anonymous
August 7, 2014

Another finding: this has nothing to do with AMF encoding. The problem seems like in the netstream properties or so. This will not be a big deal for the experts to fix, please help.

-Sahil.

A
Anonymous
Correct answer
August 8, 2014

Issue- AMG does not receive metadata embedded live streams. Once I removed the meta data injection scenario worked fine and there was no Object encoding error.

I was using stream.send("@setDataFrame","onMetaData", metaData);

But still I would like to ask experts, why is it so and how to fix it?

Thanks

Sahil.

A
Anonymous
August 13, 2014

Why isn't AMG able to receive live audio with metadata in it?

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices