1. I think I got sipviewer working so once I find that info, I'll let you know. but I can't imagine it would be this, since direct calls follow the rules correctly.
2. I'll check the staged dialing feature on the grandstream. These users are regular SIP users (from snom phones) And...you know way more than I, so I appreciate this a lot! tommy -----Original Message----- From: Tony Graziano [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 02, 2008 4:17 PM To: IT Services; [EMAIL PROTECTED] Cc: sipx-users@list.sipfoundry.org Subject: RE: [sipx-users] Call Forwarding Not Working It's most likely one of two things: 1. There is a problem with your rules and the call is not being forwarded properly by sipx. A call trace from sipx would be very helpful. 2. The gateway is not handling the forwarding properly (i.e. I think the grandstream has a strange way of handling "staged" dialing, but I have never used grandstreams for fxo gateways so what do i know). Right now the call log from your gateway shows an internal call. The silly thing is the GATEWAY should not be showing the internal call, sipx would handle that. So tell me, are either of these users not plain SIP users (i.e., are they FXS users also on the Grandstream gateway)? This is just a hunch, but what do I know. >>> "IT Services" <[EMAIL PROTECTED]> 07/02/08 18:34 PM >>> 1. subject modified to reflect what the need is. 2. the scenario is this: Ext 343 has calls forwarded to 555-1234 (example). Ext 336 dials ext 343. gets failed call. Gateway trace is listed below. Every ext has mobile turned ON. 3. version: sipXconfig (3.10.1-012233 2008-04-08T22:39:19 ecs-centos5) 4. gateway: grandstream GXW4108 Again, thanks for all of your help. I bet the fix will be something simple. tommy ________________________________ From: Tony Graziano [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 02, 2008 2:58 PM To: IT Services; [EMAIL PROTECTED] Cc: sipx-users@list.sipfoundry.org Subject: Re: [sipx-users] Call Forwarding 1. Please use a subject that is consistent and helps indicate your need. I'm sure it's an oversight, but it really does help. 2. The gateway is forwarding calls from 336 to 343 (an internal number). So look at your forwarding rule for user 336, make sure they have call permissions to MOBILE turned on (if it matters). Manually set the user call forwarding to AT THE SAME TO - ENABLED - NUMBER (the 7, 10 or 11 digit number you would normally dial from the handset to reach that number). APPLY those settings and look at the top to see if there is any RED TEXT indicating an issue. Now run the log on your gateway and see what the "To:" is indicating. 3. Verify your version/platform. (i.e. 3.10.1- Centos 5) ../sipx-config --version (i.e. sipxproxy 3.10.1-012233 2008-04-08T20:05:33 ecs-fc6) 4. Verify your gateway model. >>> "IT Services" <[EMAIL PROTECTED]> 07/02/08 05:44PM >>> Here is a trace from the gateway: Wed Jul 02 14:28:26 2008: <14>GS_LOG: [00:0B:82:13:E9:6A][000][FF51][01000102] 687 sip.c Sess: 0 Send SIP message: 100 To 192.168.1.49:5060 Wed Jul 02 14:28:26 2008: <14>GS_LOG: [00:0B:82:13:E9:6A][000][FF51][01000102] 568 sip_handle_invite.c Sess: 3 INVITE From="John Smith" <sip:[EMAIL PROTECTED];transport=udp>;tag=hr7l4wwl1v To=<sip:[EMAIL PROTECTED];user=phone> Wed Jul 02 14:28:26 2008: <14>GS_LOG: [00:0B:82:13:E9:6A][000][FF51][01000102] 620 sip_handle_invite.c Port:0 Sess:3;1 1 0;1 100;0 1 0 ch1-8:N; 100;1 0 1 1;1 5060 0 0;4 1 2 146490 Wed Jul 02 14:28:27 2008: <14>GS_LOG: [00:0B:82:13:E9:6A][000][FF51][01000102] 687 sip.c Sess: 3 Send SIP message: 180 To 192.168.1.49:5060 Wed Jul 02 14:28:27 2008: <14>GS_LOG: [00:0B:82:13:E9:6A][000][FF51][01000102] sdp.c Acc:0 RTP payload type: 0 Wed Jul 02 14:28:27 2008: <14>GS_LOG: [00:0B:82:13:E9:6A][000][FF51][01000102] 687 sip.c Sess: 3 Send SIP message: 200 To 192.168.1.49:5060 Wed Jul 02 14:28:27 2008: <14>GS_LOG: [00:0B:82:13:E9:6A][000][FF51][01000102] 1463 sip.c Received SIP message: 3 Acc:0 Wed Jul 02 14:28:27 2008: <14>GS_LOG: [00:0B:82:13:E9:6A][000][FF51][01000102] cm_api.c 232 Start fax_detect on Port:0 sess: 3 Wed Jul 02 14:29:01 2008: <14>GS_LOG: [00:0B:82:13:E9:6A][000][FF51][01000102] 1463 sip.c Received SIP message: 4 Acc:0 Wed Jul 02 14:29:01 2008: <14>GS_LOG: [00:0B:82:13:E9:6A][000][FF51][01000102] 687 sip.c Sess: 3 Send SIP message: 200 To 192.168.1.49:5060 Wed Jul 02 14:29:01 2008: <14>GS_LOG: [00:0B:82:13:E9:6A][000][FF51][01000102] 599 cm_utility.c Port:0 Sess:3 app_st: 4 drv_cs: 8 from#: 439 Wed Jul 02 14:29:03 2008: <14>GS_LOG: [00:0B:82:13:E9:6A][000][FF51][01000102] 583 cm_utility.c Port:0 Sess:3 app_st: 4 drv_cs: 0 ********** Ext 343 has calls forwarded to an external number 555-1234 (just an example). tommy -----Original Message----- From: Dale Worley [mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> Sent: Wednesday, July 02, 2008 7:24 AM To: IT Services Cc: sipx-users@list.sipfoundry.org Subject: Re: [sipx-users] sipx-users Digest, Vol 52, Issue 61 On Tue, 2008-07-01 at 17:50 -0700, IT Services wrote: > I'm having a problem with call forwarding. > I'm stuck right now so any suggestion would be helpful! You will have to get a call trace of a failed call and see what is going wrong. Dale Notice of Confidentiality: **This communication and any of its attachments is intended for the use of the person or entity to whom it is addressed and may contain information that is privileged and confidential or subject to copyright, the disclosure of which is governed by applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this information is STRICTLY PROHIBITED. If you received this message in error, please notify the sender immediately and permanently delete originals, copies & printouts of this E-mail. Thank you.** _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list..sipfoundry.org/mailman/listinfo/sipx-users <http://list.sipfoundry.org/mailman/listinfo/sipx-users> Notice of Confidentiality: **This communication and any of its attachments is intended for the use of the person or entity to whom it is addressed and may contain information that is privileged and confidential or subject to copyright, the disclosure of which is governed by applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this information is STRICTLY PROHIBITED. If you received this message in error, please notify the sender immediately and permanently delete originals, copies & printouts of this E-mail. Thank you.** Notice of Confidentiality: **This communication and any of its attachments is intended for the use of the person or entity to whom it is addressed and may contain information that is privileged and confidential or subject to copyright, the disclosure of which is governed by applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this information is STRICTLY PROHIBITED. If you received this message in error, please notify the sender immediately and permanently delete originals, copies & printouts of this E-mail. Thank you.** _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
