No ma il Provider dietro il servizio Skype Connect viene visto (ovvero "è") come un qualunque altro SIP ITSP e dunque per esso valgono le regole di configurazione già note per questi ultimi.
Attenzione che HiPath 3000 V8 è stato certificato il 4 Dicembre 2010 e solo dalla Release 5 (V8 R5.f.h) in avanti per l'utilizzo con Skype Connect (quindi va usata anche una Release adeguata della HG1500/STMI2).
Saluti,
Kimera.
P.S.
Skype Connect Technical specifications:
- Protocol: SIP (RFC3261)
- Far End NAT traversal: NAP/T
- Privacy extensions: RFC3325
- IP transport: UDP and TCP/IP
- Authentication: DIGEST or IP Authentication SIP (These are requested for both REGISTER and INVITE)
- Registration: Automatic NAT detection and change of registration timers
- Channels: Maximum of 300 simultaneous calls
- Codecs: G.729 (Annex A and B) and G.711 ulaw/ALaw
- DTMF method: RFC2833
- Call type support: Skype Connect supports the following third party call control features when used in conjunction with a Skype Connect certified SIP-enabled PBX:
- Mid call codec change
- Re-INVITE for various third party call control features including Call Hold, Call Transfer, Park, Call Divert and other types of SIP-enabled PBX call types
- Call Diversion header for Call Originating Line Presentation (COLP)
- RFC3325 for P-Asserted-ID, Remote-Party-ID and Privacy:id based calls
- Number format: E.164 (country code and national number), international number format for all calls
- FAX: Skype does not support Fax or T.38
- Emergency calls: Skype does not support calls to emergency services.