Forwarding not working

My calling forwarding is not working today. Anyone else having a problem. The line rings once and then goes to voice mail instead of being forwarded. Thanks

My call forwarding is also not working now for 3 weeks! I'm getting pretty upset and thinking about canceling my skype service. Anyone else know what is going on???

Similar Messages

Hairpin forwarding not working with CCME 4 and SIP

We are a VoIP provider and we're trying to install Cisco Unified CME 4.0 for a customer. IOS is 12.4(4)XC1 on a 2811. The customer will use our SIP service as his only outgoing trunk (no on-board ISDN or FXS cards).
On our SIP service we don't support call transfer or forwarding using the "302 Temporarily Moved" SIP method, for billing reasons. The customer needs to to hairpin routing and actually have the call go entirely through his equipment.
Following instructions, we tried enabling hairpin routing by issuing the following commands:
voice service voip
allow-connections sip to sip
no supplementary-service h450.2
no supplementary-service h450.3
supplementary-service h450.12
dial-peer voice 9000 voip
no supplementary-service h450.2
no supplementary-service h450.3
supplementary-service h450.12
Despite all this, when an ephone-dn has call forwarding enabled to an external SIP number, and a call comes in through the SIP trunk, our SIP server gets a "302 moved temporarily" message. It rejects this message and the call fails.
We even tried loopback-dn routing but we still get the same result.
Is there a way to force CCME to route the call through its inside even if it's coming and going from/to the same SIP trunk?
Thank you
-Manuel

Just an update: Davey's post was very helpful as it solved our "call forwarding not working" problem. The solution was to add the "service session" command to my voip dial peers. CME now hairpins forwarded calls correctly.
What still doesn't work at all is call transfer. If I receive an external SIP call and want to transfer it to another external SIP number, I just get the "unable to transfer call" error message on the phone, and both calls are just placed on hold. So it's not a permission problem - the call can be dialled correctly. But when hitting "transfer" the second time, CME doesn't "know" how to join them together (ie. hairpinning).
Cisco TAC's replies so far have been quite strange. I've been told that CME does not support hairpinning and that this is still being developed - apparently not, because call forwarding *does* work now. I'm only missing call transfer, then I'm all set :-)
Thank you
-Manuel

RV215W router port forwarding not working

RV215W router port forwarding not working.
Port forwarding works for a short period of time, then stops working. Reboot router, works again for short period of time, then stops again.
I have updated firmware to latest. I had seen other similar bugs posted for 220 and I think 180, not sure if this router has similar bugs and waiting for fix release to firmware.
I had recently purchased two, one deployed, will hold off on other now because of issues, and may have to move to different unit if a resolution not found this week.
Dave Gritten
IT Director
Maritime Beauty
3695 Barrington St
Halifax NS B3K 2Y3
cell 902.223.9685
phone 902.429.8510 ext231
fax 902.422.7983
[email protected]
www.MaritimeBeauty.com

It's not just single port forwarding that has bugs, the entire router has bugs and simply does not work as advertised. I have found the following bugs/aspects of this router that just does not work correctly: 1. If you have to open ports, and who doesn’t, this router will eventually stop accepting packets from WAN>LAN. You will still have Internet access but no open ports. A reboot will fix this problem. Oh, by the way, this router has no scheduled reboot option! <--That would be a workaround but a welcome one for this router. 2. Firewall Access rules do not work!! Yep, a Cisco router and basic functionality simply does not work. I called Cisco and even though the tech saw the router not working denied it was a bug! Said we have to do port mirroring, setup a workstation with WireShark and capture packets so we can debug the issues. That would take several hours. I told him I would have appreciated if Cisco would have debugged the issues with their router BEFORE they shipped the units. Stay away from Cisco Small Business Routers. I wish I had. And if there are any Cisco die-hards out there willing to prove me wrong, just reply to this and please, prove me wrong that the RV series and specifically the RV215W is not JUNK.

E4200 port forwarding not working (v1 1.0.05)

Hi there.
I'll try not to rant too much, but I've had nothing but problems with this 'supposed' high end router... and when I tried calling Cisco I got the old yee-ha to cough up $30 for tech support on a $200 router I got 10 months ago (/rant).
Anyway, following several speed drop issues with my router, I factory reset about 5 times. I later read in the internetz that QoS on these routers was causing the speed to fall to half no matter what settings are used, so I disabled QoS. This time I seem to have steady speeds, but no port forwarding method I use works! Used to work fine, but now Single PF, PF Range or anything else I can think of fails miserably. Even DMZ can't seem to open ports...
I am extremely disappointed in this router and please, don't advise me to factory reset: I've tried, it doesn't work and quite frankly I have way too many devices to painfully reconnect to not send me over the edge.
Please, if anyone has any idea what's going on, your help is more than welcome.
Thanks
-ts

