Search results

I've only made changes via the web frontend. To ensure it wasn't something I did, I redeployed a VM snapshot I took after building the server. Now it seems to be working some what. built the basic extension and registered it. Verified incoming call the FS works. Then built the gateway and...

I turned on every log I could find. Attached. The CM IP is 10.172.174.144

The 10.172.193.151 is the Zoiper softphone calling the 11 digit number. the error is 404. 2017-11-27 14:48:25.711335 [NOTICE] switch_core_state_machine.c:312 Hangup sofia/internal/2352999@10.172.210.190 [CS_ROUTING] [NO_ROUTE_DESTINATION] I can place an inbound call the that extension without...

That's what I would think as well, but instead I see the IP of the FS and not the IP of the Aavay_CM. 2017-11-27 14:13:16.271429 [WARNING] sofia_reg.c:1792 SIP auth challenge (INVITE) on sofia profile 'internal' for [18005551212@10.172.210.190] from ip 10.172.193.151 Is there anyway to force it?

This is my gateway setup. Nothing in the advanced section and adding the CM as the Proxy, still does not send the correct SIP invite. What am I missing here?

I've been testing Freeswitch/FusionPBX with our Avaya 6.3 CM. I have inbound calls working with a SIP trunk from the Avaya to Freeswitch on port 5080. I am unable to get an outbound call working. I setup the Avaya CM as an unregistered gateway and added a outbound route. Each time a place a test...