Jump to content

404 not found error


halican
 Share

Recommended Posts

Hi

I installed pbxnsip today for testing.

I sucesfully register clients and they can communicate with each other.

The problem is with my trunk.I can use this trunk with my pap2t and no problem with it but when i try to use it with pbx "i got 404 not found" error

The trunk is registering succesfuly and no problem with dial plan.I tried lots of codecs but no way.

 

 

 

You can find log details below.

 

My dial plan format is : 90 + area code + tel number

 

Thanks.

 

 

 

[5] 2009/09/22 14:08:02: Dialplan Standard Dialplan: Match 9011902122691555@89.19.4.162 to <sip:902122691555@89.149.244.206;user=phone> on trunk proyturk

[5] 2009/09/22 14:08:02: INVITE Response 404 Not Found: Terminate 56bf2388@pbx

Link to comment
Share on other sites

Hi

I installed pbxnsip today for testing.

I sucesfully register clients and they can communicate with each other.

The problem is with my trunk.I can use this trunk with my pap2t and no problem with it but when i try to use it with pbx "i got 404 not found" error

The trunk is registering succesfuly and no problem with dial plan.I tried lots of codecs but no way.

 

 

 

You can find log details below.

 

My dial plan format is : 90 + area code + tel number

 

Thanks.

 

 

 

[5] 2009/09/22 14:08:02: Dialplan Standard Dialplan: Match 9011902122691555@89.19.4.162 to <sip:902122691555@89.149.244.206;user=phone> on trunk proyturk

[5] 2009/09/22 14:08:02: INVITE Response 404 Not Found: Terminate 56bf2388@pbx

 

 

can you set the logfile to 7 so we can see more information. also set the log sip events on

Link to comment
Share on other sites

can you set the logfile to 7 so we can see more information. also set the log sip events on

 

OK you can find the 7 level log file information below.

 

[7] 2009/09/24 15:19:10: SIP Rx udp:78.191.119.125:14256:

REGISTER sip:89.19.4.162 SIP/2.0

Via: SIP/2.0/UDP 78.191.119.125:14256;branch=z9hG4bK-d8754z-0534b431d65dc70f-1---d8754z-;rport

Max-Forwards: 70

Contact: <sip:41@78.191.119.125:14256;rinstance=0d0f70c211751aba>

To: "41"<sip:41@89.19.4.162>

From: "41"<sip:41@89.19.4.162>;tag=be39c166

Call-ID: NjRkNjgwYzJmNWEyYWE3MGNkZjgxMTEzZGE4NjdiZmU.

CSeq: 45 REGISTER

Expires: 3600

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO

User-Agent: X-Lite release 1103k stamp 53621

Authorization: Digest username="41",realm="89.19.4.162",nonce="fd6885f476fb74b5cec538d7ffb4f9ff",uri="sip:89.19.4.162",response="ec15513f88a4107b82a8228c4a0df5fd",algorithm=MD5

Content-Length: 0

 

 

[7] 2009/09/24 15:19:10: SIP Tx udp:78.191.119.125:14256:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 78.191.119.125:14256;branch=z9hG4bK-d8754z-0534b431d65dc70f-1---d8754z-;rport=14256

From: "41" <sip:41@89.19.4.162>;tag=be39c166

To: "41" <sip:41@89.19.4.162>;tag=f51ec18e4a

Call-ID: NjRkNjgwYzJmNWEyYWE3MGNkZjgxMTEzZGE4NjdiZmU.

CSeq: 45 REGISTER

Contact: <sip:41@78.191.119.125:14256;rinstance=0d0f70c211751aba>;expires=32

Content-Length: 0

 

 

[7] 2009/09/24 15:19:38: SIP Rx udp:78.191.119.125:14256:

REGISTER sip:89.19.4.162 SIP/2.0

Via: SIP/2.0/UDP 78.191.119.125:14256;branch=z9hG4bK-d8754z-323c730f2b3dbf28-1---d8754z-;rport

Max-Forwards: 70

Contact: <sip:41@78.191.119.125:14256;rinstance=0d0f70c211751aba>

To: "41"<sip:41@89.19.4.162>

From: "41"<sip:41@89.19.4.162>;tag=be39c166

