Mobile Preferred and Remote Worker DTMF

[kyle555]

Hey folks,

Does anyone know if they updated the iOS and Android apps lately...perhaps in anticipation of R10 and changed how the clients do DTMF?

I just solved an issue with a customer where remote workers could no longer dial their own conference bridges on the IPO on mobile (thru SBC) but could on wifi (not thru SBC).

Eventually, I noticed in the SDP of the invites that the telephone-event/8000 SDP type was 101 for iOS and 120 for Androids (because obviously using the same media type for the same client on a different platform would make far too much sense).

Now, I checked back in the IPO remote worker devconnect doc (

https://www.devconnectprogram.com/fileMedia/download/078b0088-8b61-4d46-99fa-106db843ae8a)

and could find absolutely nothing about allowed media types requiring 101 and 120.

Every other devconnect doc for the SBCE talks about "allow preferred codecs only" being at yes for security/interop reasons and explicitly mentions what kind of RFC2833 DTMF media type is used by other end of the SIP connection.

Either I'm crazy and this never worked for my customer - or they changed something under everyone's nose and broke their previous reference configuration's documentation.

 

[janni78]

I'm assuming that the 101 and 120 is the RFC2833 Payload used.

"Trying is the first step to failure..." - Homer

 

[kyle555]

I agree - I'm just thinking an app update changed it from inband to out of band 2833 with those payload types