Displaying 5 results from an estimated 5 matches for "callingnam".
Did you mean:
callingname
2010 Jun 08
0
libpri 1.4.11.2 Now Available
...ad at
http://downloads.asterisk.org/pub/telephony/libpri/
This release fixes situation where Q.SIG calling name in FACILITY message was
not reported to the upper layer:
* pri_facility.c: Q.SIG calling name in FACILITY message not
reported to the upper layer. Q.SIG can send the CallingName,
CalledName, and ConnectedName in stand alone FACILITY messages.
If the CallingName was not sent in the SETUP message, the caller
id name was not reported to the upper layer.
(Closes issue #17458. Reported, tested by: jsmith. Patched by
rmudg...
2010 Jun 08
0
libpri 1.4.11.2 Now Available
...ad at
http://downloads.asterisk.org/pub/telephony/libpri/
This release fixes situation where Q.SIG calling name in FACILITY message was
not reported to the upper layer:
* pri_facility.c: Q.SIG calling name in FACILITY message not
reported to the upper layer. Q.SIG can send the CallingName,
CalledName, and ConnectedName in stand alone FACILITY messages.
If the CallingName was not sent in the SETUP message, the caller
id name was not reported to the upper layer.
(Closes issue #17458. Reported, tested by: jsmith. Patched by
rmudg...
2014 Apr 29
1
Inbound DAHDI Error
...PRI Span: 1 ASN.1 end
PRI Span: 1 interpretation Context Specific [11 0x0B] = 0 0x0000
PRI Span: 1 INVOKE Component Context Specific/C [1 0x01]
PRI Span: 1 invokeId Integer(2 0x02) = 1 0x0001
PRI Span: 1 operationValue Integer(2 0x02) = 0 0x0000
PRI Span: 1 operationValue = ROSE_QSIG_CallingName
PRI Span: 1 callingName Name
PRI Span: 1 namePresentationAllowedSimple Context Specific [0 0x00] =
PRI Span: 1 <4F 4D 41 58 20 43 4F 52-50 20 4E 20 47 53 4D> -
"<source_caller_name>"
PRI Span: 1 q931.c:8646 post_handle_q931_message: Call 23832 enters state 6
(Call...
2010 Jun 09
0
CID name in Facility message for Q.SIG
...quot;~"
Context Specific [0 0x00] <80> Invalid length encoding!
ASN.1 end
interpretation Context Specific [11 0x0B] = 0 0x0000
INVOKE Component Context Specific/C [1 0x01]
invokeId Integer(2 0x02) = 1 0x0001
operationValue Integer(2 0x02) = 0 0x0000
operationValue = ROSE_QSIG_CallingName
callingName Name
q931.c:7316 post_handle_q931_message: Call 256 enters state 6 (Call Present). Hold state: Idle
q931.c:4686 q931_call_proceeding: Call 256 enters state 9 (Incoming Call Proceeding). Hold state: Idle
2014 Jan 20
1
ISDN Cause Code 47 Errors
....c: [Jan 14 12:56:04] PRI Span:
4 invokeId Integer(2 0x02) = 31 0x001F
[Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04] PRI Span:
4 operationValue Integer(2 0x02) = 0 0x0000
[Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04] PRI Span:
4 operationValue = ROSE_QSIG_CallingName
[Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04] PRI Span:
4 callingName Name
[Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04] PRI Span:
4 namePresentationAllowedSimple Context Specific [0 0x00] =
[Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04]...