Call-ID: NjRkNjgwYzJmNWEyYWE3MGNkZjgxMTEzZGE4NjdiZmU.

CSeq: 46 REGISTER

Expires: 3600

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO

User-Agent: X-Lite release 1103k stamp 53621

Authorization: Digest username="41",realm="89.19.4.162",nonce="fd6885f476fb74b5cec538d7ffb4f9ff",uri="sip:89.19.4.162",response="ec15513f88a4107b82a8228c4a0df5fd",algorithm=MD5

Content-Length: 0

 

 

[7] 2009/09/24 15:19:38: SIP Tx udp:78.191.119.125:14256:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 78.191.119.125:14256;branch=z9hG4bK-d8754z-323c730f2b3dbf28-1---d8754z-;rport=14256

From: "41" <sip:41@89.19.4.162>;tag=be39c166

To: "41" <sip:41@89.19.4.162>;tag=f51ec18e4a

Call-ID: NjRkNjgwYzJmNWEyYWE3MGNkZjgxMTEzZGE4NjdiZmU.

CSeq: 46 REGISTER

Contact: <sip:41@78.191.119.125:14256;rinstance=0d0f70c211751aba>;expires=31

Content-Length: 0

 

 

[7] 2009/09/24 15:19:41: SIP Rx udp:78.191.119.125:14256:

INVITE sip:9902122352045@89.19.4.162 SIP/2.0

Via: SIP/2.0/UDP 78.191.119.125:14256;branch=z9hG4bK-d8754z-7a69001d500fca59-1---d8754z-;rport

Max-Forwards: 70

Contact: <sip:41@78.191.119.125:14256>

To: "9902122352045"<sip:9902122352045@89.19.4.162>

From: "41"<sip:41@89.19.4.162>;tag=2d6afa16

Call-ID: NTc3ZGZmMGY4MjcyZTdlZTZjZjIxMTM3Yzk4ZWM5ZTI.

CSeq: 1 INVITE

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO

Content-Type: application/sdp

User-Agent: X-Lite release 1103k stamp 53621

Content-Length: 268

 

v=0

o=- 5 2 IN IP4 192.168.1.101

s=CounterPath X-Lite 3.0

c=IN IP4 78.191.119.125

t=0 0

m=audio 36146 RTP/AVP 107 0 8 101

a=alt:1 1 : 8HP5POE2 aEyqgBc4 192.168.1.101 36146

a=fmtp:101 0-15

a=rtpmap:107 BV32/16000

a=rtpmap:101 telephone-event/8000

a=sendrecv

 

[7] 2009/09/24 15:19:41: SIP Tx udp:78.191.119.125:14256:

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 78.191.119.125:14256;branch=z9hG4bK-d8754z-7a69001d500fca59-1---d8754z-;rport=14256

From: "41" <sip:41@89.19.4.162>;tag=2d6afa16

To: "9902122352045" <sip:9902122352045@89.19.4.162>;tag=096fd4efd3

Call-ID: NTc3ZGZmMGY4MjcyZTdlZTZjZjIxMTM3Yzk4ZWM5ZTI.

CSeq: 1 INVITE

Content-Length: 0

 

 

[7] 2009/09/24 15:19:41: SIP Tx udp:78.191.119.125:14256:

SIP/2.0 401 Authentication Required

Via: SIP/2.0/UDP 78.191.119.125:14256;branch=z9hG4bK-d8754z-7a69001d500fca59-1---d8754z-;rport=14256

From: "41" <sip:41@89.19.4.162>;tag=2d6afa16

To: "9902122352045" <sip:9902122352045@89.19.4.162>;tag=096fd4efd3

Call-ID: NTc3ZGZmMGY4MjcyZTdlZTZjZjIxMTM3Yzk4ZWM5ZTI.

CSeq: 1 INVITE

User-Agent: pbxnsip-PBX/3.4.0.3201

WWW-Authenticate: Digest realm="89.19.4.162",nonce="efd429723a825aed4d65aab2180dee94",domain="sip:9902122352045@89.19.4.162",algorithm=MD5

Content-Length: 0

 

 

[7] 2009/09/24 15:19:41: SIP Rx udp:78.191.119.125:14256:

