Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SIP Trunk programming issue

Status
Not open for further replies.

conquer2006

Technical User
Apr 3, 2013
117
NG
After programming a provider Sip Trunk Links(IPNX) on MItel 3300 MXe 111, from maintenance Command (SIP LINK STATE ALL) I got the follow result, I need assistance



Number of established links: 1
Number of non-established links: 0

There are 1 SIP link(s) programmed.
Link ipnx state is IN SERVICE (link down count 0) - REGISTER Failed

There are 1 SIP link(s) programmed.
Link ipnx state is IN SERVICE (link down count 0) - REGISTER Failed

If I want to make call OUT OF SERVICE MESSAGE will display.
 
Your SIP trunk has not registered with the provider; depends on how you are authenticating for the programming you need to check.
 
Hello friends, the SIP Trunk has registered with the provide. I can receive calls, but when I try to make Trunks calls I get this message from the 5540 Console( REQUEST DENIED). I want to call these two Trunk Lines (A) 0163280009 and (B) 08033003401

This is my first time of working on SIP Trunk.
 
How do I set-up outbound proxy so that I can make trunk calls. I really need assistance if someone can even check this for me through Teamviewer.
 
You can set the proxy through the network elements form

Share what you know - Learn what you don't
 
some SIP providers need a registrar some need a proxy some need both
Who is your provider? have you checked the interop doc for settings?


Share what you know - Learn what you don't
 
Also some providers require a username which might be the telephone number for your site.
This is set in the SIP peer profile form

You probably need to speak to the provider and check what authentication settings they require.

Share what you know - Learn what you don't
 
Hello friends, the SIP Trunk has registered with the provide. I can receive calls, but when I try to make Trunks calls I get this message from the 5540 Console( BUSY). I want to call these two Trunk Lines (A) 0163280009 and (B) 08033003401

This is my first time of working on SIP Trunk.
 
11:27:43 ROL DPN PEER ipnx 79 1E ISRM_I
;10;*1#*50*604#*100*Sales#*19*Z#
11:27:43 ROL DPN PEER ipnx 79 2D SSRM_I
*58*CW*Kolw@@@@@Ax;7F;w@#*58*C6*001#*58*C4*4*1#
11:27:43 ROL DPN PEER ipnx 79 4 SSRM_I 016
11:27:43 ROL DPN PEER ipnx 79 2 SSRM_I 2
11:27:43 ROL DPN PEER ipnx 79 2 SSRM_I 8
11:27:43 ROL DPN PEER ipnx 79 2 SSRM_I 0
11:27:43 ROL DPN PEER ipnx 79 2 SSRM_I 0
11:27:44 ROL DPN PEER ipnx 79 2 SSRM_I 0
11:27:44 ROL DPN PEER ipnx 79 2 SSRM_C 9
11:27:44 RIL DPN PEER ipnx 79 7 NIM *51*3#
11:27:44 RIL DPN PEER NIL_PEER_ 79 25 CRM/CIM
;2;*59*016310250#*58*C2*G*500#*234*JP#

Registrar Configuration
-----------------------
Domain: sip.ipnxtelecoms.com IP Address 192.168.20.36
Allow Third Party Registrations: no
Default Expiry Duration: 3600 seconds
Maximum Configurable Expiry Duration: 7200 seconds

When I make outbound call-out, I get this message
 

Registrar Configuration
-----------------------
Domain: sip.ipnxtelecoms.com IP Address 192.168.20.36
Allow Third Party Registrations: no
Default Expiry Duration: 3600 seconds
Maximum Configurable Expiry Duration: 7200 seconds

This IP Address !92.168.20.36 is for MXe iii, it is supposed to be the IP address attached with the Domain.
 

MWI Entry(s)
------------

Registrar Configuration
-----------------------
Domain: sip.ipnxtelecoms.com IP Address 192.168.20.36
Allow Third Party Registrations: no
Default Expiry Duration: 3600 seconds
Maximum Configurable Expiry Duration: 7200 seconds


Registrar Entry(s)
--------------------

Registrar Entry(s)
--------------------

Registrar Statistics
--------------------
Current: 0
Accepted: 0
Refreshed: 0
Total Failed: 0
(Rejected 0)
(400 Bad Request 0)
(403 Forbidden 0)
(403 Forbidden Blocked 0)
(404 Not Found 0)
(423 Min Expires 0)
Registration request timeout: 0
CallControl response timeout: 0

There are 1 SIP link(s) programmed.
Link ipnx state is IN SERVICE (link down count 0)

Number of established links: 1
Number of non-established links: 0

