News: This forum is now permanently frozen.
Pages: [1]
Topic: Asterisk / Monowall compatibility problem  (Read 4963 times)
« on: May 13, 2008, 19:48:11 »
cliff *
Posts: 4

I recently installed PBX in a Flash (Asterisk/FreePBX) to replace Trixbox I was having trouble with.  I could not get everything working behind Monowall 1.3 B11 because of what I thought were NAT – port forwarding issues.   I set up another LAN behind a Linksys WRT54G router for testing remote extensions.  Friday I switched my Asterisk server from the Monowall LAN to the Linksys LAN and everything worked.  I played with setting all weekend and almost any change I made worked.  I moved Asterisk back to the Monowall LAN and attempted to clean my settings up but still couldn’t make Asterisk useable.  Yesterday, I set up a Monowall LAN using version 1.22 built on Sun April 2, 2006.  I moved my Asterisk server to this LAN and everything registered.  I’ve been testing for the past hour and everything appears to be working well behind the old Monowall.  Remote ATA’s from the Monowall 1.3 LAN are registering on odd ports between 24700-25300.   Both the device and server requests 5060 or 5061, but all remote extensions work.  Internal extensions and providers are using the designated ports.  I haven’t tested remote extensions from elsewhere yet.

Anyone have similar problem or know how I can fix this?

Network:  Verizon FiOS to Monowall, DDNS, FQDN, Web/mail/FTP server, Asterisk, workstations and notebooks, wireless and UMA/Cell phones.  Never a problem with Monowall until this.

Problems:  One way audio on SIP URI calls and calls from IPKall, remote extensions won’t register using externhost but will with externip.  One provider wouldn’t register with externIP.  As I play with settings I can sometimes get extensions to ring but 1 way or no audio …  When I moved Asterisk to either test LAN nearly all settings work either way.

History:  Used Monowall for about 4 years.  I used SIP from the beginning, multiple devices and providers then Asterisk  from 7-06.  I started noticing 1 way audio problems late last year and thought it was from Trixbox updates.
« Reply #1 on: May 16, 2008, 02:58:56 »
cliff *
Posts: 4

I moved all equipment to the Monowall 1.22/ Asterisk LAN and everything works well.  The remote SIP devices behind Monowall 1.33 continued to use the odd ports but worked.  Yesterday I moved them to the Linksys LAN and all registered on the requested ports and worked well.
« Reply #2 on: May 20, 2008, 20:00:33 »
cliff *
Posts: 4

Asterisk is now working flawlessly behind Monowall 1.2 with normal NAT settings and ports forwarded.  Remote extensions behind NAT work.  I attempted to check other versions of the beta 1.3 but couldn't find the older software.  I went back to 1.233 and remote extensions work on the correct ports.

Anyone else have Asterisk working with Monowall 1.3 or had problems solved by moving to 1.2?
« Reply #3 on: June 19, 2008, 22:32:28 »
brandilton *
Posts: 10

I have this same problem with Cbeyond/Switchvox/1.3b11

Cbeyond is sending the register request on port 5060 (which is open on NAT/FW with logging enabled).  Viewing the logs, I am not seeing anything on port 5060 (neither accepted nor rejected -- just not there)

Does this have something to do with the new SIP Proxy in 1.3bX that's not there in 1.2X?
 
Pages: [1]
 
 
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines