Paolo,

What we have is on the far end a 3745 router with both Vofr and Voip dial-peers (PBX attached to router via T1 - not sure what make/model PBX at this point). On the near end we have the same scenario but will replace the PBX with a Callmanager. Do you see any problem with just keeping the Vofr and VoIP dial-peers (same 4 digits used for PBX handsets will be used for new IP phones registered to CCM).

To be clear, two sites connect over frame-network.

Regards

Hi, for the reasons mentioned above, the thing is that the CM won't be able to communicate to remotes via VoFR.

The alternative is to reconfigure the remote as VoIP, or if you are very fond of they way it works now, have VoIP <--> vOFR go over a pots interface. This can be done in the same router if you want.

Thanks.

Just to be clear. If we turn both the existing near end and far end VoFR dial-peers into VoIP dial-peers, the CCM will be able to talk with the PBX over the frame network?

Regards

Yes. In fact, you need to change the remote only, because normally the near end router should have not part. That is, in the CCM you will configure as H.323 endpoint the remote 3745, and vice-versa. The near-end 3745 would loose any VoFR functionaly and get no VoIP at all, unless nedded for other reason (pots gateway perhaps).

Now, the existing VoFR setup may have certain optimizations done, like header compression, call multiplexing, QoS, that you may not immediately have in a plain IP network.

So you should check first what of that was done, what is still necessary, and reconfigure that in the equivalent for VoIP. Else you risk finding the the new voIP setup has worst results than the old VoFR.

Hope all that makes some sense to you :)

There is currently compression configured in the VoFR setup. Based on your guidance, I will configured both far end and near end routers as h.323 gateways using VoIP dial-peers (and no Vofr). Below is what I plan to do. can you validate I have all bases covered.

Near end:

CCM will communicate with near end gateway via h.323. In CCM we will have route pattern for far end PBX (four digit dialing). This route pattern will point to near h.323 gateway. Near h.323 gateway will have voip dial-peer for far end four digist destination patter (session target - pointing to far end gateway IP address). RTP compression and LFI will be used and appropriate QOS on near-end rotuer (frame-relay connection is 256K, thus need for compression and LFI).

The far end gateway will be configured in similar fashion (dial-peer pointinging to near end gateway).

Can I do a QSIG trunk over the frame-network in order to support supplementary services? I have integrated local PBX's with CCM but never with a far end PBX.

Any other guidance or recommendations.

thanks Paolo

What type of routers do you have on the far ends? A customer had MC3810's, therefore could not convert the VOfr to VoIP dial peers. They had the original original 3810's that could not take the memory and firmware upgrades to run the IOS that allowed VoIP.