No MDCX for RAN side after assignment ?
I've applied https://gerrit.osmocom.org/#/c/4980 to current osmo-msc master and Using a TTCN-3 testcase for MO call to MNCC I'm getting the attached protocol trace.First everything looks great:
- CRCX for RAN side is performed + ACKed
- CRCX for CN side is performed + ACKed
- AoIP Assignment Request is sent (with correct IP/Port)
- AoIP Assignment Complete is received (with correct IP/Port)
I would expect that the IP/Port from the AoIP Assignment Complete would then immediately result in a MGCP MDCX on the RAN side connection.
For some reason it isn't happening. Any ideas?
#1 Updated by dexter over 1 year ago
I would love to reproduce this. Is this already in osmo-ttcn3-hacks?.
It looks just like if the EV_CONNECT event is missing. This event is needed by msc_mgcp.c to move on. The Event is fired when msc_mgcp_call_complete() is called from libmsc/gsm_04_08.c. On the first look it looks just like if there were some problems with MNCC. Somehow the circuit is not closed. Are you running it with internal or with external MNCC?