ubuntuman wrote:Falak, thank you fro the help. Now I got two different states for the "true" and "False". If I put register to true I got "Wait_Fail" or something like that but if I put register "false" I got "NOREG" state near cucm and our SIP IP.
Is this fine, what to do next?
Also, what about "Fax Number is not valid" or not found. What is the problem?
Guys you are very kind with us, however, you really need to improve the documentations and make things more clear and take out any vague out of it. I hope you'll have time for this.
Documentation and help is the soul of the FOSS world, I think!!
As you write above, this means your gateway is not configured properly if it says "Wait_Fail". Sometimes, however, there is no need to set register to true like in case of VOIPInnovations gateway. And simply setting register to false and status "NOREG" is fine.
As far as, CISCO UCM is concerned, I haven't tried configuring it with Freeswitch before. So I am in no position to tell you whether setting register to true is fine or it works with register status to false also.
First thing you can do to test whether your current configurations are working or not, try calling through your gateway on Freeswitch using following command. This will make it easy for you to test and debug your gateway. Write at command line /usr/local/freeswitch/bin/fs_cli and on the fs console write following:
- Code: Select all
originate sofia/gateway/cucm/your_number_to_dial &echo()
Where cucm is name of your gateway in Freeswitch that you configured. Replace your actual phone number in place of "your_number_to_dial" in the line above. If you have done connecting CUCM with Freeswitch, rest is trivial as ICTFAX uses commands similar to above to send / receive fax.
I also recommend you to see the following links to learn more on connecting CISCO UCM and Freeswitch:http://www.voip-info.org/wiki/view/Conf ... ll+Managerhttp://wiki.freeswitch.org/wiki/Cisco_Call_Managerhttp://freeswitch-users.2379917.n2.nabb%20...%2027811.html
I also ask other members to share if they have any information or pointers to solve this issue.