Transfer to external # from phone

Discussion in '3CX Phone System - General' started by RobLloyd, Jul 26, 2007.

  1. RobLloyd

    RobLloyd Member

    Joined:
    Oct 13, 2006
    Messages:
    488
    Likes Received:
    0
    Here's what I get when I try to transfer an incoming call goes to an extension that the phone sets to forward to an external #. Internal calls forward ok for some reason.
    2032656154 is the incoming call
    2036271327 is the external # that the phone ext 100 forwards to.
    192.168.1.8 is the 3cx server

    16:04:22.821 StratInOut::eek:nHangUp [CM104007] Call(52): Call from Ln:10000@nexVortex to 999 has been terminated by Ln:10000@nexVortex; cause: BYE; from IP:66.23.129.253
    16:04:11.734 Endpoint::findSource [CM010001] Line configuration does not allow identification of the source of this call. Check Advanced Options for Gateways and Providers and match a field to a correct value from the following: Contact IP: '192.168.1.8'; From: '2032656154'; To: '100'; Rline: '912036271327'; Contact: '2032656154'
    16:04:06.757 MediaServerReporting::DTMFhandler [MS211000] Call(52) Ln:10000@nexVortex: DTMF (RTP) from 69.30.45.229:51094 arrived. in-band DTMF tone detection is turned off.
    16:03:55.749 CallLegImpl::eek:nConnected [CM103001] Call(52): Created audio channel for Ln:10000@nexVortex :)51094) with Media Server (74.93.255.190:9002)
    16:03:40.768 Endpoint::findSource [CM010001] Line configuration does not allow identification of the source of this call. Check Advanced Options for Gateways and Providers and match a field to a correct value from the following: Contact IP: '192.168.1.8'; From: '2032656154'; To: '100'; Rline: '912036271327'; Contact: '2032656154'
    16:03:40.748 CallConf::eek:nProvisional [CM103003] Call(52): Ext.101 is ringing
    16:03:40.608 CallConf::eek:nIncoming [CM103002] Call(52): Incoming call from 2032656154 (Ln:10000@nexVortex) to sip:12036786206@66.23.129.253


    Thanks,
     
  2. tjabaut

    tjabaut New Member

    Joined:
    Jul 24, 2007
    Messages:
    138
    Likes Received:
    0
    Rob, so is this call not going through?
     
  3. RobLloyd

    RobLloyd Member

    Joined:
    Oct 13, 2006
    Messages:
    488
    Likes Received:
    0
    No it's not going through. It's getting bounced back to VM. Internally it works, but from an outside caller it goes to VM.
     
  4. tjabaut

    tjabaut New Member

    Joined:
    Jul 24, 2007
    Messages:
    138
    Likes Received:
    0
    How do you have the forwarding configured?

    I just tried it and setup the forward all calls option.

    It forwarded to my cell phone just fine. (note I did have to prefix my cell phone number with a 9, which is per my outbound rule)
     
  5. tjabaut

    tjabaut New Member

    Joined:
    Jul 24, 2007
    Messages:
    138
    Likes Received:
    0
    Rob,

    I also just tried it with the forward on no answer. If I left the default No Answer Afeter (seconds) at 15 it would not work and I would get a fast busy signal. I changed it to 5 seconds for testing and it worked like a charm.
     
  6. RobLloyd

    RobLloyd Member

    Joined:
    Oct 13, 2006
    Messages:
    488
    Likes Received:
    0
    This is from the phone itself. My Linksys phones have a call forward option.

    If I run it from 3CX it works fine. But I can't go having my users login to 3CX everytime they go out of the office and change their extension rules.
     
  7. tjabaut

    tjabaut New Member

    Joined:
    Jul 24, 2007
    Messages:
    138
    Likes Received:
    0
    Rob,
    Let me try it from my end. What phones are you using? I have several Linksys and Grandstream models here.
     
  8. RobLloyd

    RobLloyd Member

    Joined:
    Oct 13, 2006
    Messages:
    488
    Likes Received:
    0
    Thanks for checking it out.
    They are SPA-942 phones. If you press Cfwd then enter the number to dial 91 area code, 7 digits, then Dial it sets it.
    If you go into the setup for the phone you can see under the User tab the phone # entered in the Cfwd field.

     
  9. tjabaut

    tjabaut New Member

    Joined:
    Jul 24, 2007
    Messages:
    138
    Likes Received:
    0
    You are correct. I have verified that this is not working properly on a grandstream GXP2000.

    Since Granstream and 3CX have a partnership agreement hopefully we can get a resolution.
     
  10. VictorN

    Joined:
    Jun 20, 2007
    Messages:
    31
    Likes Received:
    0
    Cell phone

    I have two VOIP lines (with only one line it doesn
     
  11. RobLloyd

    RobLloyd Member

    Joined:
    Oct 13, 2006
    Messages:
    488
    Likes Received:
    0
    Re: Cell phone

    I have one VOIP line but it handles as many calls in or out as I need or have bandwidth.

    This puts a twist on things!
    But why would it work from ext management and not from the phone telling it to forward?

     
  12. tjabaut

    tjabaut New Member

    Joined:
    Jul 24, 2007
    Messages:
    138
    Likes Received:
    0
    Rob

    my setup is like yours. my voip provider allows up to 10 simultaneous calls.

    I am still working on this as well, but have yet to come up with anything. I think I am going to have to run some debugging both at the phone and system level to try and see what commands are being passed.

    I will check on it when I get back in the office on monday.
     
  13. RobLloyd

    RobLloyd Member

    Joined:
    Oct 13, 2006
    Messages:
    488
    Likes Received:
    0
  14. tjabaut

    tjabaut New Member

    Joined:
    Jul 24, 2007
    Messages:
    138
    Likes Received:
    0
    Can we get someone from DEVELOPMENT to look into this, if they are listening

    Rob,

    Here is the SYSLOG capture from boith my Grandstream GXP2000 and 3CX

    07-31-2007 09:45:35 User.Info 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] Received SIP message: parse error
    07-31-2007 09:45:35 User.Debug 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] 192.168.1.3:5060 5060 4
    07-31-2007 09:45:04 User.Info 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] Received SIP message: parse error
    07-31-2007 09:45:04 User.Debug 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] 192.168.1.3:5060 5060 4
    07-31-2007 09:45:02 User.Debug 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] 956 SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.1.3:5060;branch=z9hG4bK-d87543-516b640f2071ac4e-1--d87543-;rport From: <sip:200@192.168.1.3>;tag=8549f242 To: "Tim Jabaut"<sip:200@192.168.1.3>;tag=bbf10968afd3bf3a Call-ID: 86766c095b40bfc6@192.168.1.101 CSeq: 7 NOTIFY User-Agent: Grandstream GXP2000 1.1.1.14 Contact: <sip:200@192.168.1.101:5060> Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE Supported: replaces, timer Content-Length: 0
    07-31-2007 09:45:02 User.Info 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] Send SIP message: 200 To 192.168.1.3:5060
    07-31-2007 09:45:02 User.Info 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] Received SIP message: 9
    07-31-2007 09:45:02 User.Debug 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] 192.168.1.3:5060 5060 556 NOTIFY sip:200@192.168.1.101:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.3:5060;branch=z9hG4bK-d87543-516b640f2071ac4e-1--d87543-;rport Max-Forwards: 70 Contact: <sip:200@192.168.1.3:5060> To: "Tim Jabaut"<sip:200@192.168.1.3>;tag=bbf10968afd3bf3a From: <sip:200@192.168.1.3>;tag=8549f242 Call-ID: 86766c095b40bfc6@192.168.1.101 CSeq: 7 NOTIFY Content-Type: application/simple-message-summary User-Agent: 3CXPhoneSystem Subscription-State: active;expires=1700 Event: message-summary Content-Length: 43 Messages-Waiting: yes voice-message: 1/1
    07-31-2007 09:45:02 User.Debug 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] 956 SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.1.3:5060;branch=z9hG4bK-d87543-957ea83227243117-1--d87543-;rport From: <sip:200@192.168.1.3>;tag=8549f242 To: "Tim Jabaut"<sip:200@192.168.1.3>;tag=bbf10968afd3bf3a Call-ID: 86766c095b40bfc6@192.168.1.101 CSeq: 6 NOTIFY User-Agent: Grandstream GXP2000 1.1.1.14 Contact: <sip:200@192.168.1.101:5060> Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE Supported: replaces, timer Content-Length: 0
    07-31-2007 09:45:02 User.Info 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] Send SIP message: 200 To 192.168.1.3:5060
    07-31-2007 09:45:02 User.Info 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] Received SIP message: 9
    07-31-2007 09:45:02 User.Debug 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] 192.168.1.3:5060 5060 556 NOTIFY sip:200@192.168.1.101:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.3:5060;branch=z9hG4bK-d87543-957ea83227243117-1--d87543-;rport Max-Forwards: 70 Contact: <sip:200@192.168.1.3:5060> To: "Tim Jabaut"<sip:200@192.168.1.3>;tag=bbf10968afd3bf3a From: <sip:200@192.168.1.3>;tag=8549f242 Call-ID: 86766c095b40bfc6@192.168.1.101 CSeq: 6 NOTIFY Content-Type: application/simple-message-summary User-Agent: 3CXPhoneSystem Subscription-State: active;expires=1700 Event: message-summary Content-Length: 43 Messages-Waiting: yes voice-message: 1/1
    07-31-2007 09:44:59 User.Debug 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] 956 SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.1.3:5060;branch=z9hG4bK-d87543-8313cb57da3a2311-1--d87543-;rport From: <sip:200@192.168.1.3>;tag=8549f242 To: "Tim Jabaut"<sip:200@192.168.1.3>;tag=bbf10968afd3bf3a Call-ID: 86766c095b40bfc6@192.168.1.101 CSeq: 5 NOTIFY User-Agent: Grandstream GXP2000 1.1.1.14 Contact: <sip:200@192.168.1.101:5060> Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE Supported: replaces, timer Content-Length: 0
    07-31-2007 09:44:59 User.Info 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] Send SIP message: 200 To 192.168.1.3:5060
    07-31-2007 09:44:59 User.Info 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] Received SIP message: 9
    07-31-2007 09:44:59 User.Debug 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] 192.168.1.3:5060 5060 556 NOTIFY sip:200@192.168.1.101:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.3:5060;branch=z9hG4bK-d87543-8313cb57da3a2311-1--d87543-;rport Max-Forwards: 70 Contact: <sip:200@192.168.1.3:5060> To: "Tim Jabaut"<sip:200@192.168.1.3>;tag=bbf10968afd3bf3a From: <sip:200@192.168.1.3>;tag=8549f242 Call-ID: 86766c095b40bfc6@192.168.1.101 CSeq: 5 NOTIFY Content-Type: application/simple-message-summary User-Agent: 3CXPhoneSystem Subscription-State: active;expires=1703 Event: message-summary Content-Length: 43 Messages-Waiting: yes voice-message: 1/1
    07-31-2007 09:44:59 User.Debug 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] 956 SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.1.3:5060;branch=z9hG4bK-d87543-224dd57b502b8c24-1--d87543-;rport From: <sip:200@192.168.1.3>;tag=8549f242 To: "Tim Jabaut"<sip:200@192.168.1.3>;tag=bbf10968afd3bf3a Call-ID: 86766c095b40bfc6@192.168.1.101 CSeq: 4 NOTIFY User-Agent: Grandstream GXP2000 1.1.1.14 Contact: <sip:200@192.168.1.101:5060> Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE Supported: replaces, timer Content-Length: 0
    07-31-2007 09:44:59 User.Info 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] Send SIP message: 200 To 192.168.1.3:5060
    07-31-2007 09:44:59 User.Info 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] Received SIP message: 9
    07-31-2007 09:44:59 User.Debug 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] 192.168.1.3:5060 5060 556 NOTIFY sip:200@192.168.1.101:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.3:5060;branch=z9hG4bK-d87543-224dd57b502b8c24-1--d87543-;rport Max-Forwards: 70 Contact: <sip:200@192.168.1.3:5060> To: "Tim Jabaut"<sip:200@192.168.1.3>;tag=bbf10968afd3bf3a From: <sip:200@192.168.1.3>;tag=8549f242 Call-ID: 86766c095b40bfc6@192.168.1.101 CSeq: 4 NOTIFY Content-Type: application/simple-message-summary User-Agent: 3CXPhoneSystem Subscription-State: active;expires=1703 Event: message-summary Content-Length: 43 Messages-Waiting: yes voice-message: 1/1
    07-31-2007 09:44:59 User.Debug 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] 956 SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.1.3:5060;branch=z9hG4bK-d87543-675fb5202912962c-1--d87543-;rport From: <sip:200@192.168.1.3>;tag=8549f242 To: "Tim Jabaut"<sip:200@192.168.1.3>;tag=bbf10968afd3bf3a Call-ID: 86766c095b40bfc6@192.168.1.101 CSeq: 3 NOTIFY User-Agent: Grandstream GXP2000 1.1.1.14 Contact: <sip:200@192.168.1.101:5060> Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE Supported: replaces, timer Content-Length: 0
    07-31-2007 09:44:59 User.Info 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] Send SIP message: 200 To 192.168.1.3:5060
    07-31-2007 09:44:59 User.Info 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] Received SIP message: 9
    07-31-2007 09:44:59 User.Debug 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] 192.168.1.3:5060 5060 556 NOTIFY sip:200@192.168.1.101:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.3:5060;branch=z9hG4bK-d87543-675fb5202912962c-1--d87543-;rport Max-Forwards: 70 Contact: <sip:200@192.168.1.3:5060> To: "Tim Jabaut"<sip:200@192.168.1.3>;tag=bbf10968afd3bf3a From: <sip:200@192.168.1.3>;tag=8549f242 Call-ID: 86766c095b40bfc6@192.168.1.101 CSeq: 3 NOTIFY Content-Type: application/simple-message-summary User-Agent: 3CXPhoneSystem Subscription-State: active;expires=1703 Event: message-summary Content-Length: 43 Messages-Waiting: yes voice-message: 1/1
    07-31-2007 09:44:42 Daemon.Alert 192.168.1.1 FVS318 Blocked Sites Log[84353]:SIPs Range forwarded , SIP:64.2.142.26: 16740, DIP:71.164.118.45: 8016,
    07-31-2007 09:44:41 User.Debug 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] SIP dialog not matched
    07-31-2007 09:44:41 User.Info 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] Received SIP message: 3
    07-31-2007 09:44:41 User.Debug 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] 192.168.1.3:5060 5060 339 ACK sip:200@192.168.1.101:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.3:5060;branch=z9hG4bK-d87543-7357df44b92a7063-1--d87543-;rport To: "200"<sip:200@192.168.1.101:5060>;tag=09423b73 From: "5186150113"<sip:5186150113@sip1.vitelity.net>;tag=c6114b69 Call-ID: NWE5NDdkOWQ0YWI3MDVmZTliYzMzZmY0NmE0YjU5ZDI. CSeq: 1 ACK Content-Length: 0
    07-31-2007 09:44:41 User.Debug 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] 956 SIP/2.0 302 Moved Temporarily Via: SIP/2.0/UDP 192.168.1.3:5060;branch=z9hG4bK-d87543-7357df44b92a7063-1--d87543-;rport From: "5186150113"<sip:5186150113@sip1.vitelity.net>;tag=c6114b69 To: "200"<sip:200@192.168.1.101:5060>;tag=09423b73 Call-ID: NWE5NDdkOWQ0YWI3MDVmZTliYzMzZmY0NmE0YjU5ZDI. CSeq: 1 INVITE User-Agent: Grandstream GXP2000 1.1.1.14 Contact: sip:91518542XXXX@192.168.1.3 Diversion: <sip:200@192.168.1.101:5060>;reason=unconditional Content-Length: 0
    07-31-2007 09:44:41 User.Info 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] Send SIP message: 302 To 192.168.1.3:5060
    07-31-2007 09:44:41 User.Debug 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] SIP dialog not matched

    If you look at the Red Text you wil see that the *72 unconditional call forward on my grandstream worked; however 3CX does not seem to be interpreting it correctly.

    This is horrible.
     
  15. RobLloyd

    RobLloyd Member

    Joined:
    Oct 13, 2006
    Messages:
    488
    Likes Received:
    0
    Thanks for your log post. I'll do the same later today and we can compare.
     
  16. tjabaut

    tjabaut New Member

    Joined:
    Jul 24, 2007
    Messages:
    138
    Likes Received:
    0
    Rob,

    I have also started a new thread titled Unconditional Call Forwarding and in it asked for some assistanct from thedevelopers. I see you too are a consultant. My biggest fear with this product is with a lack of true support, I am skeptical to put it production at a clients.

    My other post regarding 7-digit0-dialing is not really garnering any real answers as well. I think I may have a workaround as the Grandstream Gateway that I will be using, I believe has Regular Expression Logic in its dial patterns.

    Still not an answer from development, but it may solve my immediate need.
     
  17. archie

    archie Well-Known Member
    3CX Staff

    Joined:
    Aug 18, 2006
    Messages:
    1,309
    Likes Received:
    0
    In this line: is 91518542XXXX valid number for the 3CX PBX? I mean, do you have outbound rule which treats it right? Doesn't this rule leads to the same provider from which call has come?
    Please, make a test: try make a call from internal extension to this number. Let me know if it works.
     
  18. archie

    archie Well-Known Member
    3CX Staff

    Joined:
    Aug 18, 2006
    Messages:
    1,309
    Likes Received:
    0
    You're using forum for FREE version support. So you may expect some delay of replies from developers, because we're not reading the forum all the time -- we need that time to make new versions, fix bugs and other minor stuff like that :)

    Seriousely, you should understand, that if i will spend all the time answering the forum - you'll never get new version. If you need more quick reaction - subscribe for e-mail support and all complex question will reach me almost immediately, and easier requests will be solved by support dept, not distracting me from development. Mind, that we're mainly in development stage atm, not in support stage.
     
  19. tjabaut

    tjabaut New Member

    Joined:
    Jul 24, 2007
    Messages:
    138
    Likes Received:
    0
    Archie,

    Yes this call comes in via Vitelity and should go out over Vitelity.

    Here is the interesting thing, if I dial my vitelity number and 3cx passes the call to extension 200 as I have setup. If I then do a transfer to my cell phone (ie the 9+1+518+542xxxx number) it goes through just fine.

    Here is the SYSLOG capture

    07-31-2007 11:37:18 User.Debug 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] 956 SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.1.3:5060;branch=z9hG4bK-d87543-c065a941fa532221-1--d87543-;rport From: "5186150113"<sip:5186150113@sip1.vitelity.net>;tag=07383b3d To: "200"<sip:200@192.168.1.101:5060>;tag=c99e0e0ca4fa42e3 Call-ID: NDhkN2Q1ZTMwMjM5NjlhMDJhNjI2Y2M4YzM2Njg3ZDI. CSeq: 5 NOTIFY User-Agent: Grandstream GXP2000 1.1.1.14 Contact: <sip:200@192.168.1.101:5060> Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE Supported: replaces, timer Content-Length: 0
    07-31-2007 11:37:18 User.Info 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] Send SIP message: 200 To 192.168.1.3:5060
    07-31-2007 11:37:18 User.Debug 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] SIP dialog not matched
    07-31-2007 11:37:18 User.Info 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] Received SIP message: 9
    07-31-2007 11:37:18 User.Debug 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] 192.168.1.3:5060 5060 557 NOTIFY sip:200@192.168.1.101:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.3:5060;branch=z9hG4bK-d87543-c065a941fa532221-1--d87543-;rport Max-Forwards: 70 Contact: <sip:5186150113@192.168.1.3:5060> To: "200"<sip:200@192.168.1.101:5060>;tag=c99e0e0ca4fa42e3 From: "5186150113"<sip:5186150113@sip1.vitelity.net>;tag=07383b3d Call-ID: NDhkN2Q1ZTMwMjM5NjlhMDJhNjI2Y2M4YzM2Njg3ZDI. CSeq: 5 NOTIFY Content-Type: message/sipfrag User-Agent: 3CXPhoneSystem Subscription-State: terminated;reason=noResource Event: refer Content-Length: 18 SIP/2.0 200 OK
    07-31-2007 11:37:18 User.Info 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] Received SIP message: parse error
    07-31-2007 11:37:18 User.Debug 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] 192.168.1.3:5060 5060 4
    07-31-2007 11:37:04 User.Debug 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] SIP dialog matched to channel 0
    07-31-2007 11:37:04 User.Info 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] Received SIP message: 200
    07-31-2007 11:37:04 User.Debug 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] 192.168.1.3:5060 5060 376 SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.1.101:5060;branch=z9hG4bKa5b9f0a0064d2677 Contact: <sip:5186150113@192.168.1.3:5060> To: "5186150113"<sip:5186150113@sip1.vitelity.net>;tag=07383b3d From: "200"<sip:200@192.168.1.101:5060>;tag=c99e0e0ca4fa42e3 Call-ID: NDhkN2Q1ZTMwMjM5NjlhMDJhNjI2Y2M4YzM2Njg3ZDI. CSeq: 42135 BYE User-Agent: 3CXPhoneSystem Content-Length: 0
    07-31-2007 11:37:04 User.Debug 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] 956 BYE sip:5186150113@192.168.1.3:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.101:5060;branch=z9hG4bKa5b9f0a0064d2677 From: "200"<sip:200@192.168.1.101:5060>;tag=c99e0e0ca4fa42e3 To: "5186150113"<sip:5186150113@sip1.vitelity.net>;tag=07383b3d Proxy-Authorization: Digest username="200", realm="3CXPhoneSystem", algorithm=MD5, uri="sip:5186150113@192.168.1.3:5060", nonce="12830369821:f94e442711385b5a47b135d520d2ed0c", response="00e434e453a50cbec30dc228cb4703d7" Call-ID: NDhkN2Q1ZTMwMjM5NjlhMDJhNjI2Y2M4YzM2Njg3ZDI. CSeq: 42135 BYE User-Agent: Grandstream GXP2000 1.1.1.14 Max-Forwards: 70 Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE Content-Length: 0
    07-31-2007 11:37:04 User.Info 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] Send SIP message: 4 To 192.168.1.3:5060
    07-31-2007 11:37:03 User.Debug 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] 956 SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.1.3:5060;branch=z9hG4bK-d87543-686cea7dc20c7027-1--d87543-;rport From: "5186150113"<sip:5186150113@sip1.vitelity.net>;tag=07383b3d To: "200"<sip:200@192.168.1.101:5060>;tag=c99e0e0ca4fa42e3 Call-ID: NDhkN2Q1ZTMwMjM5NjlhMDJhNjI2Y2M4YzM2Njg3ZDI. CSeq: 4 NOTIFY User-Agent: Grandstream GXP2000 1.1.1.14 Contact: <sip:200@192.168.1.101:5060> Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE Supported: replaces, timer Content-Length: 0
    07-31-2007 11:37:03 User.Info 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] Send SIP message: 200 To 192.168.1.3:5060
    07-31-2007 11:37:03 User.Debug 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] SIP dialog matched to channel 0
    07-31-2007 11:37:03 User.Info 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] Received SIP message: 9
    07-31-2007 11:37:03 User.Debug 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] 192.168.1.3:5060 5060 558 NOTIFY sip:200@192.168.1.101:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.3:5060;branch=z9hG4bK-d87543-686cea7dc20c7027-1--d87543-;rport Max-Forwards: 70 Contact: <sip:5186150113@192.168.1.3:5060> To: "200"<sip:200@192.168.1.101:5060>;tag=c99e0e0ca4fa42e3 From: "5186150113"<sip:5186150113@sip1.vitelity.net>;tag=07383b3d Call-ID: NDhkN2Q1ZTMwMjM5NjlhMDJhNjI2Y2M4YzM2Njg3ZDI. CSeq: 4 NOTIFY Content-Type: message/sipfrag User-Agent: 3CXPhoneSystem Subscription-State: init;expires=57 Event: refer Content-Length: 32 SIP/2.0 183 Session Progress
    07-31-2007 11:37:03 User.Debug 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] 956 SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.1.3:5060;branch=z9hG4bK-d87543-2104c14b50730216-1--d87543-;rport From: "5186150113"<sip:5186150113@sip1.vitelity.net>;tag=07383b3d To: "200"<sip:200@192.168.1.101:5060>;tag=c99e0e0ca4fa42e3 Call-ID: NDhkN2Q1ZTMwMjM5NjlhMDJhNjI2Y2M4YzM2Njg3ZDI. CSeq: 3 NOTIFY User-Agent: Grandstream GXP2000 1.1.1.14 Contact: <sip:200@192.168.1.101:5060> Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE Supported: replaces, timer Content-Length: 0
    07-31-2007 11:37:03 User.Info 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] Send SIP message: 200 To 192.168.1.3:5060
    07-31-2007 11:37:03 User.Debug 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] SIP dialog matched to channel 0
    07-31-2007 11:37:03 User.Info 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] Received SIP message: 9
    07-31-2007 11:37:03 User.Debug 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] 192.168.1.3:5060 5060 558 NOTIFY sip:200@192.168.1.101:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.3:5060;branch=z9hG4bK-d87543-2104c14b50730216-1--d87543-;rport Max-Forwards: 70 Contact: <sip:5186150113@192.168.1.3:5060> To: "200"<sip:200@192.168.1.101:5060>;tag=c99e0e0ca4fa42e3 From: "5186150113"<sip:5186150113@sip1.vitelity.net>;tag=07383b3d Call-ID: NDhkN2Q1ZTMwMjM5NjlhMDJhNjI2Y2M4YzM2Njg3ZDI. CSeq: 3 NOTIFY Content-Type: message/sipfrag User-Agent: 3CXPhoneSystem Subscription-State: init;expires=57 Event: refer Content-Length: 32 SIP/2.0 183 Session Progress
    07-31-2007 11:37:03 User.Debug 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] 956 SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.1.3:5060;branch=z9hG4bK-d87543-335102237b6ab054-1--d87543-;rport From: "5186150113"<sip:5186150113@sip1.vitelity.net>;tag=07383b3d To: "200"<sip:200@192.168.1.101:5060>;tag=c99e0e0ca4fa42e3 Call-ID: NDhkN2Q1ZTMwMjM5NjlhMDJhNjI2Y2M4YzM2Njg3ZDI. CSeq: 2 NOTIFY User-Agent: Grandstream GXP2000 1.1.1.14 Contact: <sip:200@192.168.1.101:5060> Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE Supported: replaces, timer Content-Length: 0
    07-31-2007 11:37:03 User.Info 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] Send SIP message: 200 To 192.168.1.3:5060
    07-31-2007 11:37:03 User.Debug 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] SIP dialog matched to channel 0
    07-31-2007 11:37:03 User.Info 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] Received SIP message: 9
    07-31-2007 11:37:03 User.Debug 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] 192.168.1.3:5060 5060 558 NOTIFY sip:200@192.168.1.101:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.3:5060;branch=z9hG4bK-d87543-335102237b6ab054-1--d87543-;rport Max-Forwards: 70 Contact: <sip:5186150113@192.168.1.3:5060> To: "200"<sip:200@192.168.1.101:5060>;tag=c99e0e0ca4fa42e3 From: "5186150113"<sip:5186150113@sip1.vitelity.net>;tag=07383b3d Call-ID: NDhkN2Q1ZTMwMjM5NjlhMDJhNjI2Y2M4YzM2Njg3ZDI. CSeq: 2 NOTIFY Content-Type: message/sipfrag User-Agent: 3CXPhoneSystem Subscription-State: init;expires=57 Event: refer Content-Length: 32 SIP/2.0 183 Session Progress
    07-31-2007 11:37:03 Daemon.Alert 192.168.1.1 FVS318 Blocked Sites Log[85552]:SIPs Range forwarded , SIP:64.2.142.26: 16426, DIP:71.164.118.45: 8026,
    07-31-2007 11:37:00 Daemon.Alert 192.168.1.1 FVS318 Blocked Sites Log[85551]:SIPs Range forwarded , SIP:194.221.62.209: 3478, DIP:71.164.118.45: 8026,
    07-31-2007 11:37:00 User.Debug 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] SIP dialog matched to channel 0
    07-31-2007 11:37:00 User.Info 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] Received SIP message: 202
    07-31-2007 11:37:00 User.Debug 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] 192.168.1.3:5060 5060 397 SIP/2.0 202 Accepted Via: SIP/2.0/UDP 192.168.1.101:5060;branch=z9hG4bK9dbb87dac36b4b31 Contact: <sip:5186150113@192.168.1.3:5060> To: "5186150113"<sip:5186150113@sip1.vitelity.net>;tag=07383b3d From: "200"<sip:200@192.168.1.101:5060>;tag=c99e0e0ca4fa42e3 Call-ID: NDhkN2Q1ZTMwMjM5NjlhMDJhNjI2Y2M4YzM2Njg3ZDI. CSeq: 42134 REFER Expires: 60 User-Agent: 3CXPhoneSystem Content-Length: 0
    07-31-2007 11:37:00 User.Debug 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] 956 REFER sip:5186150113@192.168.1.3:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.101:5060;branch=z9hG4bK9dbb87dac36b4b31 From: "200"<sip:200@192.168.1.101:5060>;tag=c99e0e0ca4fa42e3 To: "5186150113"<sip:5186150113@sip1.vitelity.net>;tag=07383b3d Contact: <sip:200@192.168.1.101:5060> Supported: replaces Refer-To: <sip:915185425519@192.168.1.3> Referred-By: <sip:200@192.168.1.3> Proxy-Authorization: Digest username="200", realm="3CXPhoneSystem", algorithm=MD5, uri="sip:5186150113@192.168.1.3:5060", nonce="12830369821:f94e442711385b5a47b135d520d2ed0c", response="7510e530c60134e320a7503e99a9b3a9" Call-ID: NDhkN2Q1ZTMwMjM5NjlhMDJhNjI2Y2M4YzM2Njg3ZDI. CSeq: 42134 REFER User-Agent: Grandstream GXP2000 1.1.1.14 Max-Forwards: 70 Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE Content-Length: 0
    07-31-2007 11:37:00 User.Info 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] Send SIP message: 6 To 192.168.1.3:5060
    07-31-2007 11:37:00 User.Debug 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] SIP dialog matched to channel 0
    07-31-2007 11:37:00 User.Info 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] Received SIP message: 407
    07-31-2007 11:37:00 User.Debug 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] 192.168.1.3:5060 5060 479 SIP/2.0 407 Proxy Authentication Required Via: SIP/2.0/UDP 192.168.1.101:5060;branch=z9hG4bKaf7401bd13dcfed3 Proxy-Authenticate: Digest nonce="12830369821:f94e442711385b5a47b135d520d2ed0c",algorithm=MD5,realm="3CXPhoneSystem" To: "5186150113"<sip:5186150113@sip1.vitelity.net>;tag=07383b3d From: "200"<sip:200@192.168.1.101:5060>;tag=c99e0e0ca4fa42e3 Call-ID: NDhkN2Q1ZTMwMjM5NjlhMDJhNjI2Y2M4YzM2Njg3ZDI. CSeq: 42133 REFER User-Agent: 3CXPhoneSystem Content-Length: 0
    07-31-2007 11:37:00 User.Debug 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] 956 REFER sip:5186150113@192.168.1.3:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.101:5060;branch=z9hG4bKaf7401bd13dcfed3 From: "200"<sip:200@192.168.1.101:5060>;tag=c99e0e0ca4fa42e3 To: "5186150113"<sip:5186150113@sip1.vitelity.net>;tag=07383b3d Contact: <sip:200@192.168.1.101:5060> Supported: replaces Refer-To: <sip:915185425519@192.168.1.3> Referred-By: <sip:200@192.168.1.3> Call-ID: NDhkN2Q1ZTMwMjM5NjlhMDJhNjI2Y2M4YzM2Njg3ZDI. CSeq: 42133 REFER User-Agent: Grandstream GXP2000 1.1.1.14 Max-Forwards: 70 Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE Content-Length: 0
    07-31-2007 11:37:00 User.Info 192.168.1.101 GS_LOG: [00:0b:82:0a:3b:d5][000][FF71][0101010E] Send SIP message: 6 To 192.168.1.3:5060
     
  20. archie

    archie Well-Known Member
    3CX Staff

    Joined:
    Aug 18, 2006
    Messages:
    1,309
    Likes Received:
    0
    First, it's hard to read GXP logs, I get used to my own logs and they tells me more :)

    Second. I suspect the difference is that during REFER we don't check if line is 'busy' or limited on number of simultaneous calls, so please check your settings for number of simultaneous calls allowed for that line (line settings/other options/Maximum simultaneous calls). And 302 produces completely new call that is not related with diverted call, so it WILL check that settings and probably decide that line is busy.

    I'm not sure though, it's just quick guess. We need to check it.
     

Share This Page