04-21-2015 06:47 AM - edited 03-17-2019 02:44 AM
Hi, I was hoping someone can shed some light on this. I am not an IPT engineer. We are putting in a new CUCM 10 but the person who started this is no longer here and am just trying to pick up the pieces left behind. Thank you in advance.
Question -
Ignoring for now any E.911 stuff... Can 2 device pools make outbound calling against a single SIP trunk (1 IP address)? Office1 has a pub/sub and a single SIP trunk. Office2 has neither. We wanted two separate device pools. But the SIP trunk (found under Device | Trunk) can only be associated with a single DP.
We use an MPLS network dedicated to voice. The service provider is able to force inbound calls for both area codes to that SIP trunk. I guess my problem is on the outbound.
If it is possible, how do we make this happen? If not, does that imply that both offices must be in the same DP?
Thanks.
Solved! Go to Solution.
04-22-2015 10:29 AM
Not sure why MTP is checked as on...Is your CUCM SIP trunked directly to the provider or do you have a gateway that the CUCM sends traffic to then to the provider? You really don't want to be invoking MTPs if you don't need to, and in your environment so far, I don't see a reason to be using them unless something else is going on. Also, yes it will drop all calls upon a Trunk reset, I would do this after hours and then test the phones.
Let me think a bit on this and get back to you. I got a feeling if I were sitting in front of the system I would have had this solved yesterday.
Edit: What device pool is the SIP trunk in?
04-21-2015 07:18 AM
Device Pools only affect where traffic gets routed if you are using Standard Local Route Groups. If that is the case, then whatever is first in that route group will take precedence unless you are using circular routing. So yes, you could have 50 device pools and they could all route out a SIP trunk with no issue as long as the route pattern they catch sends them in that direction. The other way is to not use Standard Local Route Groups and route based on matched pattern straight to whatever destination is set.
04-21-2015 07:47 AM
Brandon:
Thank you. If I was an IPT engineer, it might make better sense but I take your explanation as correct. :-) What did you mean by "If that is the case (that is, if I'm using Std Local RG), whatever is first in that route group will take precedence..." I think I am using Std Local RG (see below) but I don't see how the presence of this causes all outbound voice traffic to go out the SIP trunk. The only top/down list I see is within a route list, but the Std Local Route Group is listed second.
Under Route Group
I have a single RG1 listed and the properties of it show my SIP trunk added as the only available device and and only RG member.
Local Route Group Names
I see we do have a Standard Local RG.
Route List
I see something he created called RL-SLRG. Within that definition, My RG1 is on top and RL-SLRG is listed second.
Route Pattern
When I view the ones of interest, I see that the Gateway/Route List is specified as the RL-SLRG. For example, if you dial 9,1,area+number, use the RL-SLRG it says. How does this even work to know that RL-SLRG is to use my service provider's SIP trunk for outbound? I don't see thru anything on the web admin interface that defines this.
I don't think the forum was intended to get a complete set of steps on how to implement so I won't bug you like that. If you can kindly give me some guidance on the above, the significance of a SLRG, etc., we can try to take it from there. Thank you again.
04-21-2015 08:26 AM
In the device pool of the phones, there is an option for Standard Local Route Group. Is that set to something specific? If it is, you need to check that Route Group to see where it is sending calls as that will be your egress point upon a Route Pattern match. Hope that makes sense? Top/down indicates it will always use the top one until it is either loaded or not available which is usually desired unless you for some reason want to round robin the calls with a circular algorithm.
04-21-2015 08:36 AM
Hi Brandon, sorry I hit "Report" by accident instead of Reply. I did an Unreport. :-)
Within both Device Pools I see "Local Route Group Settings" and the Standard Local Route Group is set to < None > on both.
Sorry, hopefully last set of questions and will mark this as answered/correct.
1. Given the Device Pools show < None > for the above, does this mean, while the guy defined some SLRG, that I'm not actually using them for Device Pools?
2. Given that my Route List shows my RG1 as the top, does that mean it gets processed first (before the SLRG)? If so, does that effectively mean I'm not really using SLRG?
3. But my Route Pattern shows that outbound calls should go thru the SLRG.
Sorry, very confused. I wish this were an ASA or something. Just easier for me...
Thank you.
04-21-2015 09:08 AM
If the device pools are set to "None" then they will route with whatever the Route Pattern has set. So if the Route Pattern has XXXXX_RL then you need to check the route lists. If the Route Pattern is set to XXXX_Trunk or Gateway then it goes straight out that gateway or Trunk. Can you post some screenshots of the setup? This looks like a basic design from what you have said.
04-21-2015 09:44 AM
04-21-2015 11:50 AM
Ok with that given, NY_SIP is the device it is using to egress your network. Not sure why there was a label of SLRG in there when it isn't an SLRG. So any device that makes a call without an Standard Local Route Group in their device pool will use the route pattern's target.
04-21-2015 12:03 PM
It sounds like you have an answer to which I didn't understand... With this particular setup:
04-21-2015 12:56 PM
Getting off here soon so someone else may need to keep this discussion going. Please don't forget to rate all useful posts and mark a correct answer should one be provided.
04-21-2015 01:02 PM
1. Two different locations both connected via private point-to-point.
2. DP2 phones (office2) can register into CUCM in office1.
3. Outbound to outside numbers have never worked out of DP2/office2. Interoffice works. Inbound works as well. The provider is able to have both area codes come in thru that single circuit in the main location.
4. Yes, both DP have "none" for SLRG.
5. Mix, strangely. Most are SIP. A few stragglers on SCCP.
6. No known restrictions under CSS/Partitions that I can see.
Will try to run the RTMT. Brandon, you are way cool. Let me try this and get back to you. If not tonight, tomorrow.
04-21-2015 01:09 PM
Are you running pure G.711 across the WAN link or are you forcing G.729? This would dump your call if you arn't transcoding properly from one codec to another. you may be pure G.729 between the links but not transcoding hitting the PSTN to G.711 is my thought. Almost sounds like a media resource problem at this point.
04-21-2015 01:42 PM
I ran RTMT and assuming I did it correctly, I saw the failed test call and it says "( 47 ) Resource, unavailable, unspecified. Explanation: A resource unavailable event occurred and no other cause in the resource unavailable class applies".
RE: your other post, when I look at Regions, the only mention is the Max Audio Bit Rate which shows 64 kbps (G.722, G.711). This is consistent across both regions. The preferred codec is to use the system default of Factory default low loss.
Not sure about media resources. I don't understand the naming convention of appending _2 or _4 after each resource but I see a pair for:
For each resource,
There is an MRG for each DP. For example:
Then there are 2 MRGL's - one for each DP. Each MRGL though contains all the MRGs.
Is my problem a media resource issue?
04-22-2015 05:53 AM
I knew it, media resources are hosing you up. When you make a call from office2, what is the path? If you are G.711 all the way across you don't need transcoding but something else is hosing you up.
Cause code 47 is definitely a media resource issue. So you checked every region and nothing noted G.729 anywhere? There is something called a Dialed number analyzer in CUCM as will show the call path from the perspective of a phone. When you log into CUCM
Other than that, I would need to know the topology and how everything is laid out with the DNA tool and Regions. My next question is, under the System--> Locations, you don't have anything setup for the sites there do you? If you do, are those put on any of the phones? Default is Hub_None and Phantom which I doubt he changed if that is all that is on there.
I bet if you completely removed all MRGs, MRGLs, and their assignments the call would complete assuming G.711 is truely what is being used. In the RTMT logs for the call, on a SIP phone, what is the SDP sending the initial INVITE with assuming you are using early offer? SDP is Session Description Protocol which looks like this:
Initial SIP INVITE message for call setup:
INVITE sip:13@10.10.1.13 SIP/2.0
Via: SIP/2.0/UDP 10.10.1.99:5060;branch=z9hG4bK343bf628;rport
From: "Test 15" <sip:15@10.10.1.99>;tag=as58f4201b
To: <sip:13@10.10.1.13>
Contact: <sip:15@10.10.1.99>
Call-ID: 326371826c80e17e6cf6c29861eb2933@10.10.1.99
CSeq: 102 INVITE
User-Agent: Asterisk PBX
Max-Forwards: 70
Date: Wed, 06 Dec 2009 14:12:45 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER,
SUBSCRIBE, NOTIFY
Supported: replaces
Content-Type: application/sdp
Content-Length: 258
Then the SDP:
v=0
o=root 1821 1821 IN IP4 10.10.1.99
s=session
c=IN IP4 10.10.1.99
t=0 0
m=audio 11424 RTP/AVP 0 8 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20
a=sendrecv
Note the PCMU/8000, in the US we generally use PCMU for everything. If you arn't offering this and there isn't anything in there when site 2 calls, that is part of the issue, but I suspect this isn't a SIP trunking issue and again, purely a media resource problem. Once I get a better picture of your topology, we can go from there. I have a feeling if you set the MRGL on a phone from Site 2 to an MRGL of Site 1, you call would complete.
04-22-2015 06:33 AM
Thank you for the primer on the various media resources. It was very good information for me. Sorry lengthy post but you had a bunch of good questions.
Call Path
When I make a call from office2 (NJ), the call traverses our 100 Mbps point-to-point into office1 (NY). Point-to-point util is no greater than 10% (peak over 6 weeks) and average util of about 3%. NY has the pub/sub and voice circuit. The NJ call is supposed to go out that way. Pretty vanilla. When office2 is on its own DP, it fails. But if set to the office1 DP, it works well.
DNA Tool
I ran the tool twice. First using a working phone from office1. I then compared that to the results of using a non-working phone from office2. The results are an identical match.
Under Call Flow, the first section is the Translation Pattern section and it doesn't show much but appears OK. Just some stuff about transformations and such.
Route Pattern looks like it just says it matches the 9.1[2-0]XX[2-9]XXXXXX.
Rout List shows 2 Route Groups. First one just says RG1 and to use the End Device Name NY_SIP. The second one says SLRG is the route group name but nothing more really listed there other than some transformation information.
Next, confirming I only have 2 regions (corresponding to offices 1 and 2) and neither have G.729 in them.
Topology:
System > Locations:
System > Regions:
The RTMT thing from yesterday that had that 47 Resource unavailable lengthy error. When I double-click it, it shows a call flow diagram of:
The next tab of Message Details\Detailed SIP\Log File just shows that request was canceled and reason same as yesterday of Q.850; cause=47.
Thank you.
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