Well the transport layer is secure anyway... On Thu, Dec 29, 2011 at 12:36 PM, Pete Burgess <[email protected]> wrote:
> Thanks for the pointers. I’ll check out the configs and go from there.**** > > ** ** > > As for why I’m registering on 5061, it would just appear to be more secure > to me. My understanding is that if I do everything via TLS then a) it’s > encrypted and b) I don’t have to put up with potential LD/International > call scammers banging away at my port 5060 trying to find a way in. My > standard disclaimer applies here… I’m not a SIP expert and my understanding > is a bit limited. Ask me to do a VMware design and we’re on a roll, but > SIP’s still not my cup of tea – I’m an old school AT&T Definity guy.**** > > ** ** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Tony Graziano > *Sent:* Thursday, December 29, 2011 12:19 PM > > *To:* Discussion list for users of sipXecs software > *Subject:* Re: [sipx-users] Remote Users**** > > ** ** > > I don't think you follow me. HOW you have the Bria configured means a lot. > I use 3cs on my iphones. I use eith csipsimple or on ICS I use the native > sip account function (fine for wifi). I also use Patton gateways. I never > have a problem with this.**** > > ** ** > > There are settings in different UA's on how they handle STUN and NAT and > whether they send an internal ip address. You need to make sure > STUN/NAT/TURN is off and if there is an option to use the local (internal) > IP address, you should select it.**** > > ** ** > > Beyond that I'll leave this for an iphone afficionadio to address. **** > > ** ** > > Why are you registering to 5061 (deselect TLS in the UA if you have it > selected).**** > > ** ** > > Good luck.**** > > On Thu, Dec 29, 2011 at 11:36 AM, Pete Burgess <[email protected]> wrote: > **** > > Hi Tony**** > > **** > > Actually the UA seems to be acting fine. As I mentioned, I can make > internal calls so I’m not too worried about that. The problem is when an > outside call is made. Hooked up Briapath and pulled a log and here’s what I > get…**** > > **** > > [11-12-18]19:25:39.248 | Debug | RESIP:DUM | "mRemoteTarget: < > sip:[email protected]:5060;user=phone;transport=tcp>" | **** > > **** > > Now I don’t know SIP well enough to know if the above line is just a “hey, > here’s what’s going on at the backend” message or if the softphone is > trying to connect to 172.20.23.3, which is my Mediant. If that’s the case > then it’s not going to work as the call is being proxied to a private IP > address which is, obviously, not available externally.**** > > **** > > **** > > **** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Tony Graziano > *Sent:* Thursday, December 29, 2011 11:08 AM > *To:* Discussion list for users of sipXecs software > *Subject:* Re: [sipx-users] Remote Users**** > > **** > > You ought to describe what iphone UA (app) you are using.**** > > **** > > #1: you should be registering over port 5060 (not 5061). 5061 assumes > tls/encryption, which will be quite a burden on any portable IMO. It's also > not fully functional in sipx with every UA yet either.**** > > #2: You should inspect your registration and make sure it states the > proper syntax for your registration.**** > > ex: sip:[email protected] < > sip:[email protected]:44252;x-sipX-privcontact=192.168.101.1>**** > > or**** > > sip:[email protected] <sip:[email protected]:5060;x-sipX-nonat> **** > > **** > > The UA is probably not able to send your local IP as its internal address > so the contact address is wrong.**** > > **** > > Try 3cx!**** > > On Thu, Dec 29, 2011 at 10:21 AM, Pete Burgess <[email protected]> wrote: > **** > > Hi folks**** > > **** > > I’ve been doing some testing with a Sip client on an iPhone and I’m having > problems. Essentially, I have port 5061 open to the internet and I can make > internal calls just fine, i.e. I hook my iPhone up to my wireless internet > at home, connect to the public IP of the SipX server, dial an extension > number and it’s all good.**** > > **** > > Dialling out to an external number, i.e. 1xxx xxx xxxx results in a failed > call. Looking at the logs, this is because of the way the call is routed… > SipX sends the call to an Audiocodes Mediant 800 on a private IP address. > The SIP header shows the call being connected from the IP of my iPhone > (public) via SipX (public) to the private IP of the Mediant. Thinking about > it I guess this is expected behavior. Any way around this ?**** > > **** > > Thanks**** > > > Pete**** > > **** > > **** > > ___________________________________________________**** > > Pete Burgess > Integrated Technical Services > 919.674.0044**** > > www.itsco.com**** > > **** > > Advanced Engineering Services**** > > *Aruba Networks, Barracuda, EMC/VMware, Microsoft, Cisco, Linux, Symantec* > **** > > *Data Center, Business Continuity, Software and Systems Design > IT Management Consulting, Enterprise LAN/WAN and***** > > *Carrier Network Services***** > > **** > > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/**** > > > > **** > > **** > > -- > ====================== > Tony Graziano, Manager > Telephone: 434.984.8430 > sip: [email protected] > Fax: 434.465.6833 > > Email: [email protected] > > LAN/Telephony/Security and Control Systems Helpdesk: > Telephone: 434.984.8426 > sip: [email protected] > > Helpdesk Customers: http://myhelp.myitdepartment.net > Blog: http://blog.myitdepartment.net > > Linked-In Profile: > http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 > Ask about our Internet Fax services!**** > > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/**** > > > > **** > > ** ** > > -- > ====================== > Tony Graziano, Manager > Telephone: 434.984.8430 > sip: [email protected] > Fax: 434.465.6833 > > Email: [email protected] > > LAN/Telephony/Security and Control Systems Helpdesk: > Telephone: 434.984.8426 > sip: [email protected] > > Helpdesk Customers: http://myhelp.myitdepartment.net > Blog: http://blog.myitdepartment.net > > Linked-In Profile: > http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 > Ask about our Internet Fax services!**** > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- Michael Picher, Director of Technical Services eZuce, Inc. 300 Brickstone Square**** Suite 201**** Andover, MA. 01810 O.978-296-1005 X2015 M.207-956-0262 @mpicher <http://twitter.com/mpicher> www.ezuce.com
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
