npb007

I've got a weird one here.... Any help with it would be very much appreciated. Thanks!

I've built 5 VoIP trunks between 2 Definity's. All trunks are up, active and get allocated for calls. However, I only get voicepath in one direction. On the other end, the called party can here me, but I cannot here them. In fact, I hear nothing at all, no dial tone, nada!

One other interesting note: I can do a round-robin type call, where I call into the far switch, dial the TAC for another trunk in the same VoIP trunk group, and route a call back to a different extension in my switch, and the call completes great! I have voicepath in both directions, and no issues with background noise or disconnection of service.

Anyone know what might be the problem here? I am pretty well stumped on this one. As a side note, I cannot ASA remotely into the far switch either. Locally, the switch does IP ASA no problem, but from a remote site, I cannot connect. We can ping the CLAN remotely, and the router is DEFINATELY NOT blocking the ASA ports, so why won't it connect? Anyway, thanks ahead of time for any help you may be able to render for me.

Nate

nexSIP

Is this a VoIP phone your trying to call from?

First off CHANGE IP-SERVICES and make sure the port is what you think it is. and make sure the REMOTE PORT is '0'
then try to telnet into that port, if you dont get a response you have routing issues.

__________________
http://www.nexsip.com
Communicate Openly and Freely

PBXtech.info

 

npb007

No, this is all using digital phones on VoIP trunks. Its just really, really odd activity. No return voicepath. Any ideas?

I'll try to telnet in and report back on the results.

nexSIP

Why you could call one phone and not another via IP trunk does not make sense.

__________________
http://www.nexsip.com
Communicate Openly and Freely

savvasc

check your collisions. Use sniffing tools to check the collisions ot the routers. (I had the same problem last year). Somewhere the configuration of the router (half/full duplex is not correct)

stubborne

Maybe you have a config problem in the signalling group on one or the other (or both) switches. Check the port assignments, network region settings. This is a stretch since it's an audio path problem, not signalling. Possible the network region setting could mess that up. Definately start there, tho. Also, double-check all your IP settings for consistency on network region, codec in ip-interface and ip-network-region forms.

__________________
Stu

PBXtech.info

 

npb007

Alright! We've got her figured out...

First, the firmware upgrade on theMedpro board at the Remote site fixed the no-return voice path problem.

Second, a reset 4 of the PBX cleared out the error in the ASA connection.

Thanks for everyones help with this.

Nate

nexSIP

I would NOT suggest people do a RESET to try and solve problems

__________________
http://www.nexsip.com
Communicate Openly and Freely

npb007

I didn't do the reset, the Business Partner did, but I do agree that this is not a normal way to fix issues. I just wanted to make anyone with the same problem, that that is how our situation was resolved.

Nate

Cephas

Yes... it's far more effective to KICK the equipment firmly... if that fails I've had marvelous success with a baseball bat... :)

Peter

phones329

I have had a similar challenge, what I found to work WITHOUT doing a reset 4, was to change the IP address of the C-lan to a different number, then change it right back. That instantly fixed the issue.