Jump to content

Dial Plan Trouble Updtae


Bill H
 Share

Recommended Posts

Well I have been hacking away at this problem and finally went to the Logging area.

 

[7] 2007/08/17 20:56:08: UDP: Opening socket on port 57004

[7] 2007/08/17 20:56:08: UDP: Opening socket on port 57005

[5] 2007/08/17 20:56:08: Identify trunk 3

[8] 2007/08/17 20:56:08: Resolve destination 253992: a udp 78.123.102.224 33665

[8] 2007/08/17 20:56:08: Resolve destination 253992: udp78.123.102.224 33665

[8] 2007/08/17 20:56:08: Send Packet 100

[6] 2007/08/17 20:56:08: Sending RTP to 78.123.102.224:3000

[8] 2007/08/17 20:56:08: Play audio_moh/noise.wav

[7] 2007/08/17 20:56:08: UDP: Opening socket on port 49594

[7] 2007/08/17 20:56:08: UDP: Opening socket on port 49595

[8] 2007/08/17 20:56:08: Resolve destination 253993: url sip:*8212122261234@192.168.1.160;user=phone

[8] 2007/08/17 20:56:08: Resolve destination 253993: udp 192.168.1.160 5060

[8] 2007/08/17 20:56:08: Send Packet INVITE

[8] 2007/08/17 20:56:08: Resolve destination 253994: a udp 78.123.102.224 33665

[8] 2007/08/17 20:56:08: Resolve destination 253994: udp 78.123.102.224 33665

[8] 2007/08/17 20:56:08: Send Packet 183

[8] 2007/08/17 20:56:08: Resolve destination 253995: url sip:*8212122261234@192.168.1.160;user=phone

[8] 2007/08/17 20:56:08: Resolve destination 253995: udp 192.168.1.160 5060

[8] 2007/08/17 20:56:08: Send Packet ACK

[5] 2007/08/17 20:56:08: INVITE Response: Terminate 6a194e63@pbx

[7] 2007/08/17 20:56:08: Other Ports: 1

[7] 2007/08/17 20:56:08: Call Port: f248812ade877381f1815ed26b5fa1b3@192.168.0.123#436a4874b8

[8] 2007/08/17 20:56:09: Resolve destination 253996: a udp 78.123.102.22433665

[8] 2007/08/17 20:56:09: Resolve destination 253996: udp 78.123.102.224 33665

[8] 2007/08/17 20:56:09: Send Packet 403

[8] 2007/08/17 20:56:10: Resolve destination 253997: a udp 192.168.1.102 5060

[8] 2007/08/17 20:56:10: Resolve destination 253997: udp 192.168.1.102 5060

[8] 2007/08/17 20:56:10: Send Packet 200

 

I can see that the *82 was entered ahead of the telephone number, but the PBXnSIP server sent me a 403 Forbidden code.

 

Anyone know why this is happening and what to do to solve it???

 

I forgot to mention that this going to a external PSTN gateway.

 

Bill H

Link to comment
Share on other sites

Does that request go to another PBX? If you want to use that to set the status of an extension, the call cannot come from a trunk (how would the PBX know what extension it should change and how about security?).

 

 

The request goes to an external PSTN Gateway.

 

I am trying to switch the Caller ID function from the Local Telephone Service Provider (PSTN) on a per call basis.

 

Normally calls going out from our system are Caller ID Blocked at the PSTN Service Provider level.

 

By sending *82 to the PSTN Provider (and then the dialled number), the Caller ID Funtion is turned on for that call to be identified.

 

Bill H

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...