3CX Hotel Module Update now works seamlessly with 3CX Phone System 12, Service Pack 6. Includes new features and improvements.

3CX Hotel Module Update

July 17, 2014 - 02:58pm

We are pleased to announce the release of an update of 3CX Hotel Module. This update of 3CX Hotel Module is designed to work seamlessly with 3CX Phone System 12, Service Pack 6. 3CX Hotel Module, is an add-on for 3CX Phone System. Once installed, it

3CX has organised a series of 3CX WebCasts this July and August. All 3CX WebCasts are free.

Upcoming Series of Free 3CX Trainings this July and August!

July 16, 2014 - 11:21am

We are pleased to announce free upcoming 3CX Trainings which will be held this July and August! These free trainings, which will be held by with 3CX WebMeeting and are  hosted by 3CX, will be demonstrating an Introduction to 3CX Phone System, Upgrading

3CX PBX • View topic - Anrufe sofort auf die Mailbox
3CX PBX • View topic - Anrufe sofort auf die Mailbox

Anrufe sofort auf die Mailbox

Allgemeiner Support zur 3CX IP-Telefonanlage sowie zu VoIP und SIP (Community-gestützt).User-to-User-Support - Forum zum Erfahrungsaustausch mit anderen 3CX-Anwendern. Über dieses Forum steht KEIN technischer Support durch 3CX zur Verfügung.

Moderator: 3CX staff

Anrufe sofort auf die Mailbox

Postby user2705 » Tue Nov 29, 2011 9:49 pm

Hallo,
Wir haben jetzt seit einiger Zeit eine Agfeo über eine Mediatrix Gateway mit der 3CX verbunden. Das funktionierte soweit (nach etwas Forschungsarbeit;-)) sehr gut. An der 3CX haben wir einen Sipgate Trunk. Wir haben auf 3CX Seite ein paar Tiptels 286, und sonst noch Softwareclients - Android/Iphone/3CXPhone Windows. Seit 2 Tagen habe ich ein merkwürdiges Phänomen: Ich kann nur noch einen Account von der ISDN Seite aus erreichen. Hier klingelt das Telefon ganz normal. Bei allen anderen - egal welchen Account ich benutze - und egal mit welchem Client ich eingebucht bin - es geht immer die Voicemailbox ran (Attempt to reach <sip:414@192.168.147.35:5060> failed. Reason: Busy). Rufe ich den gleichen Account über den Sipgate Trunk an, klingel das Telefon ganz normal. Ich finde einfach den Fehler nicht.
Hier das Log vom gelungenen(oben) und vom nicht gelungenen Anruf (unten):

21:28:17.528 [CM503003]: Call(31): Call to sip:414@192.168.146.35:5060 has failed; Cause: 487 Request Terminated; from IP:192.168.146.35:5080
21:28:17.502 [CM503003]: Call(31): Call to sip:414@192.168.147.35 has failed; Cause: 487 Request Terminated; from IP:192.168.147.65:5062
21:28:16.884 [CM503008]: Call(31): Call is terminated
21:28:09.714 [CM505001]: Ext.414: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXPhone 6.0.20943.0] PBX contact: [sip:414@192.168.146.35:5060]
21:28:09.714 [CM503002]: Call(31): Alerting sip:414@127.0.0.1:50823;rinstance=b264af8a30b35632
21:28:09.656 [CM505001]: Ext.414: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Tiptel IP 286 2.60.13.11 00156517bdf1] PBX contact: [sip:414@192.168.147.35:5060]
21:28:09.655 [CM503002]: Call(31): Alerting sip:414@192.168.147.65:5062
21:28:09.123 [CM503025]: Call(31): Calling Ext:Ext.414@[Dev:sip:414@192.168.147.65:5062]
21:28:09.121 [MS210002] C:31.3:Offer provided. Connection(transcoding mode): 192.168.147.35:7156(7157)
21:28:09.115 [CM503025]: Call(31): Calling Ext:Ext.414@[Dev:sip:414@127.0.0.1:50823;rinstance=b264af8a30b35632]
21:28:09.112 [MS210002] C:31.2:Offer provided. Connection(transcoding mode): 192.168.146.35:7154(7155)
21:28:09.089 [CM503004]: Call(31): Route 1: Ext:Ext.414@[Dev:sip:414@127.0.0.1:50823;rinstance=b264af8a30b35632,Dev:sip:414@192.168.147.65:5062]
21:28:09.088 [CM503010]: Making route(s) to <sip:414@192.168.147.35:5060>
21:28:09.088 [MS210000] C:31.1:Offer received. RTP connection: 217.10.77.24:36124(36125)
21:28:09.087 Remote SDP is set for legC:31.1
21:28:09.086 [CM505003]: Provider:[SipgateTrunk] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:1027784t0@194.77.60.27:5060]
21:28:09.070 [CM503001]: Call(31): Incoming call from anonymous@(Ln.10000@SipgateTrunk) to <sip:414@192.168.147.35:5060>
21:28:09.058 [CM503012]: Inbound any hours rule (unnamed) for 10000 forwards to DN:414
21:28:09.057 Looking for inbound target: called=004975315848414; caller=anonymous
21:28:09.055 [CM500002]: Info on incoming INVITE:
INVITE sip:1027784t0@194.77.60.27:5060;rinstance=f746d15f03df1e2d SIP/2.0
Via: SIP/2.0/UDP 217.10.68.150:5060;branch=z9hG4bK87c.aeb8d9890fe1a716d61bf451445b564b.0
Via: SIP/2.0/UDP 172.20.40.5;branch=z9hG4bK87c.13ce17ead75e0865b96daa8ed4d87121.1
Via: SIP/2.0/UDP 217.10.68.150:5060;received=217.10.68.178;branch=z9hG4bK87c.a3c0bf0730038c69d8f10439d1e1aebf.0
Via: SIP/2.0/UDP 217.10.67.135:5060;branch=z9hG4bK1f06c78f;rport=5060
Max-Forwards: 67
Record-Route: <sip:217.10.68.150;lr;ftag=as7d5b2b54>
Record-Route: <sip:172.20.40.5;lr>
Record-Route: <sip:217.10.68.150;lr;ftag=as7d5b2b54>
Contact: <sip:anonymous@217.10.67.135>
To: <sip:004975315848414@sipconnect.sipgate.de>
From: "anonymous"<sip:anonymous@sipconnect.sipgate.de>;tag=as7d5b2b54
Call-ID: 0dea7bc744f4510554392f1f468b6699@sipconnect.sipgate.de
CSeq: 103 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO
Supported: replaces, timer
Content-Length: 0
X-LEGID: 68afce37

