Page 1 of 1

ATTIVARE un CONTATTO SU una PORTA FXS in parallelo al telefo

PostPosted: 27/11/2015, 12:56
by roberto.mainenti@mainplus.eu
BUONGIORNO A TUTTI,

avrei bisogno di attivare un contatto in parallelo ad un telefono!, in quanto la vecchia centrale lo faceva (SELTA).

mi hanno collegato un contatto in parallelo al telefono, ora sto provando a realizzarlo in ufficio,

vi allego script di cosa succede quando attivo contatto:
Nov 25 12:28:36 syslog: CallManager [BF23] C81 - Send CallSetupA
Nov 25 12:28:36 syslog: SipEngine [BF24] [default] C81 CallSetupA()
Nov 25 12:28:36 syslog: CallTable [BF25] AddRefCall - Interface sip-default try to add reference to call 81.
Nov 25 12:28:36 syslog: CallTable [BF26] AddRefCall - Interface sip-default add reference to call 81.
Nov 25 12:28:36 syslog: SipEngine [BF27] [default] L2 N2 C81 CCallCx::Invite.
Nov 25 12:28:36 syslog: SipEngine [BF28] [default] L2 N2 C81 CCallCx::CreateClientContext From(10.135.0.1:0) To(10.135.0.1:0).
Nov 25 12:28:36 syslog: RTP [BF29] CRtpConnection::Open() - Enter - AID2, SID0x00000051
Nov 25 12:28:36 syslog: RTP [BF2A] CRtpConnection::SelectSessionMode() - Success - mode = 0, - AID2, SID0x00000051
Nov 25 12:28:36 syslog: RTP [BF2B] CRtpPacketizer::ModifySettings() - encoding = G729, ptime out = 20, payload size = 20, SID size = 2
Nov 25 12:28:36 syslog: RTP [BF2C] CRtpConnection::SelectCompressionAlgorithm() - Success - payload = PCMU ptime = 20, - AID2, SID0x00000051
Nov 25 12:28:36 syslog: RTP [BF2D] CRtpSession::Open() - Enter - AID2, SID0x00000051
Nov 25 12:28:36 syslog: RTP [BF2E] CRtpSession: Generate random sequence number (53536) and timestamp - AID2, SID0x00000051
Nov 25 12:28:36 syslog: RTP [BF2F] CUdpSocket::Create() - Success
Nov 25 12:28:36 syslog: RTP [BF30] CUdpSocket::Bind() - Success - :::5004
Nov 25 12:28:36 syslog: RTP [BF31] CUdpSocket::Connect() - Success - 0.0.0.0:0
Nov 25 12:28:36 syslog: RTP [BF32] CUdpSocket::SetAllowAnySource() - Success
Nov 25 12:28:36 syslog: RTP [BF33] CUdpSocket::SetUdpChecksum() - Success
Nov 25 12:28:36 syslog: RTP [BF34] CUdpSocket::SetTos() - Success - Tos= 0
Nov 25 12:28:36 syslog: RTP [BF35] CUdpSocket::SetTrafficClass() - Success - TrafficClass= 0
Nov 25 12:28:36 syslog: RTP [BF36] CUdpSocket::Set8021QUserPriority() - Success - Priority = 6
Nov 25 12:28:36 syslog: RTP [BF37] CRtpSession::Open() - Success - AID2, SID0x00000051
Nov 25 12:28:36 syslog: RTP [BF38] CRtpConnection::Open() - Success - AID2, SID0x00000051
Nov 25 12:28:36 syslog: RTP [BF39] CRtpEngine::OpenConnection() - Success - AID2, CID0x00000051
Nov 25 12:28:36 syslog: SipEngine [BF3A] [default] L2 N2 C81 - RTP stream state change from 'IDLE' to 'INACTIVE'.
Nov 25 12:28:36 syslog: SipEngine [BF3B] [default] L2 N2 C81 Context 0x015107C0 created.
Nov 25 12:28:36 syslog: SipEngine [BF3C] [default] L2 N2 C81 Sending invite (BASIC_CALL).
Nov 25 12:28:36 syslog: SipEngine [BF3D] [default] L2 N2 C81 CSipMediaNegotiation::Send - State='Idle' Reliable=yes Stream=idle Neg=full MustResp=yes
Nov 25 12:28:37 syslog: SipEngine [BF3E] [default] L2 N2 C81 CSipMediaNegotiation::Send - Generate an offer.
Nov 25 12:28:37 syslog: SdpTools [BF3F] CSessionManager::GenerateOffer(0x157bd3c) returns SUCCESS.
Nov 25 12:28:37 syslog: SipEngine [BF40] [default] L2 N2 C81 Negotiation state change from 'Idle' to 'Wait Answer'.
Nov 25 12:28:37 syslog: SipEngine [BF41] [default] L2 N2 C81 Call state change from IDLE to TRYING.
Nov 25 12:28:37 syslog: SipSignaling [BF42] > [10.135.0.36:5060] Sending SIP packet to: 10.135.0.1:5060
Nov 25 12:28:37 syslog: SipSignaling [BF43] > INVITE sip:30@10.135.0.1;maddr=10.135.0.1 SIP/2.0
Nov 25 12:28:37 syslog: SipSignaling [BF44] > Via: SIP/2.0/UDP 10.135.0.36;branch=z9hG4bK75cd9f56c2bb90c31
Nov 25 12:28:37 syslog: SipSignaling [BF45] > Max-Forwards: 70
Nov 25 12:28:37 syslog: SipSignaling [BF46] > From: "port2" <sip:36@10.135.0.1>;tag=d68e99be0f
Nov 25 12:28:37 syslog: SipSignaling [BF47] > To: <sip:30@10.135.0.1>
Nov 25 12:28:37 syslog: SipSignaling [BF48] > Call-ID: fc4d2bbdabda870a
Nov 25 12:28:37 syslog: SipSignaling [BF49] > CSeq: 1839812554 INVITE
Nov 25 12:28:37 syslog: SipSignaling [BF4A] > Allow: INVITE, ACK, BYE, CANCEL, REFER, NOTIFY, UPDATE, OPTIONS
Nov 25 12:28:37 syslog: SipSignaling [BF4B] > Contact: "port2" <sip:36@10.135.0.36:5060;transport=udp>
Nov 25 12:28:37 syslog: SipSignaling [BF4C] > Supported: sdp-anat
Nov 25 12:28:37 syslog: SipSignaling [BF4D] > Supported: replaces
Nov 25 12:28:37 syslog: SipSignaling [BF4E] > User-Agent: Wildix W04FXS 2.0.22.320 0090f80600e9
Nov 25 12:28:37 syslog: SipSignaling [BF4F] > Content-Type: application/sdp
Nov 25 12:28:37 syslog: SipSignaling [BF50] > Content-Length: 262
Nov 25 12:28:37 syslog: SipSignaling [BF51] >
Nov 25 12:28:37 syslog: SipSignaling [BF52] > v=0
Nov 25 12:28:37 syslog: SipSignaling [BF53] > o=MxSIP 33595980832537815 561915856204931370 IN IP4 10.135.0.36
Nov 25 12:28:37 syslog: SipSignaling [BF54] > s=-
Nov 25 12:28:37 syslog: SipSignaling [BF55] > c=IN IP4 10.135.0.36
Nov 25 12:28:37 syslog: SipSignaling [BF56] > t=0 0
Nov 25 12:28:37 syslog: SipSignaling [BF57] > a=sendrecv
Nov 25 12:28:37 syslog: SipSignaling [BF58] > m=audio 5004 RTP/AVP 18 99 8 0
Nov 25 12:28:37 syslog: SipSignaling [BF59] > a=rtpmap:18 G729/8000
Nov 25 12:28:37 syslog: SipSignaling [BF5A] > a=rtpmap:99 G726-32/8000
Nov 25 12:28:37 syslog: SipSignaling [BF5B] > a=rtpmap:8 PCMA/8000
Nov 25 12:28:37 syslog: SipSignaling [BF5C] > a=rtpmap:0 PCMU/8000
Nov 25 12:28:37 syslog: SipSignaling [BF5D] > a=fmtp:18 annexb=no
Nov 25 12:28:37 syslog: SipSignaling [BF5E] < [10.135.0.36:5060] Received SIP packet from: 10.135.0.1:5060
Nov 25 12:28:37 syslog: SipSignaling [BF5F] < SIP/2.0 407 Proxy Authentication Required
Nov 25 12:28:37 syslog: SipSignaling [BF60] < Via: SIP/2.0/UDP 10.135.0.36;branch=z9hG4bK75cd9f56c2bb90c31;rport=5060
Nov 25 12:28:37 syslog: SipSignaling [BF61] < From: "port2" <sip:36@10.135.0.1>;tag=d68e99be0f
Nov 25 12:28:37 syslog: SipSignaling [BF62] < To: <sip:30@10.135.0.1>;tag=b27e1a1d33761e85846fc98f5f3a7e58.2026
Nov 25 12:28:37 syslog: SipSignaling [BF63] < Call-ID: fc4d2bbdabda870a
Nov 25 12:28:37 syslog: SipSignaling [BF64] < CSeq: 1839812554 INVITE
Nov 25 12:28:37 syslog: SipSignaling [BF65] < Proxy-Authenticate: Digest realm="10.135.0.1", nonce="VlWdulZVm2Ij4XtZ65dab/w26KvFIKrb"
Nov 25 12:28:37 syslog: SipSignaling [BF66] < Server: Wildix GW-4.2.5.30176
Nov 25 12:28:37 syslog: SipSignaling [BF67] < Content-Length: 0
Nov 25 12:28:37 syslog: SipSignaling [BF68] <
Nov 25 12:28:37 syslog: SipEngine [BF69] [default] CClientAuthCx::TryFirstPassword - Trying to authenticate user '36' for realm '10.135.0.1'.
Nov 25 12:28:37 syslog: PotsEndPoint [BF6A] EP2 CAS HAPI_CAS_DETECT_EVENT 1.
Nov 25 12:28:37 syslog: PotsEndPoint [BF6B] EP2 HookStateDetected. bOnHook:1, m_eLastHookEventSent: eLHE_OFF_HOOK_EVENT
Nov 25 12:28:37 syslog: PotsEndPoint [BF6C] EP2 HHEvent - On hook detected.
Nov 25 12:28:37 syslog: SipSignaling [BF6D] > [10.135.0.36:5060] Sending SIP packet to: 10.135.0.1:5060
Nov 25 12:28:37 syslog: SipSignaling [BF6E] > ACK sip:30@10.135.0.1;maddr=10.135.0.1 SIP/2.0
Nov 25 12:28:37 syslog: SipSignaling [BF6F] > Via: SIP/2.0/UDP 10.135.0.36;branch=z9hG4bK75cd9f56c2bb90c31
Nov 25 12:28:37 syslog: SipSignaling [BF70] > Max-Forwards: 70
Nov 25 12:28:37 syslog: SipSignaling [BF71] > From: "port2" <sip:36@10.135.0.1>;tag=d68e99be0f
Nov 25 12:28:37 syslog: SipSignaling [BF72] > To: <sip:30@10.135.0.1>;tag=b27e1a1d33761e85846fc98f5f3a7e58.2026
Nov 25 12:28:37 syslog: SipSignaling [BF73] > Call-ID: fc4d2bbdabda870a
Nov 25 12:28:37 syslog: SipSignaling [BF74] > CSeq: 1839812554 ACK
Nov 25 12:28:37 syslog: SipSignaling [BF75] > User-Agent: Wildix W04FXS 2.0.22.320 0090f80600e9
Nov 25 12:28:37 syslog: SipSignaling [BF76] > Content-Length: 0
Nov 25 12:28:37 syslog: SipSignaling [BF77] >
Nov 25 12:28:37 syslog: SipSignaling [BF78] > [10.135.0.36:5060] Sending SIP packet to: 10.135.0.1:5060
Nov 25 12:28:37 syslog: SipSignaling [BF79] > INVITE sip:30@10.135.0.1;maddr=10.135.0.1 SIP/2.0
Nov 25 12:28:37 syslog: SipSignaling [BF7A] > Via: SIP/2.0/UDP 10.135.0.36;branch=z9hG4bK20a0b4c2f9e48e8c6
Nov 25 12:28:37 syslog: SipSignaling [BF7B] > Proxy-Authorization: Digest username="36",realm="10.135.0.1",nonce="VlWdulZVm2Ij4XtZ65dab/w26KvFIKrb",uri="sip:30@10.135.0.1;maddr=10.135.0.1",response="d098676e160c2c13fbe09e9a97abc45e"
Nov 25 12:28:37 syslog: SipSignaling [BF7C] > Max-Forwards: 70
Nov 25 12:28:37 syslog: SipSignaling [BF7D] > From: "port2" <sip:36@10.135.0.1>;tag=d68e99be0f
Nov 25 12:28:37 syslog: SipSignaling [BF7E] > To: <sip:30@10.135.0.1>
Nov 25 12:28:37 syslog: SipSignaling [BF7F] > Call-ID: fc4d2bbdabda870a
Nov 25 12:28:37 syslog: SipSignaling [BF80] > CSeq: 1839812555 INVITE
Nov 25 12:28:37 syslog: SipSignaling [BF81] > Allow: INVITE, ACK, BYE, CANCEL, REFER, NOTIFY, UPDATE, OPTIONS
Nov 25 12:28:37 syslog: SipSignaling [BF82] > Contact: "port2" <sip:36@10.135.0.36:5060;transport=udp>
Nov 25 12:28:37 syslog: SipSignaling [BF83] > Supported: sdp-anat
Nov 25 12:28:37 syslog: SipSignaling [BF84] > Supported: replaces
Nov 25 12:28:37 syslog: SipSignaling [BF85] > User-Agent: Wildix W04FXS 2.0.22.320 0090f80600e9
Nov 25 12:28:37 syslog: SipSignaling [BF86] > Content-Type: application/sdp
Nov 25 12:28:37 syslog: SipSignaling [BF87] > Content-Length: 262
Nov 25 12:28:37 syslog: SipSignaling [BF88] >
Nov 25 12:28:37 syslog: SipSignaling [BF89] > v=0
Nov 25 12:28:37 syslog: SipSignaling [BF8A] > o=MxSIP 33595980832537815 561915856204931370 IN IP4 10.135.0.36
Nov 25 12:28:37 syslog: SipSignaling [BF8B] > s=-
Nov 25 12:28:37 syslog: SipSignaling [BF8C] > c=IN IP4 10.135.0.36
Nov 25 12:28:37 syslog: SipSignaling [BF8D] > t=0 0
Nov 25 12:28:37 syslog: SipSignaling [BF8E] > a=sendrecv
Nov 25 12:28:37 syslog: SipSignaling [BF8F] > m=audio 5004 RTP/AVP 18 99 8 0
Nov 25 12:28:37 syslog: SipSignaling [BF90] > a=rtpmap:18 G729/8000
Nov 25 12:28:37 syslog: SipSignaling [BF91] > a=rtpmap:99 G726-32/8000
Nov 25 12:28:37 syslog: SipSignaling [BF92] > a=rtpmap:8 PCMA/8000
Nov 25 12:28:37 syslog: SipSignaling [BF93] > a=rtpmap:0 PCMU/8000
Nov 25 12:28:37 syslog: SipSignaling [BF94] > a=fmtp:18 annexb=no
Nov 25 12:28:37 syslog: FxsInterface [BF95] [Port2] L2 N2 - Event OnHook() on state "CONTROL WAITRES"
Nov 25 12:28:37 syslog: CallTable [BF96] ReleaseCall - Interface fxs-Port2 try to release call 79.
Nov 25 12:28:37 syslog: CallTable [BF97] ReleaseCall - Interface fxs-Port2 release call 79.
Nov 25 12:28:37 syslog: FxsInterface [BF98] [Port2] L2 N2 - Change state from "CONTROL WAITRES" to "ONHOOK COMPLEX"
Nov 25 12:28:37 syslog: FxsInterface [BF99] [Port2] L2 N2 - Change state from "ONHOOK COMPLEX" to "ONHOOK IDLE"
Nov 25 12:28:37 syslog: PotsEndPoint [BF9A] EP2 DataTransmission TransType: 12 ModType: 2
Nov 25 12:28:37 syslog: PotsEndPoint [BF9B] EP2 CAS HAPI_CAS_DETECT_EVENT 1.
Nov 25 12:28:37 syslog: PotsEndPoint [BF9C] EP2 HookStateDetected. bOnHook:1, m_eLastHookEventSent: eLHE_ON_HOOK_EVENT
Nov 25 12:28:37 syslog: PotsEndPoint [BF9D] EP2 Ignoring Double on hook detection
Nov 25 12:28:37 syslog: SipSignaling [BF9E] < [10.135.0.36:5060] Received SIP packet from: 10.135.0.1:5060
Nov 25 12:28:37 syslog: SipSignaling [BF9F] < SIP/2.0 100 trying -- your call is important to us
Nov 25 12:28:37 syslog: SipSignaling [BFA0] < Via: SIP/2.0/UDP 10.135.0.36;branch=z9hG4bK20a0b4c2f9e48e8c6;rport=5060
Nov 25 12:28:37 syslog: SipSignaling [BFA1] < From: "port2" <sip:36@10.135.0.1>;tag=d68e99be0f
Nov 25 12:28:37 syslog: SipSignaling [BFA2] < To: <sip:30@10.135.0.1>
Nov 25 12:28:37 syslog: SipSignaling [BFA3] < Call-ID: fc4d2bbdabda870a
Nov 25 12:28:37 syslog: SipSignaling [BFA4] < CSeq: 1839812555 INVITE
Nov 25 12:28:37 syslog: SipSignaling [BFA5] < Server: Wildix GW-4.2.5.30176
Nov 25 12:28:37 syslog: SipSignaling [BFA6] < Content-Length: 0
Nov 25 12:28:37 syslog: SipSignaling [BFA7] <
Nov 25 12:28:37 syslog: CallManager [BFA8] C79 - CallReleaseA(16, -1)
Nov 25 12:28:37 syslog: CallTable [BFA9] ReleaseCall - Interface cm-CM try to release call 79.
Nov 25 12:28:37 syslog: CallTable [BFAA] ReleaseCall - Interface cm-CM release call 79.
Nov 25 12:28:37 syslog: CallManager [BFAB] C81 - Send CallReleaseA(16)
Nov 25 12:28:37 syslog: SipEngine [BFAC] [default] C81 CallReleaseA(16)
Nov 25 12:28:37 syslog: SipEngine [BFAD] [default] L2 N2 C81 Terminate. Reason: 16.
Nov 25 12:28:37 syslog: SipEngine [BFAE] [default] L2 N2 C81 CCallCx::CmSendCallRelease cannot send a call release with cause 16 since the call is already released.
Nov 25 12:28:37 syslog: SipEngine [BFAF] [default] L2 N2 C81 Cancelling client transaction.
Nov 25 12:28:37 syslog: SipEngine [BFB0] [default] L2 N2 C81 Call state change from TRYING to CANCELLING.
Nov 25 12:28:37 syslog: RTP [BFB1] CUdpSocket::Close() - Success
Nov 25 12:28:37 syslog: RTP [BFB2] CRtpSession::Close() - Success - AID2, SID0x00000051
Nov 25 12:28:37 syslog: RTP [BFB3] CRtpConnection::Close() - AID2, SID0x00000051
Nov 25 12:28:37 syslog: RTP [BFB4] CRtpEngine::CloseConnection() - Success - AID2, CID0x00000051
Nov 25 12:28:37 syslog: SipEngine [BFB5] [default] L2 N2 C81 - RTP stream state change from 'INACTIVE' to 'INITIALIZED'.
Nov 25 12:28:37 syslog: SipSignaling [BFB6] > [10.135.0.36:5060] Sending SIP packet to: 10.135.0.1:5060
Nov 25 12:28:37 syslog: SipSignaling [BFB7] > CANCEL sip:30@10.135.0.1;maddr=10.135.0.1 SIP/2.0
Nov 25 12:28:37 syslog: SipSignaling [BFB8] > Via: SIP/2.0/UDP 10.135.0.36;branch=z9hG4bK20a0b4c2f9e48e8c6
Nov 25 12:28:37 syslog: SipSignaling [BFB9] > Max-Forwards: 70
Nov 25 12:28:37 syslog: SipSignaling [BFBA] > From: "port2" <sip:36@10.135.0.1>;tag=d68e99be0f
Nov 25 12:28:37 syslog: SipSignaling [BFBB] > To: <sip:30@10.135.0.1>
Nov 25 12:28:37 syslog: SipSignaling [BFBC] > Call-ID: fc4d2bbdabda870a
Nov 25 12:28:37 syslog: SipSignaling [BFBD] > CSeq: 1839812555 CANCEL
Nov 25 12:28:37 syslog: SipSignaling [BFBE] > User-Agent: Wildix W04FXS 2.0.22.320 0090f80600e9
Nov 25 12:28:37 syslog: SipSignaling [BFBF] > Content-Length: 0
Nov 25 12:28:37 syslog: SipSignaling [BFC0] >
Nov 25 12:28:37 syslog: SipSignaling [BFC1] < [10.135.0.36:5060] Received SIP packet from: 10.135.0.1:5060
Nov 25 12:28:37 syslog: SipSignaling [BFC2] < SIP/2.0 200 canceling
Nov 25 12:28:37 syslog: SipSignaling [BFC3] < Via: SIP/2.0/UDP 10.135.0.36;branch=z9hG4bK20a0b4c2f9e48e8c6;rport=5060
Nov 25 12:28:37 syslog: SipSignaling [BFC4] < From: "port2" <sip:36@10.135.0.1>;tag=d68e99be0f
Nov 25 12:28:37 syslog: SipSignaling [BFC5] < To: <sip:30@10.135.0.1>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-f563
Nov 25 12:28:37 syslog: SipSignaling [BFC6] < Call-ID: fc4d2bbdabda870a
Nov 25 12:28:37 syslog: SipSignaling [BFC7] < CSeq: 1839812555 CANCEL
Nov 25 12:28:37 syslog: SipSignaling [BFC8] < Server: Wildix GW-4.2.5.30176
Nov 25 12:28:37 syslog: SipSignaling [BFC9] < Content-Length: 0
Nov 25 12:28:37 syslog: SipSignaling [BFCA] <
Nov 25 12:28:37 syslog: CallManager [BFCB] C81 - CallProgressA(3)
Nov 25 12:28:37 syslog: CallManager [BFCC] C79 - Send CallProgressA(3)
Nov 25 12:28:37 syslog: FxsInterface [BFCD] [Port2] L2 N2 - The received progressing 3 is ignored.
Nov 25 12:28:37 syslog: FxsInterface [BFCE] [Port2] L2 N2 - Event EnableLine() on state "ONHOOK IDLE"
Nov 25 12:28:37 syslog: FxsInterface [BFCF] [Port2] L2 N2 - Event EnableLine was not handled by state "ONHOOK IDLE", send the event to his parent "ONHOOK COMPLEX"
Nov 25 12:28:37 syslog: FxsInterface [BFD0] [Port2] L2 N2 - Event EnableLine was not handled by state "ONHOOK COMPLEX", send the event to his parent "ROOT"
Nov 25 12:28:37 syslog: FxsInterface [BFD1] [Port2] L2 N2 - Event EnableLine was not handled
Nov 25 12:28:37 SipEp: 1400-SIP Endpoint: 100-New outgoing call 81 from 36@10.135.0.1 to 30@10.135.0.1 on endpoint Port2.
Nov 25 12:28:37 syslog: Admin [BFD2] Port2 usage state is now Idle.
Nov 25 12:28:37 syslog: SipSignaling [BFD3] < [10.135.0.36:5060] Received SIP packet from: 10.135.0.1:5060
Nov 25 12:28:37 syslog: SipSignaling [BFD4] < SIP/2.0 487 Request Terminated
Nov 25 12:28:37 syslog: SipSignaling [BFD5] < Via: SIP/2.0/UDP 10.135.0.36;rport=5060;branch=z9hG4bK20a0b4c2f9e48e8c6
Nov 25 12:28:37 syslog: SipSignaling [BFD6] < From: "port2" <sip:36@10.135.0.1>;tag=d68e99be0f
Nov 25 12:28:37 syslog: SipSignaling [BFD7] < To: <sip:30@10.135.0.1>;tag=as771d31c7
Nov 25 12:28:37 syslog: SipSignaling [BFD8] < Call-ID: fc4d2bbdabda870a
Nov 25 12:28:37 syslog: SipSignaling [BFD9] < CSeq: 1839812555 INVITE
Nov 25 12:28:37 syslog: SipSignaling [BFDA] < Server: WildixGW 30191
Nov 25 12:28:37 syslog: SipSignaling [BFDB] < Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Nov 25 12:28:37 syslog: SipSignaling [BFDC] < Supported: replaces, timer
Nov 25 12:28:37 syslog: SipSignaling [BFDD] < Caller-Image: http://10.135.0.1/user_avatar/30.png
Nov 25 12:28:37 syslog: SipSignaling [BFDE] < Content-Length: 0
Nov 25 12:28:37 syslog: SipSignaling [BFDF] < X-Next-Hop: 10.135.0.36
Nov 25 12:28:37 syslog: SipSignaling [BFE0] < X-Next-Hop-Port: 5060
Nov 25 12:28:37 syslog: SipSignaling [BFE1] < X-Dst-Addr: localnet
Nov 25 12:28:37 syslog: SipSignaling [BFE2] <
Nov 25 12:28:37 syslog: SipEngine [BFE3] [default] L2 N2 C81 CCallCx::EvFailure on call context 0x015107C0 (0).
Nov 25 12:28:37 syslog: SipEngine [BFE4] [default] L2 N2 C81 Call state change from CANCELLING to TERMINATED.
Nov 25 12:28:37 syslog: SipEngine [BFE5] [default] L2 N2 C81 CCallCx::CmSendCallRelease cannot send a call release with cause 16 since the call is already released.
Nov 25 12:28:37 syslog: SipEngine [BFE6] [default] L2 N2 C81 Releasing call context 0x015107C0.
Nov 25 12:28:37 syslog: CallTable [BFE7] ReleaseCall - Interface sip-default try to release call 81.
Nov 25 12:28:37 syslog: CallTable [BFE8] ReleaseCall - Interface sip-default release call 81.
Nov 25 12:28:37 syslog: CallTable [BFE9] ReleaseCall - Call 79-81 released.
Nov 25 12:28:37 syslog: SipSignaling [BFEA] > [10.135.0.36:5060] Sending SIP packet to: 10.135.0.1:5060
Nov 25 12:28:37 syslog: SipSignaling [BFEB] > ACK sip:30@10.135.0.1;maddr=10.135.0.1 SIP/2.0
Nov 25 12:28:37 syslog: SipSignaling [BFEC] > Via: SIP/2.0/UDP 10.135.0.36;branch=z9hG4bK20a0b4c2f9e48e8c6
Nov 25 12:28:37 syslog: SipSignaling [BFED] > Max-Forwards: 70
Nov 25 12:28:37 syslog: SipSignaling [BFEE] > From: "port2" <sip:36@10.135.0.1>;tag=d68e99be0f
Nov 25 12:28:37 syslog: SipSignaling [BFEF] > To: <sip:30@10.135.0.1>;tag=as771d31c7
Nov 25 12:28:37 syslog: SipSignaling [BFF0] > Call-ID: fc4d2bbdabda870a
Nov 25 12:28:37 syslog: SipSignaling [BFF1] > CSeq: 1839812555 ACK
Nov 25 12:28:37 syslog: SipSignaling [BFF2] > User-Agent: Wildix W04FXS 2.0.22.320 0090f80600e9
Nov 25 12:28:37 syslog: SipSignaling [BFF3] > Content-Length: 0
Nov 25 12:28:37 syslog: SipSignaling [BFF4] >
Nov 25 12:28:37 syslog: Admin [BFF5] Slot0 usage state is now Idle.
Nov 25 12:28:37 syslog: Admin [BFF6] Unit usage state is now Idle.
Nov 25 12:28:37 syslog: Admin [BFF7] Activate endpoint Port2.
Nov 25 12:28:37 syslog: PotsEndPoint [BFF8] EP2 HAPI_CAS_STATECTL_EVENT 8
Nov 25 12:28:37 syslog: FxsInterface [BFF9] [Port2] L2 N2 - Event EnableLine() on state "ONHOOK IDLE"
Nov 25 12:28:37 syslog: FxsInterface [BFFA] [Port2] L2 N2 - Event EnableLine was not handled by state "ONHOOK IDLE", send the event to his parent "ONHOOK COMPLEX"
Nov 25 12:28:37 syslog: FxsInterface [BFFB] [Port2] L2 N2 - Event EnableLine was not handled by state "ONHOOK COMPLEX", send the event to his parent "ROOT"
Nov 25 12:28:37 syslog: FxsInterface [BFFC] [Port2] L2 N2 - Event EnableLine was not handled
Nov 25 12:28:37 syslog: PotsEndPoint [BFFD] EP2 RawData = 82030B01006F
Nov 25 12:28:38 syslog: LineEngine [BFFE] EP2 LowLevel report gen ind2: trans_id=5780 group_status=3 fn_id=7208970
Nov 25 12:28:38 syslog: PotsEndPoint [BFFF] EP2 - Received VbdGenerationEvent. m_eCallerIdState == 2. m_CallerIdInfoBuffer.m_bDataSent == 1
Nov 25 12:28:38 syslog: FxsInterface [C000] [Port2] L2 N2 - Event VmwiTerminated(1) on state "ONHOOK IDLE"
Nov 25 12:28:38 syslog: PotsEndPoint [C001] EP2 Cancelling current VBD generation.
Nov 25 12:28:38 syslog: LineEngine [C002] EP2 Released.
Nov 25 12:28:38 syslog: LineEngine [C003] EP2 LowLevel report channel closed : id=0
Nov 25 12:28:53 syslog: Network [C004] LLDP (2 - Uplink): Changed state from eRX_WAIT_FOR_FRAME to eRX_FRAME
Nov 25 12:28:53 syslog: Network [C005] LLDP (2 - Uplink): Chassis Id (01:0a:87:00:4d::05) Subtype (5)
Nov 25 12:28:53 syslog: Network [C006] LLDP (2 - Uplink): Port Id (30:30:30:34:31:33:32:36:36:44:37:43:3a:50:31::07) Subtype (7)
Nov 25 12:28:53 syslog: Network [C007] LLDP (2 - Uplink): TTL (180)
Nov 25 12:28:53 syslog: Network [C008] LLDP (2 - Uplink): Port description (NET PORT)
Nov 25 12:28:53 syslog: Network [C009] LLDP (2 - Uplink): System name (snom370)
Nov 25 12:28:53 syslog: Network [C00A] LLDP (2 - Uplink): System description (snom;snom370-SIP 8.7.3.25.5;lid:8.7.3.25.5)
Nov 25 12:28:53 syslog: Network [C00B] LLDP (2 - Uplink): System capabilities (Bridge enable, Telephone enable, )
Nov 25 12:28:53 syslog: Network [C00C] LLDP-MED (2 - Uplink): Capabilities (Capabilities NetworkPolicy ExtendedPD Inventory )
Nov 25 12:28:53 syslog: Network [C00D] LLDP-MED (2 - Uplink): Device type (CLASSIII)
Nov 25 12:28:53 syslog: Network [C00E] LLDP-MED (2 - Uplink): Network policy (Voice Unknown Untagged VLanId 0 L2 Priority 0 Dscp 0)
Nov 25 12:28:53 syslog: Network [C00F] LLDP (2 - Uplink): Update MSAP Cache (30:30:30:34:31:33:32:36:36:44:37:43:3a:50:31::0701:0a:87:00:4d::05) - Changes (0) Cache Size (1)
Nov 25 12:28:53 syslog: Network [C010] LLDP (2 - Uplink): Changed state from eRX_FRAME to eRX_WAIT_FOR_FRAME
Nov 25 12:28:55 syslog: Network [C011] LLDP (2 - Uplink): Changed state from TX_IDLE to TX_INFO_FRAME
Nov 25 12:28:55 syslog: Network [C012] LLDP (2 - Uplink): Changed state from TX_INFO_FRAME to TX_IDLE

