Let me elaborate... I see the same problem with providers who do not send rtp on from the same address the invite comes from. This usually becomes a problem especially when you use more than one wan connection. On Dec 13, 2011 1:43 PM, "Tony Graziano" <[email protected]> wrote:
> You would need a sip trace to make sure it sends the invite on port 5080 > and from the expected ip address or gateway with your provider. > > Then we would want to make sure it does a proper reinvite for t.38. > > I suspect it does not come from the same provider gateway but the best > thing to do is to get a trace of the call. > On Dec 13, 2011 1:14 PM, "Ly Tran" <[email protected]> wrote: > >> We have an unusual problem with one of our DIDs not working correctly >> and cannot seem to figure out. If someone have experienced this before or >> can point me in the right direction, it would be appreciated. We have the >> most current sipx version loaded. PBX has been restarted. All other DIDs >> works correctly for incoming/outgoing calls. This one DID was used as a >> t.38 fax alias and had been working properly, until now and cannot receive >> any faxes. We have 14 other DIDs used for f t.38 faxing and they work >> fine. In testing, we removed this DID from the fax alias and assigned it >> to a user/phone. We can dial the phone internally using the extension and >> dial outbound calls, but cannot receive incoming to this DID. Dialing this >> number externally only gets “dead air”. The PBX does not seem to pick up >> the call and route.**** >> >> ** ** >> >> Ly Tran**** >> >> ** ** >> >> _______________________________________________ >> sipx-users mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >> >
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
