Call forwarding is not working properly

rybshik · 12-12-2008, 07:41 AM

as of time of writing this message. Instead of being forwarded according to my 'Call forwarding" settings, my incoming sip calls go to my voxalot voicemail. Possibly, due to the us.voxalot.com server failing to change/update my "Call forwarding" settings.

I have my IPkall DID routed to my_voxalot_ID@us.voxalot.com. And, subsequently, it is set to be call-forwarded to a landline number.

Everything worked well in the past.

Ron · 12-12-2008, 07:52 AM

I can't determine whether there was a temporary outage or other problem recently, but I'm registered with us.voxalot.com and it's working fine here at the moment.

Ron · 12-12-2008, 07:56 AM

Quote:

Originally Posted by rybshik

I have my IPkall DID routed to my_voxalot_ID@us.voxalot.com. And, subsequently, it is set to be call-forwarded to a landline number.

I haven't used IPKall in quite a while, but it used to be very slow (up to 60 minutes?) for any changes there to take effect.

rybshik · 12-12-2008, 07:58 AM

The problem is still there.

At the same time, I can use web-callback without any problems

Quote:

Originally Posted by Ron

I haven't used IPKall in quite a while, but it used to be very slow (up to 60 minutes?) for any changes there to take effect.

I have not changed my IPkall settings. I only changed my voxalot settings in "Call forwarding". It looks like my changes do not "propagate" to voxalot internal workings. Particularly, 'Inbound rule".

My Inbound Rule seems to be working only if set to 'Any', but not working if set to 'contains' with a US number in the (XXX) XXX-XXXX format. If I put just a partial number XXX-XXXX (without the area code), it is not working, either.

rybshik · 12-12-2008, 08:33 AM

Quote:

Originally Posted by Ron

You don't want anything in the incoming pattern matching rule except digits.

I only have digits, i.e. 312xxxxxxx.

Very very strange. Can you change your Inbound Rule to something different and see if it works? And then change it back and see if it works, too? In other words, can my problem have anything to do with not (timely) updating the Inbound Rule settings?

Finally, Can you please look at my voxalot settings?

Ron · 12-12-2008, 08:40 AM

I was incorrect. I thought my forwarding rule was working, but in fact, it is not. I've now tried 'equals', 'contains', and 'ends with', but the rule never takes. It would appear that either the CallerID from IPKall is faulty or the Voxalot pattern matching is not working. I don't have the capability to look at what's being received from IPKall, so that's about all I do from here.

rybshik · 12-12-2008, 08:46 AM

Quote:

Originally Posted by Ron

It would appear that either the CallerID from IPKall is faulty or the Voxalot pattern matching is not working.

As I said before, it did work well in the past (I mean IPKall+Voxalot), so it is clearly temporary issue, most likely on the Voxalot side.

Ron · 12-12-2008, 08:46 AM

Quote:

Originally Posted by rybshik

In other words, can my problem have anything to do with not (timely) updating the Inbound Rule settings?

Finally, Can you please look at my voxalot settings?

As far as I know, Voxalot forwarding rule changes should take effect immediately.

I don't have the ability to look at any of your settings.

rybshik · 12-12-2008, 09:06 AM

Quote:

Originally Posted by Ron

As far as I know, Voxalot forwarding rule changes should take effect immediately.

I don't have the ability to look at any of your settings.

I have just used my Callcentric DID instead of the IPkall DID, the problem is still there. So, it is definitely on the Voxalot side.

12-12-2008, 07:41 AM	#1
rybshik Member Join Date: Sep 2006 Location: Canada Posts: 67 Thanks: 7 Thanked 0 Times in 0 Posts	Call forwarding is not working properly as of time of writing this message. Instead of being forwarded according to my 'Call forwarding" settings, my incoming sip calls go to my voxalot voicemail. Possibly, due to the us.voxalot.com server failing to change/update my "Call forwarding" settings. I have my IPkall DID routed to my_voxalot_ID@us.voxalot.com. And, subsequently, it is set to be call-forwarded to a landline number. Everything worked well in the past. Last edited by rybshik; 12-12-2008 at 07:56 AM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
*500 not working	fpa2405	Site Information and Administration	15	01-05-2009 10:32 AM
Web CallBack not working	druids	Voxalot Support	0	05-13-2008 01:41 PM
VoXaLot not working with PBXes (VoXaLot as an extension of PBXes)	wilsonhlacerda	Voxalot Support	31	12-09-2007 02:30 PM
Does anyone have Incoming Calls working with a Voxbone, LES.NET or CallCentric DID?	richard	Voxalot Support	6	09-20-2007 02:00 PM
Voxalot incoming not working	RDP	Voxalot Support	34	11-18-2006 12:16 PM

12-12-2008, 07:52 AM	#2
Ron Join Date: Feb 2006 Posts: 447 Thanks: 4 Thanked 8 Times in 8 Posts	I can't determine whether there was a temporary outage or other problem recently, but I'm registered with us.voxalot.com and it's working fine here at the moment.

12-12-2008, 08:40 AM	#6
Ron Join Date: Feb 2006 Posts: 447 Thanks: 4 Thanked 8 Times in 8 Posts	I was incorrect. I thought my forwarding rule was working, but in fact, it is not. I've now tried 'equals', 'contains', and 'ends with', but the rule never takes. It would appear that either the CallerID from IPKall is faulty or the Voxalot pattern matching is not working. I don't have the capability to look at what's being received from IPKall, so that's about all I do from here.