Author Topic: No Ringback on SIP Trunks  (Read 3138 times)

Offline sanmar

  • Contributer
  • *
  • Posts: 9
  • Country: us
  • Karma: +0/-0
    • View Profile
No Ringback on SIP Trunks
« on: April 12, 2016, 11:50:06 AM »
I recently switched over to SIP trunks from PRI, after a couple of hiccups the only issue left is that we don't always get a ringback when we dial out. Sometimes it works and sometimes it doesn't. I am using an MBG and did some trace routes to send to SIP provider and they are telling me they are sending the SIP 180ringing back to the MBG. Any help will be appreciated. Thanks


Offline mhumphries

  • Jr. Member
  • **
  • Posts: 87
  • Country: us
  • Karma: +2/-0
    • View Profile
Re: No Ringback on SIP Trunks
« Reply #1 on: June 13, 2016, 09:18:45 AM »
i have a similar issue.  we still have out PRIs however we have added SIP trunks to the mix.  i can make a call and it completes as expected. however there is no ring back.  did you ever get to the bottom of your issue?  we are not using a border gateway. i have the SIP trunks coming through the firewall with 1-to-1 NAT.  ports 5060-5061 are open to the VMCD, as well as the RTP ports.

Offline x-man

  • Hero Member
  • *****
  • Posts: 1129
  • Country: gb
  • Karma: +25/-0
    • View Profile
Re: No Ringback on SIP Trunks
« Reply #2 on: June 13, 2016, 12:55:09 PM »
What RTP ports are you using and do they match what the provider specifies?

Offline mhumphries

  • Jr. Member
  • **
  • Posts: 87
  • Country: us
  • Karma: +2/-0
    • View Profile
Re: No Ringback on SIP Trunks
« Reply #3 on: June 13, 2016, 12:56:46 PM »
does the ringing come through the SIP Trunk as RTP?  when i spoke to the provider they did not believe that it did.  that the 180 ringing should trigger the Mitel to provide the ringing???

Offline x-man

  • Hero Member
  • *****
  • Posts: 1129
  • Country: gb
  • Karma: +25/-0
    • View Profile
Re: No Ringback on SIP Trunks
« Reply #4 on: June 13, 2016, 02:13:00 PM »
Hmmm, I was under the construct that the 180 ringback was sent as RTP from the far end subscriber....probably wrong though.


 

Sitemap 1 2 3 4 5 6 7 8 9 10