Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Inbound Routing to Ext#

Discussion in '3CX Phone System - General' started by netcom12, Dec 31, 2009.

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

    Jun 4, 2009
    Likes Received:
    I'm having some problem - likely due to my lack of understanding of SIP. Here we go:

    I have a flowroute account setup w/ 2 numbers. Registration works great - both numbers ring in fine. BUT, both numbers just route to my primary ext#101 - I can't figure out the inbound routing to get it t work.

    I've setup a DID for the second number and told it to ring on ext#102

    I see in the server log the error - but don't know what to set in the 'Source ID' to get it to route correctly. Any help would be great! Here is the in the server log. Calling from 15551237654 TO 15551234567: (changed numbers)

    14:25:45.415 [CM500002]: Unidentified incoming call. Review INVITE and adjust source identification:
    INVITE sip:15551234567@xxx.xxx.xxx.xxx SIP/2.0
    Via: SIP/2.0/UDP xxx.xxx.xxx.xxx;branch=z9hG4bK90c8.17bc68b7b8a9a8df783158c1b49b569c.0
    Via: SIP/2.0/UDP xxx.xxx.xxx.xxx;branch=z9hG4bK90c8.0d9e3919f6465a307becb1d61f7bbf66.0
    Via: SIP/2.0/UDP xxx.xxx.xxx.xxx;branch=z9hG4bK90c8.41df54d05d9f1ed33ef7540764773104.0
    Via: SIP/2.0/UDP xxx.xxx.xxx.xxx:5060;branch=z9hG4bK34948010c0vhjd0u27s1.1
    Max-Forwards: 14
    Record-Route: <sip:xxx.xxx.xxx.xxx;lr>
    Record-Route: <sip:xxx.xxx.xxx.xxx;lr>
    Contact: <sip:+15551237654@xxx.xxx.xxx.xxx:5060;transport=udp>
    To: <sip:+15551234567@xxx.xxx.xxx.xxx:5060>
    From: <sip:+15551237654@xxx.xxx.xxx.xxx>;tag=1361326
    Call-ID: 1261683158-6582020@LA4_SIP_01
    CSeq: 1 INVITE
    Expires: 330
    P-Asserted-Identity: <sip:+15551237654@pstn>
    Content-Length: 0
  2. tuxiteer

    Dec 26, 2009
    Likes Received:
    Have you created a unique inbound rule for each of your DID numbers?

    Within the inbound rule, make sure to specify the DID you wish to route and only select the port associated with your inbound channel in the associated rule. For example,

    If I have an inbound channel setup as Port 10000, and my phone number is 12345551212 your inbound rule may look as follows:

    DID Name: Main Number 123
    DID Number: 12345551212
    Available Ports: 10000 [Main Number 123]
    Office Hours: Connect to Extension = 101

    DID Name: Second Number 456
    DID Number: 14565551212
    Available Ports: 10001 [Second Number 456]
    Office Hours: Connect to Extension = 102

    Also check to see if you have an * as a number mask match. What could also be happening is that the system isn't able to identify your inbound DID and is getting caught in your "catch all".
Thread Status:
Not open for further replies.