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" <[email protected]>
wrote:
> and you nature outbound is not right. refer to my blog.
> On Jul 20, 2011 12:55 PM, "Tony Graziano" <[email protected]>
> wrote:
>> destroy your state table and restart siptrunking.
>> On Jul 20, 2011 12:18 PM, "William Salt" <[email protected]> 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]
>>>> 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
>>>>
>>>>
>>>>
>>>> On Wed, Jul 20, 2011 at 11:28 AM, William Salt <[email protected]
>>>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]> 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 <
[email protected]
>>>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, 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]
>>>>>>> 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/
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> ======================
>>>> 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/

Reply via email to