21:27:57.707 Currently active calls [none]
21:27:43.297 [CM503008]: Call(30): Call is terminated
21:27:42.626 [CM503003]: Call(29): Call to sip:414@192.168.146.35:5060 has failed; Cause: 487 Request Terminated; from IP:192.168.146.35:5080
21:27:38.146 [CM503003]: Call(29): Call to sip:414@192.168.147.35 has failed; Cause: 487 Request Terminated; from IP:192.168.147.65:5062
21:27:37.804 [CM503008]: Call(29): Call is terminated
21:27:37.621 Session 19973 of leg C:30.1 is confirmed
21:27:37.506 [CM503007]: Call(30): Device joined: sip:999@127.0.0.1:40600;rinstance=56b68c797a789841
21:27:37.499 [CM503007]: Call(30): Device joined: sip:10003@192.168.147.30:5060
21:27:37.497 [MS210003] C:30.1:Answer provided. Connection(transcoding mode[unsecure]):192.168.147.35:7150(7151)
21:27:37.494 [MS210001] C:30.2:Answer received. RTP connection[unsecure]: 127.0.0.1:40620(40621)
21:27:37.493 Remote SDP is set for legC:30.2
21:27:37.490 [CM505001]: Ext.999: Device info: Device Identified: [Man: 3CX Ltd.;Mod: Voice Mail Menu;Rev: 1] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX Voice Mail Menu] PBX contact: [sip:999@127.0.0.1:5060]
21:27:37.490 [CM503002]: Call(30): Alerting sip:999@127.0.0.1:40600;rinstance=56b68c797a789841
21:27:37.357 [CM503025]: Call(30): Calling Ext:Ext.999@[Dev:sip:999@127.0.0.1:40600;rinstance=56b68c797a789841]
21:27:37.356 [MS210002] C:30.2:Offer provided. Connection(transcoding mode): 127.0.0.1:7152(7153)
21:27:37.323 [CM503005]: Call(30): Forwarding: Ext:Ext.999@[Dev:sip:999@127.0.0.1:40600;rinstance=56b68c797a789841]
21:27:37.321 [CM503016]: Call(30): Attempt to reach <sip:414@192.168.147.35:5060> failed. Reason: Busy
21:27:37.321 [CM503014]: Call(30): No known route to target: <sip:414@192.168.147.35:5060>
21:27:37.321 [CM503010]: Making route(s) to <sip:414@192.168.147.35:5060>
21:27:37.320 [MS210000] C:30.1:Offer received. RTP connection: 192.168.147.30:5006(5007)
21:27:37.319 Remote SDP is set for legC:30.1
21:27:37.307 [CM503001]: Call(30): Incoming call from 0075339191120@(Ln.10003@MEDIATRIX) to <sip:414@192.168.147.35:5060>
21:27:37.297 [CM503012]: Inbound any hours rule (unnamed) for 10003 forwards to DN:414
21:27:37.297 Looking for inbound target: called=34; caller=0075339191120
21:27:37.295 [CM500002]: Info on incoming INVITE:
INVITE sip:10003@192.168.147.35 SIP/2.0
Via: SIP/2.0/UDP 192.168.147.30;branch=z9hG4bK52f246fbc
Route: <sip:192.168.147.35;lr>
Contact: <sip:0075339191120@192.168.147.30>
To: <sip:34@192.168.147.35>
From: <sip:0075339191120@192.168.147.35>;tag=e42c5fc7bb5c239
Call-ID: c2f812d86ce822d9d072b42ea61a968d@192.168.147.35
CSeq: 1691728788 INVITE
Session-Expires: 3600
Min-SE: 1800
Allow: INVITE, ACK, BYE, CANCEL, REFER, NOTIFY, OPTIONS
Supported: timer, replaces
User-Agent: Mediatrix 3301-001 v1.1.13.186 34XX-MX-D1100-35
Privacy: none
P-Asserted-Identity: <sip:0075339191120@192.168.147.35>
Content-Length: 0

