Skip to main content
Known Participant
May 20, 2014
Question

AMG-AMS, SIP Call Not being answered by AMG (no 200-OK after 100-Trying)

  • May 20, 2014
  • 0 replies
  • 296 views

Hello there,

I trying to integrate AMG with AMS so that a SIP Phone user can join a virtual class in AMS. Now my AMG leg service is connected with AMS but when I dial AMS extension from my sip phone, AMG doesn't answer or bridge the RTMP/SIP-RTP audio stream.

Please note that a new stream (from AMG) is created and published in AMS as I can see from the wireshark dump and AMS admin console but some call goes un-answered. Can some one please advise what exactly I am missing out here ? I have pasted AMG logs, RTMP capture and SIP capture. Please note that both AMG and AMS are installed on the same server and I am testing it on a local LAN.

In SIP traces we can see that AMG is not answering the call which means I am not getting 200-OK after INVITE and 100-TRYING.

AMG logs

2014-05-20::17:09:11.755        DEBUG   1073742997 CORE 23060   num matches: 1

2014-05-20::17:09:11.755        DEBUG   1073742997 CALLLEG      23060   [LEG ID:1] - Execute bridge(rtmp|${destNum}@t2ams)

2014-05-20::17:09:11.755        DEBUG   1073742997 CALLLEG      23060   [LEG ID:1] - Expanded String bridge(rtmp|9999@t2ams) (ID:1)

2014-05-20::17:09:11.755        DEBUG   1073742997 SIPLEG       23060   [LEG ID:1] - Call in progress

2014-05-20::17:09:11.755        INFO    1073742997 CALLLEG      23060   [LEG ID:1] - Ringing

2014-05-20::17:09:11.755        DEBUG   1073742997 CALLLEG      23060   [LEG ID:2] - Allocated new Call Leg(rtmp)

2014-05-20::17:09:11.756        INFO    1073742997 RTMPLEG      23060   [LEG ID:2] - setting silence level to 0 for Leg

2014-05-20::17:09:11.756        INFO    1073742997 RTMPLEG      23060   [LEG ID:2] - setting silence Timeout to 5000 for Leg

2014-05-20::17:09:11.756        DEBUG   1073742997 CALLLEG      23060   [LEG ID:2] - Going For State 0

2014-05-20::17:09:11.756        DEBUG   1073742997 CALLLEG      23060   [LEG ID:2] - State ALLOC

2014-05-20::17:09:11.792        INFO    1073742997 RTMP 23060   Received onStatus <Success> code <status> classType <StreamCreated> description <> details

2014-05-20::17:09:11.794        INFO    1073742997 RTMP 23060   Received onStatus <NetStream.Publish.Start> code <status> classType <fmg/AutoConnect/1 is now published.> description <(null)> details

2014-05-20::17:09:11.816        DEBUG   1073742997 CALLLEG      23060   [LEG ID:2] - State Change ALLOC -> START

2014-05-20::17:09:11.816        DEBUG   1073742997 CALLLEG      23060   [LEG ID:2] - Going For State 1

2014-05-20::17:09:11.817        DEBUG   1073742997 RTMPLEG      23060   [LEG ID:2] - Inside start handler

2014-05-20::17:09:11.817        DEBUG   1073742997 CALLLEG      23060   [LEG ID:2] - Call Leg START

2014-05-20::17:09:25.701        ERROR   1073742997 RTMP 23060   Received Invalid Command on NetConnection:_OnServerHeartBeat, Message Dropped

2014-05-20::17:09:45.700        ERROR   1073742997 RTMP 23060   Received Invalid Command on NetConnection:_OnServerHeartBeat, Message Dropped

2014-05-20::17:09:51.606        DEBUG   1073742997 SIP  23060   Local Interface : 192.168.1.109 will be used

2014-05-20::17:09:51.606        DEBUG   1073742997 SIP  23060   Registration successful for profile sipPhone2

2014-05-20::17:10:05.699        ERROR   1073742997 RTMP 23060   Received Invalid Command on NetConnection:_OnServerHeartBeat, Message Dropped

2014-05-20::17:10:11.388        DEBUG   1073742997 SIP  23060   Remote SIP address not initialize yet for Profile sipPhone

2014-05-20::17:10:11.762        DEBUG   1073742997 CALLLEG      23060   [LEG ID:2] - Timeout waiting for Answer on Call

2014-05-20::17:10:11.762        DEBUG   1073742997 CALLLEG      23060   [LEG ID:2] - Hangup Call (cause 408), from FMSMGAppNodesHelper.cpp:529

2014-05-20::17:10:11.762        INFO    1073742997 CALLLEG      23060   [LEG ID:2] - Hangup [START] [Request_timeout]

2014-05-20::17:10:11.762        ERROR   1073742997 CALLLEG      23060   [LEG ID:1] - Error Creating Call Leg for destination rtmp|9999@t2ams

2014-05-20::17:10:11.762        DEBUG   1073742997 CALLLEG      23060   [LEG ID:1] - App  bridge(rtmp|9999@t2ams) Returns 2 (next ID:1)

2014-05-20::17:10:11.762        DEBUG   1073742997 CALLLEG      23060   [LEG ID:2] - Going For State 7

2014-05-20::17:10:11.762        DEBUG   1073742997 CALLLEG      23060   [LEG ID:1] - Execute hangup(null)

2014-05-20::17:10:11.762        DEBUG   1073742997 CALLLEG      23060   [LEG ID:2] - Call Leg HANGUP, cause: Request_timeout

2014-05-20::17:10:11.762        INFO    1073742997 CALLLEG      23060   [LEG ID:2] - CallLeg Ended

RTMP network capture (using tshark)

277.991307    127.0.0.1 -> 127.0.0.1    RTMP 312 createStream() | MGCallLegServiceMessage()

277.991475    127.0.0.1 -> 127.0.0.1    RTMP 109 _result()

277.991616    127.0.0.1 -> 127.0.0.1    RTMP 127 publish('fmg/AutoConnect/1')

277.992596    127.0.0.1 -> 127.0.0.1    RTMP 241 Set Chunk Size 1024 | onStatus('NetStream.Publish.Start')

278.010156    127.0.0.1 -> 127.0.0.1    RTMP 269 MGLegServiceMessage()

278.015654    127.0.0.1 -> 127.0.0.1    RTMP 225 MGCallLegServiceMessage()

SIP network capture (using tshark)

12  31.896848 192.168.1.100 -> 192.168.1.109 SIP/SDP 968 Request: INVITE sip:9999@192.168.1.109;transport=UDP |

31.897834 192.168.1.109 -> 192.168.1.100 SIP 511 Status: 407 Proxy Authentication Required |

31.914622 192.168.1.100 -> 192.168.1.109 SIP 436 Request: ACK sip:9999@192.168.1.109;transport=UDP |

31.914640 192.168.1.100 -> 192.168.1.109 SIP/SDP 1209 Request: INVITE sip:9999@192.168.1.109;transport=UDP |

31.915874 192.168.1.109 -> 192.168.1.100 SIP 387 Status: 100 Trying |

91.926390 192.168.1.109 -> 192.168.1.100 SIP 400 Status: 408 Request Timeout |

92.029868 192.168.1.100 -> 192.168.1.109 SIP 436 Request: ACK sip:9999@192.168.1.109;transport=UDP |

This topic has been closed for replies.