dovrei riuscire a trovare il modo di diversificare o trovare un comando all'interno di questo script, che identifichi il contatto. e poi creare una regola sul pbx.

GRAZIE A TUTTI

Re: ATTIVARE un CONTATTO SU una PORTA FXS in parallelo al te

PostPosted: 28/11/2015, 0:31
by bruno.donetti@axitea.it
Ciao ma cosa intendi per attivare un contatto?
Deve chiudersi quando interno fxs suona o è in stato impegnato?
Oppure quando viene chiuso genera una chiamata dal telefono fxs ?
Come è collegato sul fxs ?

Re: ATTIVARE un CONTATTO SU una PORTA FXS in parallelo al te

PostPosted: 01/12/2015, 14:24
by roberto.mainenti@mainplus.eu
in parallelo al telefono è stato collegato un tirante bagno, in caso venga tirato il tirante deve mandare un allarme alla centrale!, il problema è che ho un solo doppino che utilizzo per telefono e contatto in parallelo, quindi vorrei capire se l'fxs da un segnale diverso rispetto all'impegno della line o della chiamata in modo da poter gestire separatamente le cose!

grazie

Re: ATTIVARE un CONTATTO SU una PORTA FXS in parallelo al te

PostPosted: 01/12/2015, 14:25
by roberto.mainenti@mainplus.eu
in realtà se avessi solo il contatto avrei gia' risolto! ma il problema è avere telefono e contatto su stessa porta !

