DMS-100 not receiving caller name anymore.
Looks like DMS-100 is using the same message as Q.SIG to receive the caller name. Add the ability to decode the ROSE calling name message defined for the Q.SIG switch on the DMS-100 switch. (closes issue #18822) Reported by: cmorford Patches: issue18822_v1.4.patch uploaded by rmudgett (license 664) Tested by: cmorford git-svn-id: https://origsvn.digium.com/svn/libpri/branches/1.4@2206 2fbb986a-6c06-0410-b554-c9c1f0a7f128
This commit is contained in:
parent
492a19ab7d
commit
df22f0e1cb
28
rose.c
28
rose.c
@ -1237,6 +1237,34 @@ static const struct rose_convert_msg rose_dms100_msgs[] = {
|
|||||||
rose_enc_dms100_RLT_ThirdParty_ARG, NULL,
|
rose_enc_dms100_RLT_ThirdParty_ARG, NULL,
|
||||||
rose_dec_dms100_RLT_ThirdParty_ARG, NULL
|
rose_dec_dms100_RLT_ThirdParty_ARG, NULL
|
||||||
},
|
},
|
||||||
|
|
||||||
|
/* DMS-100 seems to have pirated some Q.SIG messages */
|
||||||
|
/*
|
||||||
|
* localValue's from Q.SIG Name-Operations
|
||||||
|
* { iso(1) standard(0) pss1-name(13868) name-operations(0) }
|
||||||
|
*/
|
||||||
|
{
|
||||||
|
ROSE_QSIG_CallingName, NULL, 0,
|
||||||
|
rose_enc_qsig_CallingName_ARG, NULL,
|
||||||
|
rose_dec_qsig_CallingName_ARG, NULL
|
||||||
|
},
|
||||||
|
#if 0 /* ROSE_DMS100_RLT_OPERATION_IND, and ROSE_DMS100_RLT_THIRD_PARTY conflict! */
|
||||||
|
{
|
||||||
|
ROSE_QSIG_CalledName, NULL, 1,
|
||||||
|
rose_enc_qsig_CalledName_ARG, NULL,
|
||||||
|
rose_dec_qsig_CalledName_ARG, NULL
|
||||||
|
},
|
||||||
|
{
|
||||||
|
ROSE_QSIG_ConnectedName, NULL, 2,
|
||||||
|
rose_enc_qsig_ConnectedName_ARG, NULL,
|
||||||
|
rose_dec_qsig_ConnectedName_ARG, NULL
|
||||||
|
},
|
||||||
|
{
|
||||||
|
ROSE_QSIG_BusyName, NULL, 3,
|
||||||
|
rose_enc_qsig_BusyName_ARG, NULL,
|
||||||
|
rose_dec_qsig_BusyName_ARG, NULL
|
||||||
|
},
|
||||||
|
#endif
|
||||||
/* *INDENT-ON* */
|
/* *INDENT-ON* */
|
||||||
};
|
};
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user