Hier habe ich ein Post mit einem Vergleichbaren Problem gefunden:

http://www.3cx.com/forums/operator-ext-1000-returns-busy-status-21066.html

Hardware:3CX V10 mit allen aktuellen Patches auf W2K8 R2 auf W2K8-R2 Hyper-V (ähnlich wie der oben ;-)) und Mediatrix 3301-001 aktuelle Firmware.


Danke schon mal im Voraus für jeden Tip!

Jens
user2705
New User
 
Posts: 9
Joined: Fri May 27, 2011 1:14 pm

Re: Anrufe sofort auf die Mailbox

Postby StefanW » Wed Nov 30, 2011 10:23 am

wähle mal an dem Telefon *60 geht es dann wieder?
==================================
Stefan Walther
Technical Support Engineer
3CX - Developers of IP PBX Software
StefanW
3CX Support
3CX Support
 
Posts: 2395
Joined: Tue Jun 02, 2009 7:29 am

Re: Anrufe sofort auf die Mailbox

Postby user2705 » Thu Dec 01, 2011 10:12 am

Das nütz leider nichts.
Was ich schon gemacht habe:Nebenstelle gelöscht und neu eingerichtet. Telefon resettet und neu provisioniert. Gateway gelöscht un neu eingerichtet. Mittlerweile geht auch das letzte Telefon, welches noch bei Anrufen geklingelt hat, nicht mehr.
Hier mal ein syslog für die SIP-kommunikation vom Mediatrix Gateway:
192.168.147.30 12.01.2011 10:06 SipEngine:[3CX] C915 CallSetupA()
192.168.147.30 12.01.2011 10:06 SipEngine:[3CX] L2 C915 Call state change from IDLE to TRYING.
192.168.147.30 12.01.2011 10:06 1850-Integrated Services Digital Network: 310-Slot2/Bri1: Received unhandled ISDN message Info Indication.
192.168.147.30 12.01.2011 10:06 SipEngine:[3CX] L2 C915 CCallCxMgr::Invite.
192.168.147.30 12.01.2011 10:06 SipEngine:[3CX] L1 C916 Call state change from IDLE to TRYING.
192.168.147.30 12.01.2011 10:06 1850-Integrated Services Digital Network: 310-Slot2/Bri0: Received unhandled ISDN message Info Indication.
192.168.147.30 12.01.2011 10:06 SipEngine:[3CX] L2 C915 CCallCxMgr::Create.
192.168.147.30 12.01.2011 10:06 SipEngine:[3CX] L1 C916 Call state change from TRYING to LOCAL_RINGBACK.
192.168.147.30 12.01.2011 10:06 SipEngine:[3CX] L2 C915 Sending invite.
192.168.147.30 12.01.2011 10:06 SipEngine:[3CX] L1 C916 Call state change from LOCAL_RINGBACK to CONNECTED.
192.168.147.30 12.01.2011 10:06 SipEngine:[3CX] C916 CallSetupA()
192.168.147.30 12.01.2011 10:06 SipEngine:[3CX] L1 C916 CCallCxMgr::Invite.
192.168.147.30 12.01.2011 10:06 SipEngine:[3CX] L1 C916 CCallCxMgr::Create.
192.168.147.30 12.01.2011 10:06 SipEngine:[3CX] L1 C916 Sending invite.
192.168.147.30 12.01.2011 10:06 SipSignaling:> [3CX] Sending SIP packet to: 192.168.147.35:5060
192.168.147.30 12.01.2011 10:06 SipSignaling:> INVITE sip:10004@192.168.147.35 SIP/2.0
192.168.147.30 12.01.2011 10:06 "SipSignaling:> Via: SIP/2.0/UDP 192.168.147.30;branch=z9hG4bKded3136f0"
192.168.147.30 12.01.2011 10:06 SipSignaling:> Content-Length: 301
192.168.147.30 12.01.2011 10:06 SipSignaling:> To: sip:34@192.168.147.35
192.168.147.30 12.01.2011 10:06 "SipSignaling:> From: sip:14@192.168.147.35;tag=35477e9ffcc9890"
192.168.147.30 12.01.2011 10:06 SipSignaling:> Call-ID: 867e0fab5ff7031e5f0d1eeeee4fbae4@192.168.147.35
192.168.147.30 12.01.2011 10:06 SipSignaling:> CSeq: 1158426603 INVITE
192.168.147.30 12.01.2011 10:06 "SipSignaling:> Route: <sip:192.168.147.35;lr>"
192.168.147.30 12.01.2011 10:06 SipSignaling:> Supported: timer
192.168.147.30 12.01.2011 10:06 SipSignaling:> Min-SE: 1800
192.168.147.30 12.01.2011 10:06 SipSignaling:> Session-Expires: 3600
192.168.147.30 12.01.2011 10:06 SipSignaling:> Allow: INVITE, ACK, BYE, CANCEL, REFER, NOTIFY, OPTIONS
192.168.147.30 12.01.2011 10:06 SipSignaling:> Privacy: none
192.168.147.30 12.01.2011 10:06 SipSignaling:> P-Asserted-Identity: <sip:14@192.168.147.35>
192.168.147.30 12.01.2011 10:06 SipSignaling:> Content-Type: application/sdp
192.168.147.30 12.01.2011 10:06 SipSignaling:> Contact: sip:14@192.168.147.30
192.168.147.30 12.01.2011 10:06 SipSignaling:> Supported: replaces
192.168.147.30 12.01.2011 10:06 SipSignaling:> User-Agent: Mediatrix 3301-001 v1.1.13.186 34XX-MX-D1100-35
192.168.147.30 12.01.2011 10:06 SipSignaling:>
192.168.147.30 12.01.2011 10:06 SipSignaling:> v=0
192.168.147.30 12.01.2011 10:06 SipSignaling:> o=MxSIP 1227586284135208852 1451240016242902469 IN IP4 192.168.147.30
192.168.147.30 12.01.2011 10:06 SipSignaling:> s=-
192.168.147.30 12.01.2011 10:06 SipSignaling:> c=IN IP4 192.168.147.30
192.168.147.30 12.01.2011 10:06 SipSignaling:> t=0 0
192.168.147.30 12.01.2011 10:06 SipSignaling:> a=sendrecv
192.168.147.30 12.01.2011 10:06 SipSignaling:> m=audio 5004 RTP/AVP 0 18 4 8 96 13
192.168.147.30 12.01.2011 10:06 SipSignaling:> a=rtpmap:0 PCMU/8000
192.168.147.30 12.01.2011 10:06 SipSignaling:> a=rtpmap:18 G729/8000
192.168.147.30 12.01.2011 10:06 SipSignaling:> a=rtpmap:4 G723/8000
192.168.147.30 12.01.2011 10:06 SipSignaling:> a=rtpmap:8 PCMA/8000
192.168.147.30 12.01.2011 10:06 SipSignaling:> a=rtpmap:96 telephone-event/8000
192.168.147.30 12.01.2011 10:06 SipSignaling:> a=fmtp:96 0-15
192.168.147.30 12.01.2011 10:06 SipSignaling:> [3CX] Sending SIP packet to: 192.168.147.35:5060
192.168.147.30 12.01.2011 10:06 SipSignaling:> INVITE sip:10003@192.168.147.35 SIP/2.0
192.168.147.30 12.01.2011 10:06 "SipSignaling:> Via: SIP/2.0/UDP 192.168.147.30;branch=z9hG4bK15136ac5c"
192.168.147.30 12.01.2011 10:06 SipSignaling:> Content-Length: 300
192.168.147.30 12.01.2011 10:06 SipSignaling:> To: sip:34@192.168.147.35
192.168.147.30 12.01.2011 10:06 "SipSignaling:> From: sip:14@192.168.147.35;tag=4edab0f855de10a"
192.168.147.30 12.01.2011 10:06 SipSignaling:> Call-ID: c348749785214bef8d8e0fe151ad11b9@192.168.147.35
192.168.147.30 12.01.2011 10:06 SipSignaling:> CSeq: 694542890 INVITE
192.168.147.30 12.01.2011 10:06 "SipSignaling:> Route: <sip:192.168.147.35;lr>"
192.168.147.30 12.01.2011 10:06 SipSignaling:> Supported: timer
192.168.147.30 12.01.2011 10:06 SipSignaling:> Min-SE: 1800
192.168.147.30 12.01.2011 10:06 SipSignaling:> Session-Expires: 3600
192.168.147.30 12.01.2011 10:06 SipSignaling:> Allow: INVITE, ACK, BYE, CANCEL, REFER, NOTIFY, OPTIONS
192.168.147.30 12.01.2011 10:06 SipSignaling:> Privacy: none
192.168.147.30 12.01.2011 10:06 SipSignaling:> P-Asserted-Identity: <sip:14@192.168.147.35>
192.168.147.30 12.01.2011 10:06 SipSignaling:> Content-Type: application/sdp
192.168.147.30 12.01.2011 10:06 SipSignaling:> Contact: sip:14@192.168.147.30
192.168.147.30 12.01.2011 10:06 SipSignaling:> Supported: replaces
192.168.147.30 12.01.2011 10:06 SipSignaling:> User-Agent: Mediatrix 3301-001 v1.1.13.186 34XX-MX-D1100-35
192.168.147.30 12.01.2011 10:06 SipSignaling:>
192.168.147.30 12.01.2011 10:06 SipSignaling:> v=0
192.168.147.30 12.01.2011 10:06 SipSignaling:> o=MxSIP 441016918183986405 1723813381154215745 IN IP4 192.168.147.30
192.168.147.30 12.01.2011 10:06 SipSignaling:> s=-
192.168.147.30 12.01.2011 10:06 SipSignaling:> c=IN IP4 192.168.147.30
192.168.147.30 12.01.2011 10:06 SipSignaling:> t=0 0
192.168.147.30 12.01.2011 10:06 SipSignaling:> a=sendrecv
192.168.147.30 12.01.2011 10:06 SipSignaling:> m=audio 5006 RTP/AVP 0 18 4 8 96 13
192.168.147.30 12.01.2011 10:06 SipSignaling:> a=rtpmap:0 PCMU/8000
192.168.147.30 12.01.2011 10:06 SipSignaling:> a=rtpmap:18 G729/8000
192.168.147.30 12.01.2011 10:06 SipSignaling:> a=rtpmap:4 G723/8000
192.168.147.30 12.01.2011 10:06 SipSignaling:> a=rtpmap:8 PCMA/8000
192.168.147.30 12.01.2011 10:06 SipSignaling:> a=rtpmap:96 telephone-event/8000
192.168.147.30 12.01.2011 10:06 SipSignaling:> a=fmtp:96 0-15
192.168.147.30 12.01.2011 10:06 SipSignaling:< [3CX] Received SIP packet from: 192.168.147.35:5060
192.168.147.30 12.01.2011 10:06 SipSignaling:< SIP/2.0 100 Trying
192.168.147.30 12.01.2011 10:06 "SipSignaling:< Via: SIP/2.0/UDP 192.168.147.30;branch=z9hG4bKded3136f0"
192.168.147.30 12.01.2011 10:06 SipSignaling:< To: sip:34@192.168.147.35
192.168.147.30 12.01.2011 10:06 "SipSignaling:< From: sip:14@192.168.147.35;tag=35477e9ffcc9890"
192.168.147.30 12.01.2011 10:06 SipSignaling:< Call-ID: 867e0fab5ff7031e5f0d1eeeee4fbae4@192.168.147.35
192.168.147.30 12.01.2011 10:06 SipSignaling:< CSeq: 1158426603 INVITE
192.168.147.30 12.01.2011 10:06 SipSignaling:< Content-Length: 0
192.168.147.30 12.01.2011 10:06 SipSignaling:<
192.168.147.30 12.01.2011 10:06 SipSignaling:< [3CX] Received SIP packet from: 192.168.147.35:5060
192.168.147.30 12.01.2011 10:06 SipSignaling:< SIP/2.0 100 Trying
192.168.147.30 12.01.2011 10:06 "SipSignaling:< Via: SIP/2.0/UDP 192.168.147.30;branch=z9hG4bK15136ac5c"
192.168.147.30 12.01.2011 10:06 SipSignaling:< To: sip:34@192.168.147.35
192.168.147.30 12.01.2011 10:06 "SipSignaling:< From: sip:14@192.168.147.35;tag=4edab0f855de10a"
192.168.147.30 12.01.2011 10:06 SipSignaling:< Call-ID: c348749785214bef8d8e0fe151ad11b9@192.168.147.35
192.168.147.30 12.01.2011 10:06 SipSignaling:< CSeq: 694542890 INVITE
192.168.147.30 12.01.2011 10:06 SipSignaling:< Content-Length: 0
192.168.147.30 12.01.2011 10:06 SipSignaling:<
192.168.147.30 12.01.2011 10:06 SipSignaling:< [3CX] Received SIP packet from: 192.168.147.35:5060
192.168.147.30 12.01.2011 10:06 SipSignaling:< SIP/2.0 180 Ringing
192.168.147.30 12.01.2011 10:06 "SipSignaling:< Via: SIP/2.0/UDP 192.168.147.30;branch=z9hG4bK15136ac5c"
192.168.147.30 12.01.2011 10:06 SipSignaling:< Contact: <sip:10003@192.168.147.35>
192.168.147.30 12.01.2011 10:06 "SipSignaling:< To: <sip:34@192.168.147.35>;tag=ca77f24f"
192.168.147.30 12.01.2011 10:06 "SipSignaling:< From: <sip:14@192.168.147.35>;tag=4edab0f855de10a"
192.168.147.30 12.01.2011 10:06 SipSignaling:< Call-ID: c348749785214bef8d8e0fe151ad11b9@192.168.147.35
192.168.147.30 12.01.2011 10:06 SipSignaling:< CSeq: 694542890 INVITE
192.168.147.30 12.01.2011 10:06 SipSignaling:< User-Agent: 3CXPhoneSystem 10.0.22042.0
192.168.147.30 12.01.2011 10:06 SipSignaling:< Content-Length: 0
192.168.147.30 12.01.2011 10:06 SipSignaling:<
192.168.147.30 12.01.2011 10:06 SipSignaling:< [3CX] Received SIP packet from: 192.168.147.35:5060
192.168.147.30 12.01.2011 10:06 SipSignaling:< SIP/2.0 200 OK
192.168.147.30 12.01.2011 10:06 "SipSignaling:< Via: SIP/2.0/UDP 192.168.147.30;branch=z9hG4bK15136ac5c"
192.168.147.30 12.01.2011 10:06 SipSignaling:< Contact: <sip:10003@192.168.147.35:5060>
192.168.147.30 12.01.2011 10:06 "SipSignaling:< To: <sip:34@192.168.147.35>;tag=ca77f24f"
192.168.147.30 12.01.2011 10:06 "SipSignaling:< From: <sip:14@192.168.147.35>;tag=4edab0f855de10a"
192.168.147.30 12.01.2011 10:06 SipSignaling:< Call-ID: c348749785214bef8d8e0fe151ad11b9@192.168.147.35
192.168.147.30 12.01.2011 10:06 SipSignaling:< CSeq: 694542890 INVITE
192.168.147.30 12.01.2011 10:06 SipSignaling:< Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE
192.168.147.30 12.01.2011 10:06 SipSignaling:< Content-Type: application/sdp
192.168.147.30 12.01.2011 10:06 SipSignaling:< Supported: replaces
192.168.147.30 12.01.2011 10:06 SipSignaling:< User-Agent: 3CXPhoneSystem 10.0.22042.0
192.168.147.30 12.01.2011 10:06 SipSignaling:< Content-Length: 324
192.168.147.30 12.01.2011 10:06 SipSignaling:<
192.168.147.30 12.01.2011 10:06 SipSignaling:< v=0
192.168.147.30 12.01.2011 10:06 SipSignaling:< o=3cxPS 454125682688 120762400769 IN IP4 192.168.147.35
192.168.147.30 12.01.2011 10:06 SipSignaling:< s=3cxPS Audio call
192.168.147.30 12.01.2011 10:06 SipSignaling:< c=IN IP4 192.168.147.35
192.168.147.30 12.01.2011 10:06 SipSignaling:< t=0 0
192.168.147.30 12.01.2011 10:06 SipSignaling:< m=audio 7090 RTP/AVP 0 18 8 13 96
192.168.147.30 12.01.2011 10:06 SipSignaling:< c=IN IP4 192.168.147.35
192.168.147.30 12.01.2011 10:06 SipSignaling:< a=rtpmap:0 PCMU/8000
192.168.147.30 12.01.2011 10:06 SipSignaling:< a=rtpmap:18 G729/8000
192.168.147.30 12.01.2011 10:06 SipSignaling:< a=rtpmap:8 PCMA/8000
192.168.147.30 12.01.2011 10:06 SipSignaling:< a=rtpmap:13 CN/8000
192.168.147.30 12.01.2011 10:06 SipSignaling:< a=rtpmap:96 telephone-event/8000
192.168.147.30 12.01.2011 10:06 SipSignaling:< a=fmtp:96 0-15
192.168.147.30 12.01.2011 10:06 SipSignaling:< a=sendrecv
192.168.147.30 12.01.2011 10:06 SipEngine:[3CX] L1 C916 Session established.
192.168.147.30 12.01.2011 10:06 SipSignaling:> [3CX] Sending SIP packet to: 192.168.147.35:5060
192.168.147.30 12.01.2011 10:06 SipSignaling:> ACK sip:10003@192.168.147.35:5060 SIP/2.0
192.168.147.30 12.01.2011 10:06 "SipSignaling:> Via: SIP/2.0/UDP 192.168.147.30;branch=z9hG4bKd6fd98504"
192.168.147.30 12.01.2011 10:06 SipEngine:[3CX] L2 C915 Call state change from TRYING to TERMINATING.
192.168.147.30 12.01.2011 10:06 SipSignaling:> Content-Length: 0
192.168.147.30 12.01.2011 10:06 "SipSignaling:> To: sip:34@192.168.147.35;tag=ca77f24f"
192.168.147.30 12.01.2011 10:06 "SipSignaling:> From: sip:14@192.168.147.35;tag=4edab0f855de10a"
192.168.147.30 12.01.2011 10:06 SipSignaling:> Call-ID: c348749785214bef8d8e0fe151ad11b9@192.168.147.35
192.168.147.30 12.01.2011 10:06 SipSignaling:> CSeq: 694542890 ACK
192.168.147.30 12.01.2011 10:06 SipSignaling:> Contact: sip:14@192.168.147.30
192.168.147.30 12.01.2011 10:06 SipSignaling:> User-Agent: Mediatrix 3301-001 v1.1.13.186 34XX-MX-D1100-35
192.168.147.30 12.01.2011 10:06 SipSignaling:>
192.168.147.30 12.01.2011 10:06 SipEngine:[3CX] C915 CallReleaseA(26)
192.168.147.30 12.01.2011 10:06 SipEngine:[3CX] L2 C915 CCallCxMgr::Terminate.
192.168.147.30 12.01.2011 10:06 SipSignaling:> [3CX] Sending SIP packet to: 192.168.147.35:5060
192.168.147.30 12.01.2011 10:06 SipSignaling:> CANCEL sip:10004@192.168.147.35 SIP/2.0
192.168.147.30 12.01.2011 10:06 "SipSignaling:> Via: SIP/2.0/UDP 192.168.147.30;branch=z9hG4bKded3136f0"
192.168.147.30 12.01.2011 10:06 SipSignaling:> Content-Length: 0
192.168.147.30 12.01.2011 10:06 SipSignaling:> To: sip:34@192.168.147.35
192.168.147.30 12.01.2011 10:06 "SipSignaling:> From: sip:14@192.168.147.35;tag=35477e9ffcc9890"
192.168.147.30 12.01.2011 10:06 SipSignaling:> Call-ID: 867e0fab5ff7031e5f0d1eeeee4fbae4@192.168.147.35
192.168.147.30 12.01.2011 10:06 SipSignaling:> CSeq: 1158426603 CANCEL
192.168.147.30 12.01.2011 10:06 "SipSignaling:> Route: <sip:192.168.147.35;lr>"
192.168.147.30 12.01.2011 10:06 SipSignaling:> Supported: timer
192.168.147.30 12.01.2011 10:06 SipSignaling:> Supported: replaces
192.168.147.30 12.01.2011 10:06 SipSignaling:> User-Agent: Mediatrix 3301-001 v1.1.13.186 34XX-MX-D1100-35
192.168.147.30 12.01.2011 10:06 SipSignaling:>
192.168.147.30 12.01.2011 10:06 SipSignaling:< [3CX] Received SIP packet from: 192.168.147.35:5060
192.168.147.30 12.01.2011 10:06 SipSignaling:< SIP/2.0 200 OK
192.168.147.30 12.01.2011 10:06 "SipSignaling:< Via: SIP/2.0/UDP 192.168.147.30;branch=z9hG4bKded3136f0"
192.168.147.30 12.01.2011 10:06 SipSignaling:< Contact: <sip:10004@192.168.147.35>
192.168.147.30 12.01.2011 10:06 "SipSignaling:< To: <sip:34@192.168.147.35>;tag=db187463"
192.168.147.30 12.01.2011 10:06 "SipSignaling:< From: <sip:14@192.168.147.35>;tag=35477e9ffcc9890"
192.168.147.30 12.01.2011 10:06 SipSignaling:< Call-ID: 867e0fab5ff7031e5f0d1eeeee4fbae4@192.168.147.35
192.168.147.30 12.01.2011 10:06 SipSignaling:< CSeq: 1158426603 CANCEL
192.168.147.30 12.01.2011 10:06 SipSignaling:< User-Agent: 3CXPhoneSystem 10.0.22042.0
192.168.147.30 12.01.2011 10:06 SipSignaling:< Content-Length: 0
192.168.147.30 12.01.2011 10:06 SipSignaling:<
192.168.147.30 12.01.2011 10:06 SipSignaling:< [3CX] Received SIP packet from: 192.168.147.35:5060
192.168.147.30 12.01.2011 10:06 SipSignaling:< SIP/2.0 487 Request Terminated
192.168.147.30 12.01.2011 10:06 "SipSignaling:< Via: SIP/2.0/UDP 192.168.147.30;branch=z9hG4bKded3136f0"
192.168.147.30 12.01.2011 10:06 "SipSignaling:< To: <sip:34@192.168.147.35>;tag=db187463"
192.168.147.30 12.01.2011 10:06 "SipSignaling:< From: <sip:14@192.168.147.35>;tag=35477e9ffcc9890"
192.168.147.30 12.01.2011 10:06 SipSignaling:< Call-ID: 867e0fab5ff7031e5f0d1eeeee4fbae4@192.168.147.35
192.168.147.30 12.01.2011 10:06 SipSignaling:< CSeq: 1158426603 INVITE
192.168.147.30 12.01.2011 10:06 SipSignaling:< User-Agent: 3CXPhoneSystem 10.0.22042.0
192.168.147.30 12.01.2011 10:06 SipSignaling:< Content-Length: 0
192.168.147.30 12.01.2011 10:06 SipSignaling:<
192.168.147.30 12.01.2011 10:06 SipEngine:[3CX] L2 C915 Releasing Context.
192.168.147.30 12.01.2011 10:06 SipSignaling:> [3CX] Sending SIP packet to: 192.168.147.35:5060
192.168.147.30 12.01.2011 10:06 SipSignaling:> ACK sip:10004@192.168.147.35 SIP/2.0
192.168.147.30 12.01.2011 10:06 "SipSignaling:> Via: SIP/2.0/UDP 192.168.147.30;branch=z9hG4bKded3136f0"
192.168.147.30 12.01.2011 10:06 SipSignaling:> Content-Length: 0
192.168.147.30 12.01.2011 10:06 "SipSignaling:> To: sip:34@192.168.147.35;tag=db187463"
192.168.147.30 12.01.2011 10:06 "SipSignaling:> From: sip:14@192.168.147.35;tag=35477e9ffcc9890"
192.168.147.30 12.01.2011 10:06 SipSignaling:> Call-ID: 867e0fab5ff7031e5f0d1eeeee4fbae4@192.168.147.35
192.168.147.30 12.01.2011 10:06 SipSignaling:> CSeq: 1158426603 ACK
192.168.147.30 12.01.2011 10:06 "SipSignaling:> Route: <sip:192.168.147.35;lr>"
192.168.147.30 12.01.2011 10:06 SipSignaling:> User-Agent: Mediatrix 3301-001 v1.1.13.186 34XX-MX-D1100-35
192.168.147.30 12.01.2011 10:06 SipSignaling:>
user2705
New User
 