Re: ATTIVARE un CONTATTO SU una PORTA FXS in parallelo al te

PostPosted: 01/12/2015, 16:23
by bruno.donetti@axitea.it
Ma prima con il Selta il contatto Bagno era collegato spero sul telefono digitale che se non ricordo male aveva un ingresso particolare per Ingresso Pulito ...
Se così è , una volta si usavano delle borchie allarme che si mettevano in serie alla FXS ( tipo i combinatori allarme antifurto) e quando il contatto chiudeva la borchia inviava una chiamata da qualche parte .
Io usavo la sudel di bari per queste cose ma penso che oramai sia un epoca finita , puoi vedere tipo la teledif che vende delle cose analoghe per allarmi ascensori ...

Re: ATTIVARE un CONTATTO SU una PORTA FXS in parallelo al te

PostPosted: 01/12/2015, 19:24
by roberto.mainenti@mainplus.eu
confermo che selta lo faceva anche su analogici ma con un filo di terra in piu'!

comunque sono riuscito a risolvere il problema !

grazie a tutti!

Re: ATTIVARE un CONTATTO SU una PORTA FXS in parallelo al te

PostPosted: 02/12/2015, 10:14
by matteo.erba
Ci spieghi come Roberto? Credo possa essere di interesse comune :D

Re: ATTIVARE un CONTATTO SU una PORTA FXS in parallelo al te

PostPosted: 02/12/2015, 11:25
by roberto.mainenti@mainplus.eu
sugli fxs 4 esiste sotto la voce telefoni service la voce hotline!

attivandola con tempistiche e interno che si vuole chiamare, si puo' far partire una chiamata.

sul contatto necessario un rele' che mantenga contatto chiuso per il tempo impostato!

ed il gioco è fatto!

Re: ATTIVARE un CONTATTO SU una PORTA FXS in parallelo al te

PostPosted: 04/12/2015, 17:02
by matteo.erba
http://www.tematlc.it/Documentazione/AC-16-DEP-1501.pdf

Questo è il prodotto che secondo me fa al caso tuo, nasce proprio per gestire allarmi su linee analogiche.

Gia utilizzato da altri partner su allarmi bagno e centrali di allarme antincendio e antifurto