MBG not sending REGISTER messages.

[pradeepgali]

The expectation is, MBG should send "REGISTER" messages to the to the SIP Trunk IP address provisioned in "Remote Trunk Endpoint" field. I gave authentication username and password in the SIP Trunk i created.

Question:  Is there any specific configuration to enable to send REGISTER messages to SIP trunk?

[bluewhite4]

Its my understanding that MBG will only do this when it is told on behalf of the 3300/MCD. Its my experience and understanding that you have to build the trunks in the 3300/MCD to use the MBG as the trunks proxy server, and then when the 3300/MCD tries to bring the trunks "up" the MBG will send the message. Thats why if you disable the SIP Peer within Network Elements, the MBG will no longer attempt to register.

Atleast thats what I've experienced and/or learned.

[pradeepgali]

I am able to send REGISTER message from 3300 to LAN side of MBG. I don't see and REGISTER messages from MBG WAN to next hop.

[bluewhite4]

When you say "I am able to send REGISTER message" can you describe the process you're using to do that please?

[pradeepgali]

In Mitel 3300 > Network Element, the outbound Proxy IP Address is given as LAN side IP address of MBG. I have attached an image of other network element with TYPE: Other. With reference to attached image 193.168.0.10 is the ITSP IP Address. 10.10.10.30 is the WAN side IP address of MBG.(I have change the IP addresses from actual IP Address for security issues).

Please let me know if you need any other information.

[johnp]

I thought the type was supposed to be outbound proxy. Other sip peer for the provider and some licenses on the MBG.

[pradeepgali]

In my understanding, without SIP PEER PROFILE in 3300 we cannot make any inbound or outbound calls. To create SIP Peer Profile, we need a network element Type: OTHER. Correct me if i am wrong.

[bluewhite4]

YPradeepgali, you are correct, but so is johnp.

You need a SIP Peer Profile, a Network Element of Other (with the carriers info in it) but also a Network ELement of Outbound Proxy with the Lan info of your MBG server.

Are you working off of a Mitel guide at all?

[pradeepgali]

Right now i have configured in the way you mentioned(Network Element of Other with Carrier Info and Outbound proxy with MBG LAN). Did you see anything wrong in the configuration i mentioned in my previous post? Let me know.

The configuration guide also has the similar config. Only thing is i did not find is a configuration guide with MBG between Service Provider and 3300. That is the reason i could not figure out where i am going wrong.

[bluewhite4]

I would say yes, except after the changes you just made, do you still have the external SIP proxy information filled in for the carrier's network element? I think that should be blank.

[pradeepgali]

After removing the proxy IP address in SIP Peer Profile, i can see the REGISTER messages going out. from MBG to Service Provider.
The "TO" and "FROM" headers are as shown below. The expectation is username(Pilot number used for authentication) should be present before "<sip" in TO and FROM Headers. Please let me know if there any way we can add the pilot number before "<sip" in 3300 or MBG.


From: <sip:192.168.0.10>;tag=0_3766535424-101762990\r\n
To: <sip:192.168.0.10>\r\n

[bluewhite4]

Can you please post your SIP Peer profile for that then.

[pradeepgali]

The attached is my SIP Peer Profile screenshot. Sorry the expected format i mentioned in previous post is wrong. The DID number given in user Name is expected to be in TO and FROM header some thing like :<sip:8126025329@192.168.0.10"

[bluewhite4]

Put the DID number in the Registration Username slot as well.

[pradeepgali]

Great, that works. I really appropriate your timely and accurate answers. Thanks