cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
648
Views
0
Helpful
0
Replies

MGCP via Qsig Alerting and Connected Name fields different

Stefan Walter
Level 1
Level 1

Hi Community,

need your help, regarding MGCP/QSIG.

Call Manager version is -

System version: 8.6.2.20000-2

We got an error with calls to PBX via QSIG. Callflow is as follow:

H323 -> CUCM -> MGCP(QSIG) -> Alcatel (pbx) -> phone A -> CFA -> phone B

the issue happens when phone A have configured a CFA only. In other cirumstances the calling name presentation line works fine.

The allerting an connected Name fields on the remote side of a Qsig trunk will show differently.

The connected name is "Call Manager". The alertingname is correct, the display shows the calling number.

Attached you'll find a snipped trace.

Also I decode the last facility element in the setup:

Q.931

    Facility  INV: callingName

        Type: Facility (0x1c)

        Length: 34

        ...1 0001 = Protocol profile: Remote Operations Protocol (0x11)

        NetworkFacilityExtension

            sourceEntity: endPINX (0)

            destinationEntity: endPINX (0)

        ROS: invoke (1)

            invoke

                invokeId: present (0)

                    present: 0

                opcode: global (1)

                    global: 1.3.12.9.0 (iso.3.12.9.0) - callingName

                argument: 800c43616c6c204d616e61676572

            QSIG: callingName

                Operation: callingName (0)

                Service: QSIG-NA (13868) - Name-Operations

                NameArg: name (0)

                    name: namePresentationAllowed (0)

                        namePresentationAllowed: namePresentationAllowedSimple (0)

                            namePresentationAllowedSimple: Call Manager  >> his is the Information that it shown on the phone display

attached you'll find the complete trace. Hope that everyone have an hint to solve the problem.

Thanks,

Stefan

0 Replies 0