technosinner wrote:
My setup is pretty simple: a Docsys3 modem through my ISP, piped to my Cisco E4200, and a few computers and devices connected to that, all on the same level (no switch or hub).
To my knowledge the modem doesn't filter or route anything, and I don't need to login or connect to my ISP - cable internet with direct filtering on the modem. I might have missed something but here is a question: if I open a port, will it show open even if there is no application to "receive" the connection? I'm asking because I'm starting to wonder if my server might be a bit fussy...?
To protect your router against possible DNS Rebinding Attacks, certain actions will not work from behind a router. Typically, doing this is for testing purposes. What you can do to test if a certain application (port forward) works remotely, is to do it from outside your network.
To test this functionality, this must be done from the outside of the router (remote area). This includes even if the “Filter anonymous Internet requests” is unchecked.
check the site below for reference:
http://blog.trendmicro.com/trendlabs-security-intelligence/protecting-your-router-against-possibl-dn...

Router Port Forwarding not working since Mavericks

I have an iMac sat behind a BT Home Hub 3 (an ADSL router, if you're not aware), with several ports (POP3, SSH, HTTP, etc) from the outside world forwarded via the hub to my Mac. Since installing Mavericks (from Snow Leopard), NONE of these ports are now open.
They're open on the Mac, and another machine on my home network can use them locally, but from outside the network, they're hidden. Shields Up shows them as Stealth.
Things I've tried:
Rebooting everything.
Setting the Home Hub up again, forwarding all the ports again.
Turning all the sharing off in Mavericks and then back on.
Trying the same services on different ports.
Trying different services.
Turning off the Mac firewall.
Turning off the router firewall.
Trying the Mac on another IP address and reforwarding everything to the new one.
Putting the Mac in the DMZ.
I can forward ports to other devices on my network (e.g. my NAS) and they work fine, so port forwarding isn't completely broken on the router
Here's the thing though...
On a completely separate network, on a separate Mac (a 2012 MacBook Pro) that went from Mountain Lion to Mavericks, also behind a BT Home Hub 3, EXACTLY the same thing is happening. No ports can be forwarded to the MacBook Pro, but all the ports are open to the local network.
Any ideas? I'm pretty sure this must be a bug in Mavericks as I can't see anything else it can be.

It's not just single port forwarding that has bugs, the entire router has bugs and simply does not work as advertised. I have found the following bugs/aspects of this router that just does not work correctly: 1. If you have to open ports, and who doesn’t, this router will eventually stop accepting packets from WAN>LAN. You will still have Internet access but no open ports. A reboot will fix this problem. Oh, by the way, this router has no scheduled reboot option! <--That would be a workaround but a welcome one for this router. 2. Firewall Access rules do not work!! Yep, a Cisco router and basic functionality simply does not work. I called Cisco and even though the tech saw the router not working denied it was a bug! Said we have to do port mirroring, setup a workstation with WireShark and capture packets so we can debug the issues. That would take several hours. I told him I would have appreciated if Cisco would have debugged the issues with their router BEFORE they shipped the units. Stay away from Cisco Small Business Routers. I wish I had. And if there are any Cisco die-hards out there willing to prove me wrong, just reply to this and please, prove me wrong that the RV series and specifically the RV215W is not JUNK.

Port Forwarding not working after 7.7.1 Firmware update

I bought the new 6th generation Airport Extreme today, and after I set it up, everything worked great. I have a VoIP phone that needs to have traffic on port 5060 forwarded to it, and that worked just fine as well.
However, I then updated to the 7.7.1 firmware, and the port forwarding stopped working. I tried a hard reset of the Airport and re-entered all the settings, but it still didn't work. I spent about 30 minutes on the phone with 2 Apple support people who tried hard, but couldn't help. They also couldn't find a way to download the 7.7 firmware, so there was no way to downgrade. They suggested I go back to the store and exchange it for another one, which I did, and now it all works again.
Has anyone else had issues with port forwarding on 7.7.1? I'm just wondering how I'll ever be able to update the firmware, since failure means having to get a new Airport.

Huh,
turns out the problem went away with another restart of the Mac Mini. I'm still uneasy about it though, as I do not understand how it went from working to not-working over night in the first place. But, at least for now, the problem seems gone.
Thanks for commenting.
Cheers
Niels Olof

Windows 8.1 socket forwarding not working

At one of our customers we had to add an enhanced generic Client application with the vpn socket forwarding mode. With this application we were able to open a special website on one internal server. Last week we updated to SP4 and saw that the socket forwarding
does not work on Windows 8.1. On Windows 7 everything is fine. Can anyone help?
Unfortunately we can not use the normal web application for this website. Some website features doesn't work this way.
Server hostname: srvxy
Port: 80
Executable: iexplore.exe
Arguments: http://srvxy/site

Hi Zuegi,
have you found way around this problem?
We have run onto this same issue with exactly same published application.

Servlet forward not working with portal and oc4j

Scenario: page1.jsp, page2.jsp, MyServlet
Page1.jsp posts a form to MyServlet which then does some processing and forwards to page2.jsp.
Tests:
Works fine as a standalone app under oc4j.
Does not work as oc4j-driven portlet under latest portal. Specifically, it conks out on the forward.
Question:
Why?
What is the suggested workaround?
Michael Mogley
Software Engineer
LRN, Inc.

James, thanks for responding but you are misunderstanding the problem. I have been able to do multipage and form-submit portlets as you describe for a long time. The issue is I am not able to use the jsp-forward directive within a validation servlet when using oc4j with portal. Here is what I'm trying to do in pseudocode:
EntryPoint.jsp
1. Enter form data.
2. Submit form to MyServlet.
MyServlet
1. Validate form.
2. If valid, <jsp-forward page="success.jsp"/>.
3. Else, <jsp-forward page="failure.jsp"/>.
The above works fine when used in an app running on oc4j outside of portal. It does not work when the same oc4j app is portletized. By the way, the portletized app WILL work if I change jsp-forward to jsp-include. So the problem is obviously in the forwarding.
Michael
I would try looking at the samples in the PDK-Java V2 that show how to do form input and multipage behavior. The form input shows you how to make a form in a portlet that when you submit it, the entered values appear in the portlet. The multipage portlet shows you how to have a portlet display one page and then when you click on a link, it shows you the second page.
It may make sense to copy the same code used for the samples and just tweak it to create a form that passes values from page1 to page2.
For more info on V2 parameters, see the article "A Primer on Parameters and Events" in the PDK-Previews (for subscribers to Developer Services only). You can also see the V1 article called "Understanding the Parameter Passing Portlet" for more info on parameter passing with portlets in V1.
James
James

UC320w call forwarding not working with SPA504?

I'm installing UC320W for customer and cfwd
all is not working? its just hang doesnot go anywhere
if anyone can help?
As well eventhough cfwd off, when call from outside and dial that extension now it says it has been forwarded!!
any one know or facing this? pl. help

I'm installing UC320W for customer and cfwd
all is not working? its just hang doesnot go anywhere
if anyone can help?
As well eventhough cfwd off, when call from outside and dial that extension now it says it has been forwarded!!
any one know or facing this? pl. help

Port forwarding not working on WRT54G v5 Firmware Version: v1.02.2

Hi
Yesterday i updated firmware on my WRT54G v5 from v1.00.1 to v1.02.2 and now port forwarding does not work.
I have 2 PCs connected to my router. Both PCs have static ip (192.168.1.103 & 192.168.1.105). DHCP server in the router is ofcourse disabled.
For some reason i can not get port forwarding it to work. The weird thing is that
ALL requests are now forwarded to 105 regardless how i configure.
* I have set up different port forwarding rules that points to my 103 PC.
* I have put the 103 PC in DMZ.
* I have disabled DMZ and removed all port forward rules.
Still ALL requests are forwarded to 105??
What i am doing wrong? Why does it default send everything to 105?
Note that I had no problems with port forwarding before the upgrade.
Everything was working fine.
I upgraded because i wanted a fix for "DynDNS abusive updates".
I have seearched the forum for tips and tried setting MTU size to 1396 and shutting down my entire network and then restart everything. Also tried to uncheck "Block Anonymous Internet Requests" but still same behaviour.
I really need help!!
Thanks
D_M

well it is weird...anyways try resetting the router back to factory default settings and reconfigure it...check whether it works for you or not.

WRT54G Port forwarding not working

Ok this is an odd problem. Ever since I got this router I have had issues with the port forwarding.
I am forwarding 3389 TCP to 192.168.1.101 check box is enabled. The .101 address is given out by DHCP ( only set to give out 4 IPs). The forwarding did not work at all. I have configured dozens and doezens of routers with no issues except this one . It is Version 8. After a lot of reading on the net someone posted a similar issue where they could not forward ports to static IP addresses ONLY IP's given out in the DHCP range. Strange? yes you bet. So I decided to try it and sure enough I changed my 2 internal computer IP's to use DHCP and forwarded the ports to the IP of the computer I wanted ( 192.168.1.101) and it worked! How silly is that, it wouldn;t forward to static IP's. Well now the problem is back. Except this time if I forward to static IP's OR IP's given out in DHCP nothing works. As a test I moved the .101 computer into the DMZ and still nothing. This is beyond annoying. problem is this is sitting at a clients house in another city and I only have access to it via the web admin. I tried backing up the configuration and then restoring it. The restore worked but didn't fix my issue. I still can't get the forwarding to work. Resetting the defaults is not really an option cause I am not in the same city as the router.
I have about 7 other SMC routers that have been working happily for 5 years straights. Why is this thing so mental? I did upgrade to the latest firmware before installing the router. Ayone have any suggestions as to why the forward doesn't work?.
By the way I enabled the logs and watch them as I was trying to remote into the computer ( 3389) and sure enough it's hitting the router ok as it shows up in the logs. The web server is not working either, nothing is getting forwarded.
No there are no firewalls at all installed on the computer I am trying forward to. Can anyone shed some light on this?

Access router setup page ...uncheck block WAN request under security tab .... also check the updated firmware on the router ....

Mail reply and forwarding not working

After using Mail for three years, suddenly the reply and forwarding functions do not work. The replies and forwards are in the Sent mail but do not reach the recipients.
I spoke to Mac support about 10 days ago and we created a new acct. and imported the emails. Things worked for awhile, but the same problem has started again.
When I use my Comcast web mail the replies and forwards do work.
No trouble receiving mail.
Thanks for your help.

Hello nina:
Welcome to Apple discussions.
Try rebuilding your mailbox(s).
Barry

Port Forwarding not working properly.

Router: WRT54G V.6
Firmware: 1.00.9
Basically, my port forwarding does not work. Using this link (https://www.grc.com/x/portprobe=55554), I can test a port to see if it's open or not.
Whenever I open a port on the router, it displays the port as "CLOSED", while I am aiming for "OPEN". This is a new router, and this problem also was occuring on my old V.2 one. Strangly, when I first tried opening the ports, it worked fine. Next day, it appeared as close, and no other settings were changed.
Any help out there? If any more information is needed, please tell me.

Only if grc reports the port "STEALTH" you have no port forwarding. If it is "CLOSED" then the port on the computer you are forwarding to has the port closed. You must check the settings on the computer where you forward to to see whether the port is open or not. Simply setting up a port forwarding does not open a port. It simply forwards everything to the ip address configured in the port forwarding. Thus, if the port is closed there it is closed and not open.

Hp 2.4 ghz wireless optical mobile mouse - back and forward not working

Hello everyone,
I bought an HP 2.4 ghz wireless optical mobile mouse, installed the drivers and sw in the CD that came with it, but I can't get the back/forward functions on the center wheel to work (neither on Chrome nor Windows Explorer).
My OS is Windows 7 Enterprise + SP1 (64-bit).
Could it be a driver/OS issue? Or should it work out of the box and is probably a hardware issue?
I have:
- uninstalled/reinstalled the drivers on the CD;
- uninstalled/reinstalled the drivers on the HP webpage;
- uninstalled/reinstalled the drivers on the HP webpage and then the ones on the CD (which i think made some sort of upgrade on the HP Mouse Suite).
What should I do to get back/forward to work?
Thank you in advance for your help.
Regards
This question was solved.
View Solution.

Just figured out the left/right arrows on the wheel are for horizontal scrolling only, and not back/forward.
Does HP plan to support the back/forward function in this mouse model? The hardware is there, it's just a matter of drivers.
The issue was solved via remapping the mouse keys with not-HP software. This is something a standard user would probably have trouble doing.
This is an entry level product, but 99% of the mouses I've seen that have center wheel left/right capabilities can be configurated to back/forward.

Port Forwarding not working between Fios Router and Netgear R6200 AT ALL

For the past two days I've been trying to forward port 80 and port 9000 from my Fios Router to my new NetGear R6200 Router and absolutely nothing is working. I need these ports open and forwarded as I need to forward them to my surveillance system from my R6200. The problem is that port forwarding is not working AT ALL. I've literally tried EVERYTHING. I turned my firewall off completely, enabled DMZ, changed my R6200 to a static IP, turned off uPnP on both sides, and reset my router to factory settings. I'm all out of patience and ideas. This is exactly why I went out and bought the R6200 in the first place, Verizon's Routers are atrocious.
Hardware:
First Router (Gateway): Verizon Fios Aciontec MI424WR
Second Router: NetGear R6200 Dual Band 802.11AC Router
Surveillance System DVR: Zmodo H9114 DVR
OS: Windows 8 Pro 64-Bit
At this point I'm willing to try anything. Fios customer support knew absolutely nothing and wasted my time and if a tech is sent to my house I'm sure the same exact outcome will occur. I recall someone saying that cloning the MAC of a different REV. worked for them but I don't recall the details. Any help would be greatly appreciated.

#1 As addressed in http://www.dslreports.com/faq/12506
The DHCP Server in the secondary router should be off.
#2 You only forward from the main router directly to the computer that you want to host on.
If you are the original poster (OP) and your issue is solved, please remember to click the "Solution?" button so that others can more easily find it. If anyone has been helpful to you, please show your appreciation by clicking the "Kudos" button.

Forwarding not working

Similar Messages

Maybe you are looking for