> Great feedback...answers/comments below:
> 
> 1.  Interestingly, I configured the intranets on the sip 
> server to include only 172.20.1.0/24. The wiki recommends 
> removing the defaults and adding back an entry that is 
> representative of your network.  Is there a config file or db 
> that I can probe to ensure it's really been set correctly?

Very odd because seems to treat 172.20.1.213 as an endpoint that is not inside 
your private network.  You can check the subnet(s) listed under 
<localtopology><ipV4subnet> in file /etc/sipxpbx/nattraversalrules.xml.

> 
> 2.  I'll look around for a different iPhone sip client to 
> compare behavior with.  I have no affinity for the acrobits 
> client, especially given it's apparent misbehavior. I may be 
> able to substitute an x-lite soft client on a remote NAT 
> network to work around the issue in the meantime as well.
> 
> sdm
> 
> 
> On May 11, 2010, at 4:21 PM, "JOLY, ROBERT \(ROBERT\)"  
> <rj...@avaya.com> wrote:
> 
> >>
> >> Posting failedcase.pcap for review.
> >>
> >> Here's a brief on the players in the trace:
> >> -------------------------------------------
> >> Extension 18 (166.137.14.58) : iphone (remote sip soft phone) 
> >> Extension 13 (172.20.1.213)  : office (local sip hard phone) Sipx 
> >> server  (172.20.1.102)
> >>
> >> Please let me know if you have toplogy questions/etc...thanks in 
> >> advance.
> >
> > I looked at the trace you sent me and you have at least two 
> problems:
> > 1- It does not look like the Intranet topology you enteted 
> in System-
> > >Internet Calling->Intranet subnets actually reflects what your
> > network looks like.  Does not sound like 172.20.1.0/24 is 
> included in 
> > the specified range.  What range of Ips do you have there?
> > 2- The iPhone client you are using has a rather severe 
> deviation from 
> > standard SIP.  The ACKs it sends out are addressed to the value
> > we put in the Record-Route as opposed to the other end's contact.   
> > Even if you fix #1, #2 is going to be a killer.
> >
> > Let me know,
> > bob
> >
> >
> >>
> >> sdm
> >>
> >>> -----Original Message-----
> >>> From: JOLY, ROBERT (ROBERT) [mailto:rj...@avaya.com]
> >>> Sent: Tuesday, May 11, 2010 10:43 AM
> >>> To: Stephen D. Miller; sipx-users@list.sipfoundry.org
> >>> Subject: RE: Another remote worker configuration question...
> >>>
> >>>>
> >>>> I have a newly installed sipxecs 4.2 system (replaced a
> >> previously
> >>>> installed v3.10 system).  System is behind a NAT firewall.
> >>> All works
> >>>> as expected (internal extension to extension calls,
> >> outbound calls,
> >>>> inbound calls, etc). I have also followed the v4.2 remote worker 
> >>>> config guide and configured the server accordingly (port
> >>> forwarding,
> >>>> local subnet specified, etc).
> >>>>
> >>>> I have installed Acrobits SIP client on an iPhone and
> >>> configured it as
> >>>> an extension in sipxecs.  Using the local WiFi network, the
> >>> iPhone SIP
> >>>> client registers and can call/communicate with any extension as 
> >>>> expected.
> >>>>
> >>>> Using 3G, the Acrobits SIP client registers properly and 
> can call 
> >>>> internal extensions, but the media streams (RTP) are never 
> >>>> established.
> >>>>
> >>>> I have captured the net traffic at the server in the
> >>> failure case and
> >>>> it appears that the RTP traffic inbound from the
> >>>> (remote) iPhone is arriving at the sipxecs server and is being 
> >>>> properly sent on to the internal extension.  However, I
> >>> don't see any
> >>>> RTP traffic heading outbound to the iPhone.  I think this is the 
> >>>> problem...
> >>>>
> >>>> Does anyone have recommendations for further diagnosing
> >>> this scenario?
> >>>> I can post a wireshark capture of the traffic in the
> >>> failure case...if
> >>>> that's helpful.
> >>>
> >>> That would be most helpful.  Here is the best way to take a
> >> capture on
> >>> sipXecs: tcpdump -n -nn -s 0 -i  any -w failed.cap
> >>>
> >>> This will show me all the info that is required to point at
> >> something.
> >>>
> >>>
> >>>> _______________________________________________
> >>>> sipx-users mailing list sipx-users@list.sipfoundry.org 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/
> >>>>
> >>>
> >>
> 
_______________________________________________
sipx-users mailing list sipx-users@list.sipfoundry.org
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/

Reply via email to