Category:HowTo:Call Forwarding
From Snom User Wiki
Note: On snom3x0 phones this feature affects only the currently active SIP identity.
Contents |
Configuration on snom3x0 phones
Events
The following call forwarding events can be configured using the Phone User Interface, Web User Interface, or Auto Provisioning:
- Off: Call forwarding is deactivated by default.
- Always: Incoming calls are immediately forwarded to the "Always" target number
- Busy: Incoming calls are immediately forwarded when the phone is busy to the "Busy" target number Note: This feature will only work if Call Waiting is disabled.
- Time: Call forwarding to the "Timeout" target number is activated when the time (in seconds) entered has passed without the call having been answered.
SIP Trace
Call Forwarding Event "Always" has been activated on extB (2907) to extC (2908).
ExtA (2906) calls ExtB (2907)
Sent to udp...: INVITE sip:2907@ser;user=phone SIP/2.0 Via: ... From: <sip:2906@ser>;tag=8jbmt6uyae To: <sip:2907@ser;user=phone> Call-ID: 3c267129d25a-nxgouyz0hbhm CSeq: 1 INVITE Max-Forwards: 70 Contact: <sip:2906@192.168.9.3:1000;line=fnrzr7bp>;reg-id=1 ... User-Agent: snom370/7.3.10a ... Content-Type: application/sdp Content-Length: 450 ... Received from udp...: SIP/2.0 100 trying -- your call is important to us Via: ... From: <sip:2906@ser>;tag=8jbmt6uyae To: <sip:2907@ser;user=phone> Call-ID: 3c267129d25a-nxgouyz0hbhm CSeq: 1 INVITE Server: OpenSer Content-Length: 0
Call Forwarding on ExtB (2907)
Due to activated "Call Forwarding" ExtB (2907) sends the following message
Received from udp...: SIP/2.0 302 Moved Temporarily Via: ... ... From: <sip:2906@ser>... To: <sip:2907@ser;user=phone>... Call-ID: 3c267129d25a-nxgouyz0hbhm CSeq: 1 INVITE Contact: <sip:2908@ser;user=phone> Diversion: <sip:2907@192.168.5.193:2051;line=uw7mmqzi>;reason="unconditional" Content-Length: 0
where
- Contact- Header contains the call forwarding target number ExtC (2908) and
- Diversion- Header contains the Request-URI of the request prior to the diversion (ExtB = 2907) and the reason that the diversion occurred ("unconditional")
This is being acknowledged by extA (2906).
ExtA (2906) calls ExtC (2908)
From the Contact-Header (ExtC = 2908) ExtA retrieves the Request-URI to establish the call to. The Diversion- Header is included in the message:
Sent to udp...: INVITE sip:2908@ser SIP/2.0 Via: ... From: <sip:2906@ser>... To: sip:2908@ser... Call-ID: 3c26712e0ca0-277bggq3yblp CSeq: 1 INVITE Max-Forwards: 70 Contact: <sip:2906@192.168.9.3:1000;line=fnrzr7bp>;reg-id=1 ... Diversion: <sip:2907@192.168.5.193:2051;line=uw7mmqzi>;reason="unconditional" User-Agent: snom370/7.3.10a ... Content-Type: application/sdp Content-Length: 450 ... Received from udp...: SIP/2.0 100 trying -- your call is important to us Via: ... From: <sip:2906@ser>;tag=1vzevun4ns To: sip:2908@ser;user=phone Call-ID: 3c26712e0ca0-277bggq3yblp CSeq: 1 INVITE Server: OpenSer (1.1.0-notls (i386/linux)) Content-Length: 0 Received from udp...: SIP/2.0 180 Ringing Via: ... ... From: <sip:2906@ser>;tag=1vzevun4ns To: sip:2908@ser;user=phone;tag=n9p9qydq2n Call-ID: 3c26712e0ca0-277bggq3yblp CSeq: 1 INVITE Contact: <sip:2908@192.168.8.230:1025;line=dy1frf90>;reg-id=1 ...
This category currently contains no pages or media.
