Telcom Pro's
http://www.telcompros.net/cgi-bin/yabb/YaBB.cgi
PBX's and Phone Switch's >> Translations >> AVAYA pbx
http://www.telcompros.net/cgi-bin/yabb/YaBB.cgi?num=1326394196

Message started by whip22 on Jan 12th, 2012 at 1:49pm

Title: AVAYA pbx
Post by whip22 on Jan 12th, 2012 at 1:49pm
Have a Pri going from our DMS100 (cs2k) to an AVAYA PBX
when they call a disconnected number there keysystem show up as incompatible  and doesnt get the disco recording
Help would be apreciated


Vender sent me a copy of his capture

    112982mS CD: CALL: 0.1014.0 BState=Ringing Cut=3 Music=0.0 Aend="ryandesk(225)" (0.21) Bend="Line 9" [Line 9] (5.6) CalledNum=5601406 () CallingNum=225 (ryandesk) Internal=0 Time=474 AState=Dialled
    112984mS CMMap: PCG::MapBChan pcp[141]b1r0 cp_b f4e93eac other_cp_b 0 type CGTypeSimple
    112984mS CMMap: PCG::MapBChan pcp[108]b1r0 cp_b f5587564 other_cp_b f4e93eac type CGTypeSimple
    112984mS CMMap: a=0.21 b=5.6 M1
    113978mS ISDNL3Evt: v=9 stacknum=9  State, new=ReleaseReq, old=Proceeding id=1017
    114029mS ISDNL3Evt: v=9 stacknum=9  State, new=NullState, old=ReleaseReq id=1017
    114030mS CMLineRx: v=9
            CMReleaseComp
            Line: type=Q931Line 9 Call: lid=0 id=1017 in=0
            BChan: slot=0 chan=5
            Cause=1, Unallocated (unassigned) number   114030mS CMCallEvt:    0.1017.0 7 Q931 Trunk:9 CHAN=5: StateChange: END=B CMCSAccept->CMCSCompleted
    114031mS CMLOGGING:     CALL:2012/01/1212:07,00:00:00,000,225,O,5601406,5601406,ryandesk,,,0,,""n/a,0
    114031mS CD: CALL: 0.1014.0 BState=Disconnecting Cut=1 Music=0.0 Aend="ryandesk(225)" (0.21) Bend="Line 9" [Line 9] (5.6) CalledNum=5601406 () CallingNum=225 (ryandesk) Internal=0 Time=1523 AState=Dialled
    114032mS CD: CALL: 0.1014.0 Deleted
    114033mS CMExtnEvt:    ryandesk: CALL LOST (CMCauseUnallocatedNumber)
    114033mS CMExtnEvt:    ryandesk: Extn(225) Calling Party Number(225) Type(CMNTypeInternal)
    114033mS CMCallEvt:    0.1014.0 -1 ryandesk.0: StateChange: END=X CMCSDialled->CMCSCompletedTone
    114034mS CMExtnEvt:    v=6 State, new=CMESCompleted  old=Proceeding,0,0,ryandesk
    114034mS CMCallEvt:    0.1017.0 -1 Q931 Trunk:9 CHAN=5: StateChange: END=X CMCSCompleted->CMCSDelete
    114035mS CMCallEvt:    END CALL:7 (f514ec00)








Title: Re: AVAYA pbx
Post by Paul on Jan 12th, 2012 at 2:43pm
What protocol is configured between the PBX and the switch?  NI-2, DMS?  Are they the same?

Title: Re: AVAYA pbx
Post by mountain on Jan 12th, 2012 at 3:23pm
If possible capture a PMDEBUG for the session and post it.  Typically, "incompatible" means, one bearer capability can not terminate to a different bearer capability, however, this has nothing to do disconnected numbers.

If a caller from a PRI can not hear the other end, usually, the PBX is not putting the B-channel through (the voice path).  When you terminate to an announcement, the PBX will receive a CALL PROGRESS message instead of an ALERTING message.  In some PBXs, you have to configure the PRI to open the B-channel for both types of messages not just the alerting.



Title: Re: AVAYA pbx
Post by mountain on Jan 12th, 2012 at 3:47pm
The "incompatible" might be an information element in the CALL PROGRESS message the AVAYA doesn't like and the AVAYA is replying "message incompatible with call state" and the AVAYA disconnects the call.  A PMDEBUG would confirm if this is the case.

