Incoming Calls Drop or No Audio - Page 3

All4Fun · 07-26-2009, 06:46 PM

Quote:

Originally Posted by boatman

Try pointing your voip.ms SIP URI forwarding to your number at voxalot.com, not us.voxalot.com, 123456@voxalot.com, not 123456@us.voxalot.com.

I don't have a DID at my voip.ms account, but if there's a way I can test forwarding from voip.ms to my Voxalot account, let me know and I'll give it a try.

I have a DID at voip.ms you can test with. If you're willing, send me the SIP URI to forward to by PM and I'll send you the DID you can use.

I'll also make the SIP URI changes that you are suggesting and test again.

boatman · 07-26-2009, 09:25 PM

The Wireshark packet capture points to a problem with voip.ms. The events happened as follows:

Call comes from User-Agent: VoIPMS/SERAST with Connection Information (c): IN IP4 24.102.60.67

I answered the call on a PAP2.

About 0.11 sec. later VoIPMS/SERAST sent SIP re-invite with Connection Information (c): IN IP4 67.205.74.164.

PAP2 begins sending RTP to 67.205.74.164 and receiving RTP from 24.102.60.67.

For some reason the RTP outbound from PAP2 to 67.205.74.164 does not reach the party calling on the DID, therefore calling party hears nothing.

You should contact support at voip.ms. I can send you the packet capture if needed.

All4Fun · 07-26-2009, 09:55 PM

boatman, I wish there was more than "Thank You" for the amount of time and effort you have put into trying to resolve my problem. Admittedly, I was prepared to give up a long time ago.

The good news is that we know what's occurring. The bad news is that the problem still exists and is largely out of our control. I hope that voip.ms is willing to help.

I will likely need that packet capture when I do this all over again with voip.ms.

All4Fun · 07-27-2009, 01:36 AM

Great news!!!

After sending an email to voip.ms support about this issue, they just responded letting me know that they made a routing change on my account. I did a quick test and it worked. Audio is working both ways now.

I will need to monitor for the next few days but it looks like I'm back in the mix with VoXalot.

Considering the support that I've gotten here and at voip.ms (even over the weekend), I know that I've picked the right combination to provide me most of my phone needs.

And it didn't cost me a red cent but my sincere gratitude.

All4Fun · 07-31-2009, 10:55 PM

As a follow-up, I asked voip.ms what they did to resolve my problem and their response was that they "...prevented the RTP from being re-invited."

While I don't know what that means, I'm hoping the info will be of benefit to boatman and any others going forward who have this problem.

Needless to say, I've had no issues since the change was made by voip.ms a several days ago.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Free DID Numbers, Free Voip Calls, & more Voip Info	amroe	Voxalot General	54	01-13-2014 09:11 AM
incoming sip calls going directly to voicemail	vishal3110	Voxalot Support	8	12-13-2008 12:17 AM
Some incoming SIP URI dialed calls slient	Tylo	Voxalot Support	9	04-09-2008 05:24 PM
All incoming calls failing	richard	Voxalot Support	1	09-15-2007 05:42 PM
Nor receiving incoming calls	Sharps1	Voxalot Support	1	10-16-2006 12:38 PM

07-26-2009, 09:25 PM	#22
boatman Senior Member Join Date: Jul 2007 Location: Oregon, USA Posts: 365 Thanks: 17 Thanked 77 Times in 64 Posts	The Wireshark packet capture points to a problem with voip.ms. The events happened as follows: Call comes from User-Agent: VoIPMS/SERAST with Connection Information (c): IN IP4 24.102.60.67 I answered the call on a PAP2. About 0.11 sec. later VoIPMS/SERAST sent SIP re-invite with Connection Information (c): IN IP4 67.205.74.164. PAP2 begins sending RTP to 67.205.74.164 and receiving RTP from 24.102.60.67. For some reason the RTP outbound from PAP2 to 67.205.74.164 does not reach the party calling on the DID, therefore calling party hears nothing. You should contact support at voip.ms. I can send you the packet capture if needed.

07-26-2009, 09:55 PM	#23
All4Fun Junior Member Join Date: Jul 2009 Posts: 22 Thanks: 6 Thanked 3 Times in 2 Posts	boatman, I wish there was more than "Thank You" for the amount of time and effort you have put into trying to resolve my problem. Admittedly, I was prepared to give up a long time ago. The good news is that we know what's occurring. The bad news is that the problem still exists and is largely out of our control. I hope that voip.ms is willing to help. I will likely need that packet capture when I do this all over again with voip.ms.

07-27-2009, 01:36 AM	#24
All4Fun Junior Member Join Date: Jul 2009 Posts: 22 Thanks: 6 Thanked 3 Times in 2 Posts	Great news!!! After sending an email to voip.ms support about this issue, they just responded letting me know that they made a routing change on my account. I did a quick test and it worked. Audio is working both ways now. I will need to monitor for the next few days but it looks like I'm back in the mix with VoXalot. Considering the support that I've gotten here and at voip.ms (even over the weekend), I know that I've picked the right combination to provide me most of my phone needs. And it didn't cost me a red cent but my sincere gratitude.

07-31-2009, 10:55 PM	#25
All4Fun Junior Member Join Date: Jul 2009 Posts: 22 Thanks: 6 Thanked 3 Times in 2 Posts	As a follow-up, I asked voip.ms what they did to resolve my problem and their response was that they "...prevented the RTP from being re-invited." While I don't know what that means, I'm hoping the info will be of benefit to boatman and any others going forward who have this problem. Needless to say, I've had no issues since the change was made by voip.ms a several days ago.