ACK sip:9902122352045@89.19.4.162 SIP/2.0

Via: SIP/2.0/UDP 78.191.119.125:14256;branch=z9hG4bK-d8754z-7a69001d500fca59-1---d8754z-;rport

To: "9902122352045" <sip:9902122352045@89.19.4.162>;tag=096fd4efd3

From: "41"<sip:41@89.19.4.162>;tag=2d6afa16

Call-ID: NTc3ZGZmMGY4MjcyZTdlZTZjZjIxMTM3Yzk4ZWM5ZTI.

CSeq: 1 ACK

Content-Length: 0

 

 

[7] 2009/09/24 15:19:41: SIP Rx udp:78.191.119.125:14256:

INVITE sip:9902122352045@89.19.4.162 SIP/2.0

Via: SIP/2.0/UDP 78.191.119.125:14256;branch=z9hG4bK-d8754z-9406f8398e10c740-1---d8754z-;rport

Max-Forwards: 70

Contact: <sip:41@78.191.119.125:14256>

To: "9902122352045"<sip:9902122352045@89.19.4.162>

From: "41"<sip:41@89.19.4.162>;tag=2d6afa16

Call-ID: NTc3ZGZmMGY4MjcyZTdlZTZjZjIxMTM3Yzk4ZWM5ZTI.

CSeq: 2 INVITE

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO

Content-Type: application/sdp

User-Agent: X-Lite release 1103k stamp 53621

Authorization: Digest username="41",realm="89.19.4.162",nonce="efd429723a825aed4d65aab2180dee94",uri="sip:9902122352045@89.19.4.162",response="63533a1e7ec8c16507242ea11375d760",algorithm=MD5

Content-Length: 268

 

v=0

o=- 5 2 IN IP4 192.168.1.101

s=CounterPath X-Lite 3.0

c=IN IP4 78.191.119.125

t=0 0

m=audio 36146 RTP/AVP 107 0 8 101

a=alt:1 1 : 8HP5POE2 aEyqgBc4 192.168.1.101 36146

a=fmtp:101 0-15

a=rtpmap:107 BV32/16000

a=rtpmap:101 telephone-event/8000

a=sendrecv

 

[6] 2009/09/24 15:19:41: Sending RTP for NTc3ZGZmMGY4MjcyZTdlZTZjZjIxMTM3Yzk4ZWM5ZTI.#096fd4efd3 to 78.191.119.125:36146

[7] 2009/09/24 15:19:41: SIP Tx udp:78.191.119.125:14256:

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 78.191.119.125:14256;branch=z9hG4bK-d8754z-9406f8398e10c740-1---d8754z-;rport=14256

From: "41" <sip:41@89.19.4.162>;tag=2d6afa16

To: "9902122352045" <sip:9902122352045@89.19.4.162>;tag=096fd4efd3

Call-ID: NTc3ZGZmMGY4MjcyZTdlZTZjZjIxMTM3Yzk4ZWM5ZTI.

CSeq: 2 INVITE

Content-Length: 0

 

 

[5] 2009/09/24 15:19:41: Dialplan Standard Dialplan: Match 9902122352045@89.19.4.162 to <sip:902122352045@89.149.244.206;user=phone> on trunk pry

[7] 2009/09/24 15:19:41: SIP Tx udp:89.149.244.206:5060:

INVITE sip:902122352045@89.149.244.206;user=phone SIP/2.0

Via: SIP/2.0/UDP 89.19.4.165:5060;branch=z9hG4bK-b2d484122b57a25cf73115fd9ad3124e;rport

From: "Anonymous" <sip:anonymous@anonymous.invalid>;tag=24213

To: <sip:902122352045@89.149.244.206;user=phone>

Call-ID: 838cdb80@pbx

CSeq: 6247 INVITE

Max-Forwards: 70

Contact: <sip:actuelbil@89.19.4.165:5060;transport=udp>

Supported: 100rel, replaces, norefersub

Allow-Events: refer

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Accept: application/sdp

User-Agent: pbxnsip-PBX/3.4.0.3201

P-Asserted-Identity: "PRY" <sip:actuelbil@89.149.244.206>

Privacy: id

Content-Type: application/sdp