Posts: 9
Joined: Fri May 27, 2011 1:14 pm

Re: Anrufe sofort auf die Mailbox

Postby StefanW » Thu Dec 01, 2011 11:36 am

naja, das sagt mir nicht viel dieses log...
Das 3CX Trace log währe schon besser für diesen call
==================================
Stefan Walther
Technical Support Engineer
3CX - Developers of IP PBX Software
StefanW
3CX Support
3CX Support
 
Posts: 2395
Joined: Tue Jun 02, 2009 7:29 am

Re: Anrufe sofort auf die Mailbox

Postby user2705 » Thu Dec 01, 2011 1:24 pm

Gehts um dieses hier: 3CXPhoneSystem.log?
mfg
Jens Müller
user2705
New User
 
Posts: 9
Joined: Fri May 27, 2011 1:14 pm

Re: Anrufe sofort auf die Mailbox

Postby StefanW » Thu Dec 01, 2011 2:41 pm

.trece.log
==================================
Stefan Walther
Technical Support Engineer
3CX - Developers of IP PBX Software
StefanW
3CX Support
3CX Support
 
Posts: 2395
Joined: Tue Jun 02, 2009 7:29 am

Re: Anrufe sofort auf die Mailbox

Postby user2705 » Thu Dec 01, 2011 8:56 pm

