IP Office and SIP trunking

[Marshall0]

Ok, this one has been driving me nuts. Trying to do a simple incoming call through SIP to a remote IP Office system. The output from the sysmonitor is repeatable every time. It looks like this:

356962795mS SipDebugInfo: *********************************************************
356962795mS SipDebugInfo: State Transtion form Old State 10 to New state 40
356962795mS SipDebugInfo: *********************************************************
356962795mS SipDebugInfo: SipTrunks: Freed Txn Key 2016
356962842mS SIP Rx: UDP 66.23.129.253:5060 -> 192.168.40.129:5060

ACK sip:9729920820@192.168.40.129:5060 SIP/2.0
Via: SIP/2.0/UDP 66.23.129.253:5060;branch=z9hG4bKa782.76f6ed27.0
From: <sip:5048366500@216.240.109.49>;tag=22571365-fdb1080889016
Call-ID: 253-1-1196460973@216.240.109.49
To: <sip:19729920820@66.23.129.253:5060>;tag=62e4ff120960fd80
CSeq: 1 ACK
User-Agent: Sip EXpress router(0.9.6 (i386/linux))
Content-Length: 0

356962842mS SIP Trunk: 100:Rx
ACK sip:9729920820@192.168.40.129:5060 SIP/2.0
Via: SIP/2.0/UDP 66.23.129.253:5060;branch=z9hG4bKa782.76f6ed27.0
From: <sip:5048366500@216.240.109.49>;tag=22571365-fdb1080889016
Call-ID: 253-1-1196460973@216.240.109.49
To: <sip:19729920820@66.23.129.253:5060>;tag=62e4ff120960fd80
CSeq: 1 ACK
User-Agent: Sip EXpress router(0.9.6 (i386/linux))
Content-Length: 0

356962842mS SipDebugInfo: MZ SIPDialog: ReceiveFromTarget
356962845mS SipDebugInfo: MZ SIPDialog TXN : Decoding of message Succeded 1
356962846mS SipDebugInfo: SIP: ProcessInbound Message
356962846mS SipDebugInfo: Find End Point 253-1-1196460973@216.240.109.49
356962847mS SipDebugInfo: Process SIP request dialog fef21a04, method ACK in state 40
356962848mS SipDebugInfo: State is 40
356962849mS SipDebugInfo: SipTrunks: Cannot free Txn Key 2015
356962959mS RES: Fri 30/11/2007 16:16:12 FreeMem=47932392(25) CMMsg=2 (2) Buff=100 544 500 1068 5 Links=2114
356963850mS SipDebugInfo: EPTerminationTimeout, about to delete endpoint
356963850mS SipDebugInfo: SIPDialog destructor ... fef21a04
356963850mS SipDebugInfo: Dialog destructor is deleting store d SIP message
356963851mS CMCallEvt: 0.1018.2 -1 SIPTrunk Endpoint: StateChange: END=X CMCSIdle->CMCSDelete
356963851mS SipDebugInfo: ~SipTrunkEndpoint
356963853mS CMTARGET: 0.1018.2 -1 BaseEP: ~CMTargetHandler
356963853mS CMCallEvt: 0.1018.2 -1 BaseEP: DELETE CMEndpoint fedba4f8 TOTAL NOW=0 CALL_LIST=0
356967845mS SipDebugInfo: Timer 9 callback



I tried to nail down what was causing the problem with "cannot free txn key 2015" but google was no help. It seems to me that the connection starts to go downhill at that point.

 

[kwing112000]

Are you using SIP to try to connect 2 ip office units? I do not think that is supported. I could be wrong but i have never seen any docs that say you can do this. It is usually for IPO to SIP provider.

 

[Escorthosis]

Kwing112000
There is an official TechTip about SIP verification using two IPOffices:

http://marketingtools.avaya.com/kno...edProjects/bulletins/techtips/188_techtip.htm

 

[tlpeter]

I have seen the "cannot free key" before
I had the Authentication name wrong
I had the name filled in instead of the number
after that it worked for me


ACA - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[kwing112000]

I had not seen that. I will have to do some reading i guess..

 

[puregold]

You can SIP 2 IPO together. That is how we demonstrate SIP on the training courses as there isnt a web connection in the room at the moment.

It isnt supported but it does work, but you dont get all the SCN features obviously.

If you want to give me your mail address i have some walk through docs that will make this work flawlessley.



ACE - Avaya Certified Expert
ACI - Avaya Certified Instructor

 

[Marshall0]

It's a single IP Office unit that's the issue. The incoming call is SIP but it's coming from a commercial SIP provider that is technically being called from another IP Office unit, but the unit in question is using a regular telephone number provided by SIP.

This problem arises regardless of what device is initiating the connection since it's all going over POTS before being transformed into SIP.

tlpeter:

I'll go ahead and double check my settings.