Author Topic: SS7 + MGCP + Cisco freezing  (Read 167 times)

kaoe

  • Newbie
  • *
  • Posts: 3
    • View Profile
SS7 + MGCP + Cisco freezing
« on: March 28, 2019, 11:02:19 AM »
Hello,

I'm configuring an SS7 interconnect using Yate + MGCP + Cisco.
In the tests I did worked fine, but I was using a single port of cisco as audio channels.
When we did the final assembly using 3 ports of cisco we had several problems of timeout and even a freezing of cisco.
I do not know if this is correct but I came to the conclusion that the problem was caused by I having created each port as being a gw, ie
[gw cisco-port-1]
host = 192.168.10.253
user = S0 / SU1 / DS1-0 / 1
...
[gw cisco-port-2]
host = 192.168.10.253
user = S0 / SU1 / DS1-1 / 1
...
[gw cisco-port-3]
host = 192.168.10.253
user = S0 / SU2 / DS1-0 / 1
...

This way I imagine that for cisco it is as if there were 3 callagents controlling it, and at the top of the documentation it is written that it does not support this situation. I'm not sure if this is the problem but it seemed to me the only justification to work with 1 port but to freeze the cisco when I set the 3.
This way I changed the configuration to use one, with the range option. But as my cisco modules are 2 ports, my user string does not take care of the situation because * would only replace the range number and not the module, ie for a user = S0 / SU1 / DS1 - * / 1 and a range = 0-1 I can configure the S0 / SU1 / DS1-0 / 1 and S0 / SU1 / DS1-1 / 1 endpoints, but not S0 / SU2 / DS1-0 / 1.

I wonder if the cisco crash problem can even be caused by having several separate gw configurations. I searched the source code and did not find an alternative to create the endpoint that is in module 2 without creating a totally new separate configuration.

Thank you.