Content-Length: 286

 

v=0

o=- 2690 2690 IN IP4 89.19.4.165

s=-

c=IN IP4 89.19.4.165

t=0 0

m=audio 62902 RTP/AVP 0 8 9 2 3 101

a=rtpmap:0 pcmu/8000

a=rtpmap:8 pcma/8000

a=rtpmap:9 g722/8000

a=rtpmap:2 g726-32/8000

a=rtpmap:3 gsm/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=sendrecv

 

[6] 2009/09/24 15:19:41: Send codec pcmu/8000

[7] 2009/09/24 15:19:41: SIP Tx udp:78.191.119.125:14256:

SIP/2.0 183 Ringing

Via: SIP/2.0/UDP 78.191.119.125:14256;branch=z9hG4bK-d8754z-9406f8398e10c740-1---d8754z-;rport=14256

From: "41" <sip:41@89.19.4.162>;tag=2d6afa16

To: "9902122352045" <sip:9902122352045@89.19.4.162>;tag=096fd4efd3

Call-ID: NTc3ZGZmMGY4MjcyZTdlZTZjZjIxMTM3Yzk4ZWM5ZTI.

CSeq: 2 INVITE

Contact: <sip:41@89.19.4.165:5060>

Supported: 100rel, replaces, norefersub

Allow-Events: refer

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Accept: application/sdp

User-Agent: pbxnsip-PBX/3.4.0.3201

Content-Type: application/sdp

Content-Length: 214

 

v=0

o=- 60512 60512 IN IP4 89.19.4.165

s=-

c=IN IP4 89.19.4.165

t=0 0

m=audio 58792 RTP/AVP 0 8 101

a=rtpmap:0 pcmu/8000

a=rtpmap:8 pcma/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=sendrecv

 

[7] 2009/09/24 15:19:41: SIP Rx udp:89.149.244.206:5060:

SIP/2.0 407 Proxy Authentication Required

CSeq: 6247 INVITE

Via: SIP/2.0/UDP 89.19.4.165:5060;branch=z9hG4bK-b2d484122b57a25cf73115fd9ad3124e;rport

From: "Anonymous" <sip:anonymous@anonymous.invalid>;tag=24213

Call-ID: 838cdb80@pbx

To: <sip:902122352045@89.149.244.206;user=phone>;tag=240922092232119268731210233

Contact: <sip:89.149.244.206:5060;transport=udp>

Proxy-Authenticate: DIGEST realm="VoipSwitch", nonce="125382015224221026709223238438"

Content-Length: 0

 

 

[7] 2009/09/24 15:19:41: SIP Tx udp:89.149.244.206:5060:

ACK sip:902122352045@89.149.244.206;user=phone SIP/2.0

Via: SIP/2.0/UDP 89.19.4.165:5060;branch=z9hG4bK-b2d484122b57a25cf73115fd9ad3124e;rport

From: "Anonymous" <sip:anonymous@anonymous.invalid>;tag=24213

To: <sip:902122352045@89.149.244.206;user=phone>;tag=240922092232119268731210233

Call-ID: 838cdb80@pbx

CSeq: 6247 ACK

Max-Forwards: 70

Content-Length: 0

 

 

[7] 2009/09/24 15:19:41: SIP Tx udp:89.149.244.206:5060:

INVITE sip:902122352045@89.149.244.206;user=phone SIP/2.0

Via: SIP/2.0/UDP 89.19.4.165:5060;branch=z9hG4bK-7f141dd69ef7a10eeb30cf5612d603b9;rport

From: "Anonymous" <sip:anonymous@anonymous.invalid>;tag=24213

To: <sip:902122352045@89.149.244.206;user=phone>

Call-ID: 838cdb80@pbx

CSeq: 6248 INVITE

Max-Forwards: 70

Contact: <sip:actuelbil@89.19.4.165:5060;transport=udp>

Supported: 100rel, replaces, norefersub

Allow-Events: refer

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Accept: application/sdp

User-Agent: pbxnsip-PBX/3.4.0.3201

P-Asserted-Identity: "PRY" <sip:actuelbil@89.149.244.206>

Privacy: id

