Calls supposedly Failed due to 'No Answer' No Phones ring

Discussion in '3CX Phone System - General' started by goochr96, Aug 3, 2009.

Thread Status:
Not open for further replies.
  1. goochr96

    Joined:
    Aug 3, 2009
    Messages:
    12
    Likes Received:
    0
    Hello, this is my first post.
    I have been playing with the 3CX software for a short while now. I have aquired some CISCO kit, and have managed to convert it from SCCP to SIP. I have set up a few extensions within 3CX. All appears to be okay, however whe i dial a phone number, nothing happens. When i check the Server Activity Log, it all seems okay but fails on Reason: No Answer, but nothing had rang. All help is much appreicated. I hope there is enough information in the activity log to help.

    Many Thanks,
    Chris Goodman

    22:30:41.968 [CM504008]: Fax Service: registered as sip:8888@192.168.1.5 with contact sip:8888@192.168.1.1:5060;user=phone;transport=udp

    22:30:41.859 [CM504001]: Ext.4000: new contact is registered. Contact(s): [sip:4000@192.168.1.1:5060;user=phone;transport=udp/4000]

    22:30:36.203 [CM503008]: Call(36): Call is terminated

    22:30:36.187 [CM503015]: Call(36): Attempt to reach <sip:4000@192.168.1.5> failed. Reason: No Answer

    22:30:36.187 [CM503003]: Call(36): Call to sip:4000@192.168.1.5:5060 has failed; Cause: 408 Request Timeout; internal

    22:30:32.031 [CM504008]: Fax Service: registered as sip:8888@192.168.1.5:5060 with contact sip:8888@192.168.1.5:5100;user=phone

    22:30:04.078 [CM503024]: Call(36): Calling Ext:Ext.4000@[Dev:sip:4000@192.168.1.1:5060;user=phone;transport=udp]

    22:30:04.000 [CM503004]: Call(36): Route 1: Ext:Ext.4000@[Dev:sip:4000@192.168.1.1:5060;user=phone;transport=udp]

    22:30:04.000 [CM503010]: Making route(s) to <sip:4000@192.168.1.5>

    22:30:03.968 [CM505001]: Ext.1500: Device info: Device Identified: [Man: Cisco;Mod: 7940;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [Cisco-CP7940G/8.0] Transport: [sip:192.168.1.5:5060]

    22:30:03.921 [CM503001]: Call(36): Incoming call from Ext.1500 to <sip:4000@192.168.1.5>

    22:30:00.656 [CM503008]: Call(35): Call is terminated

    22:30:00.125 [CM503024]: Call(35): Calling Ext:Ext.4000@[Dev:sip:4000@192.168.1.1:5060;user=phone;transport=udp]

    22:30:00.109 [CM503004]: Call(35): Route 1: Ext:Ext.4000@[Dev:sip:4000@192.168.1.1:5060;user=phone;transport=udp]

    22:30:00.109 [CM503010]: Making route(s) to <sip:4000@192.168.1.5>

    22:30:00.093 [CM505001]: Ext.1000: Device info: Device Identified: [Man: Cisco;Mod: 7940;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [Cisco-CP7940G/8.0] Transport: [sip:192.168.1.5:5060]

    22:30:00.046 [CM503001]: Call(35): Incoming call from Ext.1000 to <sip:4000@192.168.1.5>

    22:29:55.281 [CM503008]: Call(34): Call is terminated

    22:29:50.406 [CM503024]: Call(34): Calling Ext:Ext.1000@[Dev:sip:1000@192.168.1.1:5061;transport=udp]

    22:29:50.343 [CM503004]: Call(34): Route 1: Ext:Ext.1000@[Dev:sip:1000@192.168.1.1:5061;transport=udp]

    22:29:50.343 [CM503010]: Making route(s) to <sip:1000@192.168.1.5>

    22:29:50.328 [CM505001]: Ext.1500: Device info: Device Identified: [Man: Cisco;Mod: 7940;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [Cisco-CP7940G/8.0] Transport: [sip:192.168.1.5:5060]

    22:29:50.296 [CM503001]: Call(34): Incoming call from Ext.1500 to <sip:1000@192.168.1.5>

    22:29:40.562 [CM503008]: Call(33): Call is terminated

    22:29:26.453 [CM503024]: Call(33): Calling Ext:Ext.4000@[Dev:sip:4000@192.168.1.1:5060;user=phone;transport=udp]

    22:29:26.390 [CM503004]: Call(33): Route 1: Ext:Ext.4000@[Dev:sip:4000@192.168.1.1:5060;user=phone;transport=udp]

    22:29:26.390 [CM503010]: Making route(s) to <sip:4000@192.168.1.5>

    22:29:26.390 [CM505001]: Ext.1000: Device info: Device Identified: [Man: Cisco;Mod: 7940;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [Cisco-CP7940G/8.0] Transport: [sip:192.168.1.5:5060]

    22:29:26.343 [CM503001]: Call(33): Incoming call from Ext.1000 to <sip:4000@192.168.1.5>

    22:29:16.265 [CM503008]: Call(32): Call is terminated

    22:28:56.984 [CM503024]: Call(32): Calling Ext:Ext.1000@[Dev:sip:1000@192.168.1.1:5061;transport=udp]

    22:28:56.968 [CM503004]: Call(32): Route 1: Ext:Ext.1000@[Dev:sip:1000@192.168.1.1:5061;transport=udp]

    22:28:56.968 [CM503010]: Making route(s) to <sip:1000@192.168.1.5;user=phone>

    22:28:56.968 [CM505001]: Ext.4000: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Cisco ATA 186 v3.1.0 atasip (040211A)] Transport: [sip:192.168.1.5:5060]

    22:28:56.937 [CM503001]: Call(32): Incoming call from Ext.4000 to <sip:1000@192.168.1.5;user=phone>

    22:25:31.843 [CM504008]: Fax Service: registered as sip:8888@192.168.1.5:5060 with contact sip:8888@192.168.1.5:5100;user=phone

    22:25:23.828 [CM504001]: Ext.1500: new contact is registered. Contact(s): [sip:1500@192.168.1.1:5061;transport=udp/1500]

    22:25:23.546 [CM504001]: Ext.1000: new contact is registered. Contact(s): [sip:1000@192.168.1.1:5061;transport=udp/1000]

    22:25:23.453 [CM504001]: Ext.1000: new contact is registered. Contact(s): [sip:1000@192.168.1.1:5061;transport=udp/1000]

    22:20:31.593 [CM504008]: Fax Service: registered as sip:8888@192.168.1.5:5060 with contact sip:8888@192.168.1.5:5100;user=phone

    22:15:31.406 [CM504008]: Fax Service: registered as sip:8888@192.168.1.5:5060 with contact sip:8888@192.168.1.5:5100;user=phone

    22:15:24.546 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 75.101.138.128:3478 over Transport 192.168.1.5:5060

    22:10:31.187 [CM504008]: Fax Service: registered as sip:8888@192.168.1.5:5060 with contact sip:8888@192.168.1.5:5100;user=phone

    22:05:31.000 [CM504008]: Fax Service: registered as sip:8888@192.168.1.5:5060 with contact sip:8888@192.168.1.5:5100;user=phone

    22:05:01.453 [CM504008]: Fax Service: registered as sip:8888@192.168.1.5 with contact sip:8888@192.168.1.1:5060;user=phone;transport=udp

    22:05:01.375 [CM504001]: Ext.4000: new contact is registered. Contact(s): [sip:4000@192.168.1.1:5060;user=phone;transport=udp/4000]

    22:00:30.781 [CM504008]: Fax Service: registered as sip:8888@192.168.1.5:5060 with contact sip:8888@192.168.1.5:5100;user=phone

    22:00:05.171 [CM503008]: Call(31): Call is terminated

    22:00:05.156 [CM503015]: Call(31): Attempt to reach <sip:4000@192.168.1.5> failed. Reason: No Answer

    22:00:05.156 [CM503003]: Call(31): Call to sip:4000@192.168.1.5:5060 has failed; Cause: 408 Request Timeout; internal

    21:59:33.046 [CM503024]: Call(31): Calling Ext:Ext.4000@[Dev:sip:4000@192.168.1.1:5060;user=phone;transport=udp]

    21:59:33.031 [CM503004]: Call(31): Route 1: Ext:Ext.4000@[Dev:sip:4000@192.168.1.1:5060;user=phone;transport=udp]

    21:59:33.031 [CM503010]: Making route(s) to <sip:4000@192.168.1.5>

    21:59:33.031 [CM505001]: Ext.1000: Device info: Device Identified: [Man: Cisco;Mod: 7940;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [Cisco-CP7940G/8.0] Transport: [sip:192.168.1.5:5060]

    21:59:33.000 [CM503001]: Call(31): Incoming call from Ext.1000 to <sip:4000@192.168.1.5>

    21:57:25.953 [CM503008]: Call(30): Call is terminated

    21:57:25.937 [CM503015]: Call(30): Attempt to reach <sip:4000@192.168.1.5> failed. Reason: No Answer

    21:57:25.921 [CM503003]: Call(30): Call to sip:4000@192.168.1.5:5060 has failed; Cause: 408 Request Timeout; internal

    21:56:53.843 [CM503024]: Call(30): Calling Ext:Ext.4000@[Dev:sip:4000@192.168.1.1:5060;user=phone;transport=udp]

    21:56:53.828 [CM503004]: Call(30): Route 1: Ext:Ext.4000@[Dev:sip:4000@192.168.1.1:5060;user=phone;transport=udp]

    21:56:53.796 [CM503010]: Making route(s) to <sip:4000@192.168.1.5>

    21:56:53.796 [CM505001]: Ext.1000: Device info: Device Identified: [Man: Cisco;Mod: 7940;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [Cisco-CP7940G/8.0] Transport: [sip:192.168.1.5:5060]

    21:56:53.765 [CM503001]: Call(30): Incoming call from Ext.1000 to <sip:4000@192.168.1.5>

    21:55:30.578 [CM504008]: Fax Service: registered as sip:8888@192.168.1.5:5060 with contact sip:8888@192.168.1.5:5100;user=phone

    21:55:28.187 [CM504001]: Ext.1500: new contact is registered. Contact(s): [sip:1500@192.168.1.1:5061;transport=udp/1500]

    21:55:27.859 [CM504001]: Ext.1000: new contact is registered. Contact(s): [sip:1000@192.168.1.1:5061;transport=udp/1000]

    21:55:27.781 [CM504001]: Ext.1000: new contact is registered. Contact(s): [sip:1000@192.168.1.1:5061;transport=udp/1000]

    21:55:24.312 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 75.101.138.128:3478 over Transport 192.168.1.5:5060

    21:52:29.359 [CM503008]: Call(29): Call is terminated

    21:52:24.312 [CM503024]: Call(29): Calling Ext:Ext.4000@[Dev:sip:4000@192.168.1.1:5060;user=phone;transport=udp]

    21:52:24.265 [CM503004]: Call(29): Route 1: Ext:Ext.4000@[Dev:sip:4000@192.168.1.1:5060;user=phone;transport=udp]

    21:52:24.265 [CM503010]: Making route(s) to <sip:4000@192.168.1.5>

    21:52:24.250 [CM505001]: Ext.1000: Device info: Device Identified: [Man: Cisco;Mod: 7940;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [Cisco-CP7940G/8.0] Transport: [sip:192.168.1.5:5060]

    21:52:24.218 [CM503001]: Call(29): Incoming call from Ext.1000 to <sip:4000@192.168.1.5>

    21:50:30.375 [CM504008]: Fax Service: registered as sip:8888@192.168.1.5:5060 with contact sip:8888@192.168.1.5:5100;user=phone

    21:45:30.187 [CM504008]: Fax Service: registered as sip:8888@192.168.1.5:5060 with contact sip:8888@192.168.1.5:5100;user=phone

    21:43:46.593 [CM503008]: Call(28): Call is terminated

    21:43:37.453 [CM503024]: Call(28): Calling Ext:Ext.4000@[Dev:sip:4000@192.168.1.1:5060;user=phone;transport=udp]

    21:43:37.437 [CM503004]: Call(28): Route 1: Ext:Ext.4000@[Dev:sip:4000@192.168.1.1:5060;user=phone;transport=udp]

    21:43:37.390 [CM503010]: Making route(s) to <sip:4000@192.168.1.5>

    21:43:37.375 [CM505001]: Ext.1000: Device info: Device Identified: [Man: Cisco;Mod: 7940;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [Cisco-CP7940G/8.0] Transport: [sip:192.168.1.5:5060]

    21:43:37.343 [CM503001]: Call(28): Incoming call from Ext.1000 to <sip:4000@192.168.1.5>

    21:43:34.593 [CM503008]: Call(27): Call is terminated

    21:43:22.906 [CM503024]: Call(27): Calling Ext:Ext.4000@[Dev:sip:4000@192.168.1.1:5060;user=phone;transport=udp]

    21:43:22.890 [CM503004]: Call(27): Route 1: Ext:Ext.4000@[Dev:sip:4000@192.168.1.1:5060;user=phone;transport=udp]

    21:43:22.859 [CM503010]: Making route(s) to <sip:4000@192.168.1.5>

    21:43:22.859 [CM505001]: Ext.1000: Device info: Device Identified: [Man: Cisco;Mod: 7940;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [Cisco-CP7940G/8.0] Transport: [sip:192.168.1.5:5060]

    21:43:22.828 [CM503001]: Call(27): Incoming call from Ext.1000 to <sip:4000@192.168.1.5>

    21:43:11.937 [CM503008]: Call(25): Call is terminated

    21:43:11.906 [CM503015]: Call(25): Attempt to reach <sip:1000@192.168.1.5;user=phone> failed. Reason: No Answer

    21:43:11.906 [CM503003]: Call(25): Call to sip:1000@192.168.1.5 has failed; Cause: 408 Request Timeout; internal

    21:43:05.859 [CM503008]: Call(26): Call is terminated

    21:43:05.859 [CM503015]: Call(26): Attempt to reach <sip:4000@192.168.1.5> failed. Reason: Busy

    21:43:05.843 [CM503015]: Call(26): Attempt to reach <sip:4000@192.168.1.5> failed. Reason: Busy

    21:43:05.843 [CM503014]: Call(26): No known route to target: <sip:4000@192.168.1.5>

    21:43:05.843 [CM503010]: Making route(s) to <sip:4000@192.168.1.5>

    21:43:05.843 [CM505001]: Ext.1000: Device info: Device Identified: [Man: Cisco;Mod: 7940;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [Cisco-CP7940G/8.0] Transport: [sip:192.168.1.5:5060]

    21:43:05.812 [CM503001]: Call(26): Incoming call from Ext.1000 to <sip:4000@192.168.1.5>

    21:42:39.843 [CM503024]: Call(25): Calling Ext:Ext.1000@[Dev:sip:1000@192.168.1.1:5061;transport=udp]
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,861
    Likes Received:
    302
    You don't have Ext 4000 set to use STUN do you? You don't need to do that if the set is on the same LAN as the 3CX. there was a reference to STUN in the logs and one of the failures was that that 3CX couldn't find a route to the set
     
  3. goochr96

    Joined:
    Aug 3, 2009
    Messages:
    12
    Likes Received:
    0
    Aaahh!! thank you very much, this worked!!

    Now my only problem seems to be that when I call from ex 4000 to 1000, everything works fine, however when I call from ex 1000 to 4000 it comes up with the No Answer problem again.

    Ex 1000 is a Cisco 7940
    Ex 4000 is a Cisco ATA 186 converter.

    Is the problem in this line here --
    18:06:29.562 [MS105000] C:10.1: No RTP packets were received:remoteAddr=192.168.1.1:16384,extAddr=0.0.0.0:0,localAddr=192.168.1.5:7032

    192.168.1.1 is my router and 192.168.1.5 is the 3CX Server

    18:06:40.437 [CM503008]: Call(11): Call is terminated
    18:06:40.421 [CM503015]: Call(11): Attempt to reach <sip:4000@192.168.1.5> failed. Reason: No Answer
    18:06:40.421 [CM503003]: Call(11): Call to sip:4000@192.168.1.5 has failed; Cause: 408 Request Timeout; internal
    18:06:29.562 [MS105000] C:10.1: No RTP packets were received:remoteAddr=192.168.1.1:16384,extAddr=0.0.0.0:0,localAddr=192.168.1.5:7032
    18:06:08.328 [CM503024]: Call(11): Calling Ext:Ext.4000@[Dev:sip:4000@192.168.1.1:5060;user=phone;transport=udp]
    18:06:08.312 [CM503004]: Call(11): Route 1: Ext:Ext.4000@[Dev:sip:4000@192.168.1.1:5060;user=phone;transport=udp]
    18:06:08.312 [CM503010]: Making route(s) to <sip:4000@192.168.1.5>
    18:06:08.296 [CM505001]: Ext.1000: Device info: Device Identified: [Man: Cisco;Mod: 7940;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [Cisco-CP7940G/8.0] Transport: [sip:192.168.1.5:5060]
    18:06:08.265 [CM503001]: Call(11): Incoming call from Ext.1000 to <sip:4000@192.168.1.5>
    18:05:57.453 [CM503008]: Call(10): Call is terminated
    18:05:57.437 [CM503008]: Call(10): Call is terminated
    18:05:55.484 [CM504008]: Fax Service: registered as sip:8888@192.168.1.5 with contact sip:8888@192.168.1.1:5060;user=phone;transport=udp
    18:05:53.875 [CM503007]: Call(10): Device joined: sip:1000@192.168.1.10:5061;transport=udp
    18:05:53.859 [CM503007]: Call(10): Device joined: sip:4000@192.168.1.1:5060;user=phone;transport=udp
    18:05:50.562 [CM505001]: Ext.1000: Device info: Device Identified: [Man: Cisco;Mod: 7940;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [Cisco-CP7940G/8.0] Transport: [sip:192.168.1.5:5060]
    18:05:50.562 [CM503002]: Call(10): Alerting sip:1000@192.168.1.10:5061;transport=udp
    18:05:50.250 [CM503024]: Call(10): Calling Ext:Ext.1000@[Dev:sip:1000@192.168.1.10:5061;transport=udp]
    18:05:50.234 [CM503004]: Call(10): Route 1: Ext:Ext.1000@[Dev:sip:1000@192.168.1.10:5061;transport=udp]
    18:05:50.234 [CM503010]: Making route(s) to <sip:1000@192.168.1.5;user=phone>
    18:05:50.234 [CM505001]: Ext.4000: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Cisco ATA 186 v3.1.0 atasip (040211A)] Transport: [sip:192.168.1.5:5060]
    18:05:50.203 [CM503001]: Call(10): Incoming call from Ext.4000 to <sip:1000@192.168.1.5;user=phone>
    18:05:42.734 [CM504001]: Ext.4000: new contact is registered. Contact(s): [sip:4000@192.168.1.1:5060;user=phone;transport=udp/4000]
     
  4. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,861
    Likes Received:
    302
    I'm wondering why you have Ext 4000 also using IP 192.168.1.1? It is already being used by the router on your network. You might want to try changing that phones IP to another, higher (unused) IP.
     
  5. goochr96

    Joined:
    Aug 3, 2009
    Messages:
    12
    Likes Received:
    0
    This is interesting, because that extension (4000) is assigned the ip 192.168.1.13 from the DHCP, if I ask the ATA for it's IP its says 13. Also the config page on the box says

    ata000e38fbe99c
    Version: v3.1.0 atasip (Build 040211A)
    DHCP Assigned: IP[192.168.1.13] Subnet[255.255.255.0] Route[192.168.1.1]
    MAC: 0.14.56.251.233.156
    SerialNumber: INM074611ZE
    ProductId: ATA186I2
    Features: 0x00000000
    HardwareVersion: 0x0006 0x0000

    So i'm not sure where 3CX is getting the impression that 4000 is at 192.168.1.1 ??

    Any ideas?
     
  6. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,861
    Likes Received:
    302
    It's best not to allow the sets on the local LAN to use DHCP especially when testing a new setup. Give it a fixed IP and see how it goes.

    What is that "route" setting? If that can be changed then set it to the same as the IP.
     
  7. meshad

    Joined:
    Aug 5, 2009
    Messages:
    41
    Likes Received:
    0
    I also have faced same issue.

    im using Gigaset S450IP -ext 300 and X-lite -101

    when i cal from 101 to 300 nothing happen no ring no ans and sys log shows 101 dialing and 300 registion ok ( not ringing)

    but 300 to 101 ok working

    im using at smae LAN. is that DHCP issue?
     
  8. goochr96

    Joined:
    Aug 3, 2009
    Messages:
    12
    Likes Received:
    0
    Okay, do you mean this line here

    18:06:08.312 [CM503004]: Call(11): Route 1: Ext:Ext.4000@[Dev:sip:4000@192.168.1.1:5060;user=phone;transport=udp]

    Where it says 'Route 1:'

    Is that something that i wouild have generated somewhere? I have the 3CX for Skype setup installed too. Not tested that bit yet, so unsure as to wether that side is working.
     
  9. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,861
    Likes Received:
    302
    I was referring to the "route" in this listing you posted.

    DHCP Assigned: IP[192.168.1.13] Subnet[255.255.255.0] Route[192.168.1.1]

    Does that refer to the IP of your router or is it something you can change?
     
  10. goochr96

    Joined:
    Aug 3, 2009
    Messages:
    12
    Likes Received:
    0
    That is what i copied and pasted from the ATA config page. Yes 192.168.1.1 is my router. I was wondering if deleting the extension, and re doing it might help?
     
  11. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,861
    Likes Received:
    302
    That certainly can't hurt. Before you do, try powering down Extension 4000, then have a look at the 3CX logs to see what IP it thinks the set is using when it re-registers. If it still shows the same IP as your router then that's is going to be the problem. Try the set with a fixed IP.
     
  12. goochr96

    Joined:
    Aug 3, 2009
    Messages:
    12
    Likes Received:
    0
    Okay, so I have powered down (still showed as registered in the extension status page when powered down too!!) and rebooted Ex 4000, still registers it as being at 192.168.1.1 so I thought I would delete it and re do it. Wasn't able to delete it, 3CX would not let me. Could delete any others just not that one. So I change all of the passwords and ID's to something obscure and incorrect, then it was not registered. Still couldn't delete it. So created new Ex 4000, that registered itself as being at 192.168.1.1 too. Deleted that one (was able to do that one) re configured the old one that I had 'put out of service' back to Ex 4000 (registered again) On the device itself I have turned off DHCP and given it static IP address's (192.168.1.13) static subnet, and gateway. Still comes up as 192.168.1.1
    ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    As I was typing this I was also giving a few things a try. I changed have changed the NATIP within the ATA from 192.168.1.1 to 192.168.1.13 and, hey presto (Although I thought that NAT was Network Address Translation) real would IP to internal IP thus I had it set to my router. Oh well line now being registered at the correct address :) happy!! And phone calls work both way's round too!! Thankyou very much to all that helped!
     
  13. goochr96

    Joined:
    Aug 3, 2009
    Messages:
    12
    Likes Received:
    0
    Now all i have to work out is why the '0' is being dropped off calls I am making


    22:32:56.375 [CM504001]: Ext.1500: new contact is registered. Contact(s): [sip:1500@192.168.1.10:5061;transport=udp/1500]

    22:32:56.109 [CM504001]: Ext.1000: new contact is registered. Contact(s): [sip:1000@192.168.1.10:5061;transport=udp/1000]

    22:32:55.984 [CM504001]: Ext.1000: new contact is registered. Contact(s): [sip:1000@192.168.1.10:5061;transport=udp/1000]

    22:28:47.515 [CM503008]: Call(37): Call is terminated

    22:28:47.515 [CM503008]: Call(37): Call is terminated

    22:28:38.437 [CM503007]: Call(37): Device joined: sip:10001@192.168.1.14:5062

    22:28:38.406 [CM503007]: Call(37): Device joined: sip:4000@192.168.1.13:5060;user=phone;transport=udp

    22:28:38.390 [CM505002]: Gateway:[Cisco SPA-3102] Device info: Device Identified: [Man: Linksys;Mod: SPA Series;Rev: General] Capabilities:[reinvite, no-replaces, able-no-sdp, recvonly] UserAgent: [Linksys/SPA3102-3.3.6(GW)] Transport: [sip:192.168.1.5:5060]

    22:28:38.390 [CM503002]: Call(37): Alerting sip:10001@192.168.1.14:5062

    22:28:38.328 [CM503024]: Call(37): Calling PSTNline:7760******@(Ln.10001@Cisco SPA-3102)@[Dev:sip:10001@192.168.1.14:5062]

    22:28:38.312 [CM503004]: Call(37): Route 1: PSTNline:7760******@(Ln.10001@Cisco SPA-3102)@[Dev:sip:10001@192.168.1.14:5062]

    22:28:38.281 [CM503010]: Making route(s) to <sip:07760******@192.168.1.5;user=phone>
     
  14. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,861
    Likes Received:
    302
    You aren't stripping off any digits in the outbound rules are you?
     
  15. Discovery Technology

    Joined:
    Apr 19, 2008
    Messages:
    278
    Likes Received:
    0
    Are you using a dialplan for the handsets as well?

    ie:

    dialplan.xml in your TFTP Server
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  16. goochr96

    Joined:
    Aug 3, 2009
    Messages:
    12
    Likes Received:
    0
    Yes I am using dialplan.xml Here is the contents......
    I'm not sure what any of it mean!!!

    <DIALTEMPLATE>

    <TEMPLATE MATCH="0" Timeout="1" User="Phone"/> <!-- Local operator-->

    <TEMPLATE MATCH="9,011*" Timeout="6" User="Phone"/> <!-- International calls-->

    <TEMPLATE MATCH="9,0" Timeout="8" User="Phone"/> <!-- PSTN Operator-->

    <TEMPLATE MATCH="9,11" Timeout="0" User="Phone" Route="Emergency" Rewrite="9911"/>

    <TEMPLATE MATCH="w!" Timeout="1" User="PHONE" Route="Emergency" Rewrite="9911"/>

    <TEMPLATE MATCH="9,.11" Timeout="0" User="Phone"/> <!-- Service numbers -->

    T<TEMPLATE MATCH="9,1.........." Timeout="0" User="Phone"/> <!-- Long Distance -->

    <TEMPLATE MATCH="9,......." Timeout="0" User="Phone"/> <!-- Local numbers -->

    <TEMPLATE MATCH="2..." Timeout="0" User="Phone"/> <!-- Corporate Dial plan-->

    <TEMPLATE MATCH="3..." Timeout="0" User="Phone"/> <!-- Corporate Dial plan-->

    <TEMPLATE MATCH="*" Timeout="15"/> <!-- Anything else -->

    <TEMPLATE MATCH="123#45#6" Timeout="0" User="Phone"/> <!-- Match `#' -->

    <TEMPLATE MATCH="12\*345" Timeout="0" User="Phone"/> <!-- Match * Char -->

    <TEMPLATE MATCH="8,...." TIMEOUT="0" Tone="Bellcore-Hold" /> <!-- Play Hold -->

    <TEMPLATE MATCH="8,123,...." TIMEOUT="0" Tone="Bellcore-Hold" Tone="Cisco-Zip" /> <!--Play Hold after 8, Play Zip Tone after 123-->

    </DIALTEMPLATE>
     
Thread Status:
Not open for further replies.