Can someone refresh us on this issue? This is the problem I encountered during
my initial experience with sipXecs 4.0.2-4.0.4. It was 2 weeks of continuous
testing and I found what you guys are finding but I just thought this was
"normal" behavior. Just by ticking the enable Internet Calling, it all stopped
working. If left unticked, remote workers and internal workers all worked -
even SIP dialing works. I got confused as to why "Internet Calling" was even
required. I have sipXbridge as the default and NOT default gateway - multiple
permutations but same result with Internet Calling.
So can someone clarify if this is an issue with Internet Calling or other - bug
or actual desired result? I have my mind set on the working config as
discovered - or do I have to re-learn the actual correct proper setting?
>>The 'Enable Internet Calling' setting does break remote users if
>>sipXbridge is used as the SBC.
>>If you enable the 'Enable Internet Calling' setting remote users show as
>>not being behind NAT. If you disable that setting the NAT works
>>properly and the remote users are correctly identified as being behind a
>>NAT'd device.
>>If enabled the remote user can register and make calls but can not
>>receive calls (call goes directly to voicemail). The line I pointed out
>>earlier in the sipXbridge logs also complains about an invalid ITSP.
>>Disabling 'Enable Internet Calling' resolves this issue.
>>Mike
_______________________________________________
sipx-users mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/
