Hi again guys, until the magic autoaprovisioning solution come to recue me from hell XDD I must to work hard with this case XDD. Ok I made your recommendations and:
I think like MediatrixUser that can be a capacity problem, because when no calls ( night for example) the unit don´t crash . So yesterday I made the changes that you comment to me (until I wait the response of media5corp with the new firmware):
Only a trunk in asterisk => "50000"
Remove all registration in the Mediatrix => ok
A upload a image of actual status of SIP->Registrations [imagen]
Actual status of call routing -> [imagen2]
So after this modifications the services seems ok all morning, I wait until afternoon to be sure to post but.... even though the services have not been disconnected I have now had problems with callerID. The analogic pbx see all time calls from 50000 the asterisk trunk.Pfff
This was my asterisk configuration to call mediatrix, that cause a wrong callerid:
I use this way always this other gateways, this mediatrix before changes, etc.. with no problems but now make problems
exten = 999999999,1,Dial(SIP/50000/${EXTEN},80)
exten = 999999999,2,Hangup
read more about it(including a another MediatrixUser post ( I no found the options that you say on this post, maybe because is other model) and in mediatrix 4400 configuration notes says:
"""
Enabling the “Calling Line Information Presentation” parameter makes the caller ID present in outgoing SIP to ISDN calls. WARNING: Even if the Mediatrix unit passes the caller ID, it could be suppressed further downstream on either SIP or ISDN. For caller ID problems, looking at the syslog messages containing the SEND Setup messages is a good debug approach.
"""
but I no found any interesting information about "SEND Setup" in traces
So:
I change the dial string to contact directly to the IP from mediatrix:
exten = 999999999,1,Dial(SIP/99.99.99.99/${EXTEN},80)
exten = 999999999,2,Hangup
and now the analogic PBX see the correct callerid.
I think the second way is not a good way, but I dont know why the callerid identification fail now. And this way is now working ok
I make two traces
1) Trace with callerid problems: Call from 666666666 to 856856856(asterisk)->mediatrix [file]
2) Trace with callerid OK (using asterisk second way directy to mediatrix IP): Call from 666666666 to 956956956(asterisk)->mediatrix [file]
And thanks thanks thanks thanks again for your help guys, I have the impression that we're almost at the end of solving this!!!!