.titleBar { margin-bottom: 5px!important; }

[GEKLÄRT] keine ausgehenden kostenpfl. Gespräche bei Sipgate

Dieses Thema im Forum "snom" wurde erstellt von der_Gersthofer, 29 Mai 2005.

  1. der_Gersthofer

    der_Gersthofer Admin-Team

    Registriert seit:
    17 Apr. 2004
    Beiträge:
    3,585
    Zustimmungen:
    0
    Punkte für Erfolge:
    36
  2. solaris

    solaris Neuer User

    Registriert seit:
    16 Feb. 2005
    Beiträge:
    140
    Zustimmungen:
    0
    Punkte für Erfolge:
    16
    Re: [PROBLEM] Firmware 3.60 und Sipgate; ausgehende Gespräch


    Geht es denn bei Dir mit einer anderen Firmware-Version? Wie schon im anderen Thread erwähnt, bei mir läuft es auch unter 3.56y nicht.

    cu solaris
     
  3. Rocky512

    Rocky512 IPPF-Promi

    Registriert seit:
    2 Mai 2004
    Beiträge:
    3,469
    Zustimmungen:
    0
    Punkte für Erfolge:
    0
    Ort:
    Leipzig
    Ich hab mit meiner FW-Version (siehe Signatur) keine Probleme bei ausgehenden kostenpflichtigen Gesprächen über Sipgate.
     
  4. der_Gersthofer

    der_Gersthofer Admin-Team

    Registriert seit:
    17 Apr. 2004
    Beiträge:
    3,585
    Zustimmungen:
    0
    Punkte für Erfolge:
    36
    Beim SNOM360 gibt es ja nur die Firmwarereihe 3.60
    Ich habe da von b-i alle durchprobiert und mit keiner gehen ausgehende kostenpflichtige Gespräche.

    @solaris: Geht es bei dir mit 3.56t wie bei Rocky?
     
  5. solaris

    solaris Neuer User

    Registriert seit:
    16 Feb. 2005
    Beiträge:
    140
    Zustimmungen:
    0
    Punkte für Erfolge:
    16
    Nein, geht leider auch nicht. Ich habe allerdings bei sipgate kein Guthaben. Aber ich denke, dann müsste wohl eine entsprechend andere Ansage kommen, oder?

    cu solaris
     
  6. der_Gersthofer

    der_Gersthofer Admin-Team

    Registriert seit:
    17 Apr. 2004
    Beiträge:
    3,585
    Zustimmungen:
    0
    Punkte für Erfolge:
    36
    Zwei Dinge, die im LOG auffallen:

    Loop Detected und Method not allowed. Es ist kein Wählplan eingetragen im SNOM.

    Sent to udp:192.168.0.1:5060 at 30/5/2005 16:57:56:360 (734 bytes):
    SIP/2.0 482 Loop Detected
    Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bKd02136b3035552a18dfcd7b47082b46d.0
    Via: SIP/2.0/UDP 217.10.79.9;branch=z9hG4bK3e7.c99c13c7.1
    Via: SIP/2.0/UDP 195.158.1xx.xxx:5060;branch=z9hG4bK88a2426ee0734e46547e7dc33ac3b22e.0
    Via: SIP/2.0/UDP 192.168.0.121:2054;rport=2054;branch=z9hG4bK-kvkb5yjf7pmg;received=192.168.0.121
    From: "Name" <sip:ID@sipgate.de>;tag=p1we8egm4d
    To: "Name" <sip:ID@sipgate.de>;tag=yc23iqdaxf
    Call-ID: 3c2907803a98-6npxwr71igaw@snom360
    CSeq: 1 PUBLISH
    Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO
    Allow-Events: talk, hold, refer
    Supported: timer, 100rel, replaces
    Content-Length: 0

    Received from udp:192.168.0.1:5060 at 30/5/2005 16:57:56:420 (465 bytes):
    SIP/2.0 405 Method Not Allowed
    Via: SIP/2.0/UDP 192.168.0.121:2054;branch=z9hG4bK-kvkb5yjf7pmg;received=192.168.0.121
    From: "Name" <sip:ID@sipgate.de>;tag=p1we8egm4d
    To: "Name" <sip:ID@sipgate.de>;tag=as36163d06
    Call-ID: 3c2907803a98-6npxwr71igaw@snom360
    CSeq: 1 PUBLISH
    User-Agent: sipgate voicemail (asterisk)
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
    Contact:
    Accept: application/sdp
    Content-Length: 0




    Code:
    Sent to udp:217.10.79.9:5060 at 30/5/2005 16:57:56:250 (385 bytes):
    PUBLISH sip:ID@sipgate.de SIP/2.0
    Via: SIP/2.0/UDP 192.168.0.121:2054;branch=z9hG4bK-kvkb5yjf7pmg;rport
    From: "Name" <sip:ID@sipgate.de>;tag=p1we8egm4d
    To: "Name" <sip:ID@sipgate.de>
    Call-ID: 3c2907803a98-6npxwr71igaw@snom360
    CSeq: 1 PUBLISH
    Max-Forwards: 70
    Event: proxy-config
    Content-Type: application/text
    Content-Length: 0
    
    Received from udp:192.168.0.1:5060 at 30/5/2005 16:57:56:350 (729 bytes):
    PUBLISH sip:ID@192.168.0.121:2054;line=xlxlhzi1 SIP/2.0
    Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bKd02136b3035552a18dfcd7b47082b46d.0
    Record-Route: <sip:ID@217.10.79.9;ftag=p1we8egm4d;lr=on>
    Via: SIP/2.0/UDP 217.10.79.9;branch=z9hG4bK3e7.c99c13c7.1
    Via: SIP/2.0/UDP 195.158.1xx.xxx:5060;branch=z9hG4bK88a2426ee0734e46547e7dc33ac3b22e.0
    Via: SIP/2.0/UDP 192.168.0.121:2054;rport=2054;branch=z9hG4bK-kvkb5yjf7pmg;received=192.168.0.121
    From: "Name" <sip:ID@sipgate.de>;tag=p1we8egm4d
    To: "Name" <sip:ID@sipgate.de>
    Call-ID: 3c2907803a98-6npxwr71igaw@snom360
    CSeq: 1 PUBLISH
    Max-Forwards: 67
    Event: proxy-config
    Content-Type: application/text
    Content-Length: 0
    
    Sent to udp:192.168.0.1:5060 at 30/5/2005 16:57:56:360 (734 bytes):
    SIP/2.0 482 Loop Detected
    Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bKd02136b3035552a18dfcd7b47082b46d.0
    Via: SIP/2.0/UDP 217.10.79.9;branch=z9hG4bK3e7.c99c13c7.1
    Via: SIP/2.0/UDP 195.158.1xx.xxx:5060;branch=z9hG4bK88a2426ee0734e46547e7dc33ac3b22e.0
    Via: SIP/2.0/UDP 192.168.0.121:2054;rport=2054;branch=z9hG4bK-kvkb5yjf7pmg;received=192.168.0.121
    From: "Name" <sip:ID@sipgate.de>;tag=p1we8egm4d
    To: "Name" <sip:ID@sipgate.de>;tag=yc23iqdaxf
    Call-ID: 3c2907803a98-6npxwr71igaw@snom360
    CSeq: 1 PUBLISH
    Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO
    Allow-Events: talk, hold, refer
    Supported: timer, 100rel, replaces
    Content-Length: 0
    
    Received from udp:192.168.0.1:5060 at 30/5/2005 16:57:56:420 (465 bytes):
    SIP/2.0 405 Method Not Allowed
    Via: SIP/2.0/UDP 192.168.0.121:2054;branch=z9hG4bK-kvkb5yjf7pmg;received=192.168.0.121
    From: "Name" <sip:ID@sipgate.de>;tag=p1we8egm4d
    To: "Name" <sip:ID@sipgate.de>;tag=as36163d06
    Call-ID: 3c2907803a98-6npxwr71igaw@snom360
    CSeq: 1 PUBLISH
    User-Agent: sipgate voicemail (asterisk)
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
    Contact: 
    Accept: application/sdp
    Content-Length: 0
    
    Sent to udp:217.10.79.9:5060 at 30/5/2005 16:57:56:670 (385 bytes):
    PUBLISH sip:ID@sipgate.de SIP/2.0
    Via: SIP/2.0/UDP 192.168.0.121:2054;branch=z9hG4bK-9jojil96woos;rport
    From: "Name" <sip:ID@sipgate.de>;tag=55lccbuwh8
    To: "Name" <sip:ID@sipgate.de>
    Call-ID: 3c290780a122-vybxi2t7mori@snom360
    CSeq: 1 PUBLISH
    Max-Forwards: 70
    Event: proxy-config
    Content-Type: application/text
    Content-Length: 0
    
    Received from udp:192.168.0.1:5060 at 30/5/2005 16:57:56:740 (730 bytes):
    PUBLISH sip:ID@192.168.0.121:2054;line=xlxlhzi1 SIP/2.0
    Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK14fd7862a898ab228dfcd7b47082b46d.0
    Record-Route: <sip:ID@217.10.79.9;ftag=55lccbuwh8;lr=on>
    Via: SIP/2.0/UDP 217.10.79.9;branch=z9hG4bK1c09.70e2d314.1
    Via: SIP/2.0/UDP 195.158.1xx.xxx:5060;branch=z9hG4bK10418c1fccc18705547e7dc33ac3b22e.0
    Via: SIP/2.0/UDP 192.168.0.121:2054;rport=2054;branch=z9hG4bK-9jojil96woos;received=192.168.0.121
    From: "Name" <sip:ID@sipgate.de>;tag=55lccbuwh8
    To: "Name" <sip:ID@sipgate.de>
    Call-ID: 3c290780a122-vybxi2t7mori@snom360
    CSeq: 1 PUBLISH
    Max-Forwards: 67
    Event: proxy-config
    Content-Type: application/text
    Content-Length: 0
    
    Sent to udp:192.168.0.1:5060 at 30/5/2005 16:57:56:750 (735 bytes):
    SIP/2.0 482 Loop Detected
    Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK14fd7862a898ab228dfcd7b47082b46d.0
    Via: SIP/2.0/UDP 217.10.79.9;branch=z9hG4bK1c09.70e2d314.1
    Via: SIP/2.0/UDP 195.158.1xx.xxx:5060;branch=z9hG4bK10418c1fccc18705547e7dc33ac3b22e.0
    Via: SIP/2.0/UDP 192.168.0.121:2054;rport=2054;branch=z9hG4bK-9jojil96woos;received=192.168.0.121
    From: "Name" <sip:ID@sipgate.de>;tag=55lccbuwh8
    To: "Name" <sip:ID@sipgate.de>;tag=iqmis25eob
    Call-ID: 3c290780a122-vybxi2t7mori@snom360
    CSeq: 1 PUBLISH
    Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO
    Allow-Events: talk, hold, refer
    Supported: timer, 100rel, replaces
    Content-Length: 0
    
    Received from udp:192.168.0.1:5060 at 30/5/2005 16:57:56:810 (465 bytes):
    SIP/2.0 405 Method Not Allowed
    Via: SIP/2.0/UDP 192.168.0.121:2054;branch=z9hG4bK-9jojil96woos;received=192.168.0.121
    From: "Name" <sip:ID@sipgate.de>;tag=55lccbuwh8
    To: "Name" <sip:ID@sipgate.de>;tag=as66d47ed1
    Call-ID: 3c290780a122-vybxi2t7mori@snom360
    CSeq: 1 PUBLISH
    User-Agent: sipgate voicemail (asterisk)
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
    Contact: 
    Accept: application/sdp
    Content-Length: 0
    
    Sent to udp:217.10.79.9:5060 at 30/5/2005 16:57:56:870 (385 bytes):
    PUBLISH sip:ID@sipgate.de SIP/2.0
    Via: SIP/2.0/UDP 192.168.0.121:2054;branch=z9hG4bK-rw8c3ien12j4;rport
    From: "Name" <sip:ID@sipgate.de>;tag=ed5gt58tmq
    To: "Name" <sip:ID@sipgate.de>
    Call-ID: 3c290780d1f6-owjjvk4fdo3g@snom360
    CSeq: 1 PUBLISH
    Max-Forwards: 70
    Event: proxy-config
    Content-Type: application/text
    Content-Length: 0
    
    Received from udp:192.168.0.1:5060 at 30/5/2005 16:57:56:940 (730 bytes):
    PUBLISH sip:ID@192.168.0.121:2054;line=xlxlhzi1 SIP/2.0
    Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bKe4d710937f5647058dfcd7b47082b46d.0
    Record-Route: <sip:ID@217.10.79.9;ftag=ed5gt58tmq;lr=on>
    Via: SIP/2.0/UDP 217.10.79.9;branch=z9hG4bKe243.d6698885.1
    Via: SIP/2.0/UDP 195.158.1xx.xxx:5060;branch=z9hG4bK4b6f4e2e1bab1746547e7dc33ac3b22e.0
    Via: SIP/2.0/UDP 192.168.0.121:2054;rport=2054;branch=z9hG4bK-rw8c3ien12j4;received=192.168.0.121
    From: "Name" <sip:ID@sipgate.de>;tag=ed5gt58tmq
    To: "Name" <sip:ID@sipgate.de>
    Call-ID: 3c290780d1f6-owjjvk4fdo3g@snom360
    CSeq: 1 PUBLISH
    Max-Forwards: 67
    Event: proxy-config
    Content-Type: application/text
    Content-Length: 0
    
    Sent to udp:192.168.0.1:5060 at 30/5/2005 16:57:56:950 (735 bytes):
    SIP/2.0 482 Loop Detected
    Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bKe4d710937f5647058dfcd7b47082b46d.0
    Via: SIP/2.0/UDP 217.10.79.9;branch=z9hG4bKe243.d6698885.1
    Via: SIP/2.0/UDP 195.158.1xx.xxx:5060;branch=z9hG4bK4b6f4e2e1bab1746547e7dc33ac3b22e.0
    Via: SIP/2.0/UDP 192.168.0.121:2054;rport=2054;branch=z9hG4bK-rw8c3ien12j4;received=192.168.0.121
    From: "Name" <sip:ID@sipgate.de>;tag=ed5gt58tmq
    To: "Name" <sip:ID@sipgate.de>;tag=mp2maqt346
    Call-ID: 3c290780d1f6-owjjvk4fdo3g@snom360
    CSeq: 1 PUBLISH
    Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO
    Allow-Events: talk, hold, refer
    Supported: timer, 100rel, replaces
    Content-Length: 0
    
    Received from udp:192.168.0.1:5060 at 30/5/2005 16:57:57:020 (465 bytes):
    SIP/2.0 405 Method Not Allowed
    Via: SIP/2.0/UDP 192.168.0.121:2054;branch=z9hG4bK-rw8c3ien12j4;received=192.168.0.121
    From: "Name" <sip:ID@sipgate.de>;tag=ed5gt58tmq
    To: "Name" <sip:ID@sipgate.de>;tag=as52859eb6
    Call-ID: 3c290780d1f6-owjjvk4fdo3g@snom360
    CSeq: 1 PUBLISH
    User-Agent: sipgate voicemail (asterisk)
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
    Contact: 
    Accept: application/sdp
    Content-Length: 0
    
    Sent to udp:217.10.79.9:5060 at 30/5/2005 16:57:57:170 (385 bytes):
    PUBLISH sip:ID@sipgate.de SIP/2.0
    Via: SIP/2.0/UDP 192.168.0.121:2054;branch=z9hG4bK-ndjabkdzv53r;rport
    From: "Name" <sip:ID@sipgate.de>;tag=xw3bi666zt
    To: "Name" <sip:ID@sipgate.de>
    Call-ID: 3c2907812710-skwq4t8e5p71@snom360
    CSeq: 1 PUBLISH
    Max-Forwards: 70
    Event: proxy-config
    Content-Type: application/text
    Content-Length: 0
    
    Received from udp:192.168.0.1:5060 at 30/5/2005 16:57:57:240 (730 bytes):
    PUBLISH sip:ID@192.168.0.121:2054;line=xlxlhzi1 SIP/2.0
    Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bKb8b232193b04744e8dfcd7b47082b46d.0
    Record-Route: <sip:ID@217.10.79.9;ftag=xw3bi666zt;lr=on>
    Via: SIP/2.0/UDP 217.10.79.9;branch=z9hG4bK82ab.fd25a905.1
    Via: SIP/2.0/UDP 195.158.1xx.xxx:5060;branch=z9hG4bKb18cf511fb5e18c2547e7dc33ac3b22e.0
    Via: SIP/2.0/UDP 192.168.0.121:2054;rport=2054;branch=z9hG4bK-ndjabkdzv53r;received=192.168.0.121
    From: "Name" <sip:ID@sipgate.de>;tag=xw3bi666zt
    To: "Name" <sip:ID@sipgate.de>
    Call-ID: 3c2907812710-skwq4t8e5p71@snom360
    CSeq: 1 PUBLISH
    Max-Forwards: 67
    Event: proxy-config
    Content-Type: application/text
    Content-Length: 0
    
    Sent to udp:192.168.0.1:5060 at 30/5/2005 16:57:57:250 (735 bytes):
    SIP/2.0 482 Loop Detected
    Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bKb8b232193b04744e8dfcd7b47082b46d.0
    Via: SIP/2.0/UDP 217.10.79.9;branch=z9hG4bK82ab.fd25a905.1
    Via: SIP/2.0/UDP 195.158.1xx.xxx:5060;branch=z9hG4bKb18cf511fb5e18c2547e7dc33ac3b22e.0
    Via: SIP/2.0/UDP 192.168.0.121:2054;rport=2054;branch=z9hG4bK-ndjabkdzv53r;received=192.168.0.121
    From: "Name" <sip:ID@sipgate.de>;tag=xw3bi666zt
    To: "Name" <sip:ID@sipgate.de>;tag=fkgu91w6wu
    Call-ID: 3c2907812710-skwq4t8e5p71@snom360
    CSeq: 1 PUBLISH
    Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO
    Allow-Events: talk, hold, refer
    Supported: timer, 100rel, replaces
    Content-Length: 0
    
    Received from udp:192.168.0.1:5060 at 30/5/2005 16:57:57:310 (465 bytes):
    SIP/2.0 405 Method Not Allowed
    Via: SIP/2.0/UDP 192.168.0.121:2054;branch=z9hG4bK-ndjabkdzv53r;received=192.168.0.121
    From: "Name" <sip:ID@sipgate.de>;tag=xw3bi666zt
    To: "Name" <sip:ID@sipgate.de>;tag=as3b5c7ba8
    Call-ID: 3c2907812710-skwq4t8e5p71@snom360
    CSeq: 1 PUBLISH
    User-Agent: sipgate voicemail (asterisk)
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
    Contact: 
    Accept: application/sdp
    Content-Length: 0
    
    Sent to udp:217.10.79.9:5060 at 30/5/2005 16:57:57:370 (385 bytes):
    PUBLISH sip:ID@sipgate.de SIP/2.0
    Via: SIP/2.0/UDP 192.168.0.121:2054;branch=z9hG4bK-xmtbjqpcwjoc;rport
    From: "Name" <sip:ID@sipgate.de>;tag=4rwxm63dqj
    To: "Name" <sip:ID@sipgate.de>
    Call-ID: 3c29078157e4-asgceezz2dic@snom360
    CSeq: 1 PUBLISH
    Max-Forwards: 70
    Event: proxy-config
    Content-Type: application/text
    Content-Length: 0
    
    Received from udp:192.168.0.1:5060 at 30/5/2005 16:57:57:440 (730 bytes):
    PUBLISH sip:ID@192.168.0.121:2054;line=xlxlhzi1 SIP/2.0
    Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bKf6e6b863a05068868dfcd7b47082b46d.0
    Record-Route: <sip:ID@217.10.79.9;ftag=4rwxm63dqj;lr=on>
    Via: SIP/2.0/UDP 217.10.79.9;branch=z9hG4bK1e7c.090bf9e2.1
    Via: SIP/2.0/UDP 195.158.1xx.xxx:5060;branch=z9hG4bK3fe779e5a151aa30547e7dc33ac3b22e.0
    Via: SIP/2.0/UDP 192.168.0.121:2054;rport=2054;branch=z9hG4bK-xmtbjqpcwjoc;received=192.168.0.121
    From: "Name" <sip:ID@sipgate.de>;tag=4rwxm63dqj
    To: "Name" <sip:ID@sipgate.de>
    Call-ID: 3c29078157e4-asgceezz2dic@snom360
    CSeq: 1 PUBLISH
    Max-Forwards: 67
    Event: proxy-config
    Content-Type: application/text
    Content-Length: 0
    
    Sent to udp:192.168.0.1:5060 at 30/5/2005 16:57:57:450 (735 bytes):
    SIP/2.0 482 Loop Detected
    Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bKf6e6b863a05068868dfcd7b47082b46d.0
    Via: SIP/2.0/UDP 217.10.79.9;branch=z9hG4bK1e7c.090bf9e2.1
    Via: SIP/2.0/UDP 195.158.1xx.xxx:5060;branch=z9hG4bK3fe779e5a151aa30547e7dc33ac3b22e.0
    Via: SIP/2.0/UDP 192.168.0.121:2054;rport=2054;branch=z9hG4bK-xmtbjqpcwjoc;received=192.168.0.121
    From: "Name" <sip:ID@sipgate.de>;tag=4rwxm63dqj
    To: "Name" <sip:ID@sipgate.de>;tag=66rux4co8j
    Call-ID: 3c29078157e4-asgceezz2dic@snom360
    CSeq: 1 PUBLISH
    Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO
    Allow-Events: talk, hold, refer
    Supported: timer, 100rel, replaces
    Content-Length: 0
    
    Received from udp:192.168.0.1:5060 at 30/5/2005 16:57:57:540 (465 bytes):
    SIP/2.0 405 Method Not Allowed
    Via: SIP/2.0/UDP 192.168.0.121:2054;branch=z9hG4bK-xmtbjqpcwjoc;received=192.168.0.121
    From: "Name" <sip:ID@sipgate.de>;tag=4rwxm63dqj
    To: "Name" <sip:ID@sipgate.de>;tag=as4a9dec60
    Call-ID: 3c29078157e4-asgceezz2dic@snom360
    CSeq: 1 PUBLISH
    User-Agent: sipgate voicemail (asterisk)
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
    Contact: 
    Accept: application/sdp
    Content-Length: 0
    
    Sent to udp:217.10.79.9:5060 at 30/5/2005 16:57:57:620 (385 bytes):
    PUBLISH sip:ID@sipgate.de SIP/2.0
    Via: SIP/2.0/UDP 192.168.0.121:2054;branch=z9hG4bK-kivxu05zbnb5;rport
    From: "Name" <sip:ID@sipgate.de>;tag=rmobmo3ujp
    To: "Name" <sip:ID@sipgate.de>
    Call-ID: 3c29078194ed-hctgsmef4ksf@snom360
    CSeq: 1 PUBLISH
    Max-Forwards: 70
    Event: proxy-config
    Content-Type: application/text
    Content-Length: 0
    
    Received from udp:192.168.0.1:5060 at 30/5/2005 16:57:57:700 (730 bytes):
    PUBLISH sip:ID@192.168.0.121:2054;line=xlxlhzi1 SIP/2.0
    Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK74c9ef8a473f72f78dfcd7b47082b46d.0
    Record-Route: <sip:ID@217.10.79.9;ftag=rmobmo3ujp;lr=on>
    Via: SIP/2.0/UDP 217.10.79.9;branch=z9hG4bKc0be.bfd47cd6.1
    Via: SIP/2.0/UDP 195.158.1xx.xxx:5060;branch=z9hG4bK2b662642caa09eef547e7dc33ac3b22e.0
    Via: SIP/2.0/UDP 192.168.0.121:2054;rport=2054;branch=z9hG4bK-kivxu05zbnb5;received=192.168.0.121
    From: "Name" <sip:ID@sipgate.de>;tag=rmobmo3ujp
    To: "Name" <sip:ID@sipgate.de>
    Call-ID: 3c29078194ed-hctgsmef4ksf@snom360
    CSeq: 1 PUBLISH
    Max-Forwards: 67
    Event: proxy-config
    Content-Type: application/text
    Content-Length: 0
    
    Sent to udp:192.168.0.1:5060 at 30/5/2005 16:57:57:700 (735 bytes):
    SIP/2.0 482 Loop Detected
    Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK74c9ef8a473f72f78dfcd7b47082b46d.0
    Via: SIP/2.0/UDP 217.10.79.9;branch=z9hG4bKc0be.bfd47cd6.1
    Via: SIP/2.0/UDP 195.158.1xx.xxx:5060;branch=z9hG4bK2b662642caa09eef547e7dc33ac3b22e.0
    Via: SIP/2.0/UDP 192.168.0.121:2054;rport=2054;branch=z9hG4bK-kivxu05zbnb5;received=192.168.0.121
    From: "Name" <sip:ID@sipgate.de>;tag=rmobmo3ujp
    To: "Name" <sip:ID@sipgate.de>;tag=rvtenwa2ox
    Call-ID: 3c29078194ed-hctgsmef4ksf@snom360
    CSeq: 1 PUBLISH
    Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO
    Allow-Events: talk, hold, refer
    Supported: timer, 100rel, replaces
    Content-Length: 0
    
    Received from udp:192.168.0.1:5060 at 30/5/2005 16:57:57:760 (465 bytes):
    SIP/2.0 405 Method Not Allowed
    Via: SIP/2.0/UDP 192.168.0.121:2054;branch=z9hG4bK-kivxu05zbnb5;received=192.168.0.121
    From: "Name" <sip:ID@sipgate.de>;tag=rmobmo3ujp
    To: "Name" <sip:ID@sipgate.de>;tag=as579614a4
    Call-ID: 3c29078194ed-hctgsmef4ksf@snom360
    CSeq: 1 PUBLISH
    User-Agent: sipgate voicemail (asterisk)
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
    Contact: 
    Accept: application/sdp
    Content-Length: 0
    
    Sent to udp:217.10.79.9:5060 at 30/5/2005 16:57:57:820 (385 bytes):
    PUBLISH sip:ID@sipgate.de SIP/2.0
    Via: SIP/2.0/UDP 192.168.0.121:2054;branch=z9hG4bK-jyky3ydffgqd;rport
    From: "Name" <sip:ID@sipgate.de>;tag=jz32u6qr1w
    To: "Name" <sip:ID@sipgate.de>
    Call-ID: 3c290781c5c1-jbebi8yrthna@snom360
    CSeq: 1 PUBLISH
    Max-Forwards: 70
    Event: proxy-config
    Content-Type: application/text
    Content-Length: 0
    
    Received from udp:192.168.0.1:5060 at 30/5/2005 16:57:57:890 (730 bytes):
    PUBLISH sip:ID@192.168.0.121:2054;line=xlxlhzi1 SIP/2.0
    Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK13ccf995cb9f2e828dfcd7b47082b46d.0
    Record-Route: <sip:ID@217.10.79.9;ftag=jz32u6qr1w;lr=on>
    Via: SIP/2.0/UDP 217.10.79.9;branch=z9hG4bK4fbe.dcb02006.1
    Via: SIP/2.0/UDP 195.158.1xx.xxx:5060;branch=z9hG4bK3b851b191c1922a1547e7dc33ac3b22e.0
    Via: SIP/2.0/UDP 192.168.0.121:2054;rport=2054;branch=z9hG4bK-jyky3ydffgqd;received=192.168.0.121
    From: "Name" <sip:ID@sipgate.de>;tag=jz32u6qr1w
    To: "Name" <sip:ID@sipgate.de>
    Call-ID: 3c290781c5c1-jbebi8yrthna@snom360
    CSeq: 1 PUBLISH
    Max-Forwards: 67
    Event: proxy-config
    Content-Type: application/text
    Content-Length: 0
    
    Sent to udp:192.168.0.1:5060 at 30/5/2005 16:57:57:900 (735 bytes):
    SIP/2.0 482 Loop Detected
    Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK13ccf995cb9f2e828dfcd7b47082b46d.0
    Via: SIP/2.0/UDP 217.10.79.9;branch=z9hG4bK4fbe.dcb02006.1
    Via: SIP/2.0/UDP 195.158.1xx.xxx:5060;branch=z9hG4bK3b851b191c1922a1547e7dc33ac3b22e.0
    Via: SIP/2.0/UDP 192.168.0.121:2054;rport=2054;branch=z9hG4bK-jyky3ydffgqd;received=192.168.0.121
    From: "Name" <sip:ID@sipgate.de>;tag=jz32u6qr1w
    To: "Name" <sip:ID@sipgate.de>;tag=8q5xfq31a2
    Call-ID: 3c290781c5c1-jbebi8yrthna@snom360
    CSeq: 1 PUBLISH
    Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO
    Allow-Events: talk, hold, refer
    Supported: timer, 100rel, replaces
    Content-Length: 0
    
    Received from udp:192.168.0.1:5060 at 30/5/2005 16:57:57:990 (465 bytes):
    SIP/2.0 405 Method Not Allowed
    Via: SIP/2.0/UDP 192.168.0.121:2054;branch=z9hG4bK-jyky3ydffgqd;received=192.168.0.121
    From: "Name" <sip:ID@sipgate.de>;tag=jz32u6qr1w
    To: "Name" <sip:ID@sipgate.de>;tag=as23953ccc
    Call-ID: 3c290781c5c1-jbebi8yrthna@snom360
    CSeq: 1 PUBLISH
    User-Agent: sipgate voicemail (asterisk)
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
    Contact: 
    Accept: application/sdp
    Content-Length: 0
    
    Sent to udp:217.10.79.9:5060 at 30/5/2005 16:57:58:220 (1073 bytes):
    INVITE sip:angerufeneNr@sipgate.de;user=phone SIP/2.0
    Via: SIP/2.0/UDP 192.168.0.121:2054;branch=z9hG4bK-d3hwd8pz6hk6;rport
    From: "Name" <sip:ID@sipgate.de>;tag=6qqy56o3wd
    To: <sip:angerufeneNr@sipgate.de;user=phone>
    Call-ID: 3c2907823345-80gfa8s8rrs9@snom360
    CSeq: 1 INVITE
    Max-Forwards: 70
    Contact: <sip:ID@192.168.0.121:2054;line=xlxlhzi1>
    P-Key-Flags: resolution="31x13", keys="4"
    User-Agent: snom360/3.60i
    Accept: application/sdp
    Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO
    Allow-Events: talk, hold, refer
    Supported: timer, 100rel, replaces
    Session-Expires: 3600
    Content-Type: application/sdp
    Content-Length: 368
    
    v=0
    o=root 666282267 666282267 IN IP4 192.168.0.121
    s=call
    c=IN IP4 192.168.0.121
    t=0 0
    m=audio 62936 RTP/AVP 0 8 9 2 3 18 4 101
    a=rtpmap:0 pcmu/8000
    a=rtpmap:8 pcma/8000
    a=rtpmap:9 g722/8000
    a=rtpmap:2 g726-32/8000
    a=rtpmap:3 gsm/8000
    a=rtpmap:18 g729/8000
    a=rtpmap:4 g723/8000
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-15
    a=ptime:20
    a=sendrecv
    
    Received from udp:192.168.0.1:5060 at 30/5/2005 16:57:58:340 (355 bytes):
    SIP/2.0 100 Trying
    Via: SIP/2.0/UDP 192.168.0.121:2054;branch=z9hG4bK-d3hwd8pz6hk6;received=192.168.0.121;rport=2054
    From: "Name" <sip:ID@sipgate.de>;tag=6qqy56o3wd
    Call-ID: 3c2907823345-80gfa8s8rrs9@snom360
    CSeq: 1 INVITE
    Server: Intertex ix66-3-1-5---rel-3-15 
    To: <sip:angerufeneNr@sipgate.de;user=phone>
    Content-Length: 0
    
    Received from udp:192.168.0.1:5060 at 30/5/2005 16:57:58:350 (709 bytes):
    SIP/2.0 407 Proxy Authentication Required
    Via: SIP/2.0/UDP 192.168.0.121:2054;rport=2054;branch=z9hG4bK-d3hwd8pz6hk6;received=192.168.0.121
    From: "Name" <sip:ID@sipgate.de>;tag=6qqy56o3wd
    To: <sip:angerufeneNr@sipgate.de;user=phone>;tag=b11cb9bb270104b49a99a995b8c68544.ee9e
    Call-ID: 3c2907823345-80gfa8s8rrs9@snom360
    CSeq: 1 INVITE
    Proxy-Authenticate: Digest realm="sipgate.de", nonce="429b2b23ca3c710e1e3473fbe379d969ec2bcdaf"
    Server: sipgate ser
    Content-Length: 0
    Warning: 392 217.10.79.9:5060 "Noisy feedback tells: pid=6746 req_src_ip=195.158.1xx.xxx req_src_port=5060 in_uri=sip:angerufeneNr@sipgate.de;user=phone out_uri=sip:angerufeneNr@sipgate.de;user=phone via_cnt==2"
    
    Sent to udp:217.10.79.9:5060 at 30/5/2005 16:57:58:360 (431 bytes):
    ACK sip:angerufeneNr@sipgate.de;user=phone SIP/2.0
    Via: SIP/2.0/UDP 192.168.0.121:2054;branch=z9hG4bK-d3hwd8pz6hk6;rport
    From: "Name" <sip:ID@sipgate.de>;tag=6qqy56o3wd
    To: <sip:angerufeneNr@sipgate.de;user=phone>;tag=b11cb9bb270104b49a99a995b8c68544.ee9e
    Call-ID: 3c2907823345-80gfa8s8rrs9@snom360
    CSeq: 1 ACK
    Max-Forwards: 70
    Contact: <sip:ID@192.168.0.121:2054;line=xlxlhzi1>
    Content-Length: 0
    
    Sent to udp:217.10.79.9:5060 at 30/5/2005 16:57:58:370 (1291 bytes):
    INVITE sip:angerufeneNr@sipgate.de;user=phone SIP/2.0
    Via: SIP/2.0/UDP 192.168.0.121:2054;branch=z9hG4bK-eepmp0yjet58;rport
    From: "Name" <sip:ID@sipgate.de>;tag=6qqy56o3wd
    To: <sip:angerufeneNr@sipgate.de;user=phone>
    Call-ID: 3c2907823345-80gfa8s8rrs9@snom360
    CSeq: 2 INVITE
    Max-Forwards: 70
    Contact: <sip:ID@192.168.0.121:2054;line=xlxlhzi1>
    P-Key-Flags: resolution="31x13", keys="4"
    User-Agent: snom360/3.60i
    Accept: application/sdp
    Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO
    Allow-Events: talk, hold, refer
    Supported: timer, 100rel, replaces
    Session-Expires: 3600
    Proxy-Authorization: Digest username="ID",realm="sipgate.de",nonce="429b2b23ca3c710e1e3473fbe379d969ec2bcdaf",uri="sip:angerufeneNr@sipgate.de;user=phone",response="106cbd2b34de762593182d31c0fc1675",algorithm=md5
    Content-Type: application/sdp
    Content-Length: 368
    
    v=0
    o=root 666282267 666282267 IN IP4 192.168.0.121
    s=call
    c=IN IP4 192.168.0.121
    t=0 0
    m=audio 62936 RTP/AVP 0 8 9 2 3 18 4 101
    a=rtpmap:0 pcmu/8000
    a=rtpmap:8 pcma/8000
    a=rtpmap:9 g722/8000
    a=rtpmap:2 g726-32/8000
    a=rtpmap:3 gsm/8000
    a=rtpmap:18 g729/8000
    a=rtpmap:4 g723/8000
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-15
    a=ptime:20
    a=sendrecv
    
    Received from udp:192.168.0.1:5060 at 30/5/2005 16:57:58:430 (355 bytes):
    SIP/2.0 100 Trying
    Via: SIP/2.0/UDP 192.168.0.121:2054;branch=z9hG4bK-eepmp0yjet58;received=192.168.0.121;rport=2054
    From: "Name" <sip:ID@sipgate.de>;tag=6qqy56o3wd
    Call-ID: 3c2907823345-80gfa8s8rrs9@snom360
    CSeq: 2 INVITE
    Server: Intertex ix66-3-1-5---rel-3-15 
    To: <sip:angerufeneNr@sipgate.de;user=phone>
    Content-Length: 0
    
    Received from udp:192.168.0.1:5060 at 30/5/2005 16:57:59:700 (1166 bytes):
    SIP/2.0 200 OK
    Session-Expires: 3600;refresher=uac
    Require: timer
    Via: SIP/2.0/UDP 192.168.0.121:2054;branch=z9hG4bK-eepmp0yjet58;received=192.168.0.121
    Record-Route: <sip:49angerufeneNR@217.10.79.8;ftag=6qqy56o3wd;lr=on>
    Record-Route: <sip:angerufeneNr@217.10.79.9;ftag=6qqy56o3wd;lr=on>
    Record-Route: <sip:43b26eef@192.168.0.1;lr=true>
    From: "Name" <sip:ID@sipgate.de>;tag=6qqy56o3wd
    To: <sip:angerufeneNr@sipgate.de;user=phone>;tag=as0cfdafb9
    Call-ID: 3c2907823345-80gfa8s8rrs9@snom360
    CSeq: 2 INVITE
    User-Agent: Asterisk PBX
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
    Contact: <sip:49angerufeneNR@217.10.67.7>
    Content-Type: application/sdp
    Content-Length: 465
    
    v=0
    o=root 21751 21751 IN IP4 217.10.67.7
    s=session
    c=IN IP4 217.10.67.7
    t=0 0
    m=audio 12492 RTP/AVP 8 0 3 97 18 2 4 5 110 7 10 101
    a=rtpmap:8 PCMA/8000
    a=rtpmap:0 PCMU/8000
    a=rtpmap:3 GSM/8000
    a=rtpmap:97 iLBC/8000
    a=rtpmap:18 G729/8000
    a=rtpmap:2 G726-32/8000
    a=rtpmap:4 G723/8000
    a=rtpmap:5 DVI4/8000
    a=rtpmap:110 speex/8000
    a=rtpmap:7 LPC/8000
    a=rtpmap:10 L16/8000
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-16
    a=silenceSupp:off - - - -
    
    Sent to udp:192.168.0.1:5060 at 30/5/2005 16:57:59:710 (559 bytes):
    ACK sip:49angerufeneNR@217.10.67.7 SIP/2.0
    Via: SIP/2.0/UDP 192.168.0.121:2054;branch=z9hG4bK-sd95amsb26jr;rport
    Route: <sip:43b26eef@192.168.0.1;lr=true>
    Route: <sip:angerufeneNr@217.10.79.9;ftag=6qqy56o3wd;lr=on>
    Route: <sip:49angerufeneNR@217.10.79.8;ftag=6qqy56o3wd;lr=on>
    From: "Name" <sip:ID@sipgate.de>;tag=6qqy56o3wd
    To: <sip:angerufeneNr@sipgate.de;user=phone>;tag=as0cfdafb9
    Call-ID: 3c2907823345-80gfa8s8rrs9@snom360
    CSeq: 2 ACK
    Max-Forwards: 70
    Contact: <sip:ID@192.168.0.121:2054;line=xlxlhzi1>
    Content-Length: 0
    
    Received from udp:192.168.0.1:5060 at 30/5/2005 16:58:02:320 (1166 bytes):
    SIP/2.0 200 OK
    Session-Expires: 3600;refresher=uac
    Require: timer
    Via: SIP/2.0/UDP 192.168.0.121:2054;branch=z9hG4bK-eepmp0yjet58;received=192.168.0.121
    Record-Route: <sip:49angerufeneNR@217.10.79.8;ftag=6qqy56o3wd;lr=on>
    Record-Route: <sip:angerufeneNr@217.10.79.9;ftag=6qqy56o3wd;lr=on>
    Record-Route: <sip:43b26eef@192.168.0.1;lr=true>
    From: "Name" <sip:ID@sipgate.de>;tag=6qqy56o3wd
    To: <sip:angerufeneNr@sipgate.de;user=phone>;tag=as0cfdafb9
    Call-ID: 3c2907823345-80gfa8s8rrs9@snom360
    CSeq: 2 INVITE
    User-Agent: Asterisk PBX
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
    Contact: <sip:49angerufeneNR@217.10.67.7>
    Content-Type: application/sdp
    Content-Length: 465
    
    v=0
    o=root 21751 21751 IN IP4 217.10.67.7
    s=session
    c=IN IP4 217.10.67.7
    t=0 0
    m=audio 12492 RTP/AVP 8 0 3 97 18 2 4 5 110 7 10 101
    a=rtpmap:8 PCMA/8000
    a=rtpmap:0 PCMU/8000
    a=rtpmap:3 GSM/8000
    a=rtpmap:97 iLBC/8000
    a=rtpmap:18 G729/8000
    a=rtpmap:2 G726-32/8000
    a=rtpmap:4 G723/8000
    a=rtpmap:5 DVI4/8000
    a=rtpmap:110 speex/8000
    a=rtpmap:7 LPC/8000
    a=rtpmap:10 L16/8000
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-16
    a=silenceSupp:off - - - -
    
    Sent to udp:192.168.0.1:5060 at 30/5/2005 16:58:02:320 (559 bytes):
    ACK sip:49angerufeneNR@217.10.67.7 SIP/2.0
    Via: SIP/2.0/UDP 192.168.0.121:2054;branch=z9hG4bK-sd95amsb26jr;rport
    Route: <sip:43b26eef@192.168.0.1;lr=true>
    Route: <sip:angerufeneNr@217.10.79.9;ftag=6qqy56o3wd;lr=on>
    Route: <sip:49angerufeneNR@217.10.79.8;ftag=6qqy56o3wd;lr=on>
    From: "Name" <sip:ID@sipgate.de>;tag=6qqy56o3wd
    To: <sip:angerufeneNr@sipgate.de;user=phone>;tag=as0cfdafb9
    Call-ID: 3c2907823345-80gfa8s8rrs9@snom360
    CSeq: 2 ACK
    Max-Forwards: 70
    Contact: <sip:ID@192.168.0.121:2054;line=xlxlhzi1>
    Content-Length: 0
    
    Received from udp:192.168.0.1:5060 at 30/5/2005 16:58:03:270 (1022 bytes):
    BYE sip:ID@192.168.0.121:2054;line=xlxlhzi1 SIP/2.0
    Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bKc42696836055dd02772689851d22835b.0
    Record-Route: <sip:ekUaDjL6oxZYtJcLF-ex1XZtbQ5WCAfZe2dd48mijAmxuRW_4esKVGFVUh4fx41LTPA76Y0cg98GlYBu3Z6Bw8g..@217.10.79.9;ftag=as0cfdafb9;lr=on>
    Max-Forwards: 8
    Record-Route: <sip:ekUaDjL6oxZYtJcLF-ex1XZtbQ5WCAfZe2dd48mijAmxuRW_4esKVGFVUh4fx41LTPA76Y0cg98GlYBu3Z6Bw8g..@217.10.79.8;ftag=as0cfdafb9;lr=on>
    Via: SIP/2.0/UDP 217.10.79.9;branch=z9hG4bK1557.7cac1b83.0
    Via: SIP/2.0/UDP 217.10.79.8;branch=z9hG4bK1557.3a385cb7.0
    Via: SIP/2.0/UDP 217.10.67.7:5060;branch=z9hG4bK203873ff;rport=5060
    Route: <sip:ID@192.168.0.121:2054;line=xlxlhzi1>
    From: <sip:angerufeneNr@sipgate.de;user=phone>;tag=as0cfdafb9
    To: "Name" <sip:ID@sipgate.de>;tag=6qqy56o3wd
    Contact: <sip:e0QPz8Dr0pLYFy8c7EedTNRxgwPEsR70C8fv59pvFp99c_76zWio0mKghS3zWpOyb@192.168.0.1>
    Call-ID: 3c2907823345-80gfa8s8rrs9@snom360
    CSeq: 102 BYE
    User-Agent: Asterisk PBX
    Content-Length: 0
    
    Sent to udp:192.168.0.1:5060 at 30/5/2005 16:58:03:270 (582 bytes):
    SIP/2.0 200 OK
    Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bKc42696836055dd02772689851d22835b.0
    Via: SIP/2.0/UDP 217.10.79.9;branch=z9hG4bK1557.7cac1b83.0
    Via: SIP/2.0/UDP 217.10.79.8;branch=z9hG4bK1557.3a385cb7.0
    Via: SIP/2.0/UDP 217.10.67.7:5060;branch=z9hG4bK203873ff;rport=5060
    From: <sip:angerufeneNr@sipgate.de;user=phone>;tag=as0cfdafb9
    To: "Name" <sip:ID@sipgate.de>;tag=6qqy56o3wd
    Call-ID: 3c2907823345-80gfa8s8rrs9@snom360
    CSeq: 102 BYE
    Contact: <sip:ID@192.168.0.121:2054;line=xlxlhzi1>
    User-Agent: snom360/3.60i
    Content-Length: 0
    
     
  7. Swiss62

    Swiss62 Neuer User

    Registriert seit:
    5 Juni 2004
    Beiträge:
    25
    Zustimmungen:
    0
    Punkte für Erfolge:
    0
    Habe auch ein Snom 360 und funktioniert ohne Probleme.
    Firmware 360i.
    Hatte aber zuerst auch das Problem, dass nur 0800 und intern ging bei meinem UK Account.Aber keine kostenpflichtigen Gespräche.
    Nach einer kurzen Mitteilung an den Support war das aber gefixt.
    Man beachte Absatz 3:

    Why can I call other sipgate numbers, but not pstn lines?

    There can be different reasons for this, here's what you can check:


    1. Do you have credit on your account? If the call is chargeable and you don't have sufficient credit to place the call, the call won't go through.


    2. Do you have the CLID (caller ID) in your device activated and containing your SIP ID? If caller ID isn't activated, calls to pstn lines will not go through. On the Grandstream devices, this can be found at the bottom (version 5.16) of the configuration page.


    3. Lost pstn binding? Occasionally we may need to reset a binding to our pstn gateway (this is rare but it does happen). If everything worked fine before, and you have sufficient credit and still can't connect to pstn lines, drop a note to support and we will reaffirm your pstn connection. Please make sure your voicemail is activated before sending the email to support.
     
  8. der_Gersthofer

    der_Gersthofer Admin-Team

    Registriert seit:
    17 Apr. 2004
    Beiträge:
    3,585
    Zustimmungen:
    0
    Punkte für Erfolge:
    36

    Möglicherweise wird also die ID nicht wirklich richtig übertragen...
     
  9. Swiss62

    Swiss62 Neuer User

    Registriert seit:
    5 Juni 2004
    Beiträge:
    25
    Zustimmungen:
    0
    Punkte für Erfolge:
    0
    Ich habe eher an das gedacht:

    3. Lost pstn binding? Occasionally we may need to reset a binding to our pstn gateway (this is rare but it does happen). If everything worked fine before, and you have sufficient credit and still can't connect to pstn lines, drop a note to support and we will reaffirm your pstn connection. Please make sure your voicemail is activated before sending the email to support.

    Gratis Gespräche gehen trotzdem, obwohl das ja auch PSTN ist.
    War auf jeden Fall bei mir der Fall.
    Nur eben Gespräche auf normale Anschlüsse nicht.
    Schon mal an Support geschrieben?
     
  10. der_Gersthofer

    der_Gersthofer Admin-Team

    Registriert seit:
    17 Apr. 2004
    Beiträge:
    3,585
    Zustimmungen:
    0
    Punkte für Erfolge:
    36
    Ja
     
  11. Swiss62

    Swiss62 Neuer User

    Registriert seit:
    5 Juni 2004
    Beiträge:
    25
    Zustimmungen:
    0
    Punkte für Erfolge:
    0
    Also da Du ja 5 Sterne hast und ich keinen, (lese in der Regel nur mit), möchte ich Dir nicht weiter kluge Ratschläge erteilen.
    Aber da das Snom 360 bei mir mit Firmware 360i und sipgate läuft, kann es ja eigentlich nicht an Tel und Firmware liegen.
    Was hat denn Sipgate Support dazu gemeint?
     
  12. der_Gersthofer

    der_Gersthofer Admin-Team

    Registriert seit:
    17 Apr. 2004
    Beiträge:
    3,585
    Zustimmungen:
    0
    Punkte für Erfolge:
    36
    Gar nichts, noch keine Antwort. Sehr merkwürdig ist es aber doch, dass mehrere User das Problem haben und andere wiederum nicht. Mit einem Netgear TA612V geht es aber reibungslos.


    [GEKLÄRT]
    Ursache geklärt, wenn auch noch nicht durch Sipgate gelöst
    http://www.ip-phone-forum.de/forum/viewtopic.php?t=18044