SIP Trunk on MBG

[nowickj]

I have configured SIP Trunk on My MiVoice Bordey Gateway which is in DMZ network. That MBG is clustered with MiCollab. When I make Diagnostic test - Basic connectivity tests and DNS resolution test everything is all right. But if I make SIP connectivity tests I have information Endpoint "SIP": IP address - Timeout on UDP port 5060. Could You tell Me where can I find some logs to see what is the problem?

[dilkie]

is it failing on the icp address or your trunk address?

[nowickj]

I have such information when I start SIP connectivity tests

Launching SIP connectivity test to SIP trunk provider 'SIP'...
Launching SIP connectivity test to ICP 'local_31'...
Endpoint "local_31": 10.127.10.31 - rport missing from Via header - endpoint does not support this test - you can safely ignore this
Endpoint "SIP": 213.218.117.66 - Timeout on UDP port 5060

[dilkie]

telling you it cannot access your sip provider on port 5060. is your f/w configured correctly?

If you run TNA from the internet, against your MBG's public ip, does it see 5060/udp as open?

[nowickj]

I have asked My IT departament and They  told me that all traffic is open between the IP address of the DMZ and the public IP address.
If I look on MBG System Status -> SIP Trunk Status is OK - first picture;
SIP Configuration looks like that: picture 2,3 and 4;

[nowickj]

test looks like that:

[dilkie]

well, you've got me confused.

My sip connectivity test reports my sip trunk as up with

Endpoint "Accessline-SJ": Good SIP response from 64.28.113.10

You say your test says `Endpoint "SIP"`, yet your trunk is called "SIPKrakow", so something doesn't jive.

[nowickj]

I have changed SIP configuration and now I have SIP trunked named SIPKrakow thats all So tests and configuration is showed for SIPKrakow.

[boycey9]

you should need no authentication on your MBG only on the MCD, go to diagnostics and run a packet trace, download it and filter on SIP and see what you can see.