osmo-mgw[master]: protocol: allow wildcarded DLCX

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/gerrit-log@lists.osmocom.org/.

Harald Welte gerrit-no-reply at lists.osmocom.org
Thu Oct 12 07:31:16 UTC 2017


Patch Set 1:

(1 comment)

https://gerrit.osmocom.org/#/c/4227/1//COMMIT_MSG
Commit Message:

Line 14: id is supplied with the DLCX command.
> is a missing call id compliant with MGCP?
Yes, it seems explicitly permitted to offer wild-carding.

See RFC3435 Section F.7 

> In the second example, the Call Agent instructs the gateway to delete
>   all connections related to all of the endpoints specified:
>      DLCX 1210 aaln/*@rgw-2567.whatever.net MGCP 1.0
>
>   The response indicates success:
>      250 1210 OK

In this case not only was there no Connection-Id to wildcard all connections on a given end-point, but they even wildcarded the endpoint name itsel, i.e. "delete all connections on any endpoint matching "aaln/*@rgw-2567.whatever.net"


-- 
To view, visit https://gerrit.osmocom.org/4227
To unsubscribe, visit https://gerrit.osmocom.org/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: Ib5fcc72775bf72b489ff79ade36fb345d8d20736
Gerrit-PatchSet: 1
Gerrit-Project: osmo-mgw
Gerrit-Branch: master
Gerrit-Owner: dexter <pmaier at sysmocom.de>
Gerrit-Reviewer: Harald Welte <laforge at gnumonks.org>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: Neels Hofmeyr <nhofmeyr at sysmocom.de>
Gerrit-HasComments: Yes



More information about the gerrit-log mailing list