Hello,
i have some issues wth the M300 Base Station and M25.
The M300 is connected our LAN wich is part of a MPLS Network.
There are 2 Firewalls betewen M300 and Internet (no outgoing blocks).
We drive our own SBC with some Sip Accounts in Azure cloud, where the M300 can register there extensions.
I can register several extensions and can see the registration on the SBC.
Some times Incomming and outgoing calls calls are possible, some times not, but there is no understandable reason.
both M300 and M25 have 530.2 Firmware.
I might need some support here to get the devices working.
Best regards
10 Comments
Snom Federico Rossi
Hi,
we need to check M300 sip log and syslog to try to understand what's happening. Could you post the files taken after a non-working call?
In my experience, sip traffic is very likely to be blocked.
Do firewalls have any active sip alg?
End user Christian Schurig
Hello,
thanks for this fast response.
Logfile entries with IP adresses and domainnames have been anonymiesed because of security reasons.
If you need real values for analyses, I have to send this in a more private way.
And there are no SIP rules in FW.
Other SIP devices in our Network already working with an other SIP Provider. So I assume thats not the issue.
Thanks a lot
Christian Schurig
SIP LOG, last entry after not working outgoing call.
Sent to tcp:"SBC external IP":5060 at 19/04/2022 16:36:17 (1050 bytes)
INVITE sip:+4917xxxxxxxx@"sbc.domain.com":5060;user=phone SIP/2.0
Via: SIP/2.0/TCP internal IP:52067;branch=z9hG4bKljrmn98.ikfurrpx2y7oclprn1e.we9
Max-Forwards: 70
From: "Be Lab 65" <sip:+49"sip extension"@"sbc.domain.com":5060;transport=TCP>;tag=8cwzjhff8it
To: <sip:+4917xxxxxxxx@sbc.domain.com:5060;user=phone>
Call-ID: meqi5cj5xe6cenbhek.@"sbc.domain.com"
CSeq: 40171 INVITE
Contact: <sip:+49internal sip extension@internal IP:52067;transport=TCP;line=16546>
Allow: INVITE, CANCEL, BYE, ACK, REGISTER, OPTIONS, REFER, SUBSCRIBE, NOTIFY, MESSAGE, INFO, PRACK, UPDATE
Content-Disposition: session
Min-SE: 90
Session-Expires: 3600
Supported: replaces,100rel,timer
User-Agent: snomM300/05.30.0002 (MAC=00041362B6B5; SER= 00000; HW=1)
Content-Type: application/sdp
Content-Length: 255
v=0
o=+49"sip extension" 915882401 915882401 IN IP4 "internal IP"
s=-
c=IN IP4 "Internal IP"
t=0 0
m=audio 50010 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
a=maxptime:80
a=sendrecv
a=rtcp:50011
Syslog:
loc3 .Info 2022-04-19T16:01:49Z 235-[ FpCtrlResetHandler CRE AC#1:0 RP#0 HR#0]
loc0 .Info 2022-04-19T16:01:49Z 235-[ RSSI report HS:+49xxx65 PMID:00003 RPN:00 dBm:-36]
loc0 .Info 2022-04-19T16:01:49Z 235-[ PMID:00003 Battery Level: 99]
loc7 .Info 2022-04-19T16:01:54Z 235-[ Call Release user +49xxx65 Duration: 00:00:05]
loc3 .Info 2022-04-19T16:01:54Z 235-[ FpCtrlResetHandler PR#713 AC#1:0 RP#0 HR#0]
loc3 .Info 2022-04-19T16:01:54Z 235-[ FpCtrlResetHandler TER AC#0:0 RP#0 HR#0]
loc7 .Info 2022-04-19T16:01:54Z 235-[ DECT MAC statistics: Pmid:00003 Typ:FN Res:0 Frames:541,3,0 Bho:0,0 Rssi:59]
loc7 .Info 2022-04-19T16:02:46Z 235-[ Call Outgoing user +49xxx65]
loc3 .Info 2022-04-19T16:02:46Z 235-[ FpCtrlResetHandler PR#712 AC#0:0 RP#0 HR#0]
loc3 .Info 2022-04-19T16:02:46Z 235-[ FpCtrlResetHandler CRE AC#1:0 RP#0 HR#0]
loc0 .Info 2022-04-19T16:02:46Z 235-[ RSSI report HS:+49xxx65 PMID:00003 RPN:00 dBm:-28]
loc0 .Info 2022-04-19T16:02:46Z 235-[ PMID:00003 Battery Level: 99]
loc7 .Info 2022-04-19T16:02:51Z 235-[ Call Release user +49xxx65 Duration: 00:00:05]
loc3 .Info 2022-04-19T16:02:51Z 235-[ FpCtrlResetHandler PR#713 AC#1:0 RP#0 HR#0]
loc3 .Info 2022-04-19T16:02:51Z 235-[ FpCtrlResetHandler TER AC#0:0 RP#0 HR#0]
loc7 .Info 2022-04-19T16:02:51Z 235-[ DECT MAC statistics: Pmid:00003 Typ:FN Res:0 Frames:540,3,0 Bho:0,0 Rssi:58]
loc7 .Info 2022-04-19T16:17:26Z 235-[ Roaming of user +49xxx65 on AppId#00, ExtIdx#0002]
loc7 .Info 2022-04-19T16:17:26Z 235-[ Roaming of user +49xxx66 on AppId#01, ExtIdx#0000]
loc7 .Info 2022-04-19T16:17:26Z 235-[ Roaming of user +49xxx01 on AppId#02, ExtIdx#0001]
loc3 .Info 2022-04-19T16:17:31Z 235-[ Registration of user +49xxx65 (ExtIdx#0002) on domain sbc01:5060 succeeded]
loc7 .Info 2022-04-19T16:17:31Z 235-[ updateRegistrationGroupCall all god for SipExtId #2 Used for PP's: #4]
loc3 .Info 2022-04-19T16:17:32Z 235-[ Registration of user +49xxx66 (ExtIdx#0000) on domain sbc01:5060 succeeded]
loc7 .Info 2022-04-19T16:17:32Z 235-[ updateRegistrationGroupCall all god for SipExtId #0 Used for PP's: #1]
loc3 .Info 2022-04-19T16:17:32Z 235-[ Registration of user +49xxx01 (ExtIdx#0001) on domain sbc01:5060 succeeded]
loc7 .Info 2022-04-19T16:17:32Z 235-[ updateRegistrationGroupCall all god for SipExtId #1 Used for PP's: #2]
clk .Info 2022-04-19T16:28:36Z 235-[ UTC time set initiated by SNTP (1650378516 s)]
clk .Info 2022-04-19T16:28:36Z 235-[ Local time set (2022-04-19 16:28:36)]
loc3 .Info 2022-04-19T16:28:36Z 235-[ Time and Date and DST Broadcast to handsets]
loc7 .Info 2022-04-19T16:36:17Z 235-[ Call Outgoing user +49xxx65]
loc3 .Info 2022-04-19T16:36:17Z 235-[ FpCtrlResetHandler PR#712 AC#0:0 RP#0 HR#0]
loc3 .Info 2022-04-19T16:36:17Z 235-[ FpCtrlResetHandler CRE AC#1:0 RP#0 HR#0]
loc0 .Info 2022-04-19T16:36:18Z 235-[ RSSI report HS:+49xxx65 PMID:00003 RPN:00 dBm:-40]
loc0 .Info 2022-04-19T16:36:18Z 235-[ PMID:00003 Battery Level: 98]
loc7 .Info 2022-04-19T16:36:22Z 235-[ Call Release user +49xxx65 Duration: 00:00:05]
loc3 .Info 2022-04-19T16:36:22Z 235-[ FpCtrlResetHandler PR#713 AC#1:0 RP#0 HR#0]
loc3 .Info 2022-04-19T16:36:22Z 235-[ FpCtrlResetHandler TER AC#0:0 RP#0 HR#0]
loc7 .Info 2022-04-19T16:36:23Z 235-[ DECT MAC statistics: Pmid:00003 Typ:FN Res:0 Frames:540,3,0 Bho:0,0 Rssi:59]
Snom Federico Rossi
Hi,
if there is only the INVITE in the SIP log, it means the M300 does not receive any response from the PBX. You must check the network.
End user Christian Schurig
Hello, I have a reproducible event
Reboot Basstation: all Devices regsitrated.Incomming and outgoing calls possible.
A few minutes later, even incomming and outgoing calls not possible anymore.
SIP Log:
Sent to udp:224.0.1.75:5060 at 19/04/2022 19:15:07 (686 bytes)
SUBSCRIBE sip:MAC%3a00041362B6B5@224.0.1.75 SIP/2.0
Via: SIP/2.0/UDP Internal IP;branch=z9hG4bK3gw3f5w9oxpqeqmwvz9
Max-Forwards: 70
From: <sip:PIA512@Internal IP>;tag=3.d9r
To: <sip:MAC%3a00041362B6B5@224.0.1.75>
Call-ID: ebzpj9dh5@Internal IP
CSeq: 62691 SUBSCRIBE
Contact: <sip:PIA512@Internal IP>
Allow: INVITE, CANCEL, BYE, ACK, REGISTER, OPTIONS, REFER, SUBSCRIBE, NOTIFY, MESSAGE, INFO, PRACK, UPDATE
Allow-Events: dialog,message-summary
Event: ua-profile;profile-type="device";vendor="snom";model="snomM300";version="05.30.0002"
Expires: 0
Supported: replaces,100rel
User-Agent: snomM300/05.30.0002 (MAC=00041362B6B5; SER= 00000; HW=1)
Content-Length: 0
Sent to udp:224.0.1.75:5060 at 19/04/2022 19:15:07 (686 bytes)
SUBSCRIBE sip:MAC%3a00041362B6B5@224.0.1.75 SIP/2.0
Via: SIP/2.0/UDP Internal IP;branch=z9hG4bK3gw3f5w9oxpqeqmwvz9
Max-Forwards: 70
From: <sip:PIA512@Internal IP>;tag=3.d9r
To: <sip:MAC%3a00041362B6B5@224.0.1.75>
Call-ID: ebzpj9dh5@Internal IP
CSeq: 62691 SUBSCRIBE
Contact: <sip:PIA512@Internal IP>
Allow: INVITE, CANCEL, BYE, ACK, REGISTER, OPTIONS, REFER, SUBSCRIBE, NOTIFY, MESSAGE, INFO, PRACK, UPDATE
Allow-Events: dialog,message-summary
Event: ua-profile;profile-type="device";vendor="snom";model="snomM300";version="05.30.0002"
Expires: 0
Supported: replaces,100rel
User-Agent: snomM300/05.30.0002 (MAC=00041362B6B5; SER= 00000; HW=1)
Content-Length: 0
Sent to udp:224.0.1.75:5060 at 19/04/2022 19:15:08 (686 bytes)
SUBSCRIBE sip:MAC%3a00041362B6B5@224.0.1.75 SIP/2.0
Via: SIP/2.0/UDP Internal IP;branch=z9hG4bK3gw3f5w9oxpqeqmwvz9
Max-Forwards: 70
From: <sip:PIA512@Internal IP>;tag=3.d9r
To: <sip:MAC%3a00041362B6B5@224.0.1.75>
Call-ID: ebzpj9dh5@Internal IP
CSeq: 62691 SUBSCRIBE
Contact: <sip:PIA512@Internal IP>
Allow: INVITE, CANCEL, BYE, ACK, REGISTER, OPTIONS, REFER, SUBSCRIBE, NOTIFY, MESSAGE, INFO, PRACK, UPDATE
Allow-Events: dialog,message-summary
Event: ua-profile;profile-type="device";vendor="snom";model="snomM300";version="05.30.0002"
Expires: 0
Supported: replaces,100rel
User-Agent: snomM300/05.30.0002 (MAC=00041362B6B5; SER= 00000; HW=1)
Content-Length: 0
Sent to udp:224.0.1.75:5060 at 19/04/2022 19:15:12 (686 bytes)
SUBSCRIBE sip:MAC%3a00041362B6B5@224.0.1.75 SIP/2.0
Via: SIP/2.0/UDP Internal IP;branch=z9hG4bK3gw3f5w9oxpqeqmwvz9
Max-Forwards: 70
From: <sip:PIA512@Internal IP>;tag=3.d9r
To: <sip:MAC%3a00041362B6B5@224.0.1.75>
Call-ID: ebzpj9dh5@Internal IP
CSeq: 62691 SUBSCRIBE
Contact: <sip:PIA512@Internal IP>
Allow: INVITE, CANCEL, BYE, ACK, REGISTER, OPTIONS, REFER, SUBSCRIBE, NOTIFY, MESSAGE, INFO, PRACK, UPDATE
Allow-Events: dialog,message-summary
Event: ua-profile;profile-type="device";vendor="snom";model="snomM300";version="05.30.0002"
Expires: 0
Supported: replaces,100rel
User-Agent: snomM300/05.30.0002 (MAC=00041362B6B5; SER= 00000; HW=1)
Content-Length: 0
Sent to tcp:SBC:5060 at 19/04/2022 19:15:29 (649 bytes)
REGISTER sip:SBC:5060;transport=TCP SIP/2.0
Via: SIP/2.0/TCP Internal IP:52063;branch=z9hG4bKep2b3s99g1w7h
Max-Forwards: 70
From: <sip:+49xxx01@SBC:5060;transport=TCP>;tag=zfb5ee
To: <sip:+49xxx01@SBC:5060;transport=TCP>
Call-ID: wr9vfjgbzj3c.37p0403l5
CSeq: 71476 REGISTER
Contact: <sip:+49xxx01@Internal IP:52063;transport=TCP;line=34243>
Allow: INVITE, CANCEL, BYE, ACK, REGISTER, OPTIONS, REFER, SUBSCRIBE, NOTIFY, MESSAGE, INFO, PRACK, UPDATE
Allow-Events: talk,hold
Expires: 3600
User-Agent: snomM300/05.30.0002 (MAC=00041362B6B5; SER= 00000; HW=1)
Content-Length: 0
Sent to tcp:SBC:5060 at 19/04/2022 19:15:29 (641 bytes)
REGISTER sip:SBC:5060;transport=TCP SIP/2.0
Via: SIP/2.0/TCP Internal IP:52063;branch=z9hG4bKb7c.0rvf18
Max-Forwards: 70
From: <sip:+49xxx65@SBC:5060;transport=TCP>;tag=lmmrvkq
To: <sip:+49xxx65@SBC:5060;transport=TCP>
Call-ID: qyvc2p55glfe6qnd
CSeq: 66884 REGISTER
Contact: <sip:+49xxx65@Internal IP:52063;transport=TCP;line=34877>
Allow: INVITE, CANCEL, BYE, ACK, REGISTER, OPTIONS, REFER, SUBSCRIBE, NOTIFY, MESSAGE, INFO, PRACK, UPDATE
Allow-Events: talk,hold
Expires: 3600
User-Agent: snomM300/05.30.0002 (MAC=00041362B6B5; SER= 00000; HW=1)
Content-Length: 0
Received from tcp:0.0.0.0:5060 at 19/04/2022 19:15:29 (432 bytes)
SIP/2.0 401 Unauthorized
Via: SIP/2.0/TCP Internal IP:52063;branch=z9hG4bKep2b3s99g1w7h
From: <sip:+49xxx01@SBC;transport=tcp>;tag=zfb5ee
To: <sip:+49xxx01@SBC;transport=tcp>;tag=1c804059375
Call-ID: wr9vfjgbzj3c.37p0403l5
CSeq: 71476 REGISTER
www-authenticate: Digest realm="DefaultSipRealm",nonce="MTY1Nzc3NjE2MToyMTA4OTg0NzI3",qop="auth,auth-int",algorithm=MD5
Content-Length: 0
Sent to tcp:SBC:5060 at 19/04/2022 19:15:29 (912 bytes)
REGISTER sip:SBC:5060;transport=TCP SIP/2.0
Via: SIP/2.0/TCP Internal IP:52063;branch=z9hG4bK16.0a09p6a8j40oofry6
Max-Forwards: 70
From: <sip:+49xxx01@SBC:5060;transport=TCP>;tag=zfb5ee
To: <sip:+49xxx01@SBC:5060;transport=TCP>
Call-ID: wr9vfjgbzj3c.37p0403l5
CSeq: 71477 REGISTER
Contact: <sip:+49xxx01@Internal IP:52063;transport=TCP;line=34243>
Allow: INVITE, CANCEL, BYE, ACK, REGISTER, OPTIONS, REFER, SUBSCRIBE, NOTIFY, MESSAGE, INFO, PRACK, UPDATE
Allow-Events: talk,hold
Authorization: Digest username="belab3", realm="DefaultSipRealm", nonce="MTY1Nzc3NjE2MToyMTA4OTg0NzI3", uri="sip:SBC:5060;transport=TCP", response="6e1390862adb4f17e9214c5cdb7a7309", qop=auth, nc=00000001, algorithm=MD5, cnonce="s54i3jyzxy"
Expires: 3600
User-Agent: snomM300/05.30.0002 (MAC=00041362B6B5; SER= 00000; HW=1)
Content-Length: 0
Received from tcp:0.0.0.0:5060 at 19/04/2022 19:15:29 (424 bytes)
SIP/2.0 401 Unauthorized
Via: SIP/2.0/TCP Internal IP:52063;branch=z9hG4bKb7c.0rvf18
From: <sip:+49xxx65@SBC;transport=tcp>;tag=lmmrvkq
To: <sip:+49xxx65@SBC;transport=tcp>;tag=1c885674320
Call-ID: qyvc2p55glfe6qnd
CSeq: 66884 REGISTER
www-authenticate: Digest realm="DefaultSipRealm",nonce="MTY1Nzc3NjE3NzoxNjE0NTM1NDgx",qop="auth,auth-int",algorithm=MD5
Content-Length: 0
Sent to tcp:SBC:5060 at 19/04/2022 19:15:29 (906 bytes)
REGISTER sip:SBC:5060;transport=TCP SIP/2.0
Via: SIP/2.0/TCP Internal IP:52063;branch=z9hG4bK66p53hk1eobz8yas5shx7
Max-Forwards: 70
From: <sip:+49xxx65@SBC:5060;transport=TCP>;tag=lmmrvkq
To: <sip:+49xxx65@SBC:5060;transport=TCP>
Call-ID: qyvc2p55glfe6qnd
CSeq: 66885 REGISTER
Contact: <sip:+49xxx65@Internal IP:52063;transport=TCP;line=34877>
Allow: INVITE, CANCEL, BYE, ACK, REGISTER, OPTIONS, REFER, SUBSCRIBE, NOTIFY, MESSAGE, INFO, PRACK, UPDATE
Allow-Events: talk,hold
Authorization: Digest username="belab2", realm="DefaultSipRealm", nonce="MTY1Nzc3NjE3NzoxNjE0NTM1NDgx", uri="sip:SBC:5060;transport=TCP", response="733afed07bdca1ee597eec84a5ba7c83", qop=auth, nc=00000001, algorithm=MD5, cnonce="h2tg7i50"
Expires: 3600
User-Agent: snomM300/05.30.0002 (MAC=00041362B6B5; SER= 00000; HW=1)
Content-Length: 0
Received from tcp:0.0.0.0:5060 at 19/04/2022 19:15:29 (536 bytes)
SIP/2.0 200 OK
Via: SIP/2.0/TCP Internal IP:52063;branch=z9hG4bK16.0a09p6a8j40oofry6
From: <sip:+49xxx01@SBC;transport=tcp>;tag=zfb5ee
To: <sip:+49xxx01@SBC;transport=tcp>;tag=1c1383351490
Call-ID: wr9vfjgbzj3c.37p0403l5
CSeq: 71477 REGISTER
Contact: <sip:+49xxx01@Internal IP:52063;transport=tcp;line=34243>;expires=3600
Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SUBSCRIBE,UPDATE
Expires: 3600
Server: Mediant SW/v.7.40A.250.262
Content-Length: 0
Received from tcp:0.0.0.0:5060 at 19/04/2022 19:15:29 (532 bytes)
SIP/2.0 200 OK
Via: SIP/2.0/TCP Internal IP:52063;branch=z9hG4bK66p53hk1eobz8yas5shx7
From: <sip:+49xxx65@SBC;transport=tcp>;tag=lmmrvkq
To: <sip:+49xxx65@SBC;transport=tcp>;tag=1c1129622900
Call-ID: qyvc2p55glfe6qnd
CSeq: 66885 REGISTER
Contact: <sip:+49xxx65@Internal IP:52063;transport=tcp;line=34877>;expires=3600
Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SUBSCRIBE,UPDATE
Expires: 3600
Server: Mediant SW/v.7.40A.250.262
Content-Length: 0
Sent to tcp:SBC:5060 at 19/04/2022 19:15:29 (639 bytes)
REGISTER sip:SBC:5060;transport=TCP SIP/2.0
Via: SIP/2.0/TCP Internal IP:52063;branch=z9hG4bKw1f3qo9n9k5
Max-Forwards: 70
From: <sip:+49xxx66@SBC:5060;transport=TCP>;tag=z0zzi
To: <sip:+49xxx66@SBC:5060;transport=TCP>
Call-ID: sc0zcktxoqbqzdt
CSeq: 73440 REGISTER
Contact: <sip:+49xxx66@Internal IP:52063;transport=TCP;line=65306>
Allow: INVITE, CANCEL, BYE, ACK, REGISTER, OPTIONS, REFER, SUBSCRIBE, NOTIFY, MESSAGE, INFO, PRACK, UPDATE
Allow-Events: talk,hold
Expires: 3600
User-Agent: snomM300/05.30.0002 (MAC=00041362B6B5; SER= 00000; HW=1)
Content-Length: 0
Received from tcp:0.0.0.0:5060 at 19/04/2022 19:15:29 (422 bytes)
SIP/2.0 401 Unauthorized
Via: SIP/2.0/TCP Internal IP:52063;branch=z9hG4bKw1f3qo9n9k5
From: <sip:+49xxx66@SBC;transport=tcp>;tag=z0zzi
To: <sip:+49xxx66@SBC;transport=tcp>;tag=1c153958103
Call-ID: sc0zcktxoqbqzdt
CSeq: 73440 REGISTER
www-authenticate: Digest realm="DefaultSipRealm",nonce="MTY1Nzc3Njc4NDozNDcwNDQxNzE=",qop="auth,auth-int",algorithm=MD5
Content-Length: 0
Sent to tcp:SBC:5060 at 19/04/2022 19:15:29 (899 bytes)
REGISTER sip:SBC:5060;transport=TCP SIP/2.0
Via: SIP/2.0/TCP Internal IP:52063;branch=z9hG4bKc1gtnrhax7.q4q
Max-Forwards: 70
From: <sip:+49xxx66@SBC:5060;transport=TCP>;tag=z0zzi
To: <sip:+49xxx66@SBC:5060;transport=TCP>
Call-ID: sc0zcktxoqbqzdt
CSeq: 73441 REGISTER
Contact: <sip:+49xxx66@Internal IP:52063;transport=TCP;line=65306>
Allow: INVITE, CANCEL, BYE, ACK, REGISTER, OPTIONS, REFER, SUBSCRIBE, NOTIFY, MESSAGE, INFO, PRACK, UPDATE
Allow-Events: talk,hold
Authorization: Digest username="belab1", realm="DefaultSipRealm", nonce="MTY1Nzc3Njc4NDozNDcwNDQxNzE=", uri="sip:SBC:5060;transport=TCP", response="7e7a2ff9d1145b7253dcff7f0e68a10b", qop=auth, nc=00000001, algorithm=MD5, cnonce="lc4.e4bznlq"
Expires: 3600
User-Agent: snomM300/05.30.0002 (MAC=00041362B6B5; SER= 00000; HW=1)
Content-Length: 0
Received from tcp:0.0.0.0:5060 at 19/04/2022 19:15:29 (522 bytes)
SIP/2.0 200 OK
Via: SIP/2.0/TCP Internal IP:52063;branch=z9hG4bKc1gtnrhax7.q4q
From: <sip:+49xxx66@SBC;transport=tcp>;tag=z0zzi
To: <sip:+49xxx66@SBC;transport=tcp>;tag=1c1762628427
Call-ID: sc0zcktxoqbqzdt
CSeq: 73441 REGISTER
Contact: <sip:+49xxx66@Internal IP:52063;transport=tcp;line=65306>;expires=3600
Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SUBSCRIBE,UPDATE
Expires: 3600
Server: Mediant SW/v.7.40A.250.262
Content-Length: 0
Received from tcp:0.0.0.0:5060 at 19/04/2022 19:16:30 (1077 bytes)
INVITE sip:+49xxx66@Internal IP:52063;transport=tcp;line=65306 SIP/2.0
Via: SIP/2.0/TCP SBC:5060;alias;branch=z9hG4bKac995893985
Max-Forwards: 60
From: <sip:+491743125985@teseleso.ngn.vodafone.de;user=phone>;tag=1c616680213
To: <sip:+49xxx66@hmbsx001.ngn.vodafone.de;user=phone>
Call-ID: 11238016501942022191650@SBC
CSeq: 1 INVITE
Contact: <sip:+491743125985@SBC:5060;transport=tcp>
Supported: 100rel,timer,resource-priority,sdp-anat
Allow: INVITE, ACK, PRACK, CANCEL, BYE, OPTIONS, MESSAGE, NOTIFY, UPDATE, REGISTER, INFO, REFER, SUBSCRIBE
Session-Expires: 1810;refresher=uac
Min-SE: 600
User-Agent: Mediant SW/v.7.40A.250.262
P-Asserted-Identity: <sip:+491743125985@teseleso.ngn.vodafone.de;user=phone>
Accept: application/sdp
Date: Tue, 19 Apr 2022 19:16:33 GMT
Content-Type: application/sdp
Content-Length: 177
P-Early-Media: supported
v=0
o=- 1579269708 896975789 IN IP4 SBC
s=IMSS
c=IN IP4 SBC
t=0 0
m=audio 6864 RTP/AVP 8 97
a=rtpmap:97 telephone-event/8000
a=ptime:20
a=maxptime:30
Sent to tcp:0.0.0.0:5060 at 19/04/2022 19:16:30 (312 bytes)
SIP/2.0 100 Trying
Via: SIP/2.0/TCP SBC:5060;alias;branch=z9hG4bKac995893985
From: <sip:+491743125985@teseleso.ngn.vodafone.de;user=phone>;tag=1c616680213
To: <sip:+49xxx66@hmbsx001.ngn.vodafone.de;user=phone>
Call-ID: 11238016501942022191650@SBC
CSeq: 1 INVITE
Content-Length: 0
Sent to tcp:0.0.0.0:5060 at 19/04/2022 19:16:31 (652 bytes)
SIP/2.0 180 Ringing
Via: SIP/2.0/TCP SBC:5060;alias;branch=z9hG4bKac995893985
Max-Forwards: 70
From: <sip:+491743125985@teseleso.ngn.vodafone.de;user=phone>;tag=1c616680213
To: <sip:+49xxx66@hmbsx001.ngn.vodafone.de;user=phone>;tag=cn47hvutr
Call-ID: 11238016501942022191650@SBC
CSeq: 1 INVITE
Contact: <sip:+49xxx66@Internal IP:52063;transport=TCP;line=65306>
Allow: INVITE, CANCEL, BYE, ACK, REGISTER, OPTIONS, REFER, SUBSCRIBE, NOTIFY, MESSAGE, INFO, PRACK, UPDATE
Allow-Events: talk,hold
Require: 100rel
RSeq: 8314
User-Agent: snomM300/05.30.0002 (MAC=00041362B6B5; SER= 00000; HW=1)
Content-Length: 0
Received from tcp:0.0.0.0:5060 at 19/04/2022 19:16:31 (505 bytes)
PRACK sip:+49xxx66@Internal IP:52063;transport=TCP;line=65306 SIP/2.0
Via: SIP/2.0/TCP SBC:5060;alias;branch=z9hG4bKac608585365
Max-Forwards: 60
From: <sip:+491743125985@teseleso.ngn.vodafone.de;user=phone>;tag=1c616680213
To: <sip:+49xxx66@hmbsx001.ngn.vodafone.de;user=phone>;tag=cn47hvutr
Call-ID: 11238016501942022191650@SBC
CSeq: 2 PRACK
Supported: 100rel,timer,resource-priority
RAck: 8314 1 INVITE
User-Agent: Mediant SW/v.7.40A.250.262
Content-Length: 0
Sent to tcp:0.0.0.0:5060 at 19/04/2022 19:16:31 (473 bytes)
SIP/2.0 200 OK
Via: SIP/2.0/TCP SBC:5060;alias;branch=z9hG4bKac608585365
Max-Forwards: 60
From: <sip:+491743125985@teseleso.ngn.vodafone.de;user=phone>;tag=1c616680213
To: <sip:+49xxx66@hmbsx001.ngn.vodafone.de;user=phone>;tag=cn47hvutr
Call-ID: 11238016501942022191650@SBC
CSeq: 2 PRACK
RAck: 8314 1 INVITE
Supported: 100rel,timer,resource-priority
User-Agent: snomM300/05.30.0002 (MAC=00041362B6B5; SER= 00000; HW=1)
Content-Length: 0
Sent to tcp:0.0.0.0:5060 at 19/04/2022 19:16:35 (1001 bytes)
SIP/2.0 200 OK
Via: SIP/2.0/TCP SBC:5060;alias;branch=z9hG4bKac995893985
Max-Forwards: 70
From: <sip:+491743125985@teseleso.ngn.vodafone.de;user=phone>;tag=1c616680213
To: <sip:+49xxx66@hmbsx001.ngn.vodafone.de;user=phone>;tag=cn47hvutr
Call-ID: 11238016501942022191650@SBC
CSeq: 1 INVITE
Contact: <sip:+49xxx66@Internal IP:52063;transport=TCP;line=65306>
Accept: application/sdp
Allow: INVITE, CANCEL, BYE, ACK, REGISTER, OPTIONS, REFER, SUBSCRIBE, NOTIFY, MESSAGE, INFO, PRACK, UPDATE
Content-Disposition: session
Min-SE: 90
Require: timer
Session-Expires: 1810;refresher=uac
User-Agent: snomM300/05.30.0002 (MAC=00041362B6B5; SER= 00000; HW=1)
Content-Type: application/sdp
Content-Length: 255
v=0
o=+49xxx66 901987628 901987628 IN IP4 Internal IP
s=-
c=IN IP4 Internal IP
t=0 0
m=audio 50004 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
a=maxptime:80
a=sendrecv
a=rtcp:50005
Received from tcp:0.0.0.0:5060 at 19/04/2022 19:16:35 (499 bytes)
ACK sip:+49xxx66@Internal IP:52063;transport=TCP;line=65306 SIP/2.0
Via: SIP/2.0/TCP SBC:5060;alias;branch=z9hG4bKac407442491
Max-Forwards: 60
From: <sip:+491743125985@teseleso.ngn.vodafone.de;user=phone>;tag=1c616680213
To: <sip:+49xxx66@hmbsx001.ngn.vodafone.de;user=phone>;tag=cn47hvutr
Call-ID: 11238016501942022191650@SBC
CSeq: 1 ACK
Contact: <sip:+491743125985@SBC:5060;transport=tcp>
User-Agent: Mediant SW/v.7.40A.250.262
Content-Length: 0
Sent to tcp:SBC:5060 at 19/04/2022 19:24:03 (1007 bytes)
INVITE sip:65@SBC:5060;user=phone SIP/2.0
Via: SIP/2.0/TCP Internal IP:52063;branch=z9hG4bK2s15c6reb3mh37med4
Max-Forwards: 70
From: "Be Lab 01" <sip:+49xxx01@SBC:5060;transport=TCP>;tag=okw3t0f43hpm
To: <sip:65@SBC:5060;user=phone>
Call-ID: 3wlzio1zrx@SBC
CSeq: 59088 INVITE
Contact: <sip:+49xxx01@Internal IP:52063;transport=TCP;line=34243>
Allow: INVITE, CANCEL, BYE, ACK, REGISTER, OPTIONS, REFER, SUBSCRIBE, NOTIFY, MESSAGE, INFO, PRACK, UPDATE
Content-Disposition: session
Min-SE: 90
Session-Expires: 3600
Supported: replaces,100rel,timer
User-Agent: snomM300/05.30.0002 (MAC=00041362B6B5; SER= 00000; HW=1)
Content-Type: application/sdp
Content-Length: 255
v=0
o=+49xxx01 913294759 913294759 IN IP4 Internal IP
s=-
c=IN IP4 Internal IP
t=0 0
m=audio 50006 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
a=maxptime:80
a=sendrecv
a=rtcp:50007
Sent to tcp:SBC:5060 at 19/04/2022 19:25:59 (656 bytes)
BYE sip:+491743125985@SBC:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP Internal IP:52063;branch=z9hG4bKllwcw46p9oe7yaiesokqha9sb8m82v
Max-Forwards: 70
From: <sip:+49xxx66@hmbsx001.ngn.vodafone.de;user=phone>;tag=cn47hvutr
To: <sip:+491743125985@teseleso.ngn.vodafone.de;user=phone>;tag=1c616680213
Call-ID: 11238016501942022191650@SBC
CSeq: 22332 BYE
Contact: <sip:+49xxx66@Internal IP:52063;transport=TCP;line=65306>
Allow: INVITE, CANCEL, BYE, ACK, REGISTER, OPTIONS, REFER, SUBSCRIBE, NOTIFY, MESSAGE, INFO, PRACK, UPDATE
User-Agent: snomM300/05.30.0002 (MAC=00041362B6B5; SER= 00000; HW=1)
Content-Length: 0
SysLOG:
NWK .Info 2022-04-19T19:14:59Z 235-[ ETH: Link down]
NWK .Info 2022-04-19T19:15:02Z 235-[ ETH: Link up]
NWK .Info 2022-04-19T19:15:04Z 235-[ ETH: Delta Link down/up 3s]
NWK .Info 2022-04-19T19:15:04Z 235-[ ETH: Running 100Mb/s]
NWK .Info 2022-04-19T19:15:04Z 235-[ DHCP Enabled]
NWK .Info 2022-04-19T19:15:04Z 235-[ IP Address: xxx226]
NWK .Info 2022-04-19T19:15:04Z 235-[ Gateway Address: xxx]
NWK .Info 2022-04-19T19:15:04Z 235-[ Subnet Mask: 255.255.255.0]
NWK .Info 2022-04-19T19:15:04Z 235-[ DHCP Discover completed]
loc3 .Info 2022-04-19T19:15:06Z 235-[ MAC=00041362B6B5, SER= 00000, HW=1 CHIP=452]
loc3 .Info 2022-04-19T19:15:06Z 235-[ Stun detection disabled]
loc3 .Info 2022-04-19T19:15:07Z 235-[ RemCfg: Checking for settings]
loc3 .Info 2022-04-19T19:15:07Z 235-[ RemCfg: Attempting fetch of file: http://provisioning.snom.com/snomM300.htm]
loc3 .Info 2022-04-19T19:15:07Z 235-[ RemCfg: File loaded successfully]
loc3 .Info 2022-04-19T19:15:07Z 235-[ RemCfg: Redirection detected ]
loc3 .Info 2022-04-19T19:15:07Z 235-[ RemCfg: Attempting fetch of file: http://provisioning.snom.com/snomM300/snomM300.php?mac=00041362B6B5]
loc3 .Info 2022-04-19T19:15:07Z 235-[ RemCfg: File loaded successfully]
loc3 .Info 2022-04-19T19:15:07Z 235-[ RemCfg: Detected XML file]
loc3 .Info 2022-04-19T19:15:07Z 235-[ RemCfg: Error parsing file]
loc3 .Info 2022-04-19T19:15:07Z 235-[ RemCfg: No setting server offered via SIP PNP]
loc3 .Info 2022-04-19T19:15:07Z 235-[ RemCfg: No setting server offered in DHCP]
loc3 .Info 2022-04-19T19:15:07Z 235-[ RemCfg: Provisioning completed]
loc3 .Info 2022-04-19T19:15:07Z 235-[ UpdateAllTimestamps]
loc3 .Info 2022-04-19T19:15:07Z 235-[ RemCfg: Attempting fetch of file: /]
loc3 .Info 2022-04-19T19:15:08Z 235-[ RemCfg: Error loading file]
loc3 .Info 2022-04-19T19:15:08Z 235-[ RemCfg: Provisioning PhoneBook completed]
loc7 .Info 2022-04-19T19:15:08Z 235-[ Firmware Device M300 Version:0530 Branch:0002 Rfpi:1337BC3E00]
loc7 .Info 2022-04-19T19:15:08Z 235-[ DECT Mode: EU]
loc7 .Info 2022-04-19T19:15:08Z 235-[ System Mode: (a4/55)]
loc7 .Info 2022-04-19T19:15:08Z 235-[ Normal Reboot]
loc7 .Info 2022-04-19T19:15:08Z 235-[ Extended mail full error log skipped due to no data!]
loc7 .Info 2022-04-19T19:15:08Z 235-[ DECT protocol delay timer started (single cell)]
clk .Info 2022-04-19T19:15:11Z 235-[ UTC time set initiated by SNTP (1650388511 s)]
clk .Info 2022-04-19T19:15:11Z 235-[ Local time set (2022-04-19 19:15:11)]
loc3 .Info 2022-04-19T19:15:11Z 235-[ Time and Date and DST Broadcast to handsets]
loc7 .Info 2022-04-19T19:15:25Z 235-[ DECT protocol activated, delay passed (single cell)]
loc7 .Info 2022-04-19T19:15:25Z 235-[ DECT: FP_START_MAC FpIdx#0x00: SourceFpIdx#0x00, SyncState State#0]
loc0 .Info 2022-04-19T19:15:26Z 235-[ DECT master mode]
loc7 .Info 2022-04-19T19:15:29Z 235-[ Device M25 version:0530 Branch:0002 Present@RPN00 Ipui:038D605C9B Pmid:00002 OperationTime:13831sec]
loc7 .Info 2022-04-19T19:15:29Z 235-[ updateRegistrationGroupCall all god for SipExtId #1 Used for PP's: #2]
loc7 .Info 2022-04-19T19:15:29Z 235-[ Register +49xxx01 for Line: 0]
loc7 .Info 2022-04-19T19:15:29Z 235-[ Device M25 version:0530 Branch:0002 Present@RPN00 Ipui:038D604547 Pmid:00003 OperationTime:437987sec]
loc7 .Info 2022-04-19T19:15:29Z 235-[ updateRegistrationGroupCall all god for SipExtId #2 Used for PP's: #4]
loc7 .Info 2022-04-19T19:15:29Z 235-[ Register +49xxx65 for Line: 0]
loc3 .Info 2022-04-19T19:15:29Z 235-[ Registration of user +49xxx01 (ExtIdx#0001) on domain SBC:5060 succeeded]
loc7 .Info 2022-04-19T19:15:29Z 235-[ updateRegistrationGroupCall all god for SipExtId #1 Used for PP's: #2]
loc7 .Info 2022-04-19T19:15:29Z 235-[ DECT MAC statistics: Pmid:E720D Typ:FN Res:3 Frames:60,9,0 Bho:0,0 Rssi:0]
loc7 .Info 2022-04-19T19:15:29Z 235-[ DECT MAC statistics: Pmid:E0B02 Typ:FN Res:3 Frames:59,9,0 Bho:0,0 Rssi:0]
loc3 .Info 2022-04-19T19:15:29Z 235-[ Registration of user +49xxx65 (ExtIdx#0002) on domain SBC:5060 succeeded]
loc7 .Info 2022-04-19T19:15:29Z 235-[ updateRegistrationGroupCall all god for SipExtId #2 Used for PP's: #4]
loc7 .Info 2022-04-19T19:15:29Z 235-[ Device M25 version:0530 Branch:0002 Present@RPN00 Ipui:0328D24775 Pmid:00001 OperationTime:438730sec]
loc7 .Info 2022-04-19T19:15:29Z 235-[ updateRegistrationGroupCall all god for SipExtId #0 Used for PP's: #1]
loc7 .Info 2022-04-19T19:15:29Z 235-[ Register +49xxx66 for Line: 0]
loc3 .Info 2022-04-19T19:15:29Z 235-[ Registration of user +49xxx66 (ExtIdx#0000) on domain SBC:5060 succeeded]
loc7 .Info 2022-04-19T19:15:29Z 235-[ updateRegistrationGroupCall all god for SipExtId #0 Used for PP's: #1]
loc7 .Info 2022-04-19T19:15:30Z 235-[ DECT MAC statistics: Pmid:E9A8D Typ:FN Res:3 Frames:60,9,0 Bho:0,0 Rssi:0]
loc7 .Info 2022-04-19T19:15:31Z 235-[ DECT MAC statistics: Pmid:00003 Typ:FN Res:0 Frames:213,55,0 Bho:0,0 Rssi:59]
loc7 .Info 2022-04-19T19:15:34Z 235-[ DECT MAC statistics: Pmid:00001 Typ:FN Res:0 Frames:213,55,0 Bho:0,0 Rssi:59]
loc7 .Info 2022-04-19T19:15:34Z 235-[ DECT MAC statistics: Pmid:00002 Typ:FN Res:0 Frames:215,55,0 Bho:0,0 Rssi:59]
loc7 .Info 2022-04-19T19:16:30Z 235-[ Call Incoming user +49xxx66]
loc3 .Info 2022-04-19T19:16:30Z 235-[ FpCtrlResetHandler PR#712 AC#0:0 RP#0 HR#0]
loc3 .Info 2022-04-19T19:16:30Z 235-[ FpCtrlResetHandler CRE AC#1:0 RP#0 HR#0]
loc0 .Info 2022-04-19T19:16:35Z 235-[ RSSI report HS:+49xxx66 PMID:00001 RPN:00 dBm:-24]
loc0 .Info 2022-04-19T19:16:35Z 235-[ PMID:00001 Battery Level: 99]
loc7 .Info 2022-04-19T19:16:36Z 235-[ DECT Audio active Pmid:00001]
loc7 .Info 2022-04-19T19:24:03Z 235-[ Call Outgoing user +49xxx01]
loc0 .Info 2022-04-19T19:24:03Z 235-[ RSSI report HS:+49xxx01 PMID:00002 RPN:00 dBm:-24]
loc0 .Info 2022-04-19T19:24:03Z 235-[ PMID:00002 Battery Level: 97]
loc7 .Info 2022-04-19T19:24:08Z 235-[ Call Release user +49xxx01 Duration: 00:00:05]
loc7 .Info 2022-04-19T19:24:08Z 235-[ DECT MAC statistics: Pmid:00002 Typ:FN Res:0 Frames:541,3,0 Bho:0,0 Rssi:59]
loc7 .Info 2022-04-19T19:25:59Z 235-[ Call Released user +49xxx66 Duration: 00:09:29]
loc3 .Info 2022-04-19T19:25:59Z 235-[ FpCtrlResetHandler PR#713 AC#1:0 RP#0 HR#0]
loc3 .Info 2022-04-19T19:25:59Z 235-[ FpCtrlResetHandler TER AC#0:0 RP#0 HR#0]
loc7 .Info 2022-04-19T19:25:59Z 235-[ DECT MAC statistics: Pmid:00001 Typ:FA Res:0 Frames:56841,0,0 Bho:0,0 Rssi:58]
Snom Federico Rossi
Hi,
the outgoing call INVITE (call id 3wlzio1zrx@SBC) received no response. Do you see the SIP reply on PBX/SBC?
End user Christian Schurig
Hi Federico,
thanks for your support. The Network issue seams to be solved now.
Since we added the original Firewall IPs of our Firewall Cluster member to SBC/PBX allow list, it works and incomming and outgoing calls are available.
So as a remark for other Users: if you use a Fortigate Firewall Cluster, it seams to be required to also allow the solo IPs of the Clustermembers instead of the Cluster IP only.
Howeveer, no I have some registration issues, which are new, as this device was already registeret.
There are 3 M25 registered to the M300 1 x m25 has registration issues...
Can you help me with the following siplog:
Received from tcp:0.0.0.0:5060 at 20/04/2022 13:51:00 (453 bytes)
SIP/2.0 401 Unauthorized
Via: SIP/2.0/TCP internalip6:52697;branch=z9hG4bKc59eymww3c3b3jc65jpcisje048o6vh
From: <sip:+49xxx01@sbc01;transport=tcp>;tag=9ahe7.i
To: <sip:+49xxx01@sbc01;transport=tcp>;tag=1c1244073051
Call-ID: 3a8rm9l16d6jdb9nxsgewoman9
CSeq: 123126 REGISTER
www-authenticate: Digest realm="DefaultSipRealm",nonce="MTc0MzQ0ODoxMTk4Mjk0MTcx",qop="auth,auth-int",algorithm=MD5
Content-Length: 0
Received from tcp:0.0.0.0:5060 at 20/04/2022 13:51:00 (447 bytes)
SIP/2.0 401 Unauthorized
Via: SIP/2.0/TCP internalIP:52697;branch=z9hG4bK.ae5t2ldu005vviboq5u07xm.
From: <sip:+49xxx01@sbc01;transport=tcp>;tag=9ahe7.i
To: <sip:+49xxx01@sbc01transport=tcp>;tag=1c1757889215
Call-ID: 3a8rm9l16d6jdb9nxsgewoman9
CSeq: 123130 REGISTER
www-authenticate: Digest realm="DefaultSipRealm",nonce="MTc0MzY5MjozNDY4ODQzMTM=",qop="auth,auth-int",algorithm=MD5
Content-Length: 0
Syslog:
loc3 .Info 2022-04-20T13:56:51Z 235-[ Registration of user +49xxx01 (ExtIdx#0001) on domain sbc01:5060 failed]
loc7 .Info 2022-04-20T13:56:51Z 235-[ updateRegistrationGroupCall all god for SipExtId #1 Used for PP's: #2]
loc3 .Info 2022-04-20T13:57:02Z 235-[ Registration of user +49xxx01 (ExtIdx#0001) on domain sbc01:5060 failed]
loc7 .Info 2022-04-20T13:57:02Z 235-[ updateRegistrationGroupCall all god for SipExtId #1 Used for PP's: #2]
clk .Info 2022-04-20T13:57:05Z 235-[ UTC time set initiated by SNTP (1650455825 s)]
clk .Info 2022-04-20T13:57:05Z 235-[ Local time set (2022-04-20 13:57:05)]
loc3 .Info 2022-04-20T13:57:05Z 235-[ Time and Date and DST Broadcast to handsets]
loc3 .Info 2022-04-20T13:57:13Z 235-[ Registration of user +49xxx01 (ExtIdx#0001) on domain sbc01:5060 failed]
loc7 .Info 2022-04-20T13:57:13Z 235-[ updateRegistrationGroupCall all god for SipExtId #1 Used for PP's: #2]
Snom Federico Rossi
Could you post a screenshot of the Network webpage?
End user Christian Schurig
btw. the registration issue with sip:+49xxx01@sbc01 is solved now. SBC techniken tried this account on an other device.
So existing errors look like network issues.
We have same issues now with not working calls after the FW change...sometimes Its working, somtimes not...
We try to find out if the sip device request on the PBX is visible.
Any recommendations for networksettings ?
Sent to tcp:20.218.72.45:5060 at 20/04/2022 17:49:06 (659 bytes)
REGISTER sip:sbc01:5060;transport=TCP SIP/2.0
Via: SIP/2.0/TCP internalIP:52067;branch=z9hG4bKl8oaph25vivv36.jr239tvta2o
Max-Forwards: 70
From: <sip:+49xxx65@sbc01:5060;transport=TCP>;tag=0w923xc3ruwn
To: <sip:+49xxx65@sbc01:5060;transport=TCP>
Call-ID: myd0kwa7spy.
CSeq: 166332 REGISTER
Contact: <sip:+49xxx65@internalIP:52067;transport=TCP;line=22809>
Allow: INVITE, CANCEL, BYE, ACK, REGISTER, OPTIONS, REFER, SUBSCRIBE, NOTIFY, MESSAGE, INFO, PRACK, UPDATE
Allow-Events: talk,hold
Expires: 3600
User-Agent: snomM300/05.30.0002 (MAC=00041362B6B5; SER= 00000; HW=1)
Content-Length: 0
regards
Christian Schurig
Snom Federico Rossi
Hi Christian,
I asked about Network page because the logs you posted earlier made me think about wrong values of the sip failover fields, but from the image they are correct.
FW change, do you mean firewall, right? The SIP REGISTER is ok, you must check if this message reaches the PBX and if the PBX responds.
End user Christian Schurig
Hi Federico,
yes, we changed something on the Firewall, but without any effect.
Today we startet an other test, while we changed SIP protokoll to UDP instead of TCP.
Since we have done this, I dont have this amount of SIP registration requests anymore on the M300.
And until now it seams to be stable.
(Registration request was about every 10 to 60 sec, now its 60 Minutes.)
Our Firewall and BPX Experts expect, that there is something wrong with TCP Sessions, interrupts or droped packets... definitely a firewall problem.
However, it seams like its not an Device Issue.
So thanks for your support.
Best Regards
Christian Schurig