MWI Subscription Statistics
---------------------------
Current: 0 (out of 0 Registrations)
Successful: 0
Failed: 0

MWI Entry(s)
------------

There are 1 SIP link(s) programmed.
Link ipnx state is IN SERVICE (link down count 0)

Link ipnx state is IN SERVICE (link down count 0)

Number of established links: 1
Number of non-established links: 0

MWI Subscription Statistics
---------------------------
Current: 0 (out of 0 Registrations)
Successful: 0
Failed: 0

MWI Entry(s)
------------

LDS Interface Registered components:
------------------------------------------------------
Component Id : Name:
# 1: SSP
# 2: SSM
# 3: SIPMH
# 4: DM
# 5: NTM
------------------------------------------------------
End of list.


-------- SipCommmonConfiguration ------------

SipProtocolVersion: SIP/2.0
SipServiceOperStatus: 2
SipServiceStartTime: 1394611090
SipServiceLastChance: 0
SipMaxTransaction: 0
SipServiceNotificationEnable: 0
SipEntityType: 2

-------- SipCommonStatsSummary ------------

TotalNumOfIncomingRequests: 7
TotalNumOfOutgoingRequests: 1331
TotalNumOfIncomingResponses: 1410
TotalNumOfOutgoingResponses: 12


-------- SipOtherCommonStats ------------

NumUnsupportedMethods: 0
OtherwiseDiscardedMsgs: 0

------------ SipPorts -------------------

SipPort: 5060
SipTransportRcvType: 1

SipPort: 5060
SipTransportRcvType: 2

SipPort: 5061
SipTransportRcvType: 3

SipPort: 5060
SipTransportRcvType: 1

SipPort: 5060
SipTransportRcvType: 2

SipPort: 5061
SipTransportRcvType: 3

SipPort: 5060
SipTransportRcvType: 1

SipPort: 5060
SipTransportRcvType: 2

SipPort: 5061
SipTransportRcvType: 3

SipPort: 5060
SipTransportRcvType: 1

SipPort: 5060
SipTransportRcvType: 2

SipPort: 5061
SipTransportRcvType: 3

SipPort: 5060
SipTransportRcvType: 1

SipPort: 5060
SipTransportRcvType: 2

SipPort: 5061
SipTransportRcvType: 3
Method: Ack
Total incoming: 3
Total outgoing: 231


--------- SipSupportedMethods ----------------

SipSupportedMethodIndex: 1
SipMethodName: INVITE

SipSupportedMethodIndex: 2
SipMethodName: ACK

SipSupportedMethodIndex: 3
SipMethodName: UPDATE

SipSupportedMethodIndex: 4
SipMethodName: INFO

SipSupportedMethodIndex: 5
SipMethodName: CANCEL

SipSupportedMethodIndex: 6
SipMethodName: BYE

SipSupportedMethodIndex: 7
SipMethodName: PRACK

SipSupportedMethodIndex: 8
SipMethodName: REGISTER

SipSupportedMethodIndex: 9
SipMethodName: OPTIONS

SipSupportedMethodIndex: 10
SipMethodName: SUBSCRIBE

SipSupportedMethodIndex: 11
SipMethodName: NOTIFY

SipSupportedMethodIndex: 12
SipMethodName: REFER


-------- SipTimersConfiguration ------------

TimerA: 500
TimerB: 32000
TimerC: 0
TimerD: 0
TimerE: 500
TimerF: 32000
TimerG: 500
TimerH: 32000
TimerI: 5000
TimerJ: 32000
TimerK: 5000
TimerT1: 500
TimerT2: 4000
TimerT4: 5000


Active Rejected Non-Auth Calls Auth Calls Auth Failures
Profile Calls Calls Incoming Outgoing Incoming Outgoing Incoming Outgoing
ipnx 0 0 2 0 0 0 0 0
Total 0 0 2 0 0 0 0 0

Active Rejected Non-Auth Calls Auth Calls Auth Failures
Profile Calls Calls Incoming Outgoing Incoming Outgoing Incoming Outgoing
ipnx 0 0 2 0 0 0 0 0
 
Thanks all for your support, I have concluded my installation
 
there was a particular IP address the SIP Provider were asking me if I can ping it from 3300, which I said no, so I added it to the 3300 IP properties with the subnet mask. thereafter I could make trunk calls
However, I did not use MBG for this installation.
 
I notice that when I make or recieve calls from a SIP Trunk, after 30seconds one voice pathway will stop working. the call will still be active but either the caller or the reciever will stop hearing. Please what can cause this?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top