Cheers i am hassling AQL to try and resolve the issue now. As soon as i tried a different ITSP (voipfone.net) everything worked instantly.
Many thanks for all your help in this. On Fri, Jul 22, 2011 at 12:08 AM, Tony Graziano < [email protected]> wrote: > if that is not working you need to ask the itspcwhat ip they are sending > the calls from. > > if sipx doesn't know its a gateway. all to port 5080 it will be "dead air". > On Jul 21, 2011 6:48 PM, "William Salt" <[email protected]> wrote: > > The problem still persists. > > I have now got the ITSP to respond back on port 5080. i cannot however > > register to them on 5080, is this a problem? > > > > Would anyone be kind enough to look at my snapshot and pcap dumps of > > registration and attempting to answer an inbound call and it dropping? > > > > many thanks > > Will > > > > > > > > On Wed, Jul 20, 2011 at 9:01 PM, Tony Graziano < > [email protected] > >> wrote: > > > >> Let's understand perfectly why this sort of behavior happens. > >> > >> If the call is sent to sipx on port 5060, it is considered a sip call > >> (media relay), and so call transfers using refer are not handled by > >> sipxbridge, and the call drops. The call is not anchored and sipxbridge > is > >> not involved in the call. The media is peer to peer and is not anchored > by > >> sipxbridge, the media is just being relayed by media-relay. > >> > >> Calls sent to port 5060 assume the ua at both ends supports refer. > Polycom > >> supports REFER, but if the itsp does not, the call drops because > sipxbridge > >> is not in between calls sent on port 5060, just on port 5080. sipxbridge > >> handles the refer internally so it can act as a b2bua, which is exactly > what > >> it is, a b2bua, hence it is also anchoring the media and the call state, > and > >> sees calls coming to it on port 5080 and hence how the system is able to > >> determine sip calls from trunk calls. > >> > >> > >> > >> On Wed, Jul 20, 2011 at 3:52 PM, <[email protected]> wrote: > >> > >>> Hello Will. > >>> When I had the same problem (ITSP was sending SIP messages on 5060, not > >>> 5080) I asked my ITSP to send SIP on 5080 and everything was ok. > >>> But you must be sure about the reason off call failing. But it really > >>> seems to be so, because when ITSP sends SIP on 5060, media can't go via > >>> SBC (if SBC port is not 5060) and can't pass your NAT/Firewall. Anyway, > >>> you need to make a sip-trace file, watch it via sip-viewer and find out > >>> where the problem is. Good luck. > >>> > >>> On Wed, 20 Jul 2011 20:40:53 +0100, William Salt > >>> <[email protected]> wrote: > >>> > I have now set symmetric nat internally and externally for ports > >>> > 5060-5061 5080-5081 and 30000-31000. > >>> > I still get the same problem of the inbound call failing on pickup. > >>> > > >>> > I have tcp dumped the ITSP registration process and i see the pbx > >>> > asking for a reply on 5080, but instead i see the ITSP (aql.com [1]) > >>> > replying on 5060. > >>> > > >>> > Is this the ITSPs problem, would a fix be to use another UK based > >>> > ITSP (any recommendations?) > >>> > > >>> > Cheers > >>> > Will > >>> > > >>> > On Wed, Jul 20, 2011 at 6:38 PM, Tony Graziano wrote: > >>> > > >>> > make sure manual outbound nat is checked. make sure static port nat > >>> > is used on all nat assignments for sipx. make sure sipxroxd is u > >>> > installed in pfsense. > >>> > > >>> > On Jul 20, 2011 12:56 PM, "Tony Graziano" wrote: > >>> >> and you nature outbound is not right. refer to my blog. > >>> > > On Jul 20, 2011 12:55 PM, "Tony Graziano" > >>> >> wrote: > >>> >>> destroy your state table and restart siptrunking. > >>> > >> On Jul 20, 2011 12:18 PM, "William Salt" wrote: > >>> >>>> I was under the impression i could use nat to NAT port 5080 > >>> > externally to > >>> > >>> port 5060 internally to the SBC? > >>> >>>> I have just changed the ITSP to register on port 5080, and > >>> > removed > >>> >>>> my natting on my pfsense box, so it is natting those ports to > >>> > eachother > >>> > >>> internally and externally... > >>> > >>> It wont register, so i will ask my ITSP. > >>> >>>> > >>> >>>> Regards > >>> >>>> Will > >>> >>>> > >>> >>>> On Wed, Jul 20, 2011 at 4:36 PM, Tony Graziano < > >>> >>> [email protected] [6] > >>> > >>>> wrote: > >>> >>>> > >>> >>>>> the itsp won;t work unless you can register to them on port 5080 > >>> > and > >>> >> they > >>> >>>>> send you calls on port 5080. > >>> >>>>> > >>> >>>>> your firewall is not configured properly either and is not using > >>> > >> symmetric > >>> >>>>> nat. what firewall is it? > >>> >>>>> > >>> >>>>> consider another firewall (perhaps pfsense) > >>> >>>>> > >>> >>>>> http://blog.myitdepartment.net/?p=52 [7] > >>> > >>>> > >>> >>>>> > >>> >>>>> > >>> >>>>> On Wed, Jul 20, 2011 at 11:28 AM, William Salt >>wrote: > >>> > >>>> > >>> >>>>>> Hi Tony, > >>> >>>>>> Thanks for the help. > >>> >>>>>> > >>> >>>>>> > >>> >>>>>> 1. Im registering a static IP to the ITSP (our external one) > >>> > >>>>> 2. they are sending calls to 5060, and im natting them to 6080 > >>> >>>>>> internally > >>> >>>>>> 3. Im not sure looks like from a tcpdump i am registering on > >>> > UDP port > >>> >>>>>> 5060 to them, and 62941 locally. > >>> > >>>>> > >>> >>>>>> From then, i am contacting the ITSP on port 5060 and they are > >>> >> contacting > >>> >>>>>> me on UDP 62941. > >>> >>>>>> Im guessing this is because i have registered with them on that > >>> > port, > >>> > >> and > >>> >>>>>> they are then responding to me via that port, with my firewall > >>> > keeping > >>> >>> the > >>> >>>>>> state of that port. > >>> >>>>>> > >>> >>>>>> I am using pfsense 1.2.3, which shouldn't be a problem? > >>> > >>>>> > >>> >>>>>> Regards > >>> >>>>>> Will > >>> >>>>>> > >>> >>>>>> > >>> >>>>>> On Wed, Jul 20, 2011 at 2:46 PM, Tony Graziano < > >>> >>>>>> [email protected] [9]> wrote: > >>> > >>>>> > >>> >>>>>>> Are you registering or using a static IP to the ITSP? Are they > >>> > sending > >>> >>>>>>> the calls to port 5080 or 5060? If you register does the > >>> > provider > >>> >> allow > >>> > >> you > >>> >>>>>>> to confirm ip and port they see you registering on? > >>> >>>>>>> > >>> >>>>>>> It would appear (and you can confirm) that the call is coming > >>> > in to > >>> > >> port > >>> > >>>>>> 5060 from the ITSP in the initial invite on inbound calls. > >>> >>>>>>> > >>> >>>>>>> Is you NAT static port NAT (symmetric ports) or dynamic? What > >>> > is the > >>> >>>>>>> firewall? > >>> > >>>>>> On Wed, Jul 20, 2011 at 9:43 AM, William Salt >>wrote: > >>> >>>>>>> > >>> >>>>>>>> Hi All, > >>> > >>>>>>> I am new to SipXecs, but I have worked with a couple of voip > >>> >>>>>>>> pbx's before. Ive got a few days to set up a PBX in our > >>> > office, and > >>> >> so > >>> >>> far i > >>> > >>>>>>> am struggling to find a solution to the problem i am > >>> > experiencing. So > >>> >>> id > >>> >>>>>>>> really appreciate it if someone would reach out and help me. > >>> >>>>>>>> > >>> > >>>>>>> I have a sip trunk from aql.com [11], and have configured > >>> > it, it seems to > >>> >>>>>>>> work (mostly) > >>> >>>>>>>> I can make outbound calls to mobiles, landlines etc fine, and > >>> > audio > >>> > >> and > >>> >>>>>>>> sessions establish and terminate fine. > >>> >>>>>>>> However, i cannot complete inbound calls, the internal phone > >>> > will > >>> >>> ring, > >>> >>>>>>>> and upon answering the call will terminate, however, the > >>> > external > >>> > >> callers > >>> >>>>>>>> call will connect and stay connected untill they hang up. > >>> >>>>>>>> > >>> >>>>>>>> I have my firewall + NAT rules configured correctly (ports > >>> > external > >>> > >>>>>>> 5080-5081 = 5060-5601 internally + 30000-31000) > >>> >>>>>>>> i have configured a dialplan from the username of the VOIP > >>> > provider > >>> >> to > >>> >>>>>>>> the internal extension. > >>> > >>>>>>> > >>> >>>>>>>> I have wireshark dumps, and a snapshot if anyone would have a > >>> > look at > >>> >>>>>>>> these, and possibly help diagnose my problems, i would > >>> > >>>>>>> greatly appreciate this. > >>> >>>>>>>> > >>> >>>>>>>> Regards > >>> >>>>>>>> Will > >>> >>>>>>>> > >>> >>>>>>>> > >>> > >>>>>>> _______________________________________________ > >>> >>>>>>>> sipx-users mailing list > >>> >>>>>>>> [email protected] [12] > >>> > >>>>>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ > >>> > [13] > >>> >>>>>>>> > >>> >>>>>>> > >>> > >>>>>> > >>> > >>>>>> > >>> >>>>>>> -- > >>> >>>>>>> ====================== > >>> >>>>>>> Tony Graziano, Manager > >>> >>>>>>> Telephone: 434.984.8430 > >>> >>>>>>> sip: [email protected] [14] > >>> > >>>>>> Fax: 434.326.5325 > >>> >>>>>>> > >>> >>>>>>> Email: [email protected] [15] > >>> >>>>>>> > >>> > >>>>>> LAN/Telephony/Security and Control Systems Helpdesk: > >>> > >>>>>> Telephone: 434.984.8426 > >>> >>>>>>> sip: [email protected] [16] > >>> >>>>>>> > >>> >>>>>>> Helpdesk Contract Customers: > >>> > >>>>>> http://support.myitdepartment.net [17] > >>> >>>>>>> > >>> >>>>>>> Blog: > >>> > >>>>>> http://blog.myitdepartment.net [19] > >>> >>>>>>> > >>> >>>>>>> Linked-In Profile: > >>> >> http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 [20] > >>> > >>>>>> > >>> >>>>>>> > >>> >>>>>>> _______________________________________________ > >>> >>>>>>> sipx-users mailing list > >>> >>>>>>> [email protected] [21] > >>> > >>>>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ > >>> > [22] > >>> >>>>>>> > >>> >>>>>> > >>> >>>>>> > >>> > >>>>> _______________________________________________ > >>> >>>>>> sipx-users mailing list > >>> >>>>>> [email protected] [23] > >>> > >>>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ > >>> > [24] > >>> >>>>>> > >>> >>>>> > >>> >>>>> > >>> > >>>> > >>> > >>>> -- > >>> >>>>> ====================== > >>> >>>>> Tony Graziano, Manager > >>> >>>>> Telephone: 434.984.8430 > >>> >>>>> sip: [email protected] [25] > >>> > >>>> Fax: 434.326.5325 > >>> >>>>> > >>> >>>>> Email: [email protected] [26] > >>> >>>>> > >>> >>>>> LAN/Telephony/Security and Control Systems Helpdesk: > >>> > >>>> Telephone: 434.984.8426 > >>> >>>>> sip: [email protected] [27] > >>> >>>>> > >>> >>>>> Helpdesk Contract Customers: > >>> > >>>> http://support.myitdepartment.net [28] > >>> >>>>> > >>> >>>>> Blog: > >>> > >>>> http://blog.myitdepartment.net [30] > >>> >>>>> > >>> >>>>> Linked-In Profile: > >>> > http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 [31] > >>> > >>>> > >>> >>>>> > >>> >>>>> _______________________________________________ > >>> >>>>> sipx-users mailing list > >>> >>>>> [email protected] [32] > >>> > >>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ > >>> > [33] > >>> >>>>> > >>> > > >>> > _______________________________________________ > >>> > sipx-users mailing list > >>> > [email protected] [34] > >>> > List Archive: http://list.sipfoundry.org/archive/sipx-users/ [35] > >>> > > >>> > > >>> > > >>> > Links: > >>> > ------ > >>> > [1] http://aql.com > >>> > [2] mailto:[email protected] > >>> > [3] mailto:[email protected] > >>> > [4] mailto:[email protected] > >>> > [5] mailto:[email protected] > >>> > [6] mailto:[email protected] > >>> > [7] http://blog.myitdepartment.net/?p=52 > >>> > [8] mailto:[email protected] > >>> > [9] mailto:[email protected] > >>> > [10] mailto:[email protected] > >>> > [11] http://aql.com > >>> > [12] mailto:[email protected] > >>> > [13] http://list.sipfoundry.org/archive/sipx-users/ > >>> > [14] mailto:[email protected] > >>> > [15] mailto:[email protected] > >>> > [16] mailto:[email protected] > >>> > [17] http://support.myitdepartment.net > >>> > [18] http://support.myitdepartment.net > >>> > [19] http://blog.myitdepartment.net > >>> > [20] http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 > >>> > [21] mailto:[email protected] > >>> > [22] http://list.sipfoundry.org/archive/sipx-users/ > >>> > [23] mailto:[email protected] > >>> > [24] http://list.sipfoundry.org/archive/sipx-users/ > >>> > [25] mailto:[email protected] > >>> > [26] mailto:[email protected] > >>> > [27] mailto:[email protected] > >>> > [28] http://support.myitdepartment.net > >>> > [29] http://support.myitdepartment.net > >>> > [30] http://blog.myitdepartment.net > >>> > [31] http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 > >>> > [32] mailto:[email protected] > >>> > [33] http://list.sipfoundry.org/archive/sipx-users/ > >>> > [34] mailto:[email protected] > >>> > [35] http://list.sipfoundry.org/archive/sipx-users/ > >>> > >>> _______________________________________________ > >>> 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.326.5325 > >> > >> Email: [email protected] > >> > >> LAN/Telephony/Security and Control Systems Helpdesk: > >> Telephone: 434.984.8426 > >> sip: [email protected] > >> > >> Helpdesk Contract Customers: > >> http://support.myitdepartment.net > >> > >> <http://support.myitdepartment.net>Blog: > >> http://blog.myitdepartment.net > >> > >> Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 > >> > >> > >> _______________________________________________ > >> 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/ >
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