Title: Re: AVAYA pbx
Post by whip22 on Jan 13th, 2012 at 8:19am
Here is vendors capture
Vender sent me a copy of his capture

    112982mS CD: CALL: 0.1014.0 BState=Ringing Cut=3 Music=0.0 Aend="ryandesk(225)" (0.21) Bend="Line 9" [Line 9] (5.6) CalledNum=5601406 () CallingNum=225 (ryandesk) Internal=0 Time=474 AState=Dialled
    112984mS CMMap: PCG::MapBChan pcp[141]b1r0 cp_b f4e93eac other_cp_b 0 type CGTypeSimple
    112984mS CMMap: PCG::MapBChan pcp[108]b1r0 cp_b f5587564 other_cp_b f4e93eac type CGTypeSimple
    112984mS CMMap: a=0.21 b=5.6 M1
    113978mS ISDNL3Evt: v=9 stacknum=9  State, new=ReleaseReq, old=Proceeding id=1017
    114029mS ISDNL3Evt: v=9 stacknum=9  State, new=NullState, old=ReleaseReq id=1017
    114030mS CMLineRx: v=9
            CMReleaseComp
            Line: type=Q931Line 9 Call: lid=0 id=1017 in=0
            BChan: slot=0 chan=5
            Cause=1, Unallocated (unassigned) number   114030mS CMCallEvt:    0.1017.0 7 Q931 Trunk:9 CHAN=5: StateChange: END=B CMCSAccept->CMCSCompleted
    114031mS CMLOGGING:     CALL:2012/01/1212:07,00:00:00,000,225,O,5601406,5601406,ryandesk,,,0,,""n/a,0
    114031mS CD: CALL: 0.1014.0 BState=Disconnecting Cut=1 Music=0.0 Aend="ryandesk(225)" (0.21) Bend="Line 9" [Line 9] (5.6) CalledNum=5601406 () CallingNum=225 (ryandesk) Internal=0 Time=1523 AState=Dialled
    114032mS CD: CALL: 0.1014.0 Deleted
    114033mS CMExtnEvt:    ryandesk: CALL LOST (CMCauseUnallocatedNumber)
    114033mS CMExtnEvt:    ryandesk: Extn(225) Calling Party Number(225) Type(CMNTypeInternal)
    114033mS CMCallEvt:    0.1014.0 -1 ryandesk.0: StateChange: END=X CMCSDialled->CMCSCompletedTone
    114034mS CMExtnEvt:    v=6 State, new=CMESCompleted  old=Proceeding,0,0,ryandesk
    114034mS CMCallEvt:    0.1017.0 -1 Q931 Trunk:9 CHAN=5: StateChange: END=X CMCSCompleted->CMCSDelete
    114035mS CMCallEvt:    END CALL:7 (f514ec00)


Also we have the Pri set to NI2PRI

Title: Re: AVAYA pbx
Post by Paul on Jan 13th, 2012 at 9:04am
You are using the word "Incompatible" but in this trace I see "Unallocated", does "Incompatible" appear on the keyset screen or in another trace?

I see that your subscriber is trying to call 5601406 and is getting an unallocated number response, which is valid for a number that is not built either on your local switch or as a response to your switch trying to go off-net and getting a similar ISUP or SIP response.

Your switch is sending the PBX an "Unallocated" response message and the question is, should you be playing an announcement instead?

Do you have any other similar PBX customers that you can test with to determine what they get for a response to an unallocated number?

I am rusty on DMS datafill but this trace appears normal if the PBX has the capacity to play an announcement to it's end user but if not your switch will have to play the announcement rather than returning an unallocated response message to the PBX.

Title: Re: AVAYA pbx
Post by mountain on Jan 13th, 2012 at 9:47am
That protocol dump is impossible to read.

In table LTDATA-SERV, change prompt AUDTRMT to Y.  This will prevent the CALL PROGRESS message from being sent.  I think the PBX is disconnecting the call with that PROGRESS message, but can;t be sure.

Title: Re: AVAYA pbx
Post by mountain on Jan 13th, 2012 at 10:09am
Paul is correct.  When a RELEASE message is sent with a cause value, the PBX is responsible for playing announcements or treatments.  However, changing the field AUDTRMT to Y should allow inband playing of treatments and announcements.  Can't say I have ever set this field to Y so you will have to test.

Title: Re: AVAYA pbx
Post by DMSBrit on Jan 13th, 2012 at 11:58am

mountain wrote on Jan 13th, 2012 at 9:47am:
In table LTDATA-SERV, change prompt AUDTRMT to Y. 


This may be dependent on DMS software load. Frankly I'm clueless about the US domestic loads, but in the later International loads the AUDTRMT function was made redundant even though the prompt still appears and has to have a Y or N datafilled.

Instead in these later Int'l loads you have to add the option NET_CALLFAIL_ON to LTDATA-SERV for example:

TABLE: LTDATA
LTDKEY LTDRSLT
--------------
ISDN 527 SERV SERV N N SCREENED ALWAYS (NET_CALLFAIL_ON)

Title: Re: AVAYA pbx
Post by whip22 on Jan 13th, 2012 at 12:32pm
switched ltdata serv   AUDTRMT to Y and fixed it
THX


Telcom Pro's » Powered by YaBB 2.5 AE!
YaBB Forum Software © 2000-2010. All Rights Reserved.