Proxy-Authorization: Digest realm="VoipSwitch",nonce="125382015224221026709223238438",response="7ee94b3f58dcf8742b10e68180862517",username="actuelbil",uri="sip:902122352045@89.149.244.206;user=phone",algorithm=MD5

Content-Type: application/sdp

Content-Length: 286

 

v=0

o=- 2690 2690 IN IP4 89.19.4.165

s=-

c=IN IP4 89.19.4.165

t=0 0

m=audio 62902 RTP/AVP 0 8 9 2 3 101

a=rtpmap:0 pcmu/8000

a=rtpmap:8 pcma/8000

a=rtpmap:9 g722/8000

a=rtpmap:2 g726-32/8000

a=rtpmap:3 gsm/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=sendrecv

 

[7] 2009/09/24 15:19:42: SIP Rx udp:89.149.244.206:5060:

SIP/2.0 404 Not Found

CSeq: 6248 INVITE

Via: SIP/2.0/UDP 89.19.4.165:5060;branch=z9hG4bK-7f141dd69ef7a10eeb30cf5612d603b9;rport

From: "Anonymous" <sip:anonymous@anonymous.invalid>;tag=24213

Call-ID: 838cdb80@pbx

To: <sip:902122352045@89.149.244.206;user=phone>;tag=240922092232119268731210233

Contact: <sip:89.149.244.206:5060;transport=udp>

Content-Length: 0

 

 

[7] 2009/09/24 15:19:42: Call 838cdb80@pbx#24213: Clear last INVITE

[7] 2009/09/24 15:19:42: SIP Tx udp:89.149.244.206:5060:

ACK sip:902122352045@89.149.244.206;user=phone SIP/2.0

Via: SIP/2.0/UDP 89.19.4.165:5060;branch=z9hG4bK-7f141dd69ef7a10eeb30cf5612d603b9;rport

From: "Anonymous" <sip:anonymous@anonymous.invalid>;tag=24213

To: <sip:902122352045@89.149.244.206;user=phone>;tag=240922092232119268731210233

Call-ID: 838cdb80@pbx

CSeq: 6248 ACK

Max-Forwards: 70

Contact: <sip:actuelbil@89.19.4.165:5060;transport=udp>

P-Asserted-Identity: "PRY" <sip:actuelbil@89.149.244.206>

Privacy: id

Content-Length: 0

 

 

[5] 2009/09/24 15:19:42: INVITE Response 404 Not Found: Terminate 838cdb80@pbx

[7] 2009/09/24 15:19:42: Other Ports: 1

[7] 2009/09/24 15:19:42: Call Port: NTc3ZGZmMGY4MjcyZTdlZTZjZjIxMTM3Yzk4ZWM5ZTI.#096fd4efd3

[7] 2009/09/24 15:19:42: SIP Tx udp:78.191.119.125:14256:

SIP/2.0 404 Not Found

Via: SIP/2.0/UDP 78.191.119.125:14256;branch=z9hG4bK-d8754z-9406f8398e10c740-1---d8754z-;rport=14256

From: "41" <sip:41@89.19.4.162>;tag=2d6afa16

To: "9902122352045" <sip:9902122352045@89.19.4.162>;tag=096fd4efd3

Call-ID: NTc3ZGZmMGY4MjcyZTdlZTZjZjIxMTM3Yzk4ZWM5ZTI.

CSeq: 2 INVITE

Contact: <sip:41@89.19.4.165:5060>

Supported: 100rel, replaces, norefersub

Allow-Events: refer

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Accept: application/sdp

User-Agent: pbxnsip-PBX/3.4.0.3201

Content-Length: 0

 

 

[7] 2009/09/24 15:19:42: SIP Rx udp:78.191.119.125:14256:

ACK sip:9902122352045@89.19.4.162 SIP/2.0

Via: SIP/2.0/UDP 78.191.119.125:14256;branch=z9hG4bK-d8754z-9406f8398e10c740-1---d8754z-;rport

To: "9902122352045" <sip:9902122352045@89.19.4.162>;tag=096fd4efd3

From: "41"<sip:41@89.19.4.162>;tag=2d6afa16

Call-ID: NTc3ZGZmMGY4MjcyZTdlZTZjZjIxMTM3Yzk4ZWM5ZTI.

