locked
Lync - Officemaster - PBX --> Please check the number and try again! RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    when calling a PBX extension, the PBX phone only rings once and displays the identifier of the line.

    The Lync client shows "Please check the number and try again".

    We have a firewall between Lync and gateway (officemaster) which is connected via S2M with PBX.

    Lync Log:

    >>>>>>>>>>>>Outgoing SipMessage c=[<SipTlsConnection_1E29445>], Mediation:5070->Mediation:53703
    SIP/2.0 484 Address incomplete
    FROM: "xxx"<sip:xxx>;tag=127940a043;epid=9d42c993a8
    TO: <sip:+49123456789@xxx.de;user=phone>;tag=2bd6d0a7ec;epid=E83BD1C12F
    CSEQ: 1 INVITE
    CALL-ID: a234087c78f14f889173fdd4695715a4
    VIA: SIP/2.0/TLS Mediation:53703;branch=z9hG4bK88F0627A.CD74B15AA5FC5269;branched=FALSE,SIP/2.0/TLS Client:61274;ms-received-port=61274;ms-received-cid=853000
    CONTENT-LENGTH: 0
    P-ASSERTED-IDENTITY: <sip:+49123456789@xxx.com;user=phone>
    SERVER: RTCC/4.0.0.0 MediationServer
    ms-diagnostics: 10484;source="FE-Pool";reason="Gateway responded with 484 Address Incomplete";component="MediationServer";SipResponseCode="484";SipResponseText="Address incomplete";GatewayFqdn="officemaster"
    ms-diagnostics-public: 10484;reason="Gateway responded with 484 Address Incomplete";component="MediationServer";SipResponseCode="484";SipResponseText="Address incomplete"
    ms-trunking-peer: Officemaster;User-Agent="Ferrari electronic OMG 3.3 (3.3-99,3.3-22,3.3-61)"
    ms-endpoint-location-data: NetworkScope;ms-media-location-type=intranet
    ------------EndOfOutgoing SipMessage

    (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
    Trace-Correlation-Id: 3386127172
    Instance-Id: 00438F61
    Direction: incoming
    Peer: FE-Pool:5070
    Message-Type: response
    Start-Line: SIP/2.0 484 Address incomplete
    From: "xxx"<sipxxx>;tag=127940a043;epid=9d42c993a8
    To: <sip:+49123456789@xxx.de;user=phone>;tag=2bd6d0a7ec;epid=E83BD1C12F
    CSeq: 1 INVITE
    Call-ID: a234087c78f14f889173fdd4695715a4
    VIA: SIP/2.0/TLS Mediation:53703;branch=z9hG4bK88F0627A.CD74B15AA5FC5269;branched=FALSE,SIP/2.0/TLS Client:61274;ms-received-port=61274;ms-received-cid=853000
    CONTENT-LENGTH: 0
    P-ASSERTED-IDENTITY: <sip:+49123456789@xxx.com;user=phone>
    SERVER: RTCC/4.0.0.0 MediationServer
    ms-diagnostics: 10484;source="FE-Pool";reason="Gateway responded with 484 Address Incomplete";component="MediationServer";SipResponseCode="484";SipResponseText="Address incomplete";GatewayFqdn="officemaster"
    ms-diagnostics-public: 10484;reason="Gateway responded with 484 Address Incomplete";component="MediationServer";SipResponseCode="484";SipResponseText="Address incomplete"
    ms-trunking-peer: Officemaster1;User-Agent="Ferrari electronic OMG 3.3 (3.3-99,3.3-22,3.3-61)"
    ms-endpoint-location-data: NetworkScope;ms-media-location-type=intranet
    Message-Body: –
    $$end_record

    (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
    Trace-Correlation-Id: 3386127172
    Instance-Id: 00438F61
    Direction: outgoing
    Peer: Client:61274
    Message-Type: response
    Start-Line: SIP/2.0 484 Address incomplete
    From: "xxx"<sip:xxx.de>;tag=127940a043;epid=9d42c993a8
    To: <sip:+49123456789@xxx.de;user=phone>;tag=2bd6d0a7ec;epid=E83BD1C12F
    CSeq: 1 INVITE
    Call-ID: a234087c78f14f889173fdd4695715a4
    Authentication-Info: TLS-DSK qop="auth", opaque="607463FF", srand="D78432E1", snum="267", rspauth="d66d352344e7145bc0749121d5b0acfd9115cb26", targetname="FE-Pool", realm="SIP Communications Service", version=4
    Via: SIP/2.0/TLS Client:61274;ms-received-port=61274;ms-received-cid=853000
    CONTENT-LENGTH: 0
    P-ASSERTED-IDENTITY: <sip:+49123456789@xxx.com;user=phone>
    SERVER: RTCC/4.0.0.0 MediationServer
    ms-diagnostics: 10484;source="FE-Pool";reason="Gateway responded with 484 Address Incomplete";component="MediationServer";SipResponseCode="484";SipResponseText="Address incomplete";GatewayFqdn="officemaster"
    ms-diagnostics-public: 10484;reason="Gateway responded with 484 Address Incomplete";component="MediationServer";SipResponseCode="484";SipResponseText="Address incomplete"
    ms-trunking-peer: officemaster;User-Agent="Ferrari electronic OMG 3.3 (3.3-99,3.3-22,3.3-61)"
    ms-endpoint-location-data: NetworkScope;ms-media-location-type=intranet
    Message-Body: –
    $$end_record

    Thanks!



    • Edited by JaSch Wednesday, April 25, 2012 8:26 AM
    Wednesday, April 25, 2012 8:24 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    But if you dial the complete number in the gateway you make an outsitecall over the PBX, why don't you call 2010 to the PBX because it is your internal extension in the PBX. How are your settings of the S2m?

    Is the newest Firmware installed.  Configure Debuglevel to default and Syslog to TCP. I missed in the log the important information.

    If you can read german try to use this link

    http://forum.ferrari-electronic.de/archive/index.php/f-29.html

    regards Holger Technical Specialist UC




    • Edited by Holger Bunkradt Wednesday, April 25, 2012 3:11 PM
    • Marked as answer by JaSch Monday, August 18, 2014 9:10 AM
    Wednesday, April 25, 2012 2:52 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    It looks like a misconfiguration of the Gateway or the S2m from the PBX, because SIP 484 means "Address Incomplete". Maybe you have to configure some timeout settings for the call.

    regards Holger Technical Specialist UC

    Wednesday, April 25, 2012 8:57 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Unfortunately we are not able to check the S2M configuration for PBX at the moment.

    Maybe the gateway log helps to resolve my issue.

    Gateway log:

    OSR0100207 callp: mux_isdn:0 (1) ISDN[1](1606): L3M : 13==13
    OSR0100207 callp: mux_isdn:0 (1) ISDN[1](1606): L3M : 10:24:37,017 KillPCE: pce_idx=13
    OSR0100207 callp: mux_isdn:0 (1) ISDN[1](1606): L3M : 10:24:37,017 Layer3Management: ML3_REMOVE_RESP
    OSR0100207 callp: mux_isdn:0 (1) ISDN[1](1606): ML4 : ML4_REMOVE_RESP 0c
    OSR0100207 callp: mux_isdn:0 (1) ISDN[1](1606): APP : ML4_REMOVE_IND
    OSR0100207 callp: mux_isdn:0 (1) ISDN[1](1606): ML4 : MCC_KILL_REQ
    OSR0100207 callp: mux_isdn:0 (1) ISDN[1](1606): CC  : <-- state=CC_IDLE(1) ----------
    OSR0100207 callp: mux_isdn:0 (1) ISDN[1](1606): CC  : --> (Idx=12) 10:24:37,016 state=CC_IDLE(0x1), event=MCC_KILL_IND(0x52)----------
    OSR0100207 callp: mux_isdn:0 (1) ISDN[1](1606): ML4 : ML3_REMOVE_IND 0c
    OSR0100207 callp: mux_isdn:0 (1) ISDN[1](1606): L3X : unable to deregister PCE task 13
    OSR0100207 callp: mux_isdn:0 (1) ISDN[1](1606): L3X : 10:24:37,015 deregistering layer 3 task 13 for protocol 'Q.931(I.451) user-network call control messages'
    OSR0100207 callp: mux_isdn:0 (1) ISDN[1](1606): L3X : 10:24:37,015 Layer3MultiplexProceedure event=MPC_REMOVE_IND (84)
    OSR0100207 callp: mux_isdn:0 (1) ISDN[1](1606): L3M : 13==13
    OSR0100207 callp: mux_isdn:0 (1) ISDN[1](1606): L3M : 10:24:37,015 PCEDown: pce_idx=13
    OSR0100207 callp: mux_isdn:0 (1) ISDN[1](1606): L3M : 10:24:37,015 Layer3Management: MPC_KILL_REQ
    OSR0100207 callp: mux_isdn:0 (1) ISDN[1](1606): DSS1: 10:24:37,015 cpn=00123456 instance=1 callref=70 <-- state=DSS1_U0
    OSR0100207 callp: mux_isdn:0 (1) ISDN[1](1606): DSS1: 10:24:37,015 cpn=00123456 instance=1 callref=70 --> state=DSS1_U0, event=TIMEOUT_T303
    OSR0100207 callp: ip:server:t:mediation:55514:70: (1) closeNetwork: 3 CallpExit from 'sip_isdn:44b7a9e6-6a90-4326-9c92-c153b4a0feeb' for 'ip:server:t:mediation:55514:70:'
    OSR0100207 callp: ip:server:t:mediation:55514:70: (1) 4 got message from 'sip_isdn:44b7a9e6-6a90-4326-9c92-c153b4a0feeb' to 'ip:server:t:mediation:55514:70:'
    OSR0100207 callp: mux_isdn:0 (1) ISDN[1](1606): '
    OSR0100207 callp: mux_isdn:0 (1) ISDN[1](1606): APP : 10:24:34,393 (1) 106 bytes written ':CCA_RELEASE_CONF;+49123456789;;00123456;;CCAPI_CIP_ANALOG_VOICE;;0;0;0;0;109;1;xxx;;0
    OSR0100207 callp: mux_isdn:0 (1) ISDN[1](1606): '
    OSR0100207 callp: mux_isdn:0 (1) ISDN[1](1606): APP : 10:24:34,393 106 bytes written ':CCA_RELEASE_CONF;+4912345689;;00123456;;CCAPI_CIP_ANALOG_VOICE;;0;0;0;0;109;1;xxx;;0
    OSR0100207 callp: mux_isdn:0 (1) ISDN1 send to 'sip_isdn:44b7a9e6-6a90-4326-9c92-c153b4a0feeb'
    OSR0100207 callp: CCA_RELEASE_CONF
    OSR0100207 callp: mux_isdn:0 (1) ISDN[1](1606) <== :CCA_RELEASE_CONF;+496201802084;;00123456;;CCAPI_CIP_ANALOG_VOICE;;0;0;0;0;109;1;xxx;;0
    OSR0100207 callp: mux_isdn:0 (1) ISDN[1](1606): APP : 0 called_name =''-->''
    OSR0100207 callp: sip_isdn:44b7a9e6-6a90-4326-9c92-c153b4a0feeb (1) closeNetwork: send CallpExit to 'ip:server:t:mediation:55514:70:'
    OSR0100207 callp: mux_isdn:0 (1) ISDN[1](1606): APP : 17 calling_name ='xxx'-->'xxx'
    OSR0100207 callp: sip_isdn:44b7a9e6-6a90-4326-9c92-c153b4a0feeb (1)           
    OSR0100207 callp: sip_isdn:44b7a9e6-6a90-4326-9c92-c153b4a0feeb (1)           ip:server:t:mediation:55514:70:=true
    OSR0100207 callp: mux_isdn:0 (1) ISDN[1](1606): APP : CCA_RELEASE_CONF 5
    OSR0100207 callp: mux_isdn:0 (1) ISDN[1](1606): CC  : <-- state=CC_IDLE(1) ----------
    OSR0100207 callp: sip_isdn:44b7a9e6-6a90-4326-9c92-c153b4a0feeb (1) closeNetwork: network partners are
    OSR0100207 callp: sip_isdn:44b7a9e6-6a90-4326-9c92-c153b4a0feeb (1) Job is done, Bye!
    OSR0100207 callp: sip_isdn:44b7a9e6-6a90-4326-9c92-c153b4a0feeb (1) <<< Kill
    OSR0100207 callp: sip_isdn:44b7a9e6-6a90-4326-9c92-c153b4a0feeb (1) inboundCleanup: rc='Kill'
    OSR0100207 callp: sip_isdn:44b7a9e6-6a90-4326-9c92-c153b4a0feeb (1) BPROC: call.pid = 30500; call.pid2 = nil; pid = 30500; '101 30500 0 (has died)'
    OSR0100207 callp: mux_sip:0 (1) send to 'sip_isdn:44b7a9e6-6a90-4326-9c92-c153b4a0feeb'
    OSR0100207 callp: mux_isdn:0 (1) ISDN[1](1606): CC  : b_if='' b_interface='1.a/B%d/S2M/2xG704IDT_E1' b_ch=0

    Thanks!

    Wednesday, April 25, 2012 9:07 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    what is the extension number you are dialling so i can see whats happening in the translation.

    thanks

    neil

    Wednesday, April 25, 2012 12:30 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    extension : 2010

    translated number lync :+49xxx2010

    translated number lync :+49xxx2010

    translated number gateway :00xxx2010

    translation should be fine.

    called extension only rings once!

    changed the numbers in log!

    Wednesday, April 25, 2012 12:39 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    can you call from the PBX phone to a Lync extension?
    Wednesday, April 25, 2012 12:47 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    No, both directions do not work.

    But we have already used this S2M (same configuration) with the same gateway.

    We only assigned another FE-Pool to the gateway.

    Regards

    Wednesday, April 25, 2012 1:27 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    okay, can you perform a dial test from the gateway itself? I have used Audiocodes, NET and Dialogic in the past and i know you can with all these.

    If you can, does the anolgue phone ring more than once?

    If the signalling is hitting the pbx phone then i am wondering if its the return leg that causing the call to stop/ fail after a single ring - although i would have expected you to be able to answer the phone but there be no media.

    Neil

    Wednesday, April 25, 2012 1:33 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    But if you dial the complete number in the gateway you make an outsitecall over the PBX, why don't you call 2010 to the PBX because it is your internal extension in the PBX. How are your settings of the S2m?

    Is the newest Firmware installed.  Configure Debuglevel to default and Syslog to TCP. I missed in the log the important information.

    If you can read german try to use this link

    http://forum.ferrari-electronic.de/archive/index.php/f-29.html

    regards Holger Technical Specialist UC




    • Edited by Holger Bunkradt Wednesday, April 25, 2012 3:11 PM
    • Marked as answer by JaSch Monday, August 18, 2014 9:10 AM
    Wednesday, April 25, 2012 2:52 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    This looks like some misconfiguration of translation rules on gateway or the pbx.

    -Santosh

    Tuesday, May 8, 2012 5:05 AM