05-05-2015 07:53 AM - edited 03-18-2019 11:30 AM
The following questions are the continuation of the questions I already asked here.
SIP Trunking can be deployed:
In the deployment #1 (See attachment 1), the call manager cluster and the connected IP phones can be in one of the branch office and the VoIP gateways can be in various regions and connects to appropriate region's PSTN (either via PRI or SIP). While configuring SIP trunks in CUCM, in the destination IP in the SIP Information section the respective gateway's IP address needs to be given (though the gateway have CUBE update or not). We can configure multiple gateways in the same section and the dial plan will/should be having the information on what calls to be routed to which gateway. In this kind of deployment, SIP trunking is a logical connection between the CUCM cluster and the VoIP gateway when the devices are in different geo locations. Service provider cannot restrict the number of parallel SIP sessions between CUCM cluster and VoIP gateway but the bandwidth does.
In the deployment #2 (See attachment 2), the VoIP gateway will be connected to the service provider via SIP trunk (again a logical connection only via the internet bandwidth provided by the service provider). In case of a SIP call to an analog phone, the VoIP gateway will be routing the call to the service provider via the SIP trunk and the provider will be routing the call to PSTN (unlike PRI directly does the same from VoIP gateway). Here the company have to buy SIP sessions from the service provider in addition to the internet service purchased. There may be some restrictions with the number of parallel calls made.
Correct me if the above understanding is wrong.
Also please help by clarifying the following questions:
Please help by clarifying the understanding/assumptions. It would be of great help.
Thanks,
Prasanna
Solved! Go to Solution.
05-05-2015 09:28 AM
You are absolutely right for both of the deployment scenarios.
1. In deployment#1, you only configure SIP trunk in CUCM whereas in gateway, no SIP trunk. In gateway, you only configure the dial-peers (with session protocol sipv2) which tells gateway to route the call to CUCM using SIP.
2. show sip-ua commands will give you desired output.
As you already mentioned, depends on codec being invoked for a call, bandwidth will be utilized. For instance, G.711 will utilize 64 Kbps (w/o other layers overhead).
05-05-2015 09:28 AM
You are absolutely right for both of the deployment scenarios.
1. In deployment#1, you only configure SIP trunk in CUCM whereas in gateway, no SIP trunk. In gateway, you only configure the dial-peers (with session protocol sipv2) which tells gateway to route the call to CUCM using SIP.
2. show sip-ua commands will give you desired output.
As you already mentioned, depends on codec being invoked for a call, bandwidth will be utilized. For instance, G.711 will utilize 64 Kbps (w/o other layers overhead).
05-05-2015 10:07 AM
Thank you Vivek for your response.
So, with the dial-peer configuration, the gateway will be using the SIP trunk to route the in-bound calls to the CUCM and CUCM will use the gateway IP and dial plan to route the calls to the appropriate gateway.
I will explore "sip-ua" commands on gateway side for scenario#2. It would be of great help if you can clarify the commands I can use on CUCM side to get the list of SIP trunks configured on CUCM.
Thanks once again!
Prasanna
05-05-2015 10:16 AM
So, with the dial-peer configuration, the gateway will be using the SIP trunk to route the in-bound calls to the CUCM and CUCM will use the gateway IP and dial plan to route the calls to the appropriate gateway.
In IOS, this kind of peering (with session protocol sipv2 command configured under dial-peer) is generally not referred as SIP trunk. However what you have mentioned is right regarding the call flow.
When CUCM receives this call, it will first match the gateway (or SIP trunk) and then check the inbound routing configuration. Generally, you configure inbound CSS on SIP trunk to route the call to desired destination.
It would be of great help if you can clarify the commands I can use on CUCM side to get the list of SIP trunks configured on CUCM.
CUCM has well defined and intuitive web GUI for configuration and status. You don't need to use CLI interface/commands for regular administrative task.
05-05-2015 10:24 AM
Thank you Vivek :)
Regards,
Prasanna
05-05-2015 10:28 AM
You are most welcome.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide