Ucm 6208 + patton sn 4131


#1

Hi ,
I’m planning to buy:
nr. 1 - UCM 6208
nr. 1 - Patton SmartNode 4131

I need to manage 4 ISDN line , after configuring the patton and registering it on the UCM 6208 , i need to create SIP trunk , that’s the correct way?

  • the device UCM 6208 works correctly and supports the Patton SmartNode 4131?

thanks


#2

While I am have not used this particular Patton device, as long as it conforms to the SIP RFC, then it will interface to to the UCM.

Patton support is excellent, so if any doubts, give them a call.


#3

Thanks for your reply , ok i will call them before buying , but after i will connect my 4 ISDN on the Patton i will need to create 4 SIP Trunk to manage my lines , that’s correct?


#4

You only need to create a single peer trunk on the UCM to the Patton gateway


#5

Hi ,
I’m trying to configure UCM 6208 + Patton SmartNode 4131 , but on the Dashboard of UCM on the trunk section, the trunk of the patton have red point ( rejected ) .

Does the patton have to register on UCM? or The UCM does to register on the patton?

LAN port of UCM goes to switch and LAN port of patton goes to the same switch , all the device are on the same IP class (192.168.0.X).


#6

All you need to do is create a peer trunk on the UCM to the gateway and one in the other direction


#7

thanks for you reply , but i have also to configure the Patton , and on the web wizard i need to choose 1 or 2 or 3 answer :

1 - ITSP SIP Trunk (SmartNode sends SIP registration)
2 - IPPBX in LAN (SmartNode accepts SIP registration)
3 - No incoming or outgoing registration

when i create SIP trunk on UCM , i need to compile password field , so i think i need to choose answer nr 2…


#8

In that case its 3 because its a peer trunk and doesn’t need registration


#9

thank you very much, problem solved, I continue to configure …


#10

I’m planning inbound routers :

  • 3 ISDN LINE ( 6 voice channels)
  • OFFICE TIME 8:00 -12:30 and 14:00 - 18:30
  • First “ring group” that receive calls ( extensions nr. 1-2-3 )
  • Second “ring group” that receive calls ( extensions nr. 1-2-3-4-5-6)

I create first group ring ( Extensions nr 1-2-3) with a time condition( office time) in Inbound Routes , if nobody answer or all extensions are busy , call will be transfer to the Queue.
In the Queue i insert as static agent (Extensions nr. 1-2-3-4-5-6) , with no max wait time.

(instead of create the second ring group a will create a queue)
Is this a good or the best configuration? other ideas?

thanks


#11

Should will i create 2 Queue? one for the first ring group and one for the second?


#12

To me, the question as to which is better, a ring group or Q, is dependent on a couple of things.
Personally, I prefer Qs as they provide more flexibility, but a Q may require some additional thought -

A ring group is a collection of phones that can be programmed with a ring strategy of ring all or on order. If the call is not answered, then it can be sent to a different handling method. If all members of the RG are busy, the call will immediately go to the other destination if one is programmed and if not, the call will be disconnected.

A Q on the other hand looks for available agents and when found will direct the call to same. If an agent is not available, the Q will hold the caller pending an agent becoming available. There are more ring strategies available as well as other options to include a callback function. The Q requires that the agents may need to manage their availability depending on the strategy. Despite the agents being static, if you use some of the ring strategies, the system will send the phone to an agent and if that agent does not answer (sick, vacation, etc., the call will go to the other handling option, if programmed or will disconnect if not programmed. So, there may be a need to have the extensions that are not manned for some reason, to be set to agent pause, DND or otherwise taken out of the Q. It simply depends on how you setup.

I also would not set a wait time with no limit Callers call to speak with someone, not to listen to MOH. Use the call-back feature, time the call out and move to a destination elsewhere, do anything and everything you can to get the call answered within a reasonable period. No one likes to be put on-hold and the longer the wait, the more apt they are to hang-up, become more aggressive, etc… The message this sends is that the company is understaffed, can’t handle their calls, customer service is lacking and there must be other companies that I can find that are better.

In any event, experiment some and see what works best using both RG and Q for the site and their personnel.


#13

Hi @lpneblett ,
thanks for you reply , today i try to link , Patton at my ISDN Line ( one of the 3 Avaiable ) , i try to make a call and all works fine , but if i try to call the number of my ISDN (receive a call) i don’t I don’t hear no one ring and the line falls.

I can not understand why… how can I proceed?

I Have only one imbound route , with that patter " _* " directed only to one extension , i don’t find nothing reveice call on UCM , so i think the problem cloud be on the patton …


#14

_* isn’t a valid dialplan. If you want a catchall dialplan for testing use _X.


#15

Thanks @rtl ;

I modified dialplan to _X. but same problem , no ring and line falls…


#16

How can I understand if the problem is on the Patton or on UCM?


#17

I think incoming call to be routede to UCM , this is a part of Patton log:

3:13.000 ISDN-SIG # High layer compatibility : telephony
10:33:13.000 ISDN-SIG # CCITT
10:33:13.000 ISDN-DP # [EP IF_ISDN_00-0x21a320] Change dtmf detection to ‘disabled’
10:33:13.000 ISDN-DP # [EP IF_ISDN_00-0x21a320] Acquired b-Channel 0 (Datapath termination 10000000)
10:33:13.000 ISDN-SIG # [EP IF_ISDN_00-0x21a320] State: NULL, Event: TERMINAL SETUP IND
10:33:13.000 ISDN-SIG # [EP IF_ISDN_00-0x21a320] Set state to CALL PRESENT
10:33:13.000 ISDN-DP # [EP IF_ISDN_00-0x21a320] Change datapath direction to Send/Receive.
10:33:13.000 ISDN-SIG # [EP IF_ISDN_00-0x21a320] set call key: 51
10:33:13.000 ISDN-SIG # [EP IF_ISDN_00-0x21a320] Set state to INCOMING PROCEEDING
10:33:13.893 BRCT:0/0 # notifyL3Message()
10:33:13.893 BRCT:0/0 # sendL3MsgToStack
10:33:13.893 BRL3:0/0 # new call state : L3PcSt06U
10:33:13.893 BRL2:0/0 # [bri 0 0 0/D-CHANNEL/Isdn][0] PH-State=PhAct | Primitive=PhDataReq
10:33:13.893 BRL2:0/0 # [bri 0 0 0/D-CHANNEL/Isdn][0] S: sapi: 0 cr=1 ea=0 tei: 0 ea=1 RR Nr( 23) pf=0
10:33:13.893 BRL2:0/0 # [bri 0 0 0/D-CHANNEL/Isdn] Transmit HDLC frame of 4 bytes
10:33:13.000 ISDN-SIG # [EP IF_ISDN_00-0x21a320] >> [080002]
10:33:13.000 ISDN-SIG # CALL PROCEEDING (DSS1 User)
10:33:13.000 ISDN-SIG # [1E028582]
10:33:13.000 ISDN-SIG # Progress indicator : destination address is non-ISDN
10:33:13.000 ISDN-SIG # private network serving remote user - CCITT
10:33:13.000 ISDN-DP # [EP IF_ISDN_00-0x21a320] Add termination
10:33:13.898 BRCT:0/0 # L3_SIG to stack
10:33:13.898 BRCT:0/0 # sendL3MsgToStack
10:33:13.898 BRCT:0/0 # sendL3MsgToStack msgLen: 172, pMessage->newParam.tmcLength: 4
10:33:13.898 BRL3:0/0 # [bri 0 0 0/D-CHANNEL/Isdn][0] from CC key: 51 L3ProceedingReq
10:33:13.898 BRL3:0/0 # cause : Transparent
10:33:13.898 BRL3:0/0 # hex:1E 02 85 82
10:33:13.898 BRL3:0/0 # IE: ProgressInd
10:33:13.898 BRL3:0/0 # —> Layer2 tei: 0 sapi: 0 CallProc
10:33:13.898 BRL3:0/0 # hex:08 01 C6 02 18 01 89 1E 02 85 82
10:33:13.898 BRL3:0/0 # IE: ChannelId BCh0 excl otherIf
10:33:13.898 BRL3:0/0 # IE: ProgressInd
10:33:13.898 BRL3:0/0 # new call state : L3PcSt09U
10:33:13.898 BRL2:0/0 # [bri 0 0 0/D-CHANNEL/Isdn][0] Process signal ‘SigDChannel’
10:33:13.898 BRL2:0/0 # [bri 0 0 0/D-CHANNEL/Isdn][0] L2-State=7-MultipleFrameEstablished | Primitive=DlDataReq
10:33:13.000 ISDN-SIG # [EP IF_ISDN_00-0x21a320] Hold State: IDLE, Hold Event: PEER RELEASED
10:33:13.000 ISDN-SIG # [EP IF_ISDN_00-0x21a320] State: INCOMING PROCEEDING, Event: PEER RELEASED
10:33:13.000 ISDN-SIG # [EP IF_ISDN_00-0x21a320] Set state to DISCONNECT REQUEST
10:33:13.000 ISDN-DP # [EP IF_ISDN_00-0x21a320] Change datapath direction to Receive Only.
10:33:13.000 ISDN-SIG # [EP IF_ISDN_00-0x21a320] AOC-S User << Call Clearing
10:33:13.000 ISDN-SIG # [EP IF_ISDN_00-0x21a320] AOC-D User << Call Clearing
10:33:13.000 ISDN-SIG # [EP IF_ISDN_00-0x21a320] AOC-E User << Call Clearing
10:33:13.000 ISDN-SIG # [EP IF_ISDN_00-0x21a320] >> [080045]
10:33:13.000 ISDN-SIG # DISCONNECT (DSS1 User)
10:33:13.000 ISDN-SIG # [08028583]
10:33:13.000 ISDN-SIG # Cause : no route to destination
10:33:13.000 ISDN-SIG # private network serving remote user - CCITT - Q.931
10:33:13.908 ISDN-CTL # osCancelTmo: id 144586
10:33:13.908 ISDN-CTL # osSetTmo: Timeout 1000, id 144587
10:33:13.908 BRL2:0/0 # [bri 0 0 0/D-CHANNEL/Isdn][0] PH-State=PhAct | Primitive=PhDataReq
10:33:13.908 BRL2:0/0 # [bri 0 0 0/D-CHANNEL/Isdn][0] S: sapi: 0 cr=0 ea=0 tei: 0 ea=1 INFO Nr( 23) Ns( 33) pf=0
10:33:13.908 BRL2:0/0 # [bri 0 0 0/D-CHANNEL/Isdn] Transmit HDLC frame of 15 bytes
10:33:13.908 BRCT:0/0 # L3_SIG to stack
10:33:13.908 BRCT:0/0 # sendL3MsgToStack
10:33:13.908 BRCT:0/0 # sendL3MsgToStack msgLen: 172, pMessage->newParam.tmcLength: 4
10:33:13.908 BRL3:0/0 # [bri 0 0 0/D-CHANNEL/Isdn][0] from CC key: 51 L3DisconnectReq
10:33:13.908 BRL3:0/0 # cause : Transparent
10:33:13.908 BRL3:0/0 # hex:08 02 85 83
10:33:13.908 BRL3:0/0 # IE: Cause NoRouteToDestaination
10:33:13.908 BRL3:0/0 # —> Layer2 tei: 0 sapi: 0 Disconnect
10:33:13.908 BRL3:0/0 # hex:08 01 C6 45 08 02 85 83
10:33:13.908 BRL3:0/0 # IE: Cause NoRouteToDestaination
10:33:13.908 ISDN-CTL # osSetTmo: Timeout 30000, id 144588
10:33:13.908 BRL3:0/0 # new call state : L3PcSt11U

Someone could give me some information?
Below there is a log to download…
Log.zip (3.7 KB)


#18

On the surface, it appears that you may not have created a route in the Patton device to tell it how to get to the UCM. You will also need a route in the UCM to take in the call. Assuming you have created a route in the UCM, then you may want to use the UCM network capture capability to confirm if any traffic is seen from the Patton. If not, then the issue is with the Patton and you can try your hand at fixing or call Patton for assistance as their support is usually quite good.