Am am complete novice when it comes to all things Cisco and IP based, so please bear that in mind when reading this post.
What I am trying to achieve is to set-up a SOHO PBX that utilises a Raspberry Pi as the device that runs the PBX software (FreePBX Asterisk based system) so that in the office where we are we can utilise the 2 avalable POTS lines coming in across more than 2 phones (have 4 at present, will be more eventually).
I have set-up the Pi so that all 4 phones can connect and call each other, but am having great difficulty getting this connected to the outside world.
As the connection to the outside world I have a 2621XM router that has a NM-1V and VIC 2FXO-EU.
What I am aiming to do is have calls from port 1/0/0 (extension #3521) route to FreePBX and connect to a dial-group #601 and calls on port 1/0/1 do the same, but go to dial-group #602. For outbound calls, I am wanting any phone to be able to dial out on any available line connected to the FXO card
At present, this is what I have on my router config (has been copied for second port, so only port 1/0/0 is shown)
input gain 10
output attenuation 10
connection plar opx 601
dial-peer voice 601 voip
session transport udp
session target ipv4:192.168.1.10:5060
session protocol sipv2
retry invite 3
retry bye 3
retry cancel 3
timers trying 1000
voice rtp serd-recv
In FreePBX have the following in both the Inbound and Outbound config ares for the SIP Trunk
At present am unable to have anything go to the Pi or have anything passed from there out.
What I am noticing is that if i dial the extension that is connected to the FXO card on port 1/0/0 then teh 'In Use'LED on port 1/0/1 comes on. I would have expected it to come on on teh port that was receiving the call. This is what is confusing me (amongst several other things)
If anyone can please help that would be greatly appreciated. As I have said and as you can see, I know next to nothing on this and am on a very steep learning curve indeed.
Looking into that now. Found a post on teh FreePBX forum for installing a module that is supposed to allow H323 trunks. Working on getting that installed (also teaching myself some Linux in this project too)
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
[toc:faq]CUCM Database Replication is an area in which Cisco customers
and partners have asked for more in-depth training in being able to
properly assess a replication problem and potentially resolve an issue
without involving TAC. This document discusse...