  espaeth Digital Plumber Premium,MVM join:2001-04-21 Minneapolis, MN | reply to MartinM Re: [Other] VOIP.MS
Quick question:
For termination service do your servers support re-invite to establish RTP streams directly to the egress PSTN gateway, or are RTP streams required to route through the SIP servers? |
|
 gbh2o
join:2000-12-18 Greenville, NC
·Future Nine Corpor..
·callwithus
·MyPhoneCompany
·VBUZZER
·Voxee
·Embarq
·VOIPo
·STANAPHONE
·Axvoice
·Packet8
| Just a guess, sometimes, from their example configuration example...
canreinvite=nonat
which is defined as "An additional option is to allow media path redirection (reinvite) but only when the peer where the media is being sent is known to not be behind a NAT (as the RTP core can determine it based on the apparent IP address the media arrives from)." |
|
 MartinM
join:2008-07-21 Montreal, QC | By default, our system will always stay in the media path. In the past, we did try letting users "choose" but it caused all kind of problems since we are a BYOD. If you want the RTP to be re-invited, we can set it on your account by request. |
|
 gg22
join:2008-08-19
·voip.ms
| reply to espaeth said by espaeth :Quick question: For termination service do your servers support re-invite to establish RTP streams directly to the egress PSTN gateway, or are RTP streams required to route through the SIP servers? This is interesting. What are the advantages of doing so? Reduced latency or improved sound quality? Or both? |
|
  espaeth Digital Plumber Premium,MVM join:2001-04-21 Minneapolis, MN
·voip.ms
·Vitelity VOIP
·Callcentric
·VoiceStick
·ViaTalk
·Comcast
·Embarq
| said by gg22 :This is interesting. What are the advantages of doing so? Reduced latency or improved sound quality? Or both? Potentially both. At a minimum you're taking a box out of the middle of the connection path, which reduces the possibility of resource issues on the call manager causing degradation on the call.
The issue with re-invites is that there are many problems with NAT. Basically you start off talking to the call manager at 10.10.10.10, then it sets up the call and your actual voice traffic starts arriving from 20.20.20.20 -- that scenario breaks with dynamic NAT. If you have ports forwarded to your ATA or * box, it usually works. In most cases, though, it's really only safe to do this when there is no NAT involved. |
|