CSeq: 2 ACK

Content-Length: 0

Link to comment
Share on other sites

[7] 2009/09/24 15:19:42: SIP Rx udp:89.149.244.206:5060:

SIP/2.0 404 Not Found

 

 

89.149.244.206 is rejecting the call.

 

Couple of things you can check before contacting "pry" trunk provider. That is to check whether extension 41 has "Block outgoing caller-ID" is set to "yes". Other thing you can try is different settings on the "Remote Party/Privacy Indication" field on this trunk on the PBX side. This field generally controls what is being sent out.

Link to comment
Share on other sites

[7] 2009/09/24 15:19:42: SIP Rx udp:89.149.244.206:5060:

SIP/2.0 404 Not Found

 

 

89.149.244.206 is rejecting the call.

 

Couple of things you can check before contacting "pry" trunk provider. That is to check whether extension 41 has "Block outgoing caller-ID" is set to "yes". Other thing you can try is different settings on the "Remote Party/Privacy Indication" field on this trunk on the PBX side. This field generally controls what is being sent out.

 

Thanks for reply.

 

My "Block outgoing caller id " is set "YES" and i have tried all the parameters on the "Remote Party / Pricacy Indication" field but i am stil getting "404 Not Found Error"

 

When i try another provider for example 12Voip there is no problem. The main problem is i can not get connect with my main providers. I am thinking use this PBX with my customers but to connect my providers is very important.The turkish voice support is working fine.I think i can sell this product to my customers if i can solve all the problems

 

 

Thanks for all.

 

Halim YESIL.

Link to comment
Share on other sites

Thanks for reply.

 

My "Block outgoing caller id " is set "YES" and i have tried all the parameters on the "Remote Party / Pricacy Indication" field but i am stil getting "404 Not Found Error"

 

When i try another provider for example 12Voip there is no problem. The main problem is i can not get connect with my main providers. I am thinking use this PBX with my customers but to connect my providers is very important.The turkish voice support is working fine.I think i can sell this product to my customers if i can solve all the problems

 

 

Thanks for all.

 

Halim YESIL.

 

I guess, the point I was trying to make was if you set "Block outgoing caller id " to "No", your call should go through.

Link to comment
Share on other sites

  • 10 months later...
  • 2 years later...

Ive got a similar issue.

 

The trunk is up, I can call out. The DID is active.

 

But when I call in the call gets rejected with a 404 not found.

 

This is something on the domain. I have tried the same trunk creds on the same box, but different domain and it works. I can call in and out. If I move the same trunk to the defective domain it breaks.

 

All the trunk settings are the same. I have no idea what this issue is and suspect it may be a bug.

 

Anyone have any ideas?

Link to comment
Share on other sites

Check:

 

Is the INVITE coming from the same IP address where the PBX registered?

 

Do you have multiple domains? If the answer if yes, is the trunk in the right domain? If it is global, do the alias names (DID) of the accounts have a global number? You can check that in the user_alias directory.

 

Does it work when you enter e.g. the auto attendant in the field "send call to extension"? If yes, then the problem if finding the right destination in the domain.

Link to comment
Share on other sites

Check:

 

Is the INVITE coming from the same IP address where the PBX registered?

 

Do you have multiple domains? If the answer if yes, is the trunk in the right domain? If it is global, do the alias names (DID) of the accounts have a global number? You can check that in the user_alias directory.

 

Does it work when you enter e.g. the auto attendant in the field "send call to extension"? If yes, then the problem if finding the right destination in the domain.

 

The invite it coming from mu voip switch box to the pbx.

 

The trunk is on the right domain and its not global.

 

If I dial the DID from a device registered on the domain, it rings through and I get the voice mailbox.

Link to comment
Share on other sites

So I finally just deleted the domain and started over.

 

I think I may know what the issue was.

 

Initially, I was coping and pasting the numbers from an excel spread sheet and I think this is what caused the issue.

 

This second time around I was inputing the DID's (not c/p them over) and I noticed when I hit save, the system would add the dashes between the DID (XXX-XXX-XXXX). Its now working.

 

Cant say for sure that this was the issue, but this is not the first time c/p has led me astray.

 

Thx

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...