Excellent summary, which wasn't entirely clear to me before; I still had the concepts of rtpbridge/* vs dahdi/<fixed> mixed up.
So that patch was acceptable because it solved an inconsistency between config and endpoint use of the currently anyway incomplete/wrong endpoint interpretation. It won't matter as soon as endpoint strings are overhauled. IIUC until now we have a '*' in the Connection Id field, still need to implement the class/instance@domain, particularly rtpbridge/*@domain. ~N On Sat, Dec 02, 2017 at 10:25:04PM +0100, Harald Welte wrote: > As mentioned before, the best way to go about endpoint naming is to > adopt something like an "class/[email protected]" notation, where we have > something like > rtpbridge/[email protected] > for RTP-bridge and > dahdi/L0/[email protected] > for E1 timeslot 0 at line 0 of a DAHDI card, or > dahdi/L1/S5/[email protected] > for E1 sub-slot 2 in timeslot 5 at line 1 of a DAHDI card > > The mgcp client can then simply request something like > "rtpbrige/*@mgw.sysmocom.de" which will trigger the MGW to allocat an > unused RTP bridge endpoint and respond with that in the CRCX response. > > Contrary to RTP, the mgcp client in the BSC for E1 will have a-priori > knowledge which E1 line/slot/subslot is to be used, as there is a 1:1 > mapping from air-interface-channel to E1 slot/subslot, which is > configured in the BSC configuration. So in that case, no "*" notation > would be used.
signature.asc
Description: PGP signature
