Author Topic: SIP Trunk on MBG  (Read 3137 times)

Offline nowickj

  • Jr. Member
  • **
  • Posts: 61
  • Country: pl
  • Karma: +1/-0
    • View Profile
SIP Trunk on MBG
« on: February 09, 2016, 08:46:27 AM »
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?


Offline dilkie

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 344
  • Karma: +11/-0
    • View Profile
Re: SIP Trunk on MBG
« Reply #1 on: February 09, 2016, 09:58:12 AM »
is it failing on the icp address or your trunk address?

Offline nowickj

  • Jr. Member
  • **
  • Posts: 61
  • Country: pl
  • Karma: +1/-0
    • View Profile
Re: SIP Trunk on MBG
« Reply #2 on: February 10, 2016, 02:48:04 AM »
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

Offline dilkie

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 344
  • Karma: +11/-0
    • View Profile
Re: SIP Trunk on MBG
« Reply #3 on: February 10, 2016, 06:58:30 AM »
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?

Offline nowickj

  • Jr. Member
  • **
  • Posts: 61
  • Country: pl
  • Karma: +1/-0
    • View Profile
Re: SIP Trunk on MBG
« Reply #4 on: February 10, 2016, 08:58:21 AM »
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;


Offline nowickj

  • Jr. Member
  • **
  • Posts: 61
  • Country: pl
  • Karma: +1/-0
    • View Profile
Re: SIP Trunk on MBG
« Reply #5 on: February 10, 2016, 08:59:09 AM »
test looks like that:
« Last Edit: February 10, 2016, 09:00:46 AM by nowickj »

Offline dilkie

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 344
  • Karma: +11/-0
    • View Profile
Re: SIP Trunk on MBG
« Reply #6 on: February 10, 2016, 09:31:01 AM »
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.

Offline nowickj

  • Jr. Member
  • **
  • Posts: 61
  • Country: pl
  • Karma: +1/-0
    • View Profile
Re: SIP Trunk on MBG
« Reply #7 on: February 11, 2016, 03:24:13 AM »
I have changed SIP configuration and now I have SIP trunked named SIPKrakow thats all :) So tests and configuration is showed for SIPKrakow.

Offline boycey9

  • Full Member
  • ***
  • Posts: 182
  • Karma: +4/-0
    • View Profile
Re: SIP Trunk on MBG
« Reply #8 on: February 22, 2016, 03:09:57 PM »
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.


 

Sitemap 1 2 3 4 5 6 7 8 9 10