Ich hänge das mal als File mit dran. Es beginnt oben mit dem Anruf via ISDN und in der Mitte dann bei 20:42:33.008 beginnt der Anruf via Sipgate Trunk.
Der ISDN geht auf die Mailbox, der SIPgate wird verbunden.

Danke Jens
user2705
New User
 
Posts: 9
Joined: Fri May 27, 2011 1:14 pm

Re: Anrufe sofort auf die Mailbox

Postby user2705 » Thu Dec 01, 2011 9:39 pm

Ich habe jetzt noch mal einen Test gemacht:3cx auf einen anderen Server installiert, ISDN Gateway genau gleich angebunden(zusätzlich) - funktionierte sofort. Ich habe alles noch mal verglichen, aber es gibt keine Unterschiede in der Konfiguration, bis auf das die Test3CX in einem anderen Subnet ist.
user2705
New User
 
Posts: 9
Joined: Fri May 27, 2011 1:14 pm

Re: Anrufe sofort auf die Mailbox

Postby StefanW » Fri Dec 02, 2011 8:38 am

keine logs = case closed, also suche es dir aus was du nun tuen willst
==================================
Stefan Walther
Technical Support Engineer
3CX - Developers of IP PBX Software
StefanW
3CX Support
3CX Support
 
Posts: 2395
Joined: Tue Jun 02, 2009 7:29 am

