cfive
Free User
- Joined
- Aug 20, 2009
- Messages
- 278
- Reaction score
- 5
Hi,
v9 SP4 and SP5.
Extension belongs to ring group.
Extension has call forwarding Exception configured (specific hours, or, Outside of business hours - tried both) to forward to external number.
When the ring group receives a call, *anytime, not only during specific hours*:
The ring group extensions get notified and start to ring.
Once the extension with the exception rings, it transfers the call to the external number.
The server activity log shows below:
This ring group 801 has 2 extensions, 106 and 107 - 106 has the Exception configured. Does the call to extension 106 not look odd?
17:18:22.669 [MS210007] C:32.3:Answer provided. Connection(by pass mode): 192.168.16.51:4872(4873)
17:18:22.668 [MS210001] C:32.1:Answer received. RTP connection[unsecure]: 192.168.16.51:4872(4873)
17:18:22.667 Remote SDP is set for legC:32.1
17:18:22.614 [CM503003]: Call(32): Call to sip:[email protected] has failed; Cause: 487 Request Cancelled; from IP:192.168.16.36:5060
17:18:22.435 [CM503007]: Call(32): Device joined: sip:[email protected]:5062
17:18:22.433 [MS210006] C:32.1:Offer provided. Connection(by pass mode): 192.168.16.51:4874(4875)
17:18:22.429 [MS210000] C:32.3:Offer received. RTP connection: 192.168.16.51:4874(4875)
17:18:22.427 Remote SDP is set for legC:32.3
17:18:22.427 [CM505002]: Gateway:[Patton1] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Patton SN4114 JO EUI 00A0BA051552 R5.4 2009-11-18 H323 SIP FXS FXO M5T SIP Stack/4.0.28.28] PBX contact: [sip:[email protected]:5060]
17:18:22.426 [CM503002]: Call(32): Alerting sip:[email protected]:5062
17:18:19.716 [CM505001]: Ext.107: Device info: Device Identified: [Man: Polycom;Mod: SoundPoint IP series;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [PolycomSoundPointIP-SPIP_601-UA/3.1.3.0439] PBX contact: [sip:[email protected]:5060]
17:18:19.716 [CM503002]: Call(32): Alerting sip:[email protected]:5060
17:18:19.405 [CM503025]: Call(32): Calling RingAll801:1067297376@(Ln.10001@Patton1)107Ext.107@[Dev:sip:[email protected]:5060]
17:18:19.395 [CM503025]: Call(32): Calling RingAll801:1067297376@(Ln.10001@Patton1)107Ext.107@[Dev:sip:[email protected]:5062]
17:18:19.353 [CM503004]: Call(32): Route 1: RingAll801:1067297376@(Ln.10001@Patton1)107Ext.107@[Dev:sip:[email protected]:5062,Dev:sip:[email protected]:5060]
17:18:19.336 [CM503010]: Making route(s) to <sip:[email protected]:5060>
This makes the exceptions useless, because they kill the ring group.
Thanks, Les.
v9 SP4 and SP5.
Extension belongs to ring group.
Extension has call forwarding Exception configured (specific hours, or, Outside of business hours - tried both) to forward to external number.
When the ring group receives a call, *anytime, not only during specific hours*:
The ring group extensions get notified and start to ring.
Once the extension with the exception rings, it transfers the call to the external number.
The server activity log shows below:
This ring group 801 has 2 extensions, 106 and 107 - 106 has the Exception configured. Does the call to extension 106 not look odd?
17:18:22.669 [MS210007] C:32.3:Answer provided. Connection(by pass mode): 192.168.16.51:4872(4873)
17:18:22.668 [MS210001] C:32.1:Answer received. RTP connection[unsecure]: 192.168.16.51:4872(4873)
17:18:22.667 Remote SDP is set for legC:32.1
17:18:22.614 [CM503003]: Call(32): Call to sip:[email protected] has failed; Cause: 487 Request Cancelled; from IP:192.168.16.36:5060
17:18:22.435 [CM503007]: Call(32): Device joined: sip:[email protected]:5062
17:18:22.433 [MS210006] C:32.1:Offer provided. Connection(by pass mode): 192.168.16.51:4874(4875)
17:18:22.429 [MS210000] C:32.3:Offer received. RTP connection: 192.168.16.51:4874(4875)
17:18:22.427 Remote SDP is set for legC:32.3
17:18:22.427 [CM505002]: Gateway:[Patton1] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Patton SN4114 JO EUI 00A0BA051552 R5.4 2009-11-18 H323 SIP FXS FXO M5T SIP Stack/4.0.28.28] PBX contact: [sip:[email protected]:5060]
17:18:22.426 [CM503002]: Call(32): Alerting sip:[email protected]:5062
17:18:19.716 [CM505001]: Ext.107: Device info: Device Identified: [Man: Polycom;Mod: SoundPoint IP series;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [PolycomSoundPointIP-SPIP_601-UA/3.1.3.0439] PBX contact: [sip:[email protected]:5060]
17:18:19.716 [CM503002]: Call(32): Alerting sip:[email protected]:5060
17:18:19.405 [CM503025]: Call(32): Calling RingAll801:1067297376@(Ln.10001@Patton1)107Ext.107@[Dev:sip:[email protected]:5060]
17:18:19.395 [CM503025]: Call(32): Calling RingAll801:1067297376@(Ln.10001@Patton1)107Ext.107@[Dev:sip:[email protected]:5062]
17:18:19.353 [CM503004]: Call(32): Route 1: RingAll801:1067297376@(Ln.10001@Patton1)107Ext.107@[Dev:sip:[email protected]:5062,Dev:sip:[email protected]:5060]
17:18:19.336 [CM503010]: Making route(s) to <sip:[email protected]:5060>
This makes the exceptions useless, because they kill the ring group.
Thanks, Les.