01-24-2020 11:02 AM
I have a strange situation in my scenario.
I have a CUCM 9.1, and a CUBE 15.0 (1r) M16 running on a 2901.
The scenario would be PHONE <-> CUCM <-> CUBE <-> ITSP
When I receive the call through ITSP and answer on an internal extension, when trying to transfer to a cell phone, the call goes down after pressing the transfer button.
Follow the log.
Solved! Go to Solution.
01-28-2020 03:32 AM
Couple of quick comments and checks. It looks as if you may be configured to use different codecs for inbound and outbound calls. Quicker than rummaging through all those dial peers (why so many?), could you do a couple of quick checks.
(1) Place an outbound call and see what codecs are in use, and which dial peers
"sh call act voice comp" and "sh call act voice | i PeerId"
(2) Place an inbound call and do the same.
You have an amazing number of dial peers and lots of them have no codec specified, which means they'll default to G729. You have a codec class with G711u applied to a couple of dial peers. In spite of that your log shows outbound call connects with G711a. It's not quite clear to me how or why that's negotiated, but I think that's the issue.
Inbound call is established as G729
You make an outbound call as G711a
Then the transfer fails as the two calls have different codec.
01-26-2020 07:01 AM
Hello Rafael,
have you configured a sip trunk dedicated for fowarding with g711ulaw codec?
Kalliopi
01-27-2020 04:42 AM
Hello Kalliopi,
Yes. It is actually configured with 711alaw.
01-27-2020 04:55 AM
Hello Rafael,
could you please create another trunk with g711ulaw and check the call again?
Kalliopi
01-27-2020 10:13 AM
I made it. However, when I try to transfer the call, it drops.
01-27-2020 07:56 AM
Can you confirm details of the call at issue in that log file? Original called number, calling number and the number that you tried to transfer the call to?
01-27-2020 10:22 AM
01-28-2020 03:32 AM
Couple of quick comments and checks. It looks as if you may be configured to use different codecs for inbound and outbound calls. Quicker than rummaging through all those dial peers (why so many?), could you do a couple of quick checks.
(1) Place an outbound call and see what codecs are in use, and which dial peers
"sh call act voice comp" and "sh call act voice | i PeerId"
(2) Place an inbound call and do the same.
You have an amazing number of dial peers and lots of them have no codec specified, which means they'll default to G729. You have a codec class with G711u applied to a couple of dial peers. In spite of that your log shows outbound call connects with G711a. It's not quite clear to me how or why that's negotiated, but I think that's the issue.
Inbound call is established as G729
You make an outbound call as G711a
Then the transfer fails as the two calls have different codec.
01-28-2020 05:33 AM
Hello,
in older deployments i used to create mtp resources (ios) in cucm and assign them as sccp in CUBE for every different sip trunk codec. i also created the necessary mrg and configured sip trunk as attached. Cube configuration example follows
dspfarm profile 2 mtp
codec g711alaw
maximum sessions software 4
associate application SCCP
no shutdown
!
dspfarm profile 3 mtp
no codec g711ulaw
codec g729r8
maximum sessions software 4
associate application SCCP
no shutdown
sccp ccm group 1
associate profile 2 register mtp711_XXX
associate profile 3 register mtp729_XXX
01-28-2020 06:41 AM
Personally I think you should harden up the existing configuration in the first instance. Then we can see whether you need more stuff. Codecs first.
Inbound - PSTN to CUCM. As far as I can see this will always use G729 as there is no codec defined so the default is used. It's not clear if that is a deliberate choice.
Outbound CUCM to PSTN, in the example given you use G711a. We need to understand how that comes about. It looks as if the call is relaying off an MTP or Transcoder. What are your region settings? How is the trunk configured?
I think we want the same codec in both directions, then review and see what else needs fixing.
If I was taking over that installation I'd be looking to get rid of most of those dial peers, I am sure that matching by IP address and using wildcard destination patterns could consolidate them down. My installs mostly have just two.
01-29-2020 01:55 AM
@Kalliopi Vazima wrote:Hello,
in older deployments i used to create mtp resources (ios) in cucm and assign them as sccp in CUBE for every different sip trunk codec. i also created the necessary mrg and configured sip trunk as attached. Cube configuration example follows
Can I ask why? You could have a single transcoder profile doing all of that. A transcoder can act as an MTP but an MTP can't be a transcoder.
01-28-2020 09:31 AM
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