Re: Anrufe sofort auf die Mailbox

Postby user2705 » Fri Dec 02, 2011 11:23 am

Hallo Stefan,
ich habe doch das Logfile hochgeladen...(via Upload attachment). Ich kann dasd nicht Posten da ich folgende Fehlermeldungf erhalte:
Your message contains 366158 characters. The maximum number of allowed characters is 60000
Trotzdem nur der Abschnitt mit den Beiden Anrufen drin ist.
Ich hänge es nochmal ran (via Upload attachment).
Ich kann das sonst ja in verschiedene Teile aufsplitten.
user2705
New User
 
Posts: 9
Joined: Fri May 27, 2011 1:14 pm

Re: Anrufe sofort auf die Mailbox

Postby StefanW » Fri Dec 02, 2011 11:54 am

wie wäre es wenn du einfach die Datei hoch lädst und uns einen Link gibts?
Zudem musste ich deine Posts löschen, da dort öffentliche IPs eingetragen warten, welches gegen die Foren regeln gehen, ist zu deiner eingen sicherheit!
==================================
Stefan Walther
Technical Support Engineer
3CX - Developers of IP PBX Software
StefanW
3CX Support
3CX Support
 
Posts: 2395
Joined: Tue Jun 02, 2009 7:29 am

Re: Anrufe sofort auf die Mailbox

