Codex showing as 729 in SIP call

[KenMeans]

I have a DR MM with SIP and it was working in December but now will not take a call.

The trace shows that the codex is 729 and then i get a 488 error not acceptable here. I have looked at all of the network regions and they all have a G711 in them. The DR MM is on a ESS and it is using SES for the SIP integration.

What am I missing?



Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[kyle555]

I'm sure they all have 711, but maybe 729 is allowable thru to MM and a primary choice for something trying to get over.

to say, look at all your codec sets, see which don't do 711. Then look at how those NRs connect to MM's NR.
In theory, I could want G729 from all sites to my core. In my core, everything to IP trunks or MM from those sites pins to a gateway in the core and transcodes from 729 to 711.

Unless MM rejects a SIP offer of "729 or 711", I'd reckon a trace on it would show it's only being offered 729 and due to the network region connectivity.

 

[KenMeans]

It is only showing 729 in the trace. I do have one set to 729 then 729A and g711 as the 3rd choice but that is all i can find so far

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[kyle555]

remember - your codec choice is not based on page 1 of the network region - that's only for calls within your region.
It's the later pages with the matrix that define the codec set used to get to each other region.

So, regions 1-100 in north america, 101-200 in Europe. All on page 1 have codec set 1 (711 first).
NR 1's later pages have "codec set 1" between 2-100 and 2 (729 only) to 101-200. So it's 711 local and on the wan within NA but 729 to Europe. Just like Europe can be 711 within Europe, but 729 to NA.

That's how you'd build it out. Now, suppose the closest gateway is in a NR that has 729 only - or 729 only on a codec set to the other regions AND is in front of MM, where it's connectivity lets 711 or 729 get to MM, then introducing any exclusive 729 leg in a call to MM across regions where 729 is a common denominator could darn well force a 729 only offer to MM.

I honestly don't know off hand if 729-->729-->gateway with 711+729-->MM in a NR supporting 711+729 would offer MM both with the option of the last gateway transcoding to 711 or just 729 to get you your failure.

But that's where I see your problem to be

 

[KenMeans]

Thanks i'll check that out. I just wonder how it changed

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)