Postby user2705 » Fri Dec 02, 2011 12:33 pm

;-) hätte ich auch selber drau kommen können...

https://www2.mdbw.net/public/3CXPhoneSystem.trace.log.txt

Gruß Jens
user2705
New User
 
Posts: 9
Joined: Fri May 27, 2011 1:14 pm

Re: Anrufe sofort auf die Mailbox

Postby StefanW » Fri Dec 02, 2011 2:20 pm

Also ein Call kommt von 001762444XXXX and die DID 34
Hinter der 34 DID steht route alles an die 414.
Bis hier ist noch alles einfach.

Nun wird lustig, lösung ist einfach, kauf dir ein gutes gateway, zB eine Beronet.
Das Gateway schickt 2 anfragen von 10003 und 10004 kann diese aber nicht mehr auseinander halten auf welcher anfrage wir was antworten. Durch die beiden calls die das gateway schickt beantworten wir eins als Telefon ist schon busy und daher auf das Vbox system dieses verwirrt das gateway und es bricht den call zum telefon ab.

Mach mal den Spaß und setze 414 auf "kann mehr als einen anruf entgegennehmen" in der Weiterleitungs regel "verfügbar" und du wirst sehen das 2 anrufe kommen für ein gespräch.

Also fehl konfig oder fehler im gerät
==================================
Stefan Walther
Technical Support Engineer
3CX - Developers of IP PBX Software
StefanW
3CX Support
3CX Support
 
Posts: 2395
Joined: Tue Jun 02, 2009 7:29 am

Re: Anrufe sofort auf die Mailbox

Postby user2705 » Sat Dec 03, 2011 9:38 pm

Super, das hat mir schon sehr geholfen! Ich signalsiere einfach nur entsprechend die DIDs auf einem S0 der dann wiederum an einen Port der 3CX hängt.
Vielleicht kann ich ja über die "Signaling Properties" am Gateway noch was manipulieren...
Danke für die schnelle Hilfe,
Jens
user2705
New User
 
Posts: 9
Joined: Fri May 27, 2011 1:14 pm


Return to Deutsch


Who is online

Users browsing this forum: No registered users and 0 guests